A balance sheet reconciliation is not complete merely because a spreadsheet contains a number that agrees to the general ledger. A useful reconciliation explains what the balance represents, demonstrates that the underlying records are complete and accurate, identifies unexpected movements, and shows how differences were resolved. For financial controllers, the goal is to focus review effort on the accounts and assertions where errors could matter most—without turning the close into a box-ticking exercise.
This article sets out a risk-based approach that works across ERP environments, including SAP S/4HANA Finance. It is a control-design guide, not a substitute for an entity’s accounting policies, applicable reporting framework, or auditor-specific requirements.
1. Start with risk, not a uniform checklist
Not every balance carries the same risk. A small prepaid expense with stable activity may need a different review depth from a material estimate, a complex intercompany balance, or an account affected by manual journals and system interfaces. Rank reconciliations using factors such as:
- Magnitude and materiality: current balance, movement, and possible aggregate impact.
- Judgment and estimation: assumptions, model inputs, and uncertainty.
- Transaction complexity: multiple systems, currencies, entities, or counterparties.
- History of exceptions: recurring reconciling items, late adjustments, or prior errors.
- Fraud or override exposure: manual entries, privileged access, and unusual transactions.
- Change: new systems, account mappings, reorganisations, acquisitions, or process owners.
The PCAOB’s AS 2201 describes a top-down, risk-based approach to ICFR audits, beginning with financial-statement-level risks and focusing on significant accounts, disclosures, and relevant assertions. The standard applies to the audits within its scope; its risk-oriented thinking can also inform internal control design more broadly.
2. Define what a good reconciliation must prove
Document a minimum standard for every reconciliation. At a minimum, the file should identify the entity, account, reporting period, preparer, reviewer, source reports, and completion date. It should show how the supporting balance ties to the GL and explain each material reconciling item. The reviewer should be able to follow the evidence without relying on undocumented explanations from the preparer.
Different accounts need different evidence. A bank reconciliation may tie to an external statement; fixed assets may tie to a subledger and additions/disposals report; accruals may require calculations and subsequent invoices; intercompany balances may require counterparty confirmation or matched transaction detail. A template alone does not establish that the evidence is sufficient.
3. Reconcile the source to the ledger—and validate the source
For each material account, identify the authoritative source and the route by which data reaches the general ledger. Confirm that the period, entity, currency, account, and report filters are correct. Where reports are exported from an ERP, retain the report name, parameters, extraction date, and relevant control totals. For spreadsheets, protect key formulas, track changes, and keep a controlled version.
In SAP S/4HANA Finance or another ERP, check that the subledger or operational report agrees to the relevant ledger account and that interface failures, parked documents, reversals, and late postings are considered. If a reconciliation relies on a custom report, validate its logic and completeness under the organisation’s report-control process. A signed spreadsheet is not persuasive evidence if the report omitted a company code or excluded a transaction type.
4. Analyse movements, not just ending balances
A balance can look plausible while containing offsetting errors. Review significant period-over-period movements and compare them with business drivers, budgets, operational metrics, and expectations. Set thresholds that prompt investigation, but allow reviewers to challenge items below thresholds when qualitative risk is high.
For example, a warranty accrual may remain close to last month’s amount even though claims volume and product mix have changed sharply. The reconciliation should explain the estimate, key assumptions, actual claims, and any required adjustment—not merely carry forward the prior balance. For estimates, distinguish evidence supporting the recorded amount from evidence that only explains why the balance changed.
5. Control reconciling items by age and cause
Every unresolved item should have an amount, origin, explanation, owner, target resolution date, and proposed accounting treatment where needed. Age items from their original occurrence rather than resetting the clock when they are copied into a new month’s file. Define escalation rules for material, long-outstanding, recurring, or unexplained differences.
Do not use unsupported write-offs or reclassifications to make an account balance. A difference should be resolved through evidence, a supported journal, or a documented conclusion that it is a valid timing item. If the same issue appears repeatedly, assign someone to correct the underlying process, mapping, or interface.
6. Make reviewer sign-off meaningful
Reviewers should have the authority, competence, and time to challenge the reconciliation. Evidence of review should indicate what was checked and how exceptions were handled. A date and initials may be insufficient for a complex, high-risk account if they do not show the scope or depth of review.
For high-risk accounts, require evidence of independent recalculation, inspection of source support, challenge of assumptions, and follow-up on prior-period issues as appropriate. Separate preparation and approval where practical. If staffing limitations prevent full segregation, design a compensating review that is sufficiently independent and precise to address the risk.
7. Connect account controls to ICFR
Map material balance sheet accounts to relevant financial statement assertions—such as existence, completeness, valuation, rights and obligations, and presentation—based on the account and risk. Then identify which reconciliation or other control addresses each risk. Not every account requires the same assertions or the same control frequency.
The PCAOB standard explains that control design and operating effectiveness are different questions: a well-designed control may still fail if it is not performed by an appropriate person or does not operate as prescribed. Keep evidence of both the control’s intended design and its actual performance. Where a reconciliation identifies a possible misstatement, assess whether it signals an isolated error, a recurring process weakness, or a broader control deficiency.
8. A practical month-end checklist
- Confirm account ownership, risk rating, and required completion date.
- Use the correct entity, period, ledger, currency, and source-report parameters.
- Tie supporting records to the GL and check report completeness.
- Explain material movements and assess unusual or unexpected balances.
- Document reconciling items with age, owner, cause, and due date.
- Support journals and obtain approval before posting.
- Record evidence of reviewer challenge and resolution of exceptions.
- Escalate aged or recurring items and assign root-cause remediation.
- Retain evidence in the approved repository with appropriate access restrictions.
9. Measure whether the process is improving
Useful metrics include on-time completion, number and value of aged items, recurring reconciling items, post-close adjustments, rejected reconciliations, and time spent resolving exceptions. Interpret the metrics together: a low exception count can mean the process is healthy, or it can mean reviewers are not challenging balances. Periodically sample completed reconciliations and independently reperform key steps to assess quality.
Controllers should use trends to improve process design, not merely rank staff. Repeated errors may point to unclear ownership, unreliable reports, weak master data, system configuration, or inadequate training. Assign remediation to the team that can fix the root cause.
Conclusion
Effective balance sheet reconciliation is a risk-based financial reporting control, not an administrative sign-off. Set clear evidence standards, validate source data, investigate movements, manage aged items, and require reviewers to demonstrate meaningful challenge. The result is a more reliable close, clearer accountability, and stronger support for audit readiness.
Informational only: This article provides general control-design guidance and is not legal, audit, or accounting advice. Apply the accounting framework, control obligations, and materiality considerations relevant to your organisation.
Sources
- PCAOB — AS 2201, An Audit of Internal Control Over Financial Reporting That Is Integrated with an Audit of Financial Statements. The PCAOB also publishes an amended version effective December 15, 2026; use the version applicable to the relevant audit period.
- U.S. Securities and Exchange Commission — Management’s Report on Internal Control Over Financial Reporting and Certification of Disclosure in Exchange Act Periodic Reports.
