General Ledger Reconciliation: The GL Reconciliation Process, Account by Account

General ledger reconciliation is the check that proves each balance in your general ledger is supported by something outside the ledger. You take the GL balance for an account, compare it to an independent source (a bank statement, a subledger, an amortization schedule, a payroll register), and explain every dollar of difference. An account is reconciled when the difference is zero or fully itemized.

It is the single control that stops a bad number reaching your financial statements, and it is also the part of the close most teams do worst: reconciling everything at the same cadence, keeping the evidence in someone's inbox, and signing off on schedules that agree to themselves rather than to an outside source. Below: the process, which accounts actually need reconciling and how often, the four subledger tie-outs that matter, what the documentation has to contain, and the differences that keep showing up.

What is general ledger reconciliation?

Reconciliation is a two-sided comparison. On one side is the ledger balance: what your accounting system says the account holds at a point in time. On the other is independent evidence: what a third party or a separate detailed record says it should hold. Reconciliation is the work of getting from one to the other and documenting the bridge.

The word "independent" is doing the work in that sentence. A schedule you built by exporting the same ledger you are trying to prove is not evidence, it is a restatement. This is the most common failure in a reconciliation file: a prepaid schedule that ties perfectly to the GL because it was generated from the GL, and would tie just as perfectly if the balance were completely wrong.

Reconciliation is also not the same as review. Review asks whether a number looks reasonable. Reconciliation asks whether it can be proved. A cash balance that has looked reasonable for eleven months can still be off by an uncleared check from March, and only the reconciliation finds it.

General ledger reconciliation vs bank reconciliation vs balance sheet reconciliation

These three terms get used as if they were interchangeable and they are not, though they overlap.

Bank reconciliation is one specific reconciliation: the cash accounts in your ledger against the bank statements. It is the one everybody knows, the one QuickBooks has a dedicated tool for, and the only one with a genuinely external source document. It is a subset of GL reconciliation, not a synonym for it.

Balance sheet reconciliation means reconciling the balance sheet accounts: cash, receivables, payables, prepaids, fixed assets, accrued liabilities, debt, equity. In practice this is what most people mean when they say GL reconciliation, because balance sheet accounts are where errors accumulate. A balance sheet account carries its balance forward forever, so a mistake made in year one is still sitting there in year four until someone reconciles it out.

General ledger reconciliation is the broadest of the three: any GL account reconciled to independent support, including income statement accounts where that makes sense (revenue to a billing system, payroll expense to the payroll provider's register).

Income statement accounts mostly do not need individual reconciliation, and this is where teams waste effort. Revenue and expense accounts reset to zero each year, so errors do not compound the way balance sheet errors do, and a misposting between two expense accounts is usually caught faster by variance review than by a reconciliation. The exceptions are payroll and revenue, both of which have an external record worth tying to.

The general ledger reconciliation process, step by step

1. Close the period first, or at least freeze it. Reconciling a period that is still receiving postings means reconciling twice. Set a closing date in your accounting system before you start, so that a backdated entry cannot quietly invalidate work you have already signed off.

2. Pull the ledger balance and the independent source for the same date. Same day, same accounting basis. A cash-basis GL balance compared to an accrual subledger will produce a difference on every account, and it will not be an error.

3. Compare the totals and calculate the gap. If it is zero, you are done in one step, which is the case for most accounts most months. That is the point of a risk-based approach: the accounts that reconcile instantly should take a minute, not an hour.

4. Itemize every reconciling item. Each difference gets a line: what it is, the dollar amount, the date it arose, and whether it will clear on its own. Outstanding checks and deposits in transit are legitimate timing items and belong here. An unexplained plug does not. If you cannot name the difference, the account is not reconciled, no matter how small the number is.

5. Post the corrections that are real. Bank fees, interest, and NSF items that the bank recorded and you did not are not reconciling items, they are missing journal entries. Reconciling items are timing differences that will resolve themselves; anything else needs an entry.

6. Age the items that carry forward. A deposit in transit dated four days before period end is normal. The same item still open ninety days later is not a timing difference, it is an error nobody has investigated. Most reconciliation failures are visible in the aging of the reconciling items long before they are visible in the balance.

7. Have someone other than the preparer review and sign. Segregation matters most on cash and on any account where the preparer also has the ability to post entries. In a two-person finance team this is usually the controller reviewing the bookkeeper, and it should be documented and dated, not verbal. Teams that formalize this treat each reconciliation as a documented internal control with a named owner and a due date rather than a task somebody remembers to do.

Which accounts to reconcile, and how often

Reconciling every account every month is the most common way a small team turns a three-day close into a ten-day one. The working approach is risk-based: frequency follows volume, volatility, and how much damage a wrong balance would do. Here is a defensible starting policy for a US small or mid-sized business.

A risk-based general ledger reconciliation schedule

Account	Independent source	Frequency	Why
Cash and credit cards	Bank and card statements	Monthly, always	High volume, external source, and the account most exposed to fraud
Accounts receivable	AR aging subledger	Monthly	Direct journal entries to AR break the tie and nothing warns you
Accounts payable	AP aging subledger	Monthly	Same failure mode as AR, plus unrecorded liabilities at period end
Payroll liabilities	Payroll provider register and filings	Monthly	Penalties attach to errors here, and the amounts are objectively knowable
Inventory	Perpetual inventory or count sheets	Monthly if perpetual, otherwise at count	Feeds cost of goods sold, so an error moves gross margin
Prepaid expenses	Amortization schedule built from invoices	Monthly	Small effort, and the schedule is what proves the expense timing
Fixed assets	Fixed asset register and depreciation schedule	Quarterly	Low transaction volume, but disposals get missed for years
Debt and notes payable	Lender amortization schedule	Quarterly	Principal and interest split is routinely posted wrong
Accrued liabilities	Supporting accrual calculation	Monthly	The account auditors test first, because it is where plugs hide
Equity	Roll-forward from prior year	Annually	Little activity, but distributions coded to expense show up here

Two accounts deserve a standing rule rather than a frequency. Suspense and clearing accounts should be zero at every period end, by definition. And holding accounts like Uncategorized Expense, Uncategorized Income and Ask My Accountant should also be zero, because a balance in them means a transaction nobody has classified and your statements are wrong by that amount. Both belong on the month end close checklist before anything else.

General ledger to subledger reconciliation

A subledger is a detailed record that rolls up into a single GL account. The GL says accounts receivable is $412,600; the AR subledger says which 94 invoices make it up. The control account should always equal the sum of its subledger, and when it does not, something bypassed the subledger.

Almost every GL-to-subledger break has the same cause: a manual journal entry posted directly to the control account. Someone books a write-off with a journal entry to Accounts Receivable instead of a credit memo. The balance sheet moves, the aging does not, and the two reports disagree from that day forward with nothing to flag it. The fix is preventive: lock the control accounts so entries have to go through the subledger.

The four subledger reconciliations that matter for most businesses:

AR to the aging. The aging total must equal the GL receivable balance. The four things that break it, and how to find each, are on the AR aging report. Also check that the allowance for doubtful accounts is presented as a contra account, reducing receivables rather than adding to them.

AP to the aging. Same mechanics, mirrored. The extra step at period end is the search for unrecorded liabilities: invoices received after close for goods or services delivered before it. This is the single most common accrual-basis error in small business books, and it flatters both net income and the current ratio.

Cash to the bank. Standard bank reconciliation, with the aging discipline applied to outstanding items. Reconcile every account, including the ones with almost no activity, because a dormant account is where an unauthorized transaction survives longest.

Payroll liabilities to the provider. Accrued wages, employer taxes and withholdings against the provider's register and filed returns. This one is objectively checkable and carries real penalties, so it is worth doing every month even when the balances are small.

What a completed reconciliation should contain

The file, not the number, is the deliverable. A reconciliation that nobody else can follow six months later has not really been performed. At minimum it should show the account and period, the GL balance and where it came from, the independent source balance and where it came from, each reconciling item with a date and an explanation, the resulting difference (which should be zero), and the preparer and reviewer with dates.

Two habits separate files that survive an audit from files that do not. Attach the source document rather than referencing it, because a bank statement that lives in a portal will not be retrievable on the same terms in three years. And write the explanation for a reader who was not there. "Timing" is not an explanation. "Check 4471 to Anderson Supply, issued 12/29, cleared 1/6" is.

When a CPA firm picks the file up for a compilation or review, this is the first thing they ask for, and the quality of it decides how much of your fee goes on their cleanup rather than their work. What the firm is required to do at each service level is on compilation vs review vs audit.

Differences that keep showing up

Timing, which is not an error. Outstanding checks, deposits in transit, and payments in flight at period end. These belong on the reconciliation as itemized reconciling items and clear on their own. Age them anyway.

Transactions the other side recorded and you did not. Bank fees, interest earned, merchant processor deductions, NSF returns and automatic transfers. These are missing entries, not reconciling items, and they need to be posted.

Duplicates. An invoice entered twice, a payment applied twice, or a bank feed importing a transaction that was also entered manually. The last of these is the most frequent cause of a cash difference in a QuickBooks file with an active feed.

Transposition. A difference divisible by 9 is a transposed digit almost every time. $540 out, check for 4,671 entered as 4,617. It is a cheap first test before searching transaction by transaction.

Entries in a closed period. Without a closing date and password, a backdated transaction changes a period you already reported and reconciled. The statement you sent your lender last quarter no longer matches what your file produces today, and nothing alerts you. This is worth fixing once as a setting rather than repeatedly as a surprise.

Retained earnings that will not tie. QuickBooks calculates retained earnings at report time rather than posting to it, so the account does not behave like the rest of the ledger. What to check is on why QuickBooks retained earnings is incorrect.

How reconciliation connects to the statements

Reconciliation proves the balances. The statements present them. Between the two sits the summarization step: the ledger collapses to one closing balance per account, which is the trial balance, and each account is then assigned to the statement caption it reports under. The detail behind all of it is the ledger itself, which you can pull as the QuickBooks general ledger report.

The reason the order matters is that an unreconciled account produces a statement that looks perfectly normal. A balance sheet balances whether or not the cash figure is right, because both sides were built from the same ledger. Nothing in the presentation reveals an unreconciled account, which is exactly why the reconciliation has to happen before the pack goes out rather than after someone questions it.

Once the balances are proved, producing the pack is mechanical. AIStatements takes the QuickBooks, Xero or CSV export, summarizes it, maps every account to a caption, reconciles the mapped total back to the trial balance total so nothing drops out silently, and produces the balance sheet, income statement and cash flow statement from one map, with the ratio analysis and red flags written alongside. The mapping method itself is on trial balance mapping, and the full path from a ledger export to a finished pack is on general ledger to financial statements, with the QuickBooks-specific route on QuickBooks general ledger to financial statements. If you are weighing whether to buy a tool for the proving step rather than the reporting step, the shortlist and what each vendor publishes is in general ledger reconciliation software compared.

AIStatements is software that formats and analyzes the data you provide. It is not accounting, audit or tax advice, it is not a CPA, and it does not guarantee GAAP compliance. Anything you file or send to a lender should be reviewed by a licensed professional.