Reconciliation compares independent records or balances, explains every difference, and documents the corrections or timing items needed to reach agreement.
Reconciliation is the control process of comparing two records or independently derived balances, identifying every difference, and documenting the correction or timing explanation needed to bring them into agreement. A completed reconciliation shows not only that totals match, but why they match and who reviewed unresolved items.
Reconciliation does not mean changing one record until the numbers agree. Valid reconciling items must be supported, errors must be corrected in the record where they occurred, and old exceptions must be investigated.
| Reconciliation | Records compared | Typical reconciling items |
|---|---|---|
| Bank | Bank statement or confirmation vs. cash ledger | Deposits in transit, outstanding payments, fees, interest, errors |
| Subledger to general ledger | Customer, vendor, inventory, payroll, or fixed-asset detail vs. control account | Unposted batches, duplicate entries, mapping errors, write-offs |
| Intercompany | Receivable, payable, revenue, expense, and funding records between group entities | Timing, currency, markup, settlement, and entity-code differences |
| Inventory | Physical counts and movement records vs. inventory ledger | Shrinkage, receiving cutoff, unit-of-measure errors, obsolete stock |
| Debt | Lender statements and contracts vs. debt ledger | Principal, accrued interest, fees, foreign exchange, covenant adjustments |
| Tax and payroll | Returns, remittances, and agency records vs. ledger | Accrual timing, withheld amounts, payments, assessments, and amendments |
| Financial-statement roll-forward | Opening balance plus activity vs. closing balance | Acquisitions, disposals, remeasurement, reclassification, and translation |
The frequency should reflect risk, transaction volume, close deadlines, and the consequences of error. Daily cash or trading reconciliations can be necessary, while a low-volume account may be reconciled monthly or quarterly.
At month-end, a company’s cash ledger shows $147,300 and its bank statement shows $151,900. Review identifies:
| Bank-side reconciliation | Amount |
|---|---|
| Balance per bank statement | $151,900 |
| Add deposit in transit | +$5,400 |
| Subtract outstanding checks | -$9,200 |
| Adjusted bank balance | $148,100 |
The company does not post entries for the deposit in transit or outstanding checks because both are already in its ledger. They are timing differences in bank processing.
| Book-side reconciliation | Amount |
|---|---|
| Balance per cash ledger | $147,300 |
| Add customer electronic payment | +$1,100 |
| Subtract bank service fee | -$300 |
| Adjusted ledger balance | $148,100 |
The company records the missing bank activity:
1Dr Cash $1,100
2 Cr Accounts Receivable $1,100
3
4Dr Bank Fee Expense $300
5 Cr Cash $300
Both adjusted balances now equal $148,100. The reconciliation should retain evidence for the electronic receipt and fee, list the outstanding items, and confirm that they clear after month-end.
The preparer and reviewer should be identifiable. A signature without evidence of review is weaker than documented questions, follow-up, and resolution.
| Difference | Typical treatment |
|---|---|
| Valid timing difference | Document and monitor until it clears |
| Missing entity transaction | Record a journal entry in the entity’s books |
| Duplicate or incorrect entity entry | Correct or reverse the entity’s entry |
| Bank, vendor, or counterparty error | Contact the external party and track correction |
| Unsupported difference | Escalate; do not carry indefinitely as a plug |
| Difference below an administrative threshold | Apply policy, but still consider aggregation, fraud, and qualitative risk |
A reconciling item should not remain open merely because it repeats each month. Persistent differences can indicate broken interfaces, duplicate records, unrecorded liabilities, fraud, or poor cutoff.
Reconciliation software can match large transaction volumes, enforce workflows, age exceptions, and retain approvals. It can also produce false confidence when:
Controls should cover source completeness, matching rules, access, overrides, exception reporting, and changes to automation logic.
This page is educational and does not provide accounting, audit, fraud-investigation, tax, banking, legal, or investment advice.