What GL reconciliation means and why it matters
GL reconciliation, also written G/L reconciliation or general ledger account reconciliation, answers one question: does a general ledger account agree with the detail that is supposed to support it for the same period? The test covers the opening balance, the activity posted during the period and the closing balance, not only the final total.
Accounts receivable and accounts payable subledgers contain transaction-level detail, while their GL control accounts summarize that activity. Reconciliation tests whether both views cover the same entity, period, currency, accounts, and transaction population. A difference is a signal to investigate, not automatic proof that an accounting entry is wrong.
How to reconcile general ledger accounts, step by step
The general ledger reconciliation process runs in four steps for each account in scope, usually as part of the period close.
- Define a common scope. Select the entity, period, currency, GL control account, subledger, cutoff, and included transaction population. Both sides must use comparable boundaries.
- Compare balances and activity. Compare beginning balances, period debits and credits, and ending balances. Retain the detail needed to trace a total back to transactions or journals.
- Investigate each difference. Check for unaccounted transactions, excluded accounts, outside journals, untransferred or unposted activity, mapping errors, and legitimate timing or report-scope differences.
- Resolve and review. Correct real errors through the approved process, document valid reconciling items, and obtain the required review. Do not use an unsupported balancing entry to hide a variance.
A reliable comparison starts with the reports themselves. Retain the extraction time, account range, posting status, and currency basis alongside each file. A report containing only posted journals cannot be compared as though it includes every transaction entered in a subledger. These details let a reviewer reproduce the comparison instead of relying on a total copied into a worksheet.
The relationship between accounts also needs to be explicit. If several auxiliary accounts feed one control account, the supporting population must include all of them within the agreed scope. A missing mapping can create an apparent shortage even when the underlying entries are correct.
General ledger reconciliation example
At month-end, an accounts payable subledger shows $482,000, while the corresponding GL control account shows $476,500. Comparing the activity, not just the totals, shows where the gap forms. Accounts payable is a liability, so new invoices are credits and payments are debits.
| Line | AP subledger | GL control account | Difference |
|---|---|---|---|
| Beginning balance | $451,200 | $451,200 | $0 |
| Invoices recorded (credits) | $318,300 | $312,800 | $5,500 |
| Payments (debits) | $287,500 | $287,500 | $0 |
| Ending balance | $482,000 | $476,500 | $5,500 |
The $5,500 difference sits entirely in the invoice line. It is traced to a supplier invoice recorded in AP whose journal was not yet transferred and posted to the GL at the reporting cutoff. The documented timing bridge is $476,500 plus $5,500, which equals the $482,000 subledger balance. After the valid journal is posted, the GL balance becomes $482,000 and the difference is $0.
The $5,500 bridge explains the difference at the original cutoff; it does not prove that posting subsequently succeeded. The reviewer needs the invoice reference, the corresponding journal, and evidence of its posting status. Repeating the comparison after posting confirms whether the same item cleared. If another difference appears, it requires its own explanation rather than being absorbed into the original timing item.
Does every GL difference require an adjustment?
No. A difference may result from timing, an excluded account range, a different entity or currency filter, or activity that has not transferred or posted. The reconciliation should bridge a valid scope difference with evidence. An adjusting entry requires an identified accounting error, supporting evidence, and the appropriate approval.
| Type of difference | How it shows up | Adjusting entry? |
|---|---|---|
| Timing or unposted activity | An item exists in the subledger but its journal had not reached the GL at the cutoff, as in the example. | No. Document the item and confirm that the posting clears it. |
| Report scope | The two reports use a different entity, currency, account range or posting status. | No. Rerun the comparison on matching boundaries. |
| Missing account mapping | An auxiliary account that feeds the control account was left out of the supporting population. | No. Correct the mapping and compare again. |
| Journal posted outside the subledger | A manual entry hits the control account directly and has no subledger detail behind it. | Only if the entry is invalid. A valid one is documented as a reconciling item under the policy. |
| Posting error | A duplicate, a wrong amount or an entry booked to the wrong account. | Yes, a correcting or reclassification entry with support and approval. |
A useful reconciliation record gives each unresolved item a specific cause, supporting reference, responsible person, and next action. Labeling a difference as timing is only a working conclusion until the expected event can be checked. When an item remains open into another period, the next review should establish whether that explanation still holds and whether escalation is needed under the organization’s policy. Documented account reconciliation best practices set those escalation points in advance.
Likewise, an equal ending balance alone does not demonstrate that all activity is correct. Reviewing beginning balances and period movements helps test how the closing total was formed. The objective is a supported conclusion about the defined account population, with a clear trail from totals to records and any approved correction.
What a GL reconciliation statement should show
A GL reconciliation statement, or reconciliation report, is the record a reviewer signs off. For each account it shows the account number and name, the period and cutoff, the GL balance, the supporting balance and its source, and the difference between them. It then lists each reconciling item with its amount, cause, reference, owner and expected clearing date, states the unexplained difference, which should be zero before sign-off, and records the preparer, the reviewer and their dates.
GL reconciliation vs. balance sheet and bank reconciliation
| Criterion | GL reconciliation | Balance sheet reconciliation | Bank reconciliation |
|---|---|---|---|
| Question it answers | Does the GL account agree with its subledger or detail for the period? | Is each closing balance supported by evidence at the reporting date? | Does the book cash balance agree with the bank statement? |
| Accounts in scope | Any GL account, including control accounts and income statement accounts | Asset, liability and equity accounts | Cash and bank accounts |
| What is compared | Beginning balance, period activity and ending balance | The closing balance and its composition | Book entries and statement lines, item by item |
| Typical support | Subledger reports and journal detail | Subledgers, schedules, confirmations and statements | The bank statement |
The terms overlap in practice. A balance sheet reconciliation asks whether each closing balance is supported at a date, while GL reconciliation asks whether the ledger and its detail tell the same story across the period. A bank reconciliation is the cash case of both, so stating the account population, date and source of support matters more than the label.
How Simetrik supports general ledger reconciliation
Simetrik is an AI-native financial control platform that works below the ledger, on the transaction and operational data from banks, processors and internal systems. Many GL differences begin as a single transaction that one record has and the other lacks: a refund recorded on one side only, a settlement that arrives short because of fees, or a chargeback that reverses a sale weeks later. Simetrik’s deterministic engine applies configured matching rules to those records, so the difference is found at the transaction level, where it is faster and more traceable to resolve than as an unexplained gap between two balances.
For entries generated in Simetrik, each posting is validated before it syncs with the ERP, and errors are handled and reprocessed with a trail from transaction to entry to ERP. A journal like the one in the example is then tracked through its posting lifecycle instead of surfacing only as a month-end difference.
For balances, Simetrik can organize ERP balances and supporting evidence by account and period, surface variances, and assign preparation and review responsibilities. A preparer documents the evidence and marks the account Prepared, and a certifier reviews and signs it, within its account reconciliation and certification workflow. These journal entry and account certification controls keep the comparison and its explanation together. Finance teams define the source population, account mappings, comparison rules, and approval criteria.