NetSuite Bank Reconciliation for Client Files

NetSuite bank reconciliation starts with matching bank data, then closes the statement on Reconcile Account Statement. For an authorised client file, check the account and opening balance first, resolve exceptions and retain the completed reports for review.

Confirm the Client Account and Banking Setup

Confirm that the bank statement and NetSuite account belong to the same client entity before importing or matching anything. Record the NetSuite account, subsidiary where applicable, bank or card account, currency and statement period. Compare the source statement’s opening balance with the previous accepted closing statement and its outstanding items. Confirm your agreed scope and authority to make corrections.

Your role needs Accounts access, Reconcile permission with Edit access to match and close, and Reconcile Reporting access for reports. File imports also need Import Online Banking File permission. Subsidiary and other role restrictions can limit which accounts appear. An administrator can check these against Oracle’s banking permissions.

For an existing account, check Lists > Accounting > Accounts > Edit. The setting is Use Match Bank Data and Reconcile Account Statement Pages. New accounts have it selected automatically. Agree any change with the client’s administrator before saving.

Oracle’s account setup instructions select the supported pages. The older Reconcile Bank Statement and Reconcile Credit Card Statement pages are unsupported.

This procedure uses native banking pages. The separately sold NetSuite Account Reconciliation module covers broader general-ledger reconciliation and close work.

The steps below use the 2026.2 banking labels. Oracle’s banking release notes replace separate manual matching and submission with Match and Submit. Clear and Submit also combines those actions. Match Suggestions replaces the former Review subtab on Match Bank Data. If the client still has the earlier labels, follow its release-specific help before continuing.

The opening checkpoint is one account, one currency and one agreed period across the source, prior reconciliation and accounting records. For the broader workpaper method, use the bank reconciliation guide.

Match the Imported Bank Data

Import the missing bank data once, then review the suggested and manual matches against the underlying records.

1. Establish the import coverage. Compare the source period with Banking Import History and existing lines before uploading. With an existing automatic connection, use Update Imported Bank Data on Match Bank Data when a refresh is needed. Confirm the mapped bank account and inspect the resulting coverage before adding another file.
2. For a manual import without financial institution records, open Transactions > Bank > Upload File. Choose the source file, select Import with default parser and choose the correct Account. Set encoding if requested, then click Import. Follow Oracle’s default-parser procedure for accepted formats and CSV requirements. A configured financial institution uses its format profile instead. Check Banking Import History for completion or errors. Retain the original statement separately because NetSuite removes the uploaded file after processing.
3. Open Transactions > Bank > Bank Matching and Reconciliation > Match Bank Data and select the account. On Match Suggestions, compare each proposed match’s amount, direction, reference and counterparty with the source. Use View for a single option or Review for multiple options. Submit the correct suggestion and reject an incorrect one. Rejected lines move to Transactions to Match. Oracle’s suggestion review instructions describe these actions.
4. On Transactions to Match, select the imported line and its corresponding account transaction or group. Check the references and group membership as well as a zero matching Difference. Use Match and Submit in 2026.2. The submitted group becomes available on Reconcile Account Statement. A matching total alone cannot distinguish two unrelated payments of the same amount.
5. Inspect transactions already submitted automatically. The Automatically Accept Exact Matches preference can submit eligible suggestions during import or reconciliation-rule processing. Review these on Reconcile Account Statement too, including rows whose Submitted By value is System. Oracle explains the automatic acceptance rules.

A submitted match is ready for statement reconciliation. It does not mean the statement has been completed.

Resolve Unmatched or Incorrect Items

Diagnose each exception from the bank source and transaction record before changing its status or accounting treatment.

Exception Checks and Correction Routes

Symptom	Check	Correction route
Bank line has no account transaction	Search the account and wider transaction records for its reference, amount and posting period. Check filters first.	If genuinely missing, create the evidenced transaction using the appropriate entry page or supported matching action, then match it.
Two imported lines appear identical	Compare both lines with the original statement and import coverage. Establish whether there are two actual bank movements.	Exclude only the confirmed duplicate imported line. Keep the import evidence and exclusion reason.
A bank line is matched to the wrong payment	Open the submitted match details and compare the original payment evidence.	Before reconciliation, use Undo Match or select the match and Undo Selected on the statement’s Review subtab. Rematch the returned items correctly.
Transaction sits in the wrong account	Compare the bank account, subsidiary and original transaction record.	Obtain approval for the accounting correction. Check both affected accounts and reconciliation status after changing it.
Opening balance does not agree	Compare the previous accepted statement, outstanding items and later transaction changes.	Resolve the earlier difference with the reviewer before closing this statement. Do not post an unexplained balancing entry.

Excluding an imported line removes it from matching without deleting it or creating an accounting entry. A real bank charge missing from the accounts still needs an entry. If a valid line was excluded, select it on Excluded Transactions and use Restore. It returns for matching. Oracle documents exclusion and restoration separately.

A cleared item has a different undo action. Open its Cleared details on the statement’s Review subtab and use Undo Clear, or select it for Undo Selected. Confirm it returns to Transactions to Match. These actions are covered by viewing submitted transactions.

For an open-period error, retain the original evidence, correction record and reason. For previously accepted work or a period used in a lodged return or BAS, obtain the responsible agent’s approval first. Record whether a tax correction is needed separately from the NetSuite correction. A completed reconciliation needs its statement history assessed before any undo or recreation.

Fictional Wrong Match

An imported supplier payment of $500 has been matched to a different $500 payment. The correct supplier payment exists in the account, so creating another payment would duplicate it. Before closing, undo the incorrect submitted match. Match the bank line to the correct payment and retain both references with the correction note. The other payment stays outstanding until its own bank evidence supports clearing it.

Complete the NetSuite Statement Reconciliation

Complete the statement only after the selected transactions explain its closing balance and every outstanding item has evidence.

6. Open Transactions > Bank > Reconcile Account Statement. Select the account and confirm its displayed currency. Enter the source Statement End Date and Ending Statement Balance. Compare Last Reconciled Balance with the prior accepted statement. Replace any unsuitable default values.
7. Inspect submitted items on Review, then use Reconcile to select the statement’s transactions. Check filters, other pages and whole match groups. Leave genuine timing items outside this statement. Selecting no transactions causes Reconcile to include all, so inspect the selection deliberately.
8. Compare the selected movement plus the prior reconciled balance with the statement closing balance. Resolve unexplained differences before completion. NetSuite permits reconciliation with a non-zero difference, so clicking the button alone does not establish agreement.
9. Click Reconcile, inspect the Close Statement confirmation and click OK. The end date becomes the unchangeable Close Date. Use the completed source statement’s past end date. The expected destination is the Reconciled Statements list. Oracle’s statement reconciliation instructions also distinguish saved selections from completing the statement.

Fictional Statement With a Charge and Timing Item

Assume the previous statement and accepted reconciliation both close at $10,000, with no opening outstanding items. During the period, the bank records $5,000 of receipts, $3,000 of cleared payments and a $20 bank charge. The statement closes at $11,980.

The account records those receipts and payments, plus a $700 supplier payment that has not reached the bank. It omits the $20 charge. Before correction, the account balance is $11,300. The $700 payment has source evidence and is a genuine timing item.

Create the missing $20 charge from its bank evidence, debit bank-fee expense and credit the bank account. This invented charge has no GST component. In Match Bank Data, select its imported line and use Add Charge, complete the details and click Add. Refresh the account grid, then match and submit the charge.

Oracle’s charge instructions state that the popup has no tax-code or rate controls. Where tax coding is required, use the standard Check or Credit Card Transaction page and match afterwards.

Expected Example Balances

Check	Calculation	Expected result
Statement closing balance	$10,000 + $5,000 - $3,000 - $20	$11,980
Account after recording charge	$11,300 - $20	$11,280
Reconciled statement movement	$5,000 - $3,000 - $20	$1,980
Prior balance plus reconciled movement	$10,000 + $1,980	$11,980
Statement less outstanding payment	$11,980 - $700	$11,280

Include the cleared receipts, cleared payments and recorded charge in the statement. Leave the $700 payment outstanding. Do not enter a second payment or an adjustment to remove that timing difference. The completed reconciliation has no unexplained difference, while the account balance remains $11,280.

Verify the Reports Before Client Handover

Retrieve the completed statement and compare its reports with the bank source before giving the file to your reviewer.

10. Go to Transactions > Bank > Reconcile Account Statement > List and filter by account. Confirm the completed statement appears with the correct closing date. From Reconcile Account Statement, select the account and open Reconciliation History Report to inspect earlier statements.
11. Open Reports > Banking/Budgeting > Reconciliation for Summary and its Detail report for transaction-level checks. In Detail, select Account and Statement Date, then Refresh. Oracle’s report navigation identifies these routes. Export or print the reports before reconciling another account, as Oracle warns the same information cannot be recaptured.
12. Compare the report account, currency and statement period with the source and bank register. Check balances and every outstanding item. For the example, Summary and Detail must explain the $11,980 reconciled balance and $700 outstanding payment against the $11,280 account balance. The recorded charge must appear once. Clear any filters that hide exceptions before accepting the output.

Retain the source statement, Summary, Detail and relevant history with the correction evidence. Add the preparer’s identity and the reviewer’s acceptance. Record unresolved decisions with their owners. Keep any unresolved accounting decision visible to the reviewer. The year-end checklist for bookkeepers places this bank evidence in the wider file handover.

Later changes can invalidate the accepted result. Oracle’s reconciliation troubleshooting explains that changing a reconciled amount can unmatch and unreconcile the whole match group. Changing an account does not automatically unreconcile the item. Compare the saved reports with the changed transaction, its System Information notes and current match status before deciding the correction.

If a completed period needs additional transactions, Oracle’s statement recreation procedure deletes the latest reconciled statement before recreating it. Deletion removes that period’s report access and leaves transactions matched and submitted but unreconciled. Obtain approval and preserve the reports first. Do not delete successive historical statements to force agreement. Refer an earlier-period change to the responsible reviewer with its affected statements and accounting consequences.

Release the reconciled file when the saved statement agrees with the source, the reports explain the account balance and the reviewer accepts the corrections and outstanding items.