General Ledger Reconciliation: Practical Examples and Best Practices

General ledger reconciliation is one of the highest-leverage controls in finance: it validates that what sits in the general ledger is complete, accurate, and supported by verifiable evidence. When executed consistently, reconciliation reduces the risk of misstatement, surfaces operational issues early (billing gaps, timing differences, duplicate postings), and strengthens confidence in management reporting. Yet, in our experience, many teams still treat it as a monthly checklist rather than a disciplined process tied to materiality, risk, and accountability.

This article provides an end-to-end operating playbook with a detailed general ledger reconciliation example you can adapt to your chart of accounts. If you need a foundational definition and the “why” behind each control, align first on the concepts in our guide on reconciliation principles. From there, we’ll move into practical templates, risk-based scoping, evidence standards, and escalation protocols that hold up under audit scrutiny.

In practice, the strongest reconciliation programs do three things well: they prioritize high-risk accounts, they standardize documentation, and they connect reconciling items to specific owners and resolution dates. We will also address how workflow and tooling decisions impact cycle time—without referencing any specific vendor—so you can choose an approach that fits your team’s maturity and close cadence.

Reconciliation Fundamentals

At its core, a reconciliation compares the balance in a general ledger account to an independent source of truth, then explains any difference with documented reconciling items. Independent sources include subledgers (such as accounts receivable detail), third-party statements (such as bank statements), or system-generated reports controlled outside the GL posting process. The objective is not merely to “make it match,” but to demonstrate why it matches—or, if it doesn’t, what is being done to correct it and by when.

A practical way to think about reconciliations is as three layers of assurance. First, completeness: all transactions that should be recorded are recorded. Second, accuracy: amounts, dates, and classifications are correct. Third, validity: the balance is supported by underlying documentation and business rationale. For example, a prepaid expense balance should map to a schedule of unamortized policies or contracts; an accrual should map to an approved calculation tied to services received.

Account Risk Scoping

Not all accounts deserve the same intensity of reconciliation, and treating them equally often wastes capacity. A professional-grade program scopes accounts based on materiality (size relative to financial statements), susceptibility to error (manual journals, complex estimates), volatility (large month-over-month swings), and fraud risk (cash-like or easily manipulated balances). Many organizations use a tiered approach—high, medium, low—with different frequency and review depth.

A practical scoping model is to reconcile high-risk accounts monthly with documented evidence and supervisory review, medium-risk accounts monthly or quarterly depending on volatility, and low-risk accounts quarterly with analytical review. For example, cash, revenue clearing, payroll liabilities, and intercompany often sit in the high-risk tier, while small fixed recurring accruals may be medium. Keep the scoping decisions documented, and revisit them at least annually or when the business changes (new revenue streams, acquisitions, new payment methods).

Evidence And Standards

The fastest way to create reconciliation rework is unclear standards for support. Define what “good evidence” means: it should be independent, complete, and reproducible. Independent means it is generated from a source not easily altered by the preparer (such as bank statements or system reports with access controls). Complete means it includes the population necessary to support the balance (e.g., full subledger aging, not a filtered view). Reproducible means another person could rerun the report using documented parameters and get the same result.

Standardize the reconciliation package so every account has the same structure: (1) account number and description, (2) GL ending balance, (3) support balance from source, (4) reconciling items with explanations, (5) conclusion and sign-off, and (6) preparer/reviewer names and dates. Include cut-off parameters for reports (as-of date and time), currency (local vs reporting), and any mapping logic (e.g., which subledger statuses are included). This discipline reduces review time because reviewers stop hunting for basics and focus on judgment areas.

Step By Step Process

A repeatable process keeps quality high even when teams are stretched. Step 1: pull the GL trial balance after the posting window closes (or use a controlled “pre-close” snapshot). Step 2: run independent support reports for each account based on defined parameters. Step 3: compare balances, quantify differences, and classify each difference as timing, missing posting, misposting, or unsupported balance. Step 4: propose corrective action—journal entry, subledger fix, or documented timing explanation.

Step 5: document reconciling items with owner and target resolution date; avoid leaving items open without a plan. Step 6: reviewer performs a reasonableness review, focusing on unusual reconciling items, repeated open items, and any adjustments near thresholds. Step 7: finalize the reconciliation package, link or attach evidence, and archive with consistent naming conventions for audit traceability. If you are formalizing approvals and due dates, align the workflow to your close calendar using guidance like our guide on mastering accounting workflow software for financial teams to reduce bottlenecks and late reviews.

Cash Reconciliation Example

Consider a monthly cash account reconciliation, a classic general ledger reconciliation example with clear independent evidence. Assume the GL cash balance is $2,485,200 at month-end. The bank statement ending balance is $2,512,900. The difference is $27,700, which must be explained through reconciling items.

A strong reconciliation might list: outstanding checks of $41,300 (issued and recorded in GL, not yet cleared), deposits in transit of $18,600 (recorded in GL but posted to bank next day), and bank fees of $5,000 (captured on bank statement, not yet recorded in GL). Netting these items: $2,512,900 - $41,300 + $18,600 - $5,000 = $2,485,200, matching the GL. The action is to book a $5,000 bank fee entry in the correct period, and to track outstanding checks over a defined aging threshold (often 90 days) for reissuance or escheatment consideration, in alignment with company policy and jurisdiction rules.

Subledger Tie-Outs

Subledger reconciliations are where operational reality meets financial reporting. A common approach is to reconcile accounts receivable control accounts to the AR aging report as of the same cut-off timestamp and in the same currency. Differences typically arise from timing (cash received but not applied), mapping issues (certain invoice statuses excluded), or manual journals posted directly to the control account.

For instance, suppose the GL AR control is $9,840,000 while the AR aging totals $9,790,000, leaving a $50,000 difference. A clean explanation might be: $35,000 of cash receipts posted to GL but still sitting unapplied in the subledger due to missing remittance details, plus $15,000 of invoices in a pending status excluded from the aging by report logic. The corrective actions are operational: resolve remittance and adjust report parameters or status handling. The reconciliation conclusion should explicitly state whether the AR balance is fairly stated and what will be done to prevent recurrence.

Accruals And Prepaids

Accrual and prepaid accounts often carry the most judgment and the highest risk of “set-and-forget” balances. The best practice is to reconcile them to a rollforward schedule that begins with prior balance, adds current period accruals, subtracts reversals or payments, and ends at the GL balance. The schedule should clearly separate recurring accruals (e.g., utilities) from event-driven items (e.g., legal settlement estimate) and identify who owns each estimate.

A practical scenario: a prepaid insurance account has a GL balance of $360,000. The support schedule shows three annual policies totaling $480,000, with $120,000 amortized year-to-date, leaving $360,000 unamortized—perfect tie-out. If the schedule instead shows $345,000, the $15,000 difference might be a missed amortization entry or a policy renewal recorded in the wrong account. This is where reconciliations protect the P&L: small balance-sheet errors can create recurring expense misstatements for months if not corrected.

Common Reconciliation Breaks

Most reconciliation issues fall into a handful of repeatable patterns. Timing differences are normal but must be bounded and aged; anything still “timing” after one or two cycles deserves scrutiny. Mispostings (wrong account, department, or period) create distorted analytics and can cascade into management KPIs. Missing postings can indicate upstream process failures—unbilled revenue, unrecorded vendor invoices, or incomplete payroll feeds.

Another frequent break is direct posting to control accounts that should be system-controlled (e.g., AR, AP, inventory). Even if the amount is correct, bypassing subledgers breaks audit trails and complicates future tie-outs. Establish clear policy: any direct entries require documented justification, controller approval, and a plan to reclassify or reverse into the appropriate process. Use exception reporting to identify these postings early in the close.

Controls And Governance

A mature reconciliation program is defined by ownership, review, and escalation—not by heroics at month-end. Assign each balance sheet account a named preparer and reviewer, with a documented due date aligned to your close calendar. Set expectations for review depth: reviewers should validate evidence quality, evaluate reconciling item legitimacy, and challenge unusual movements, rather than simply confirming that the spreadsheet foots.

Governance also means managing reconciling items like a backlog. Require each reconciling item to have (1) a reason code, (2) an owner, (3) a dollar amount, (4) a created date, and (5) a target clearance date. Many finance leaders use thresholds such as: no reconciling item over a defined materiality threshold can remain open beyond one close cycle without executive sign-off, and any item aged over 60–90 days triggers an incident review. This turns reconciliations into continuous improvement rather than repetitive documentation.

Automation And Workflow

Automation does not eliminate judgment, but it can eliminate low-value steps: collecting reports, matching transactions, routing approvals, and maintaining audit trails. Start by mapping your reconciliation process and identifying where time is spent—often 30–50% of reconciliation effort is administrative rather than analytical. Then prioritize automation for high-volume matching (cash receipts, bank transactions), standardized templates, and workflow routing.

When assessing tools and process design, focus on controls: role-based access, version control, standardized evidence attachments, and clear approvals. To evaluate approaches without getting lost in features, use a structured framework like our guide on selecting general ledger reconciliation software for finance teams. If your organization relies heavily on a packaged accounting ecosystem, also consider how process design intersects with your platform setup and close sequencing, as discussed in our guides on online accounting packages and streamlining accounting workflows.

Documentation That Audits

Audit-ready documentation is less about volume and more about clarity, traceability, and consistency. Each reconciliation should stand alone: an auditor or internal reviewer should be able to understand what was tested, what evidence was used, and how differences were resolved—without needing verbal explanations. Include report names, parameters, run dates, and the exact population tied to the balance. If you use spreadsheets, protect key formulas and clearly label inputs versus calculated fields.

A useful discipline is the “two-minute test”: could an informed finance professional review the reconciliation and understand the story in two minutes? If not, you likely need a clearer narrative, better organization of reconciling items, or improved evidence. Also document your close cut-offs and posting rules, because many reconciliation disputes are actually cut-off misunderstandings—especially around month-end weekends, global time zones, or batch jobs that post after midnight.

Practical Case Scenario

Imagine a mid-sized services business that closes in 10 business days and has recurring issues with balance sheet accuracy. The controller identifies that 40% of reconciliations are completed after the reporting deadline, and 25% of accounts carry reconciling items older than 90 days. In response, the finance team re-tiers accounts by risk, moving 30 low-risk accounts to quarterly analytical review and reallocating capacity to cash, revenue clearing, payroll liabilities, and deferred revenue.

They also implement a standardized reconciliation cover sheet and reconciling item log. Within two quarters, late reconciliations drop from 40% to under 10%, and aged items over 90 days fall by more than half because each item has an owner and clearance date. The most valuable outcome is qualitative: management reporting improves because the team stops carrying unexplained balances forward. This type of operating cadence is often the difference between a “close that finishes” and a “close you can trust.”

Best Practices

Start with policy and cadence. Document your reconciliation policy (frequency, evidence standards, review requirements, aging limits) and tie it to a close calendar that includes time for review and remediation—not just preparation. Use materiality thoughtfully: a $2,000 variance might be immaterial for the financial statements but material for a specific KPI or business unit budget, so incorporate both external and internal lenses.

Next, design for prevention. Reduce direct postings to control accounts, standardize journal entry support, and use exception reports for unusual transactions such as negative balances, large manual entries, and postings outside normal departments. Finally, invest in reviewer capability: train reviewers to challenge assumptions, verify report logic, and focus on trend and reasonableness checks. A reconciliation program becomes truly efficient when it prevents errors upstream rather than documenting them downstream.

FAQ

General Ledger Reconciliation FAQs

What is a general ledger reconciliation example that auditors accept?
A strong general ledger reconciliation example includes the GL balance, an independent support balance, a clear bridge of reconciling items, and documented evidence with report parameters. It also shows preparer and reviewer sign-off dates and a conclusion that explains whether the balance is fairly stated.

How often should balance sheet accounts be reconciled?
High-risk and material accounts are typically reconciled monthly, while lower-risk accounts may be reconciled quarterly using analytical procedures. The right frequency depends on volatility, judgment, fraud risk, and how quickly errors could become material.

What are the most common causes of unreconciled balances?
The most common drivers are timing differences that are not aged, manual journal mispostings, incomplete subledger processing, and unclear report parameters. Repeated open items often signal a broken upstream process rather than a one-off accounting issue.

How do you manage reconciling items so they don’t linger?
Treat reconciling items like tracked issues: assign an owner, root cause, and target clearance date, and review an aging report during close. Set escalation rules for items exceeding thresholds or aging beyond 60–90 days.

How can workflow improvements shorten reconciliation time?
Standard templates, clear evidence standards, automated routing for approvals, and exception reporting can remove administrative effort and reduce rework. The biggest time savings usually come from preventing errors (controls at entry) rather than accelerating documentation.

Conclusion

A disciplined reconciliation program turns the general ledger into a reliable source of information for decision-making. By scoping accounts based on risk, standardizing evidence, enforcing ownership of reconciling items, and embedding review into the close calendar, finance leaders can reduce late surprises and improve confidence in reporting. The most effective teams use reconciliations to detect process issues early—before they become audit findings or restatements.

If you take only one step, make it this: adopt a consistent template and require every reconciliation to tell a clear story, supported by independent evidence and actionable reconciling items. Use the cash walkthrough above as a repeatable general ledger reconciliation example, then expand the same discipline to subledger tie-outs, accruals, and higher-judgment accounts. Over time, you will build a reconciliation culture that is faster, cleaner, and audit-ready—without sacrificing control.