NetSuite bank reconciliation runs in two stages. First, imported bank lines are matched to NetSuite transactions on the Match Bank Data page, by rules or by hand. Then you submit the matches and reconcile the statement on the Reconcile Account Statement page. Matching clears the items; reconciling proves the cleared balance equals the bank's.
NetSuite bank data matching rules
NetSuite pairs bank lines with transactions through reconciliation rules run by a feature called Intelligent Transaction Matching. After you import bank lines, the rules run on their own and propose matches against transactions already in the account. You can also run them again by hand. The rules decide what is proposed; you decide what is accepted.
Oracle describes the flow in its help topic on bank data matching and reconciliation. Three points from it matter in daily work:
- The account must be set up for the matching pages. For an existing account, the Edit Account page has a box for using the Match Bank Data and Reconcile Account Statement pages. New accounts have it checked.
- Users need the banking role permissions for those pages.
- Oracle advises running Automated Cash Application first. It turns imported bank lines into customer payments where it can, and those payments are matched and cleared automatically.
What a rule compares
A rule compares fields on the bank line with fields on a transaction. The usual candidates are the amount, the date, a reference or check number, and sometimes the memo or payee text. Narrow rules, such as an exact amount plus the same check number, produce few false matches. Broad rules, such as amount alone within a few days, produce more matches and more mistakes. Oracle's page on Intelligent Transaction Matching for bank data says you choose the order of your own user rules, beside system rules you cannot change. Put the narrow rules first and the broad ones last, because a broad rule that runs first can claim a line that a stricter rule would have paired correctly.
The mechanics of date windows and amount tolerances are common to every matching tool. Rather than repeat them here, the guide on how match tolerances work covers the trade-off between a loose and a strict window.
The Match Bank Data page
The page shows imported bank lines and NetSuite transactions for the account side by side. On it you can match transactions to bank lines, mark transactions that have no bank line as cleared pending submission, exclude imported lines, and review what is matched. Nothing is final until you submit it.
Reviewing unmatched bank lines and exceptions in NetSuite
After the rules run, some bank lines stay unmatched. Review them one by one and give each an outcome: match it to an existing transaction, create the missing transaction, exclude the line, or leave it open with a reason. An unmatched line always means either NetSuite is missing something or the bank line does not belong.
Work through the leftovers in groups, not in statement order. Groups make patterns visible.
Common groups of leftovers
| Leftover | Likely cause | What to do |
|---|---|---|
| Bank fee or interest with no transaction | Never recorded | Record it, then match it |
| Deposit that is one line in the bank but several in NetSuite | Several receipts banked together | Select all the transactions and match them to the one bank line |
| Check in NetSuite with no bank line | Outstanding check | Leave it uncleared; it carries to next month |
| Bank line with a payee but no NetSuite entry | Unrecorded payment or a transaction in another account | Find it, record it in the right account |
| Two identical bank lines | A real repeat charge, or a duplicate import | Check the statement before excluding either |
| Refund or reversal | Matches an earlier charge | Match the pair, and make sure each is recorded once |
Excluding lines
NetSuite lets you exclude an imported bank line. Use it for lines that should not be matched, such as a duplicate import of a line you already have. Write down why you excluded it. An exclusion with no note is the first thing a reviewer questions.
A worked example
Suppose the statement shows a deposit of 4,350.00 on March 31 and NetSuite shows three customer payments: 1,200.00, 1,500.00 and 1,650.00, all dated March 29. No single transaction equals the bank line, so a rule keyed on amount will not pair them. Select the three transactions together on the Match Bank Data page and match them to the one bank line. The total, 4,350.00, equals the bank amount, and the three payments clear together. These numbers are an example.
What does the first bank reconciliation in NetSuite need?
The first reconciliation of an account needs a starting point: the bank balance at a date, and the NetSuite transactions that were already outstanding then. Without it, the cleared balance begins at zero and the first statement will not agree. Treat the first month as set-up work and allow extra time.
Gather these before you start:
- The opening statement. Pick the statement whose ending balance is your starting point.
- The list of items outstanding on that date. Checks written but not paid, and deposits recorded but not yet credited by the bank.
- A ledger balance for the account on the same date, so you can prove the starting figures.
- Imported bank lines for the first period, so that the matching pages have something to match against.
Historic items
Transactions posted before your first statement that never cleared will sit in the list. Decide for each whether it is genuinely outstanding or stale. Genuine ones will clear in the coming statements. Stale ones, such as a check that was voided on paper but never in the system, need to be corrected in the books, not ignored. Oracle's help topic also notes that if you have statements but cannot import bank data, you can mark the corresponding transactions as cleared without importing lines, which is the fallback for an account with no feed.
Prove the opening position
Before you reconcile the first statement, calculate: the ledger balance, less outstanding payments, plus deposits in transit, should equal the opening bank balance. If it does not, find the difference before reconciling. The general approach to adjusting both sides until they agree is the same as in the guide to how to reconcile bank statements.
Submitting and reopening a NetSuite reconciliation
Submitting moves your matched and marked transactions into the reconciliation. On the Reconcile Account Statement page you then review them, include or exclude each, and reconcile the statement. Per Oracle's topic, submitting clears the transactions in the system, and reconciling the statement is the final step.
The order of work
- Finish matching on the Match Bank Data page.
- Submit the matches and the user-cleared transactions.
- Open Reconcile Account Statement for the same account and period.
- Compare the statement balance and the reconciled balance. The difference should be zero.
- Reconcile the statement.
Reopening
Oracle's page does not describe reopening a reconciled statement or unreconciling transactions; it points to separate documentation. This guide does not state the exact steps, because the official page it relies on does not give them. Before you reopen a period, check the current Oracle help for your release, and confirm what your role allows. Do not edit a reconciled transaction and assume the reconciliation still holds. Changing the amount of a cleared item changes the proof, and the reviewer should see why.
When NetSuite auto-matching should not be trusted
Auto-matching is a proposal, and some proposals deserve a second look every time. A rule satisfied on amount and date can still pair two different events, and a wrong match clears an item and hides a real problem for months.
The risky groups are the same in every tool: round amounts, repeat charges, matches across a month end, grouped matches and matches on amount alone. They are set out in full in which transaction matches a person should always review.
Two points are specific to NetSuite. Oracle's Intelligent Transaction Matching page says that when a rule finds two or more possible matches, NetSuite does not pick one, so those lines come to you for a manual match. Treat that list as a warning sign about the rule, not just a chore. And review transfers between your own accounts by hand, because both legs must clear, one in each account.
A quick test
Sort matched items by amount, then look for equal amounts matched to different dates. Duplicates and look-alikes cluster there. The guide to finding duplicate transactions on bank statement lines goes deeper on telling a real repeat from a double posting.
Is a NetSuite bank reconciliation enough evidence for an auditor?
A completed NetSuite reconciliation shows the system's result, but an auditor usually wants to see the source: the bank statement, the list of outstanding items, and who reviewed it. Export or save the statement, the reconciliation detail and the exceptions with their reasons. The system record alone rarely stands as the whole file.
The month-end list below is the concrete routine. It runs from statement to a submitted reconciliation.
Month-end checklist
- Download the bank statement as a PDF from the bank, and keep it unchanged.
- Confirm the statement's opening balance equals last month's reconciled closing balance.
- Foot the statement: opening balance plus deposits less withdrawals equals the closing balance.
- Import bank lines for the period and run the matching rules.
- Review every auto-match in the risk groups above.
- Work the unmatched lines: record, match, exclude with a note, or leave open.
- Confirm outstanding checks and deposits in transit, with dates, and check the oldest ones.
- Submit the matches and open Reconcile Account Statement.
- Confirm the difference is zero before you reconcile.
- Save the statement, the reconciliation report and the exception notes to the period folder.
- Have a second person review and sign.
What to add beyond the system
Step 3 is the one a ledger system cannot do for a PDF it did not read. PreciseBankFlow does that footing, flags duplicates and gaps, and exports an exception report to Excel or PDF for your workpapers; it does not replace the reconciliation, and the sign-off stays with you. It is opening in small groups, so request a spot if you want to try it.
For the same routine in other systems, see reconciling in QuickBooks Online and the guide to Sage bank reconciliation.