Resolving NetSuite Bank Reconciliation Exceptions
Resolve NetSuite bank reconciliation exceptions by identifying whether the difference comes from the bank import, an existing book transaction, a missing book entry or normal timing. Correct the originating issue with approval, then complete statement reconciliation using reproducible balances and evidence. Matching an imported line is one stage of the control.
The workflow below is designed for controllers, cash accountants and NetSuite administrators. Account connectivity, parser behaviour and available banking features vary. Use your bank's original statement as the independent reference and test the procedure in the account before adopting it.
Confirm the reconciliation population
Start with the bank account, currency, statement dates and ending balance. Verify that the statement belongs to the intended legal entity and that the selected NetSuite account is correct. Record the prior accepted reconciliation and opening balance.
Check that all expected statement activity was imported once. Compare the date range and count of imported records with the source where practicable. Look for overlapping imports, partial files, missing days and inconsistent signs. A feed showing recent transactions does not prove that the entire statement period is complete.
Keep the original statement or permitted export unchanged. If a file needs transformation, preserve both the original and the transformation record. Otherwise a later reviewer may be unable to determine whether the difference originated at the bank or during preparation.
Review matching before creating entries
Oracle describes a sequence of reviewing match suggestions, handling unmatched transactions or exclusions, and then reconciling the account statement. The matching page requires the relevant reconciliation permission.
For each unmatched bank line, search the books by amount, reference, counterparty and a reasonable date window. Consider payments in transit, grouped deposits and payment-provider settlements. Do not create another transaction merely because the first search did not find a match.
Review both proposed and automatically submitted matches under an appropriate control process. Repeated amounts and generic payment references can make a wrong match look plausible. Set the review depth according to the risk, and retain the evidence needed to explain unusual or material matches.
Route exceptions by cause
Import problems belong with the feed or file owner. Examples include duplicated lines, truncated references and missing batches. Resolve the import condition before changing the ledger to accommodate it.
Book-entry problems belong with the process that created the transaction. A payment posted to the wrong account, an omitted bank fee or a duplicated receipt needs accounting review and an approved correction. Give the originating team enough detail to reproduce the problem.
Timing differences require an expected clearing date and a follow-up owner. A cheque or transfer outstanding at month end may be legitimate, but an old item that never clears deserves renewed investigation. Do not repeatedly carry an unexplained item simply because it was present last month.
Unknown or suspicious activity needs prompt escalation under the company's treasury and security procedures. Do not normalise an unexplained withdrawal as an ordinary bank charge just to finish the reconciliation.
Hypothetical settlement example
A fictional company records customer receipts totalling USD 12,000. Its payment provider deposits USD 11,760 and supplies a settlement statement showing USD 240 of fees. Assume finance has confirmed the fee treatment and there are no reserves, refunds or currency differences in this simplified example.
The accountant should reconcile the USD 12,000 gross receipts to the settlement detail and the USD 11,760 bank deposit, with the USD 240 difference supported by the fee evidence. A second customer receipt for USD 11,760 would duplicate cash activity and leave the original receipts unresolved.
Now suppose the provider statement also contains a USD 300 refund from a prior batch. The first arithmetic no longer describes the deposit. The accountant expands the bridge to include that refund and traces it to the approved customer transaction. The bank amount by itself cannot reveal which components belong in the books.
Keep the provider settlement reference, constituent receipt identifiers, fee evidence and final accounting references together. This makes the next similar exception quicker to resolve without relying on memory.
Control exclusions and duplicates
An excluded imported line should have a reason, source reference and reviewer. Exclusion may be appropriate for an import duplicate, but it should not become a way to hide a real bank transaction. Confirm what remains in the import and reconciliation population after the action.
Before a reimport, establish whether the original attempt partially succeeded. Compare source identifiers and existing lines rather than resending the entire file blindly. A recovery procedure should explain how to identify accepted, failed and uncertain records.
For duplicated book entries, use the company's approved correction method and preserve the audit trail. Avoid deletion or date changes undertaken solely to make matching easier. The correction must leave cash, customer or supplier balances and related reports consistent.
Reconcile and review the statement
Once matching exceptions are resolved or properly explained, reconcile the statement using the intended ending balance and date. Check the movement from opening book cash through posted activity to closing book cash and compare it with the bank side and outstanding items.
The reviewer should verify the bank evidence independently, inspect old outstanding items and confirm that corrections were approved. Include foreign-currency considerations when the bank account or related settlements require them. Do not merge an exchange-rate difference into an unexplained cash variance.
Oracle notes that changing the amount of a previously reconciled transaction makes it unreconciled. Include that behaviour in the post-close change review.
Save the final reconciliation with its report parameters and accepted exception register. If an underlying transaction changes afterward, identify whether the reconciliation must be repeated and retain the replacement evidence.
A usable exception log
For each unresolved line, record:
- Bank account, statement date and source reference
- Amount, currency and direction of movement
- Candidate book transaction and why it does or does not match
- Cause category and supporting evidence
- Action owner, approval requirement and target date
- Correcting transaction or documented timing explanation
- Reviewer and final clearing outcome
Summarise recurring causes monthly. If many exceptions stem from missing references, fix the payment or integration process. If deposits repeatedly require manual splitting, review the settlement data available from the provider. Improving the source usually helps more than creating another matching rule.
Can matching replace statement reconciliation?
No. Matching connects imported activity to book records. Statement reconciliation establishes that the full account balance is explained at the chosen cutoff.
Should every unmatched transaction become a journal?
No. Search for existing activity and investigate import and timing causes first. A journal is appropriate only when finance has determined that it is the correct accounting response.
Use a recent statement and its three most persistent exceptions for a bank reconciliation process review. That gives the team a concrete starting point for better controls.