General ledger reconciliation: Process, worked example, and review rules

General ledger reconciliation is the check that each GL account balance agrees with an independent source, with every difference explained by a dated, documented reconciling item and nothing left unexplained. Teams also call it GL account reconciliation or reconciliation of the general ledger. It's account reconciliation applied to every account in your ledger, including income statement accounts.

• Control accountA GL account that holds the total of a subledger, such as accounts receivable (AR), accounts payable (AP), or fixed assets
• Reconciling itemA specific, documented amount that explains part of the difference between the GL and its support
• SubstantiationProving the balance itself is real and correct with evidence, such as an invoice or calculation behind each accrual line

Skipping it lets errors build up across months, so a small posting mistake becomes a misstatement and a hard cleanup later. Errors are frequent: Gartner surveyed 497 controllership staff in July 2023 and reported on February 21, 2024, that 18% of accountants make financial errors at least daily and 59% make several each month. For companies subject to internal control audits, missing or late reconciliations can be reported as a significant deficiency or a material weakness.

In this general ledger reconciliation example, 10 accounts at October 31, 2026, show seven differences, and every one is explained down to an unexplained difference of zero.

Cash to the bank statement

The bank shows $33,800 more than the books, and three items explain all of it.

The receipts are in the bank but not the books, so they sit on the GL side and need an entry. Deposits in transit and outstanding checks are already in the books but not yet at the bank, so they adjust the bank side and need no entry. For the full method, see bank reconciliation.

Accounts receivable to the AR aging

The AR control account is $28,500 higher than the aging, and two items explain the full amount.

• Unposted batchThe receipts lowered customer balances in the subledger, but the GL entry sat in an unposted batch, so the GL stayed higher. It's the same $21,000 as on the cash reconciliation, and one posting fixes both accounts.
• Manual journalThe tenant isn't a customer in the billing system, so the debit raised the GL with nothing behind it in the aging. It belongs in other receivables.

Prepaid expenses to the amortization schedule

The GL is $15,000 higher than the schedule, so the asset is overstated. The schedule rolls forward from $186,000 at October 1, with no new prepayments, less $15,000 of October amortization on a $180,000 annual insurance policy, to $171,000. The amortization entry never posted.

Equipment and accumulated depreciation to the fixed asset register

The equipment account is $43,200 higher than the register, and here the GL is right. A server bought on AP invoice 88305 posted to 15000 Equipment but was never set up as an asset. Adding it to the register with an October in-service date and a 36-month life brings register cost to $6,523,200.

Under a full-month convention, the register then calculates October depreciation of $1,200 ($43,200 ÷ 36). Register accumulated depreciation becomes $2,194,600, which is $1,200 more than the GL, so the GL needs the depreciation entry.

Accounts payable to the AP aging

The AP control account is $36,600 lower than the aging, so the GL understates what the company owes. Invoices 88412 ($12,400), 88419 ($15,800), and 88427 ($8,400) cover goods received October 29–31 but were entered with a November 1 accounting date.

The aging was run by invoice date, so it included them, while the GL at October 31 didn't. Rerunning the aging by accounting date would make both show $2,914,600, but the goods were received in October, so, with title passing on or before receipt, the liability belongs in October. Changing the accounting date in the AP subledger posts the entry to the GL.

Accrued liabilities, wages, payroll liabilities, and debt

These accounts have no subledger, so each ties to a schedule or a report from outside the GL.

• Accrued liabilitiesThe GL shows $13,800 less owed than the schedule. The schedule includes October legal fees from the law firm's month-end estimate, but the accrual was never booked, so the liability is understated.
• Wages expenseThe GL is $7,200 higher than the register because of JE-2230, the October accrual for a bonus paid in December. The register shows only wages paid, so the item is valid, stays documented, and needs no entry.
• Payroll liabilitiesThe provider's report shows $96,180 of federal withholding and FICA, $18,400 of state withholding, and $27,800 of 401(k) deferrals, a total of $142,380 that matches the GL.
• Term loanThe lender's October statement shows $5,000,000 of principal, which matches the GL.

A GL reconciliation needs a correcting entry only when the ledger is wrong, such as an unposted batch, a misposted manual journal, a missed accrual, or a cutoff error. Timing items that clear on their own need none, and subledger errors get fixed in the subledger.

The example needs six entries, all dated October 31, 2026:

JE 4, JE 5, and JE 6 lower October pre-tax income by $30,000 ($1,200 + $15,000 + $13,800). The other three move amounts between balance sheet accounts. JE 3 also moves the three invoices out of November, so November's AP activity should fall by the same $36,600.

For how accruals, reclasses, and corrections are built and approved, see month-end journal entries.

Which side do you fix: the GL or the subledger?

Fix the record that's wrong, at its source: correct the GL when a posting is missing or misposted there, and correct the subledger when the subledger is incomplete. Fixing the wrong side makes the numbers agree this month and break again next month.

• Fix the GLWhen the subledger is right and the posting never reached the ledger, as with the receipts batch, or when a manual journal hit a control account, as with JE-2215
• Fix the subledgerWhen it's missing the transaction, as with the server. A journal to the GL equipment account would have left the register short and the asset undepreciated.
• Fix the transactionWhen both sides hold it with the wrong date or account, as with the AP invoices. Correct it in the subledger so the subledger posts the change.
• Never plugA balancing entry that forces the difference to zero hides the error and fails review.

Then stop the repeat. Restricting the AR and AP control accounts to subledger postings would have blocked JE-2215 before it posted.

To reconcile the general ledger, close the subledgers, pull each account's balance and its support as of the same date and basis, explain every difference, post corrections, and send the signed workpaper for review. The same eight steps work for every account and serve as your per-account checklist.

1. 1Close the subledgersPost every batch and stop new transactions for the period. Oracle's Cloud ERP guide (Release 26A, December 2025) says to run its reconciliation reports "only after the Receivables and Payables periods are closed to additional subledger transactions."
2. 2Pull the GL balanceTake it from the trial balance as of period end. At year-end, tie the new year's opening balances to the post-closing trial balance.
3. 3Run the support on the same basisUse the same date, entity, currency, and date basis. The AP difference in the example came from an aging run by invoice date instead of accounting date.
4. 4Check the opening balanceIt should equal last period's reconciled ending balance. AccountingTools (March 2026) notes that a break here can trace back several periods if the account went unreconciled.
5. 5Compute the difference and find the causeFor a control account, filter the GL detail by source. Any line that didn't come from the subledger is the first place to look.
6. 6Classify each itemWashington State's Office of Financial Management, in its basic GL reconciliation guide, sorts differences into timing differences, errors, and other items, such as bank fees or rounding, that need further investigation
7. 7Post correctionsRecord correcting entries in the period they belong to, and fix the subledger where the subledger is wrong
8. 8Document and signAttach the support, show an unexplained difference of zero, and send the reconciliation to a reviewer who didn't prepare it

Shorter guides list five steps: gather, compare, investigate, correct, and review. They cover the same work, with the first four steps above merged. In QuickBooks Online, use the Reconcile tool for bank and credit card statements (Intuit's help, updated August 2026). Reconcile every other account by running its general ledger report as of period end and tying it to support in a workpaper.

Differences between the general ledger and a subledger come from postings that reached only one side, such as an unposted batch, a manual journal to a control account, a cutoff mismatch, or a report run too early. Oracle's Cloud ERP guide (December 2025) lists "Manually entered journals that posted to the general ledger account" and "Transactions that don't have complete accounting" among the exceptions its reconciliation reports flag.

Whether the GL is higher or lower tells you where to start. If GL AR is higher than the aging, look for credits that reached only the subledger, such as receipts and credit memos, or debits that reached only the GL, such as manual journals. If your NetSuite AR account doesn't match the A/R Aging report, run both for the same date, subsidiary, and currency before you hunt for errors.

When a difference has carried forward for months, find the last month the account reconciled to zero and compare the difference month by month. A difference that stays the same points to one old item. A difference that grows each month points to a process that keeps breaking, such as an interface that skips one transaction type.

GL to subledger reconciliation compares a control account in the general ledger, such as AR, AP, or fixed assets, with the total of the subledger behind it on the same date. The two should agree, so every difference traces to something specific, usually a posting that reached only one side or a report run on a different date or basis.

Report names come from NetSuite's online help and Oracle's Cloud ERP Release 26A guide (December 2025), checked November 11, 2026. For the GL side, run the account's general ledger detail, or Oracle's Account Analysis Report, so you can filter postings by source. The AR, AP, and equipment accounts in the October example are general ledger to subledger reconciliation examples.

For an account with no subledger, reconcile the balance to an outside statement or to a schedule that rolls forward from last month's reconciled balance and ties each line to an invoice, contract, or calculation. These accounts need the most care, because no system total exists to compare against.

Accrued liabilities take the most judgment. Confirm last month's accruals reversed, and keep the basis for each estimate, such as the law firm's estimate in the example. For schedule mechanics, see prepaid expenses and accrued expenses.

How to reconcile payroll to the general ledger

To reconcile payroll to the general ledger, tie the payroll register's gross wages and employer taxes to the GL expense accounts, net pay to the cash paid, and withholdings and deductions to the liability accounts. The liability accounts should clear when you make the deposits.

Each quarter, tie wages, federal income tax withheld, and Social Security and Medicare taxes to Form 941, the IRS's quarterly federal tax return for employers. State withholding and unemployment taxes tie to their own returns.

A reconciliation account is a general ledger account linked to a subledger, such as customers, vendors, or assets, that updates only from subledger postings, while an ordinary GL account also accepts manual journals. SAP uses the term for its customer, vendor, and asset control accounts.

SAP's ERP 6.0 documentation states, "You cannot post to reconciliation accounts manually." When you post to a subledger account, "the system automatically posts to the corresponding reconciliation account." In SAP, you reconcile by comparing each reconciliation account's balance to the total of its subledger for the same period.

Other ERPs reach the same control with a setting. Oracle's Cloud ERP guide (December 2025) recommends "designating a control account and not allowing other sources to post to them."

A GL reconciliation workpaper shows the account, period end, GL balance, support balance and its source, and each reconciling item with date, amount, cause, and owner, ending in an unexplained difference of zero. It names the preparer and reviewer with dates and attaches the evidence. A GL detail export on its own isn't a reconciliation, because it only repeats what the ledger already says.

Header: Entity, account number and name, period end, support source with the date the report was run, risk tier, preparer and date, and reviewer and date.

Balance block, filled in with the AR account from the example, for a simple Excel general ledger reconciliation template:

Reconciling items, from row 13: date the item arose, description, reference, type (timing, error, or missing entry), amount, side (GL or support), fix or entry number, owner, clear-by date, and age. Calculate age with =$C$4-B13, where C4 holds the period end. Some teams call the finished workpaper a reconciliation statement or reconciliation report, and the contents are the same.

For a ready-made workbook in this layout, for up to 150 accounts, download the free account reconciliation template.

A GL reconciliation is right when each reconciling item sits on the side of the record that's missing it, the adjusted balances match, and the unexplained difference is zero. An item on the wrong side is an easy way to produce a reconciliation that looks finished but doesn't tie.

Then run five checks before you send it for review:

1. 1FootEach column adds to its total
2. 2Cross-footThe GL plus GL-side items equals the adjusted GL, the support plus support-side items equals the adjusted support, and the two match
3. 3Explain the gap in fullIn the example, the cash items net to $33,800 ($21,000 + $48,200 − $35,400), exactly the gap between bank and book
4. 4Balance the entriesTotal debits equal total credits, and each entry changes the account in the direction its item requires
5. 5Watch next monthTiming items should clear on the next statement or subledger run, and any that don't become errors to investigate

Reconcile most general ledger accounts monthly as part of the close, and reconcile cash and other high-volume or high-risk accounts more often. AccountingTools (March 2026) says high-risk or high-volume accounts, such as cash or payroll liabilities, may need weekly or daily reconciliation, and low-activity accounts can be reconciled quarterly with adequate monitoring.

APQC benchmarking data, reported by the finance publication CFO on September 4, 2024, puts the median time for general ledger reconciliation at six hours. Organizations at the 25th percentile take five hours, and those at the 75th percentile take 10. The same article notes that liability and revenue accounts often need tracing back to source documents, which adds time.

At a SaaS company on NetSuite or a similar ERP, deferred revenue, payment processor clearing accounts, and accruals often take the longest, because each ties back to contracts or source files. Track three numbers each close: the share of reconciliations signed by their due date, open items older than 60 days, and reconciliations reopened after sign-off.

A staff or senior accountant prepares each GL reconciliation, and someone who didn't prepare it, usually an accounting manager or the controller, reviews and signs it. Keeping those roles apart turns the reconciliation into a control your auditors can test.

• PreparerPulls the balance and support, lists reconciling items, drafts entries, and signs and dates the workpaper
• ReviewerChecks the support and each item, approves the entries, and signs and dates the workpaper
• ControllerReviews high-risk accounts and approves write-offs and policy exceptions
• Close leadTracks completion against due dates and chases late reconciliations

Before signing, or before an audit, the reviewer confirms:

1. 1The GL balance matches the final trial balance for the right entity and period
2. 2The support is independent of the GL, dated at period end, run on the same basis, and attached
3. 3The opening balance equals last period's reconciled closing balance
4. 4Each reconciling item is specific, documented, on the correct side, and within the aging policy
5. 5Every needed entry is posted and referenced by number, and none is only listed
6. 6The unexplained difference is zero
7. 7The preparer signed and dated it, and the reviewer isn't the preparer

Write the rules down in a reconciliation policy: risk tiers, frequency, due dates by business day, dollar thresholds that trigger extra review (not a size below which a difference can stay unexplained), aging rules, who approves write-offs, and what support each account needs. Back it with system controls: restrict control accounts to subledger postings, lock the accounting period after sign-off, and reopen any reconciliation whose balance changes later. For public companies, these reconciliations are often key controls within the internal control over financial reporting that SOX Section 404 requires management to assess.

Balance sheet reconciliation is a subset of general ledger reconciliation: GL reconciliation covers every account in the ledger, including income statement accounts, while balance sheet reconciliation substantiates only asset, liability, and equity balances at period end.

Income statement accounts need reconciling when they tie to a source report, as wages tie to the payroll register in the example. Review the rest against budget and last month instead of tying each balance. For the balance sheet side in depth, see balance sheet reconciliation.

Start with your ERP's own reports, such as NetSuite's A/R Aging and GL detail or Oracle's Payables and Receivables to Ledger Reconciliation reports, and add reconciliation software when spreadsheets can't keep up. That point usually comes when you need matching, carried-forward items, and sign-off across hundreds of accounts.

When you compare general ledger reconciliation software, check for:

• A direct ERP connectionIt reads GL and subledger balances from your ERP, such as NetSuite or Business Central, without manual exports and posts approved entries back
• Matching rulesHigh-volume accounts, such as cash and clearing accounts, get matched automatically, leaving only exceptions
• Open items carried forwardReconciling items roll to the next period with their age, owner, and evidence
• Workpaper and sign-off in one placePreparer and reviewer sign-off with dates, and support attached to each account
• Cloud access and permissionsRemote reviewers and auditors see the same evidence, with role-based rights

If you run QuickBooks or Xero, bank feeds handle much of cash, but accruals, prepaids, and payroll liabilities still need workpapers. For a comparison of tools, see best account reconciliation software.

Can AI do GL reconciliation?

Yes, AI can prepare most of a general ledger reconciliation: pulling balances, matching transactions, explaining differences, and drafting balanced correcting entries with their support. A person still approves each entry, judges estimates, and signs off, so the AI acts as preparer and never as approver.

The benefit is that your team's time shifts from tick-and-tie to review. Before you trust an AI tool with the ledger, confirm four controls:

• Named approvalA named person approves the exact lines of each entry before it posts
• Rule-based checksDebits equal credits, account codes are valid, and the period is open, checked by rules rather than the model
• EvidenceEvery match and entry is logged with its source documents
• Period lockThe period can't lock until every reconciliation is signed off

Can you outsource general ledger reconciliation?

Yes, you can outsource general ledger reconciliation to a CPA firm, an outsourced accounting firm, or a fractional controller who prepares the reconciliations each month. Keep the final review and sign-off with someone on your own team.

Agree on four things up front:

• DeadlineThe business day each reconciliation is due
• FormatYour workpaper, so reconciliations match from month to month
• EntriesWho drafts and who posts correcting entries
• AccessRead-only access to the GL and subledgers, with posting rights only where needed

Our Close Agent prepares each GL reconciliation on your close checklist, ties every account to its source, and shows each difference with its amount, date, source, and reference. It prepares the balanced correcting entry and workpaper, a named approver approves the exact lines before anything posts, and the month can't lock until every task is signed off. To have that prep done before your team starts the close, explore our Close Agent.