Key Takeaways
- SOX auditors classify unresolved reconciliation differences as material weaknesses: If auditors find a misstatement the company cannot prove it would have caught independently, it is classified as a material weakness requiring public disclosure.
- Automating reconciliation eliminates 70% of the manual process: Including spreadsheet compilation, manual balance verification, and formula-based matching, according to HighRadius research.
- Account reconciliation covers six account categories beyond just bank: Balance sheet, AR, AP, inventory, intercompany, and accruals all require reconciliation with a designated supporting source.
- NetSuite NSAR automates reconciliation for AP, AR, bank, intercompany, prepaid, accruals, and fixed assets: It integrates directly with the period-end close checklist and stores completed reconciliations in a secure document repository.
Introduction
Account reconciliation is the last line of defense before financial statements go out. Every material misstatement that surfaces in an audit, every restatement that triggers SEC disclosure, every board meeting where the CFO cannot answer a question about a balance. These trace back to reconciliations that were missed, delayed, or done carelessly.
The stakes are significant. Under SOX Section 302 and 404, CEOs and CFOs certify personally that financial statements are accurate. If an auditor finds a misstatement, the company cannot prove it would have caught through its own controls, that error is classified as a material weakness. Material weaknesses require public disclosure, damage investor confidence, and can trigger an SEC investigation.
NetSuite’s account reconciliation capabilities automate the matching, flagging unresolved differences, tracking reconciliation status across the close cycle, and storing completed reconciliations in an audit-ready document repository.
This guide covers what account reconciliation is, the four-step process, the account types that require reconciliation, common pitfalls, and how NetSuite’s toolset handles reconciliation in practice.
What Is Account Reconciliation
Account reconciliation is the process of comparing a balance in your general ledger to an independent source of the same data, verifying they agree, and investigating and resolving any differences. The objective is to confirm that the GL balance accurately reflects the underlying activity it is supposed to represent.
Each account type has a corresponding reconciliation source:
- Bank accounts: GL cash balance compared to the bank statement ending balance
- Accounts Receivable: GL AR balance compared to the aging report or customer ledger subledger
- Accounts Payable: GL AP balance compared to the vendor ledger subledger or supplier statements
- Inventory: GL inventory balance compared to the physical count or the inventory subledger
- Intercompany: Balances between related entities compared to confirm eliminations are complete and accurate
- Accruals and prepaid expenses: GL balance compared to the supporting schedule that tracks what has been recognized vs. what remains deferred
A reconciliation is complete when the GL balance equals the supporting source, or when all identified differences are explained (timing differences with documented resolution dates, for example), and the reconciliation is signed off by an authorized reviewer.
The Four-Step Reconciliation Process in NetSuite
Step 1: Identify Accounts and Confirm Period
Start by confirming which accounts require reconciliation for this close cycle, the period covered (calendar month, fiscal period, etc.), and the statement date for the external source. Matching the period is critical: a bank statement dated January 31 must be reconciled to the GL balance as of January 31, not to a different date.
In NetSuite, the Period Close Checklist organizes reconciliation tasks by period. Each task is assigned to a responsible team member with a due date. This gives the controller visibility into which reconciliations are in progress, which are complete, and which are overdue without having to chase status updates manually.
Step 2: Compare and Match Transactions
Pull the GL transactions for the period and the corresponding statement or subledger. Match each transaction in the GL to its counterpart in the supporting source. Identical matches (same date, amount, and description) are straightforward. Partial matches (same amount, different date) require judgment about whether the difference reflects a timing issue.
For bank reconciliation in NetSuite specifically, the bank reconciliation screen shows uncleared GL transactions alongside imported bank statement lines. Transactions can be matched automatically based on amount and date, or manually matched where the system cannot make a confident automatic match. See our step-by-step guide to matching bank data in NetSuite for period reconciliation for the detailed mechanics.
Step 3: Investigate and Resolve Differences
Any unmatched item is a difference that needs investigation. Differences fall into two categories:
- Timing differences: A transaction recorded in the GL in one period but not yet reflected in the external source (outstanding checks, deposits in transit). These are expected and self-correcting, but must be documented
- Errors and discrepancies: A transaction in the external source not recorded in the GL, or vice versa, that should not exist. These require a correcting entry, a vendor call, a banking inquiry, or flagging for fraud investigation depending on the nature
For each difference, document the explanation and the resolution plan. If a difference is flagged as an error, record the correcting journal entry in NetSuite before closing the reconciliation. If it is a timing item, document the expected resolution date.
Step 4: Confirm Balance and Sign Off
After all differences are addressed, confirm that the adjusted GL balance equals the supporting source balance (or that all remaining differences are documented timing items with resolution dates). Reconciliations must be reviewed and approved by someone other than the preparer. This segregation of duties is a SOX requirement: the person who prepares the reconciliation cannot also approve it.
In NetSuite’s NSAR module, completed reconciliations are stored in a document repository with preparer and approver stamps and timestamps. This creates the audit trail that external auditors require during SOX testing.
Common Pitfalls in Account Reconciliation
1. Reconciling to the Wrong Date
The GL balance must be compared to the supporting source as of the same date. Comparing a January 31 GL balance to a January 28 bank statement introduces automatic differences that are not real errors. Always confirm statement dates before starting.
2. Carrying Forward Unresolved Differences
Unresolved differences from one period that roll into the next are the most common source of material misstatements. A small unexplained difference in October that nobody investigates becomes a carried-forward entry in November, December, and January. By the time it is investigated, the supporting documentation is weeks or months old and the root cause is much harder to identify.
Reconciliation policy should require that all differences above a defined threshold are investigated and resolved within the same period they are identified. Differences below the threshold may be waived with documented approval, but the approval must be explicit, not implicit.
3. No Segregation of Duties
The same person who posts journal entries should not also reconcile the account and approve their own reconciliation. Without segregation of duties, errors (and intentional misstatements) can be concealed within the reconciliation. SOX auditors will flag this as a control deficiency. NetSuite role-based permissions support proper segregation by restricting who can approve reconciliations versus who can prepare them.
4. Reconciling Only Bank Accounts
Many finance teams reconcile their bank accounts monthly but do not formally reconcile AR, AP, inventory, accruals, or intercompany balances. These account types also accumulate errors. An AR balance that has not been reconciled against the aging for three months may contain invoices posted to wrong customers, credits not applied, or write-offs not recorded. By the time the imbalance surfaces, it is too large to correct without a restatement.
5. Reconciliations Stored in Email and Shared Drives
Reconciliations stored in personal email, informal SharePoint folders, or individual hard drives are not auditable. Auditors need evidence that reconciliations were completed on schedule, reviewed by an authorized approver, and retained in an access-controlled repository. Files stored informally may be modified, deleted, or simply unavailable when needed.
6. Over-Reliance on Auto-Matching Without Review
Automated matching tools (including NetSuite’s native bank matching) match transactions by amount and date. They can produce incorrect matches when two transactions have the same amount but represent different activity. Over-trusting auto-match results without reviewing them produces a technically complete reconciliation that is substantively wrong.
How NetSuite Handles Account Reconciliation
Native Bank Reconciliation
NetSuite includes a built-in bank reconciliation screen for each bank and credit card account. Bank statement data is uploaded directly into NetSuite. The system auto-matches transactions against the GL by amount and date, flagging unmatched items on both sides. The reconciliation is locked for the period when confirmed, preventing retroactive changes to cleared transactions. For the complete walkthrough of the bank data matching process, see our guide to bank reconciliation in NetSuite including import, matching, and period lock.
NetSuite Smart Account Reconciliation (NSAR)
NSAR extends reconciliation automation to all account types, not just bank accounts. It covers AP, AR, bank and credit card, intercompany, prepaid accounts, accruals, and fixed assets. Key capabilities include:
- Automated transaction matching: Rule-based matching logic identifies matches across data sources without manual review of each line
- Journal entry creation: Post adjusting journal entries from within the reconciliation interface, with entries flowing directly to the GL
- Workflow-based approval: Reconciliations route to designated approvers; no reconciliation can be finalized without an authorized sign-off
- Document repository: All completed reconciliations stored with preparer/approver stamps, timestamps, and attached evidence — accessible to auditors without requiring staff to locate files
- Period close integration: NSAR status appears in the Period Close Checklist, giving controllers real-time visibility into reconciliation progress across all accounts
For a full breakdown of NSAR’s capabilities and how it compares to manual reconciliation, see our guide to NetSuite NSAR key features and reconciliation automation benefits.
Period Close Checklist
The Period Close Checklist in NetSuite organizes all close tasks, including account reconciliations, as a tracked workflow. Each task has an assigned owner, a due date, and a status (Not Started, In Progress, Complete). Controllers can see the full close status at any point without status calls or email updates.
Account Reconciliation and SOX Compliance
For publicly traded companies, account reconciliation is not a best practice; it is a control requirement. SOX Section 404 requires management to assess the effectiveness of internal controls over financial reporting (ICFR). Account reconciliations are detective controls: they identify errors and misstatements after transactions have been recorded.
SOX auditors test reconciliation controls specifically:
- Were reconciliations completed for all material accounts in scope?
- Were they completed within the period close timeline?
- Were all differences investigated and resolved, or formally waived?
- Was there proper segregation of duties between preparer and approver?
- Are completed reconciliations retained in an accessible, controlled repository?
KPMG’s 2025 SOX Survey found that the average number of SOX key controls increased by 18% in FY24 (546) compared to FY22 (463). Organizations that invest in automated reconciliation controls reduce both the cost of compliance and the evidence-collection burden during audits.
For the broader context of how reconciliation fits into NetSuite’s financial management architecture, see our guide to NetSuite financial management modules including GL, AP, AR, and cash management.
Conclusion
Account reconciliation is the process that keeps financial statements trustworthy. When reconciliations are done well, errors surface and are corrected before they accumulate into material misstatements. When they are skipped, delayed, or performed carelessly, those errors compound, and by the time they surface in an audit, the correction is expensive and the damage to credibility is real.
The common pitfalls are consistent: wrong period dates, carried-forward differences, missing segregation of duties, incomplete account coverage, and informal document storage. Each of these has a specific process fix and a NetSuite configuration that enforces it.
Small reconciliation issues can become significant financial risks over time. Book a meeting with our NetSuite consultants to evaluate your current processes and strengthen the controls that keep your financial data accurate and audit-ready.
