Ledger Reconciliation

Ledger reconciliation is the process of checking a general-ledger account’s balance and relevant activity against supporting records, subsidiary ledgers or schedules for the same reporting date or period. The general ledger is an organization’s central accounting record, where transactions are grouped into accounts used to prepare financial statements.

What Reconciliation Checks

The purpose of ledger reconciliation is to show what supports a recorded balance and explain any differences from the supporting evidence. It is broader than matching individual transactions: a set of matched entries may still leave an opening balance, an adjustment or an unexplained remainder unresolved.

The appropriate evidence depends on the account. A supporting schedule sets out the amounts that make up an account balance. Bank reconciliation checks recorded cash against bank statements and is one application of this wider process. A receivables account may be checked against a subsidiary ledger of customer balances, with invoices and payment records supporting the underlying items. Both sources must cover the intended date or period; comparing different cut-off dates can create apparent discrepancies.

For accounts payable, reconciliation can compare the control account with the supplier subledger, then use invoices, credit notes, payment records and available supplier statements to investigate differences. This can reveal a missing invoice, a duplicated liability or a payment allocated to the wrong supplier. Fixed-asset reconciliation compares ledger balances with the asset register and supporting acquisition, disposal and depreciation records. The aim is to explain both the recorded assets and movements in their carrying amounts, not simply match purchase invoices to the closing balance.

How Ledger Reconciliation Works

A ledger reconciliation starts with the account balance, the relevant activity and the records that should support them. The person preparing it compares totals and examines the underlying items to identify amounts that are missing, duplicated, recorded differently or still outstanding. Agreement between totals is useful, but it does not replace understanding how the balance was built up.

Each difference is traced to available evidence before deciding whether the ledger needs a correction or the difference needs an explanation. Necessary corrections are recorded, and the reconciliation is updated to show their effect. Any remaining differences are listed with their cause, status and required follow-up. The completed record and its supporting evidence are then made available for review according to the organization’s procedures.

How Differences Are Resolved

Ledger reconciliation distinguishes accounting errors from legitimate timing differences. An omitted transaction, duplicate posting or entry to the wrong account may require a justified correcting journal entry. If the supporting record is wrong, it may need correction instead of the ledger. The correction should be supported by evidence and explain what was changed; it should not be an unexplained adjustment made simply to force agreement.

A timing difference occurs when the records recognize or process an item at different times. For example, a payment recorded in the cash ledger may not yet appear on the bank statement. If the accounting treatment is appropriate, the item is documented and followed up rather than automatically corrected. An old or unexplained outstanding item needs further investigation, because its continued presence may indicate an error rather than a normal delay.

Documentation and Limitations

A useful reconciliation records the account and reporting date, the balance checked, the supporting records used, the differences identified and any corrections made. It also preserves explanations for unresolved items and enough detail for another person to understand the work. This documentation helps finance teams prepare more reliable reports and gives auditors a record they can assess alongside other evidence.

Ledger reconciliation can reveal discrepancies, but agreement alone does not prove that every transaction is valid or that the financial statements are correct. Two records can agree while sharing the same error, or both can omit a transaction. The quality and completeness of the supporting evidence therefore matter as much as the comparison itself. Auditors evaluate that evidence and other relevant controls; a completed reconciliation does not independently provide audit assurance.

Reconciliation software can import records, apply matching rules and group exceptions for investigation. Its usefulness depends on complete inputs, suitable matching criteria and controls over changes to those criteria. A suggested match is not proof that the underlying entry is correct, and unmatched items still require ownership and follow-up. Retaining the evidence, changes and review history allows another person to assess the work even when much of the matching was automated.