Subledger to General Ledger Reconciliation: How to Tie Out

Subledger to general ledger reconciliation is the check that the detail supporting an account still adds up to the control balance in the general ledger. You take the closing total of the subledger, such as the accounts payable aging, compare it to the GL control account for the same date, and explain any difference. If the two agree, the detail behind the balance is trustworthy. If they do not, the balance on your financial statements is not supported by anything.

Last updated July 2026.

This is one of the least glamorous reconciliations in the close and one of the most consequential. An unreconciled AP subledger means you do not actually know what you owe, and nobody notices until a vendor calls about an invoice that was paid twice or an auditor asks you to prove the payables balance. What follows is the process, the AP and AR versions specifically, and the short list of things that cause the two sides to drift apart.

What is subledger reconciliation?

Subledger reconciliation is the process of proving that the sum of the individual records in a subsidiary ledger equals the balance of the corresponding control account in the general ledger. A subledger holds transaction-level detail, one line per vendor invoice or per customer invoice. The general ledger holds one summarized balance. Reconciling them confirms nothing was posted to the control account without a corresponding detail record, and nothing sits in the detail that never made it to the ledger.

The relationship is meant to be automatic. In most accounting systems, posting a vendor bill writes both the subledger entry and the GL entry in the same transaction, so they cannot disagree. That is the theory. In practice they do disagree, and the reasons are almost always the small number of ways somebody can write to one side without the other.

What is the difference between a subledger and a general ledger?

The general ledger is the summary: one balance per account, and those balances become your financial statements. A subledger is the supporting detail behind a single GL account, broken out by the dimension that matters for that account. Accounts payable is broken out by vendor and invoice. Accounts receivable is broken out by customer and invoice. Fixed assets is broken out by individual asset.

The GL account that a subledger supports is called the control account. The defining rule is that you should never post directly to a control account. Every movement in it should arrive through the subledger, because a direct journal entry to accounts payable creates a balance with no invoice behind it, and that is exactly the difference you will spend an afternoon hunting for three months later.

Which accounts have subledgers?

The common ones are accounts payable, accounts receivable, fixed assets and accumulated depreciation, inventory, and payroll liabilities. Cash is a slightly different case: the bank statement acts as the external detail rather than an internal subledger, which is why bank reconciliation is treated as its own procedure. Some organizations also run subledgers for prepaid expenses, accrued liabilities, and intercompany balances, usually as schedules maintained outside the accounting system.

That last group is where risk concentrates, because a subledger maintained in a spreadsheet has no enforcement behind it. Nothing stops somebody posting a journal entry to the GL account and forgetting the schedule. The wider version of this problem, proving every balance sheet account rather than just the ones with real subledgers, is covered on our page about balance sheet reconciliation software.

How do you reconcile a subledger to the general ledger?

The process is the same regardless of which subledger you are working on. Six steps.

1. Fix the date and freeze it. Run both reports as of the same period end, and make sure no one is still posting to the period. A subledger report run at 9am against a GL balance pulled at 4pm will disagree for reasons that have nothing to do with an error.
2. Pull the subledger total. For AP, the aging summary. For AR, the customer aging. Take the grand total, not a filtered subset, and check that the report includes zero-balance and credit-balance accounts, because excluding them is a common source of a phantom difference.
3. Pull the GL control account balance. Same date, same entity, same currency.
4. Calculate the difference. If it is zero, document it and move on. If not, note whether the GL is higher or lower than the subledger, because the direction immediately halves the list of possible causes.
5. Find the difference. Start with the fastest test: run the GL account detail and filter for entries whose source is a manual journal rather than the subledger. In most cases the entire difference is sitting right there.
6. Correct and document. Post the correction in the right place, which usually means the subledger rather than the GL, and keep the reconciliation with the reason attached to the period.

Step five is the one that consumes the time, and step six is the one people skip. A reconciliation with no written explanation is a number somebody has to reproduce from scratch next time the question comes up.

What causes a subledger to general ledger difference?

There is a short list, and it accounts for the overwhelming majority of cases.

The last row deserves attention. A difference that is identical month after month is not seven separate problems, it is one problem that happened once and has been carried forward ever since. The efficient move is to work backwards through prior period reconciliations until you find the month it first appears, then investigate only that month. Teams routinely spend an hour a month re-investigating a static difference rather than spending two hours once to kill it.

How do you reconcile the AP subledger to the GL?

Run the AP aging summary as of the period end and compare the total to the accounts payable control account. Then check three things specifically, because AP has its own recurring failure modes.

First, debit balances in AP. A vendor you overpaid or who issued a credit shows as a negative payable. The aging includes it, and if somebody has reclassified debit balances to a receivable account in the GL for presentation, the two sides will differ by exactly that amount, correctly. Document it as a reconciling item rather than chasing it.

Second, invoices received but not entered. These are not a subledger to GL difference at all, since they are in neither, but they surface during the same review and they are the reason an accrual exists. Third, payments in transit: checks written and posted against AP but not yet cleared. Those reduce AP in both places and belong to the bank reconciliation instead.

If a chunk of the AP detail only exists as vendor PDFs that nobody has entered yet, it is worth turning those invoices into a sortable list of amounts and dates before you start ticking, because comparing two sorted columns takes minutes and comparing a report against a folder of paper takes an afternoon.

How do you reconcile the AR subledger to the general ledger?

Same structure, different pitfalls. Run the AR aging and compare it to the receivables control account, then look for the three things that typically break it.

Unapplied cash is first. A customer payment received and recorded but not applied to a specific invoice sits in AR as a credit, and depending on how your system handles it, may or may not appear in the aging. Second is the allowance for doubtful accounts, which lives in the GL as a contra account and has no subledger detail behind it at all, so it must be excluded from the comparison rather than treated as a difference. Third is revenue recognized without an invoice, which belongs in a contract asset account rather than AR, and ends up in the control account when somebody takes a shortcut.

Deposits received against future work are the mirror image and belong in a liability account. If they sit as credit balances in AR, your receivables are understated and your aging is telling you something false about collections.

What is the sub ledger reconciliation process at scale?

Everything above works for one entity and a handful of accounts. It stops working when you have twelve entities, each with AP, AR, fixed assets, inventory, and payroll subledgers, and four working days to close. At that point the constraint is not the arithmetic, it is that the reconciliations are being done by different people at different times using slightly different report parameters, and nobody can see which ones are done until the last day.

The mechanical part, comparing two lists and reporting what does not correspond, is exactly what a transaction matching engine does. Reconciler connects your bank feeds, corporate cards, payment processors, and your ledger read-only, matches transaction-level detail across both sides, and returns a ranked list of what did not tie with a plain English reason attached to every match it did make. Nothing is posted on your behalf, and there is no setting that turns that on.

Worth being straight about the boundary: Reconciler substantiates transaction-backed accounts, meaning cash, corporate cards, clearing and suspense accounts, undeposited funds, and processor receivables. It does not build rollforward schedules for prepaids, accruals, or fixed assets, and it does not run a certification workflow. If your subledger problem is fixed assets or a prepaid schedule, a close platform is the right tool and we are not it.

How often should you reconcile subledgers to the general ledger?

Monthly, as part of the close, for every account with a subledger behind it. AP and AR should be reconciled every period without exception, because they move constantly and they feed working capital decisions. Fixed assets and inventory can reasonably run on a quarterly cycle in a stable business, provided a monthly review confirms nothing unusual posted to the control account.

The one rule worth holding firm on is that a difference should never be carried forward twice. Once an unexplained difference survives a second close, it becomes permanent furniture, and the cost of finding it grows with every period of transactions layered on top. Investigating a $412 difference in the month it appears takes twenty minutes. Investigating the same $412 eleven months later means reading eleven months of activity.

Where to go next

If the control account itself is what you are trying to prove, the broader procedure is in our guide to general ledger reconciliation, and the account-by-account version at close is covered in balance sheet reconciliation. If the difference you are chasing turns out to be sitting in a holding account rather than the subledger, the distinction between a clearing account and a suspense account will tell you which of the two you are looking at and how urgently it needs clearing.

On the software side, discrepancy detection covers what happens to items that never match, and audit trail covers keeping the reasoning attached to the period so a reviewer who was not there can follow it. Teams running this across several entities usually start at multi-entity reconciliation, and if your ledger is NetSuite, NetSuite reconciliation covers how the connection works.