Account reconciliation is the process of proving that a general-ledger account balance is complete, accurate, and supported at a defined date. The preparer compares the ledger balance with an appropriate source of truth, explains every difference, records the owner and expected resolution of open items, and submits the work for independent review.
The supporting source depends on the account. A bank account is compared with a bank statement; an AR control account with the receivables subledger; a prepaid account with a roll-forward schedule; and an intercompany account with the counterparty entity. The control is not complete merely because two totals happen to agree. The underlying population, accounting period, mappings, and unresolved items must also be valid.
What account reconciliation proves
| Assertion | Question for the preparer | Evidence |
|---|---|---|
| Completeness | Are all relevant transactions and supporting items included? | Controlled source extracts, report parameters, sequence or population checks |
| Existence and support | Does the balance represent real assets, liabilities, activity, or timing items? | Third-party statements, subledgers, contracts, invoices, schedules, or confirmations |
| Accuracy | Are amounts, currencies, calculations, and mappings correct? | Recalculation, source-to-ledger comparison, exchange-rate and mapping checks |
| Cutoff | Is activity recorded in the appropriate accounting period? | Transaction, value, service, invoice, posting, and settlement dates |
| Classification | Is the balance in the correct account, entity, cost centre, or other dimension? | Chart-of-accounts policy, source details, and approved mappings |
| Ownership | Does every open item have an accountable owner and next action? | Exception log, aging, due date, escalation, and resolution evidence |
Sources used for different account types
| Account | Ledger balance compared with | Typical reconciling items |
|---|---|---|
| Cash and bank | Bank statement or controlled bank feed | Deposits in transit, outstanding payments, fees, interest, and posting timing |
| Accounts receivable | Customer open-item subledger and receipt records | Unapplied cash, direct GL journals, credit notes, and failed batches |
| Accounts payable | Supplier subledger and, where relevant, vendor statements | Unrecorded invoices, duplicate postings, direct GL journals, and payment timing |
| Intercompany | Counterparty entity ledger or agreed intercompany statement | Timing, currency, entity mapping, netting, and unmatched charges |
| Prepayments and accruals | Contract, calculation, and period-by-period roll-forward | Missed releases, stale estimates, incorrect start dates, and unsupported additions |
| Fixed assets | Asset register and depreciation roll-forward | Unrecorded disposals, capital additions, transfers, and depreciation differences |
| Payroll and benefits | Payroll register, payment records, and liability schedules | Cutoff, rejected payments, benefit deductions, and manual journals |
| Clearing and suspense | Transaction-level source and expected clearing event | Failed interfaces, unidentified receipts, duplicates, and items without an owner |
Account reconciliation process
- Define the account and period. Confirm the legal entity, ledger, account, currency, reporting date, preparer, reviewer, due date, frequency, and risk classification. Opening the correct report for the wrong entity is not a valid starting point.
- Obtain the final ledger balance. Use a controlled trial balance or account detail after the relevant posting cutoff. Preserve the report parameters and extraction time, and identify later postings that could change the result.
- Gather independent support. Obtain the statement, subledger, schedule, contract, confirmation, or source-system population appropriate to the account. Test that the supporting report is complete and uses the same date, entity, and currency basis.
- Compare balances and underlying items. Reconcile the ledger total with the support, then inspect transaction-level detail, roll-forward movement, or relevant mapping. A zero difference between incomplete reports does not prove the account.
- Identify reconciling items. Separate genuine timing differences from errors, missing postings, duplicates, unsupported balances, and classification issues. Each item should have a source reference and a clear explanation.
- Resolve or document the difference. Prepare supported corrections where the ledger is wrong. Carry valid timing items with an owner, age, due date, expected clearing event, and evidence. Do not use a plug entry to force agreement.
- Certify and review. The preparer confirms the work is complete. An authorized reviewer evaluates the support, judgment, age and materiality of open items, unusual movement, and evidence of subsequent resolution.
What an account reconciliation workpaper contains
| Section | Minimum content |
|---|---|
| Header and scope | Entity, account, currency, period, purpose, frequency, preparer, reviewer, and due date |
| Balance summary | Ledger balance, supported balance, reconciling items, and final unexplained difference |
| Source evidence | Final ledger detail and the independent statement, subledger, schedule, or confirmation |
| Open-item schedule | Amount, date, age, cause, owner, action, due date, and expected clearing evidence |
| Adjustments | Approved correcting-journal reference and link to the item it resolves |
| Movement analysis | Explanation of significant or unusual change from the prior period where required |
| Certification | Preparer completion, reviewer approval, comments, timestamps, and later reopening history |
Worked account reconciliation example
An illustrative supplier-control account shows a closing GL balance of 1,240,000, while the final AP subledger totals 1,225,000 for the same entity, currency, and date. The difference is 15,000. Investigation finds a manual journal posted directly to the control account for a supplier charge that should have entered through the AP subledger.
| Reconciliation line | Amount | Evidence or action |
|---|---|---|
| GL control-account balance | 1,240,000 | Final trial balance and account detail |
| AP subledger balance | 1,225,000 | Final supplier open-item report |
| Difference | 15,000 | Direct GL journal identified |
| Resolution | 15,000 | Reverse or reprocess under the approved AP and journal policy |
| Unexplained difference after action | 0 | Posting and subledger balance reverified |
A zero final difference is not the only evidence of completion. The workpaper should retain the ledger and subledger extracts, journal reference, source charge, approval, posting result, and proof that the item appears correctly after reprocessing. Amounts are illustrative, and the accounting treatment follows the organization's policies and system design.
Reconciling items versus accounting errors
A reconciling item is a specific, explainable difference between the ledger and its support. Some are valid timing items: for example, a bank transaction recorded by one party before the other. Others are errors requiring correction, such as a duplicate, wrong entity, missing posting, or unsupported journal. Labeling every difference as timing postpones the control rather than completing it.
| Item | Can it remain open? | Required evidence |
|---|---|---|
| Defined timing difference | Temporarily, within policy | Source date, expected clearing event, owner, due date, and subsequent verification |
| Ledger error | Only until an approved correction is posted | Root cause, correcting entry, approval, and final posting result |
| Supporting-system error | Only under controlled remediation | Source-system ticket or correction, impact assessment, and re-extract |
| Unidentified difference | Not as a completed reconciliation | Escalation, investigation record, and explicit review disposition |
| Immaterial difference | Only if policy permits | Threshold, aggregation check, approval, and consistent treatment |
Aging and follow-up of open items
Open items should be aged from a defined event, such as transaction date, statement date, or first identification. The schedule should record when the item is expected to clear and what proof will close it. Repeatedly copying an item into the next month without new evidence is not resolution. Older balances, recurring breaks, and items that cross reporting periods should receive increasing review and escalation under the account's policy.
How often should accounts be reconciled?
Frequency should follow risk rather than a single rule for every account. Transaction volume, balance, susceptibility to error or fraud, system complexity, judgment, regulatory or close requirements, and prior exceptions all matter. High-volume cash or clearing accounts may need daily operation. Material control accounts are commonly included in each reporting close. Stable, low-activity accounts may be reviewed less frequently if the organization's policy permits and the risk assessment is documented.
Account reconciliation versus related controls
| Control | Primary scope | Relationship |
|---|---|---|
| Account reconciliation | One GL account and its supporting source at a defined date | Core practitioner process described on this page |
| Balance-sheet reconciliation | The full population of balance-sheet accounts, risk tiers, cadence, and certification | Programme containing many account reconciliations |
| Financial reconciliation | Broad comparison of financial records, including operational and ledger reconciliations | Umbrella discipline spanning more than individual GL accounts |
| Transaction matching | Line-level comparison based on identifiers, amounts, dates, and rules | Can support a reconciliation but does not prove the whole account or review open items |
| Flux or variance analysis | Unexpected movement between periods, budget, or expectation | Can identify an unusual change even when supporting totals agree |
Account reconciliation software and managed operations
A reconciliation platform can standardize templates, import balances, match transactions, age open items, enforce deadlines, and retain approval evidence. It does not define the right support for every account, correct weak source data, or investigate exceptions without an operating model. Teams comparing platforms can use the separate account reconciliation software guide.
Aetherix runs reconciliation preparation, matching, exception investigation, evidence assembly, and close tracking within managed operations while authorized finance owners retain policy and approval decisions. See the scope of ledger reconciliation services and the controls used in reconciliation automation.
Frequently asked questions
What is the main purpose of account reconciliation?
Its purpose is to prove that a ledger account is complete, accurate, and supported at a defined date, while making every difference visible, owned, and reviewable.
Does an account reconcile when the difference is zero?
Not necessarily. Two incomplete reports can agree, or a wrong entry can offset another error. The preparer must also validate the population, period, support, mappings, and unresolved items.
Who should prepare and review an account reconciliation?
An assigned preparer gathers the evidence and investigates differences. An authorized reviewer who is independent of preparation should challenge support, judgment, old items, unusual movement, and corrections according to the organization's control design.
What is an unreconciled item?
It is a difference or unsupported amount that has not been explained and resolved under the reconciliation policy. It should not be hidden in a plug, carried without ownership, or treated as complete solely because it is small.