An account reconciliation workflow defines which balances must be proven, which evidence is authoritative, how differences are resolved, who reviews the conclusion, and how completion supports the financial close. It covers far more than bank accounts.
Set the reconciliation scope
Inventory balance-sheet and material clearing accounts. Assign frequency and rigor based on value, volume, complexity, judgment, fraud, prior error, regulation, and system change. Low-risk accounts may use a simplified review; cash, customer funds, tax, debt, and suspense usually require stronger evidence.
Standard reconciliation package
| Component | Minimum content |
|---|---|
| Header | Entity, account, period, preparer, reviewer, due dates |
| Ledger | Ending balance and source report parameters |
| Support | Independent subledger, statement, confirmation, or calculation |
| Differences | Amount, cause, age, owner, action, resolution date |
| Conclusion | Adjusted balance and explicit assertion |
| Review | Questions, corrections, approval, and lock evidence |
Close workflow
- Publish the calendar and lock source periods.
- Validate report completeness and opening balances.
- Match balances or transactions using stable identifiers.
- Analyze unmatched and unusual items.
- Prepare supported correcting entries.
- Escalate aged or high-risk exceptions.
- Complete independent review before reporting.
- Archive the approved package and track late changes.
Different accounts need different evidence
- Receivables: subledger, invoices, cash, credits, and aging
- Inventory: perpetual records, counts, costing, and reserves
- Fixed assets: register, invoices, placed-in-service evidence, disposals
- Debt: lender statement, amortization, interest, and covenants
- Tax: returns, payments, notices, and account roll-forward
- Accruals: method, source data, reversal, and subsequent settlement
Reviewer responsibilities
The reviewer confirms sources, recalculates material items, challenges stale differences and unusual mappings, verifies entries, and assesses whether the account makes sense relative to operations. A signature without evidence of review adds little control.
Automation governance
Approve rules and tolerances, restrict changes, validate data completeness, sample matched items, review manual overrides, and retain logs. Measure exceptions resolved—not the percentage automatically matched in isolation.
Use Critical Reconciliation for material accounts and Bank Reconciliation for cash-specific examples.
At period end, the controller should review completion, aged exceptions, post-close entries, repeated root causes, and accounts with weak evidence. Convert recurring differences into process actions with owners and deadlines. The goal is not merely a signed checklist; it is a reliable balance and a shrinking population of preventable exceptions.
Frequently asked questions
Must every account be reconciled monthly?
Frequency should reflect risk and reporting needs. Document why a different cadence is appropriate.
Can zero-balance accounts be skipped?
Not automatically. Activity, unauthorized use, or offsetting errors can exist even when ending balance is zero.
What closes an exception?
Evidence that the cause was corrected or validly resolved, not merely a comment copied into the next period.
Sources reviewed
Last reviewed: August 15, 2026. Adapt workflow, evidence, and review to the entity’s accounting framework and risks.