Try it now, capture a real invoice
Free plan · No credit card · Your data stays yours
General ledger reconciliation is the process of proving that the balance in each general ledger account is supported by independent evidence: a bank statement, a subledger total, an amortization schedule, or a signed contract. You are not checking that the ledger adds up. You are checking that it is true. An account reconciles when the GL balance equals the supporting detail and every difference is explained and documented.
What is general ledger reconciliation?
Every month, the ledger says accounts payable is $842,317. Reconciliation asks: prove it. You pull the AP subledger aging, total the open invoices, and see whether it equals $842,317. If it does, the account is reconciled and you sign it off. If it says $839,902, you have a $2,415 difference, and finding it is the job.
The distinction that matters: a balanced ledger is not a reconciled ledger. Double-entry bookkeeping guarantees debits equal credits, so the trial balance always balances, even when it is completely wrong. Reconciliation is the only step that catches a payment posted to the wrong account, a duplicate journal entry, or an invoice booked twice under two vendor records.
Which accounts need reconciling?
Not all of them, and controllers who try to reconcile every account monthly burn their team out for nothing. Reconcile every balance sheet account. Income statement accounts get reviewed for reasonableness, not reconciled, because their support is the transactions themselves.
| Account | Reconciled against | Risk if you skip it |
|---|---|---|
| Cash | Bank statement | Unrecorded fees, fraud, checks that never cleared |
| Accounts receivable | AR aging subledger | Revenue overstated, collections chasing invoices already paid |
| Accounts payable | AP aging subledger | Liabilities understated, duplicate payments hidden |
| Accrued liabilities | Accrual schedule | Expenses land in the wrong period |
| GRNI clearing | Received-not-invoiced report | A growing balance nobody owns, which is where errors go to hide |
| Prepaid expenses | Amortization schedule | Expense recognized too early or never |
| Fixed assets | Fixed asset register | Depreciation wrong, assets on the books that were scrapped |
| Payroll liabilities | Payroll provider reports | Tax remittance errors, which carry penalties |
| Intercompany | The other entity's ledger | Consolidation does not eliminate, and the auditors will find it |
The general ledger reconciliation process, step by step
- Close the subledgers first. Stop posting to AP, AR, and payroll before you reconcile. Reconciling against a moving target is how people spend a day chasing a difference that was a colleague still keying invoices.
- Pull the GL balance. Take the ending balance for the account, for the period, straight from the trial balance.
- Pull the independent support. The bank statement, the subledger aging, the schedule. Independent is the operative word: a report generated from the same ledger you are trying to prove is not evidence.
- Compare and list the differences. Not the net difference, the individual items. A $0 net difference can hide a $50,000 error offsetting a $50,000 error, and that happens more often than anyone likes to admit.
- Explain each reconciling item. A check written but not yet cleared is a legitimate reconciling item. A $2,415 difference nobody can explain is not: it is an error you have not found yet.
- Post correcting entries. Fix the ledger, do not fix the reconciliation. Plugging a difference to make the schedule tie is the classic sin, and it compounds every month afterward.
- Get it reviewed and signed. Preparer and reviewer must be different people. An unreviewed reconciliation is not a control, and every audit and SOX framework treats it that way.
General ledger reconciliation example: accounts payable
Say the GL shows AP at $842,317 and the AP aging totals $839,902. The difference is $2,415. Work it in this order:
| Check | What you are looking for | Typical finding |
|---|---|---|
| Manual journals to the AP control account | Any journal entry posted directly to 2000, not through the subledger | Someone accrued an expense straight to AP instead of accrued liabilities. This is the number one cause |
| Timing | Invoices entered after the cutoff, payments posted in a different period | An invoice dated the 30th, keyed on the 2nd, sitting in the wrong month |
| Voids and credits | A voided check or credit memo applied in one system and not the other | A vendor credit recorded against the invoice but never posted to the GL |
| Currency | Revaluation of foreign-currency payables | The subledger holds transaction currency, the GL holds functional currency after revaluation |
| Duplicates | The same invoice booked under two vendor records | Two records for the same supplier, both open. See duplicate invoice payments |
In practice the manual journal is the culprit maybe half the time. The AP control account should be fed exclusively by the AP subledger, and every direct posting to it guarantees the two will never agree again until someone unwinds it. Lock that account down against manual journals in the ERP, and this reconciliation goes from an afternoon to ten minutes.
Bank reconciliation, and why it is the one people dread
Cash is reconciled against the bank statement, and it is the account where errors surface first because the bank is a genuinely independent third party. The mechanics are straightforward: start with the bank balance, add deposits in transit, subtract outstanding checks, and compare to the GL cash balance.
The pain is almost always data entry. Someone is retyping a PDF bank statement into a spreadsheet, line by line, so they can match it against the ledger. That is a solved problem: pull the statement and convert it into a file your accounting system imports directly, then match. The reconciliation itself takes twenty minutes. The retyping used to take three hours and introduced the errors you then spent another hour hunting.
Watch for stale-dated checks here too. A check outstanding for eight months is not really outstanding, it is an escheatment question, and leaving it on the reconciliation forever is how outstanding-check lists grow to 300 lines nobody reads.
General ledger reconciliation checklist
Hand this to the team at close:
- Subledgers closed and locked before reconciliation starts
- Every balance sheet account has a named owner and a due date
- Support attached to the reconciliation, not referenced in a folder someone has to go find
- Reconciling items listed individually, each with an explanation and an expected clearing date
- No unexplained difference above the materiality threshold your controller set (set one, in writing)
- Aged reconciling items escalated: anything sitting unresolved for two months is an error, not an item
- Preparer and reviewer are different people, both recorded with a date
- Correcting entries posted to the ledger, never plugged into the schedule
That last pair are what a SOX tester samples for. If your company is subject to SOX compliance, an unreviewed account reconciliation is a control deficiency on its own, regardless of whether the numbers happened to be right.
How to make reconciliation take an hour instead of a week
The teams that close fast are not working harder in the last five days. They removed the errors that make reconciliation slow:
- Ban manual journals to control accounts. AP, AR, and inventory control accounts get fed by their subledgers, full stop. This single rule eliminates most AP reconciliation differences.
- Enforce a hard cutoff. Invoices received after the cutoff belong to next month, with an accrual if material. A soft cutoff means the subledger keeps moving while you reconcile it.
- Automate invoice capture and coding. Miskeyed amounts and wrong GL accounts are the raw material of every reconciling item. If invoices are read, coded, and posted automatically, the errors never enter the ledger in the first place, which is the only reliable way to shorten the close. See accounts payable software and our accounts payable month-end close guide.
- Reconcile the volatile accounts weekly. Cash and GRNI, at minimum. Finding a difference in week one is a five-minute conversation. Finding it on day four of close is a crisis.
Reconciliation exists to prove the numbers are true. The faster it is, the fewer things went wrong upstream, and that is the only meaningful measure of an accounting operation.