NetSuite bank reconciliation, step by step: from bank feed to reconciled statement

How bank reconciliation works in NetSuite today

NetSuite has two generations of this feature. The original Reconcile Bank Statement pages have not been supported since release 2021.1. The current flow is two pages under Transactions, Bank: Match Bank Data, where imported bank lines are paired with your transactions, and Reconcile Account Statement, where you close a statement and produce the report. If an account still opens the old page, edit it under Lists, Accounting, Accounts and tick the box for the new pages. New accounts get it by default.

The same two pages handle credit card accounts, and any cash account is treated as a bank account, petty cash included.

The six steps

1. Get the bank lines in. Either automatically, with the Bank Feeds SuiteApp pulling data once a day (it is not real time, and the feed breaks whenever your bank asks for a new security code), or by uploading a file under Transactions, Bank, Upload File. The default parsers read BAI2, CAMT.053, CSV, OFX and QFX; QIF is not supported. Keep an import under 10,000 lines. NetSuite does not store the file after parsing, so keep your own copy.
2. Let the system rules run. On import, Intelligent Transaction Matching tries four rules in order: transaction number and amount; the same ignoring prefixes and leading zeros; amount with a date within the previous 3 days; amount within the previous 90 days. Since the 2026.2 release, an exact one-to-one match is accepted and submitted automatically unless an administrator switches off the Automatically Accept Exact Matches preference. Where two candidates are equally plausible (two $70 deposits, say), nothing is matched and a person decides.
3. Add your own rules for what your bank does to you. Under User Rules you can match on memo, payee or date windows (Equals, Equals ignoring prefix, Within x previous days), and auto-create rules can create and match a recurring bank fee or processor charge by itself. Those created transactions do not touch the ledger until they are submitted. We set up three or four rules per client in the first month and they carry most of the volume from then on.
4. Work the Transactions to Match subtab. Select the bank line and the matching transaction; when the Difference reads zero, click Match and Submit. Create the missing deposit, charge or journal if it does not exist yet, mark a transaction Cleared if the bank line is not going to arrive, and Exclude a bank line you should not match, such as a duplicate. Remember the mirror: a deposit is a credit on the bank statement and a debit in your ledger.
5. Reconcile the statement. On Reconcile Account Statement, NetSuite fills the Statement End Date and Ending Statement Balance from the imported statement and shows Last Reconciled Balance and Reconciled This Statement. Include or exclude the submitted transactions and click Reconcile. Two warnings from Oracle's own pages: you can reconcile even when the difference is not zero, and the end date cannot be changed afterwards. Never reconcile with a difference, and never use today's date, because lines that arrive later that day can no longer be picked up.
6. Print the reports, then lock the period. The Reconciliation Summary, Reconciliation Detail and Reconciliation History reports live under Reports, Banking/Budgeting, Reconciliation. Print or save them before you reconcile the next account. Then close the period through the Period Close Checklist. NetSuite does not make bank reconciliation a checklist task and will let you close with unreconciled items, so put it in your own close schedule before the lock.

The ways bank data gets in

Reconciling the other balance sheet accounts

Bank and card accounts have their own pages. Everything else on the balance sheet (loans, payroll liabilities, sales tax, deferred revenue, intercompany balances, fixed assets) has no reconciliation page in standard NetSuite. Oracle sells a separate product for it, NetSuite Account Reconciliation, which sits in its EPM suite and is connected by a sync SuiteApp. For most mid-sized companies a schedule per account does the job: the ledger balance, the balance from outside evidence (the loan statement, the payroll report, the tax return), the reconciling items with a reason each, and a named person who signs it. We keep those schedules as workbooks that check themselves, and the Trial Balance is the index.

Where AI helps, and where it does not

NetSuite itself now uses AI in two places here. Enriched Bank Data, on by default, uses generative AI to read the payee out of a bank line and pick between candidates with the same amount within seven days. The Transaction Matching Assistant, part of the phased NetSuite Next rollout, recommends the most likely of several candidates and explains why, but it never submits a match by itself and, in Oracle's words, "does not learn from past decisions". Oracle also says AI-assisted results "can be erroneous and should always be verified". That is the right attitude.

In our own practice AI does the volume: matching, grouping, the first draft of the fee and charge entries, and the line-by-line comparison of every import with the bank statement. The senior accountant on the account decides the ambiguous cases, checks the exceptions and signs the reconciliation. Cash is the one balance where a wrong number reaches everything else, so nobody on our team lets a machine close it alone.

Where this goes wrong

First published 2024. Rewritten and checked in September 2026. If something here is out of date, tell us and we will fix it.