Two kinds of reconciliation in NetSuite
| Type | Accounts | Where it happens |
|---|---|---|
| Bank and credit card | Cash, credit cards | NetSuite's bank data matching and statement reconciliation pages |
| Balance sheet | AR, AP, prepaids, accruals, fixed assets, deferred revenue, intercompany | Saved searches and reports in NetSuite, compared to subledgers and schedules, usually in Excel or close software |
Most teams handle the first well and struggle with the second.
How to reconcile a bank account in NetSuite
1. Bring in bank data
Connect the bank through NetSuite's bank feeds or import a statement file (such as BAI2, CSV or OFX, depending on your setup). Check the imported line count and total against the statement before matching.
2. Match bank data to NetSuite transactions
On the bank data matching page, NetSuite suggests matches using its matching rules. Review them, accept the correct ones and handle exceptions. You can configure auto-match rules for recurring patterns.
3. Create transactions for bank-only items
Bank fees, interest and unrecorded debits need transactions in NetSuite before they can match. Create them with a clear memo and the statement reference.
4. Reconcile the account statement
On the statement reconciliation page, enter the statement's ending date and balance, confirm the matched and cleared items, and check the difference is zero. Then submit to save the reconciliation.
5. Save the evidence
Export or save the reconciliation report with the bank statement, the list of outstanding items and the reviewer's sign-off. Your auditor will ask for all three.
How to reconcile balance sheet accounts in NetSuite
NetSuite holds the GL balances; the independent source usually sits elsewhere.
| Account | Pull from NetSuite | Compare to |
|---|---|---|
| Accounts receivable | AR aging report | AR control account balance |
| Accounts payable | AP aging report | AP control account balance |
| Prepaid expenses | GL detail for the account (saved search) | Prepaid schedule |
| Accrued liabilities | GL detail | Accrual schedule |
| Fixed assets | Fixed asset register (if using the Fixed Assets module) | GL fixed asset and accumulated depreciation accounts |
| Deferred revenue | Revenue recognition reports | GL deferred revenue balance |
| Intercompany | Balances by subsidiary | Counterparty subsidiary's balance → /resources/intercompany-reconciliation |
Tip: build one saved search per reconciled account with fixed criteria (account, subsidiary, period) and save it. That makes the data pull repeatable, and a reviewer can rerun it.
Where NetSuite reconciliations usually break
1. Aging reports that don't tie to the control account. Usually caused by manual journal entries posted straight to AR or AP. Find them with a saved search on the control account filtered to journal entries.
2. Duplicate bank imports. A statement imported twice creates duplicate bank lines. Check line counts and totals at every import.
3. Timing across subsidiaries. In NetSuite OneWorld, intercompany transactions posted on different dates or rates leave differences at consolidation. Reconcile intercompany by subsidiary pair, before consolidation.
4. Reopened periods. A change to a closed period after the reconciliation was signed makes the signed reconciliation wrong. Restrict who can post to closed periods and review any reopen.
5. Saved searches that drift. Someone edits a saved search's criteria and next month's reconciliation pulls different data. Lock or version the searches you rely on.
6. Manual matching without a reason. When a match is forced by hand, record why. Otherwise the reviewer, and the auditor, can't tell.
Keeping the evidence your auditor needs
For each NetSuite reconciliation, keep:
- The NetSuite balance and the report or saved search that produced it, with its criteria.
- The independent source (statement, aging, schedule) for the same date.
- The reconciling items, each with a date, explanation and owner.
- Preparer and reviewer sign-off, with dates.
Auditors treat saved-search output as information produced by the entity (IPE) and will want evidence it's complete and accurate. Saved criteria and row counts help.
Using AI with NetSuite
NetSuite supports MCP connections through its AI Connector Service, which lets AI tools query records and, with permission, create transactions. Before connecting AI to your GL, read our ten controls → /blog/erp-mcp-journal-entry-controls.
Reconciling NetSuite with Yoraito
Yoraito connects to your GL and banks and reconciles every balance sheet account each close. Every match, tie-out and balance comes with the SQL that produced it, so your reviewer and auditor can rerun it. Your NetSuite stays the system of record. Supported systems: 22 named, 11 direct.