Last reviewed: 10 October 2026. Product details reflect this review date. Availability and behavior can vary by account, role and release.
Editorial ink illustration: A reconciliation specialist investigates one unmatched record.
A bank line for a receipt appears after the customer payment has already been recorded in NetSuite. The finance user finds the payment and matches it. That is progress, but it does not establish that the entire bank statement has been reconciled.
The difference matters because importing, matching, clearing and reconciling are related stages with different purposes. Treating them as interchangeable can leave exceptions unexplained or create duplicate transactions.
This lesson follows a simple receipt and bank-fee example through the redesigned NetSuite workflow. The example is educational, not an instruction to transfer money or a recommendation about an organization’s accounting policy.
Before looking at individual lines, confirm the bank or credit card account being reconciled. Check its currency, the statement end date and the ending balance shown by the statement.
The statement defines the evidence boundary. An imported feed may contain activity beyond that boundary or may not yet include everything needed for it. A successful import is therefore useful evidence about data receipt, but it does not prove statement completeness.
Record which statement you are reconciling and where the approved source is retained. Keep bank account information and transaction details within authorized finance access. An unrelated screenshot or an unlabelled exported file is a weak starting point for a review.
Also confirm the reconciliation workflow used by the account. The redesigned workflow uses Match Bank Data and Reconcile Account Statement. The original reconciliation feature is no longer supported. Older screenshots and instructions can therefore describe a different process.
Do not change account settings simply to make a training guide match. Have the administrator verify the current setup and approved workflow first.
An imported bank line describes activity reported by the bank or credit card source. A NetSuite ledger transaction records activity in the company’s books. They are related evidence, but one is not automatically a substitute for the other.
The same receipt may already exist as a recorded transaction by the time its bank line arrives. Creating another payment from the bank line would duplicate the accounting event rather than complete the match.
Conversely, a bank fee may appear on the statement before the finance team has recorded the appropriate accounting entry. That line needs investigation and approved treatment. It should not be treated as a customer payment merely because no match is immediately visible.
For each line, ask: “What business event is this, and is that event already recorded?” Amount alone is insufficient. Review relevant references, dates, counterparty information and the correct account. Two unrelated receipts can have the same amount.
Use Match Bank Data to review suggestions and investigate lines requiring manual attention. The documented matching route is Transactions > Bank > Bank Matching and Reconciliation > Match Bank Data. Navigation can vary with role and configuration.
A match connects imported evidence with the relevant recorded transaction or transactions. Review the proposed relationship rather than assuming every suggestion is correct.
NetSuite also supports clearing general-ledger transactions without a corresponding imported bank line. That means importing bank data is not mandatory for every reconciliation approach. Clearing still requires appropriate supporting evidence and an authorized process; it is not permission to mark uncertain activity complete.
Matched or cleared transactions are submitted for statement reconciliation. They have reached the next stage. They have not necessarily completed the statement-level review.
Payment application suggestions and Automated Cash Application can involve creating and applying payments, with their own prerequisites and scope. Do not confuse those capabilities with simply matching an existing transaction. Before using any creation path, confirm that an equivalent payment has not already been recorded and that the intended accounting action is authorized.
For matching and account reconciliation, the role needs the relevant Reconcile permission. Edit-level Reconcile supports matching and closing a reconciliation; View access provides more limited inspection. The role also needs at least View-level Accounts access to select the relevant account.
Subsidiary and other role restrictions can affect the accounts and detail visible to the user. A colleague’s account list is not proof that the current user should see every entry on it.
Importing statement files is a separate capability with the Import Online Banking File permission. Having permission to inspect reconciliation information does not automatically establish permission to import files, create payments or change matching rules.
Ask the administrator to check the exact task and scope. Do not assign broad financial permissions to make a training exercise convenient. The roles and permissions access review guide is useful when those responsibilities need a wider review.
Consider a fictional statement for one account in one currency. Its opening balance is 1,000. It contains a receipt of 600 and a bank fee of 15, giving an ending balance of 1,585. Assume there are no other transactions or outstanding items in this simplified exercise.
The receipt has already been recorded in NetSuite. The first job is to identify that transaction and confirm that it represents the same bank activity. Check the amount, reference, account and relevant dates. If the evidence agrees, the authorized user can match the bank line to the existing transaction.
The correct learning point is that a second receipt is unnecessary. Matching supplies the relationship between the two evidence sources; it does not require recording the business event again.
Now inspect the fee. In this example, no corresponding accounting entry has yet been confirmed. The reviewer checks whether it is already recorded under another reference, whether the imported line is duplicated and whether it belongs to the selected statement and account.
Only after resolving those questions does the finance owner decide the appropriate accounting treatment. The authorized team records any needed entry through its approved process and verifies the result. The example does not prescribe an expense account, tax treatment or payment action.
Before the fee is appropriately reflected in this simplified example, the books show 1,600 from the opening balance plus the receipt, while the statement ends at 1,585. The 15 difference points to the missing fee treatment under the stated assumptions. In a real reconciliation, other timing items or errors may also explain a difference. Do not generalize the example into a rule that every difference needs a new expense.
Reconcile Account Statement is the stage where the reviewer confirms the account, statement end date, ending balance and the matched or cleared transactions included in the reconciliation. The documented route is Transactions > Bank > Reconcile Account Statement.
Check the displayed currency and statement details against the approved bank evidence. Defaults are a starting point, not proof that the page represents the intended statement.
Review which transactions are included and whether outstanding items are appropriately explained. The sum of visible selected activity is meaningful only in relation to the prior reconciled balance and the stated ending balance.
Two product behaviors make deliberate review especially important. NetSuite permits a statement to be reconciled even when the difference is not zero. Also, selecting no transactions before clicking Reconcile can include them all. Do not treat the availability of the button, or a successful submission, as an accounting quality check.
The statement end date becomes the close date and cannot later be edited in place. Confirm it before finalizing. This is another reason to use a completed statement boundary and an approved review process rather than casually closing today’s still-changing activity.
This article focuses on the distinction between stages. Use your organization’s approved instructions for the final action, including its review and evidence requirements.
A persistent difference deserves a structured investigation. Confirm the account, currency, ending balance and date boundary first. Then examine missing imports, duplicate imported lines, existing transactions, timing items and changes to previously reviewed entries.
Do not create an unexplained adjustment merely to produce a zero. A zero difference can still conceal a duplicate receipt offset by an incorrect entry. The objective is an explainable relationship between the bank statement and the books.
Likewise, matching everything does not establish that every match is appropriate. Review unusual references, many-to-one relationships and large or unexpected items with the relevant finance owner.
If the problem involves a closed accounting period, refer to locked and closed accounting periods. Decide the correct accounting treatment before changing period controls. Period status and reconciliation status answer different questions.
A good handoff identifies the account and statement, the reviewer, unresolved or outstanding items, and the explanation for any difference. Keep the relevant reconciliation reports and references to approved exception treatment.
The evidence should allow another authorized reviewer to understand the conclusion without repeating the entire investigation. “All green on the page” is weaker than a documented account, date boundary, balance comparison and exception explanation.
If a transaction or statement needs correction later, use the approved correction process and preserve the reason. Do not casually delete a reconciled statement or alter a transaction to remove an inconvenient difference. The effect on previously retained evidence needs review.
For the broader task of tracing approved accounting changes, see NetSuite audit evidence for journal and master-data changes.
For help improving the surrounding workflow and exception handling, explore CuriousRubik NetSuite optimization. A useful review begins with one statement and the specific point where matching, accounting treatment or final reconciliation becomes unclear.