General Ledger Reconciliation: Process, Checklist and Best Practices

Your financial statements are only as dependable as the ledger supporting them. Yet general ledger reconciliation remains one of the most inconsistently applied controls in finance—executed rigorously at some companies, superficially at others, and sometimes ignored altogether until auditors raise concerns. If month-end close produces figures that lack confidence, the gap almost always lies in the GL reconciliation process. This guide outlines the procedure, provides a practical checklist, and highlights the practices that distinguish accurate records from recurring issues.

What General Ledger Reconciliation Actually Controls — and Why It Sits at the Centre of Close

The general ledger serves as the single source of truth for all financial statements a business produces. General ledger reconciliation is the process that validates that truth—ensuring each account balance is accurate, backed by documentation, and free from posting errors, duplicates, or missing transactions. Without this control, balance sheets may present unverified figures, and income statements rest on an untested foundation.

Ledger reconciliation spans every balance sheet account: cash, receivables, payables, inventory, prepaid expenses, accrued liabilities, fixed assets, and intercompany balances. Each account requires specific supporting documents and carries its own common risk patterns. As a result, GL reconciliation is not a one-off task but a structured program of account-by-account verification that runs in parallel with the month-end close.

The General Ledger Reconciliation Process — Five Steps To Reliable Results

The GL reconciliation process follows the same logic across all accounts. While the supporting documents vary, the sequence itself remains consistent.

• Identify accounts and gather documentation Begin by confirming which GL accounts require reconciliation for the period and collect all relevant source documents. For cash accounts, this means the bank statement; for receivables, the aging report; for fixed assets, the depreciation schedule. Incomplete documentation is the most common reason reconciliations must be redone. A standardized checklist helps ensure nothing is overlooked before comparisons begin.
• Verify opening balances Confirm that the opening balance matches the prior period’s reconciled closing balance. Any break here indicates an unresolved issue from the previous period that is now compounding. This step is often skipped under deadline pressure, which is why prior-period errors persist across multiple closes. Reconciliation must always start from a verified balance.
• Match GL balances to source documents line by line Compare each transaction in the GL against its corresponding entry in the source document, marking off matches as you go. Do not rely solely on closing balance agreement—two records can show identical balances while hiding offsetting errors. Transaction-level matching uncovers duplicates, misclassifications, timing differences, and fraud that balance-level checks miss.
• Investigate unmatched items thoroughly Every discrepancy requires a documented explanation before sign-off. Timing differences, such as transactions recorded in the ledger but not yet reflected externally, are valid. Errors, duplicates, and missing entries are not. Each must be classified, and correcting journal entries posted in the same period. Carrying unresolved items forward undermines the control value of reconciliation.
• Document, review, and sign off The reconciliation workpaper should show the opening balance, transactions reviewed, unmatched items with explanations, adjustments posted, and the closing balance. An independent reviewer—someone other than the preparer—must sign off before filing. This review layer provides the control authority. Without it, reconciliation becomes a self-checked document that auditors and managers cannot rely on.

GL Reconciliation Checklist — Account by Account Coverage for Month-End Close

A structured checklist is the most practical tool for ensuring ledger reconciliation covers all accounts at the right frequency with the right source documents. The table below maps each core GL account to its source document, recommended frequency, and the primary risk created when reconciliation is skipped or done superficially.

Finance teams at MBG Corporate Services (mbgcorp.com/ae) use this structure as a baseline for GL reconciliation programmes across sectors — adapting frequency and account scope to each client’s transaction volume, regulatory environment, and reporting requirements.

Prioritise high-risk, high-volume accounts — cash, AR, and AP — for the most rigorous transaction-level review. Lower-volume accounts like prepaid expenses and fixed assets still require monthly reconciliation but typically carry smaller transaction sets. The key discipline is consistent coverage across all balance sheet accounts, not selective reconciliation of the ones that are easiest to clear.

Best Practices That Separate a Functional GL Reconciliation Programme from a Checkbox Exercise

• Reconcile at transaction level, not balance level. A matching closing balance only means no net error exists. It won’t catch duplicate postings, offsetting errors, or misclassifications. Line-by-line matching is non-negotiable for cash, AR, AP, and inventory.
• Set and enforce a close deadline. Reconciliation completed three weeks late has little control value — errors compound and adjustments become harder to trace. Best practice is sign-off within five business days of month-end, every time.
• Segregate preparation from review. The preparer and approver must be different people. Same-person sign-off gives auditors nothing to rely on. Build the two-person requirement into your close process permanently.
• Standardise your workpaper template. Inconsistent formats slow review and complicate audit support. One template across all accounts — opening balance, unmatched items, adjustments, sign-off — keeps things clean and consistent.
• Treat recurring exceptions as process signals. If the same account flags unmatched items every month, the root cause needs fixing — not just clearing. Repeating the same workaround twelve months running wastes capacity and masks a real gap.