General Ledger Reconciliation: A Beginner’s Guide

General ledger reconciliation connects a financial statement balance to independent evidence, explains every difference, and leaves a reviewable record of how the account was proved.

The goal is not merely to make two totals match. A good reconciliation shows what the ledger balance contains, why legitimate timing items remain, which errors were corrected, and who reviewed the result. It turns a balance from an unsupported number into an accounting conclusion.

What is general ledger reconciliation?

The general ledger contains the accounts used to produce the balance sheet and income statement. A reconciliation compares one of those accounts with a reliable source or a detailed supporting schedule.

Examples include:

• Comparing a bank account in the ledger with the bank statement.
• Comparing accounts receivable with the customer aging report.
• Comparing accounts payable with the vendor aging report.
• Comparing a credit card account with the issuer statement.
• Comparing a loan account with the lender statement and amortization schedule.
• Comparing payroll liabilities with payroll reports and subsequent payments.
• Comparing fixed assets and accumulated depreciation with the asset register.

Some accounts have a natural third-party statement. Others require a roll-forward or schedule built from contracts, invoices, payment records, or other source documents.

The four parts of a complete reconciliation

1. Ledger balance

State the account number, account name, reporting date, and ending balance from the general ledger. Save the report or identify the report settings used, because a live report can change after transactions are edited.

2. Independent support

Identify the source that should support the balance. Independence does not always mean an outside party, but the support should not simply repeat the same ledger data in a different format.

3. Reconciling items

List differences individually. Distinguish valid timing items from errors. Each item should have a date, amount, explanation, owner, and expected resolution where applicable.

4. Conclusion and review

Show the adjusted comparison and whether the account is reconciled. Record who prepared and reviewed it, when the work was completed, and what corrections were posted.

General ledger reconciliation example

Assume the general ledger shows an illustrative cash balance of $48,250 at month-end, while the bank statement shows $44,900. The difference is $3,350.

The preparer identifies a $4,000 customer deposit recorded in the ledger on the last day of the month but posted by the bank the next day, and a $650 bank withdrawal that belongs to the month but has not been recorded in the ledger.

Reconciliation line	Amount
Bank statement ending balance	$44,900
Add: deposit in transit	$4,000
Adjusted bank balance	$48,900
General ledger ending balance	$48,250
Add to ledger: unrecorded withdrawal correction shown as reduction	$650 difference to resolve

The illustration reveals that the unrecorded withdrawal needs careful handling. If the bank withdrew $650, recording it would reduce the ledger balance to $47,600, not increase it to $48,900. The apparent explanation does not reconcile the account and may contain a sign error or missing fact.

This is exactly why a reconciliation should show the arithmetic, not just a note saying “bank fee” or “timing.” The preparer must inspect the transaction, confirm whether it was already included elsewhere, and revise the schedule. A plausible label is not proof.

Step-by-step reconciliation process

Step 1: lock the scope

Choose the legal entity, account, reporting date, currency, and ledger basis. Confirm that the beginning balance agrees with the prior approved reconciliation. If it does not, identify post-close changes or an unresolved prior-period difference before continuing.

Step 2: gather the support

Collect the ledger detail, bank or vendor statements, subledger reports, schedules, invoices, contracts, payment records, and prior reconciliation. Use reports with dates and filters visible so another reviewer can reproduce them.

Step 3: compare the totals

Compare the ledger balance with the supporting balance. When the totals differ, do not immediately post the difference. Determine whether the support requires adjustment for timing, whether the ledger is incomplete, or whether the two reports cover different populations.

Step 4: match activity

Match transactions by date, reference, amount, and business purpose. For high-volume accounts, software may assist with matching, but unusual, old, duplicate, and manually posted items still need human review.

Step 5: classify each difference

• Timing item: valid activity recorded in different periods by the two sources.
• Ledger error: missing, duplicate, misdated, or misclassified entry.
• Source error: an outside statement or subledger contains a mistake requiring correction.
• Scope difference: the two reports use different accounts, entities, dates, or filters.
• Unsupported item: the cause is not yet known and remains an exception.

Step 6: post supported corrections

Correct source transactions when practical. Use a journal entry only when it is the appropriate accounting record, and attach the calculation and approval. Avoid posting a plug to force agreement.

Step 7: prove the ending balance

Update the schedule after corrections. The adjusted support and adjusted ledger should agree, or the reconciliation should state the remaining unresolved difference clearly. A zero unexplained difference is the normal completion standard.

Step 8: review and retain the package

The reviewer should test the arithmetic, inspect selected support, challenge old reconciling items, and confirm that corrections were posted. Retain the final ledger report, outside support, reconciliation schedule, journal entries, and evidence of review.

Different types of general ledger reconciliation

Bank and credit card reconciliation

These compare cash or card accounts with statements. Pay particular attention to duplicate transactions, old outstanding checks, transfers recorded on one side, processor clearing, and activity after the statement date.

Subledger-to-general-ledger reconciliation

Accounts receivable and accounts payable often have detailed customer or vendor subledgers. Their totals should agree with the corresponding control accounts. Direct journal entries to control accounts, deleted documents, or incorrect dates can create differences.

Balance sheet schedule reconciliation

Prepaid expenses, fixed assets, loans, deferred revenue, deposits, and accruals may use roll-forward schedules. A roll-forward begins with the prior balance, adds current-period increases, subtracts releases or payments, and arrives at the ending supported balance.

Income statement review

Revenue and expense accounts may not reconcile to one statement in the same way as cash. They can still be tested through trend analysis, source-system totals, payroll reports, contracts, invoice populations, and period cutoff procedures. Call this review or substantiation accurately rather than pretending every account has an outside balance.

How often should accounts be reconciled?

Set the cadence based on risk and account behavior, not an invented universal amount. Consider transaction volume, susceptibility to error or fraud, cash impact, reporting importance, volatility, and how quickly a problem must be found.

Cash, credit cards, receivables, payables, payroll liabilities, and clearing accounts often need monthly attention and sometimes more frequent operating review. Stable long-term accounts may use a less frequent detailed review if activity is limited and controls support that decision. Every material balance included in financial reporting should have a defined owner and evidence standard.

Common reconciliation failures

• Beginning balance not tied to prior work: later activity cannot explain an opening difference.
• Report filters hidden: the support cannot be reproduced.
• Old reconciling items rolled forward: timing becomes a permanent explanation.
• Plug entries: the total matches while the underlying error remains.
• Direct entries to control accounts: the general ledger moves without the customer or vendor detail.
• No evidence of review: arithmetic or classification errors pass through the close.
• Reconciliations completed before postings stop: later changes invalidate the saved work.

A reconciliation proof packet

Use one folder or controlled record for each account and period. Include the ledger report, independent support, reconciliation schedule, reconciling-item detail, corrections, and review evidence. Name files consistently and preserve the final version.

This packet shortens the next close because the new preparer can start from the prior approved balance. It also helps a tax preparer, lender, auditor, or new accounting provider understand how the number was built without asking the owner to reconstruct months of history.

For related concepts, review the chart of accounts and the general ledger. Reconciliation is the control that connects those structures to evidence.