A sub-ledger is a subsidiary accounting record that holds the transaction-level detail behind a single General Ledger control account. The AR sub-ledger, for example, stores every open invoice, payment, credit memo, and write-off by customer, and its balance must reconcile to the AR control account in the GL.
A sub-ledger is a subsidiary accounting record that captures the transaction-level detail behind a single control account in the General Ledger. Where the GL summarizes financial activity at the account level (one balance for Accounts Receivable, one for Accounts Payable, one for Inventory) the sub-ledger holds every underlying transaction that rolls up into that balance. The GL answers "how much do customers owe us in total?" The sub-ledger answers "which customers, on which invoices, due on which dates?"
Sub-ledgers exist because the GL would collapse under its own weight if every line-item transaction posted at the customer, supplier, or asset level. A mid-market company processing 10,000 invoices a month does not want 10,000 GL entries, it wants one AR control account balance that ties cleanly to a sub-ledger containing the full detail. The sub-ledger gives finance teams the drill-down they need for operations and audit without bloating the GL or breaking the trial balance.
Structurally, each sub-ledger maps to one or more GL control accounts. The sub-ledger's running total must equal the GL control account balance at any point in time. When the two diverge, the period cannot close cleanly until the break is identified and corrected.
Most ERPs maintain a standard set of sub-ledgers, each tied to one or more GL control accounts:
Each of these supports a distinct operational workflow. Collections cannot run off the GL; it needs the AR sub-ledger. Procurement cannot pay suppliers from a single AP control balance; it needs the AP sub-ledger. The sub-ledger is where finance operations actually live.
For an AR or collections team, the AR sub-ledger is the system of record. It contains every open invoice, every partial payment, every credit memo, every dispute deduction, and every write-off, all attached to a customer master record. From this single dataset the team derives:
Every operational AR metric (DSO, CEI, bad-debt ratio, dispute cycle time) is calculated from sub-ledger data, not from the GL. The GL gives auditors a clean balance; the sub-ledger gives operators something they can actually work.
The cardinal rule: sub-ledger totals must equal the GL control account balance. Most teams reconcile monthly as part of the close, though leading organizations do it daily. Three categories of breaks dominate:
Period close is sequential: the sub-ledger closes first, the reconciliation runs, and only then can the GL close. A messy AR sub-ledger is one of the most common reasons a close runs long.
Historically, sub-ledgers operated in batch: transactions accumulated through the day or month and posted to the GL on a schedule. That model survives in many older ERPs and is the root cause of the "month-end fire drill" most controllers know well. Modern systems increasingly offer real-time posting: every sub-ledger transaction flows to the GL the moment it is recorded, and reconciliation becomes a continuous control rather than a periodic project.
Real-time sub-ledgers change the operating cadence of finance. Cash applied this morning is visible in the GL this afternoon. Disputes raised today are reflected in aging tonight. The close shortens because there is no backlog to clear, the reconciliation has been happening all month.
AI-native finance platforms treat sub-ledger-to-GL reconciliation as a continuous, automated control rather than a monthly accountant task. Three capabilities matter:
For AR teams, the result is a sub-ledger that is always reconciled, always operations-ready, and always audit-defensible, which means the close compresses and the team spends its time on cash, not on cleanup.
The General Ledger holds summary balances by account: one number for total Accounts Receivable, one for total inventory, and so on. A sub-ledger holds the transaction-level detail behind a single GL control account. The AR sub-ledger, for example, lists every open invoice by customer, and its total must equal the AR balance in the GL.
Without sub-ledgers, every customer invoice or supplier bill would post directly to the GL, making the GL impossibly detailed and the trial balance unmanageable. Sub-ledgers let finance teams drill into transaction-level detail for operations and audit while keeping the GL clean and summarized.
The standard set includes Accounts Receivable, Accounts Payable, inventory, fixed assets, and payroll. Each ties to one or more GL control accounts and supports the operational workflows that the GL itself cannot, collections, supplier payment, depreciation schedules, and so on.
At minimum monthly, as part of the period close. Leading finance teams reconcile daily, and AI-native platforms reconcile continuously. The longer reconciliation is deferred, the harder breaks are to investigate because the underlying transactions become harder to trace.
Three causes dominate: timing differences at period cutoff, manual journal entries posted directly to the GL control account without a matching sub-ledger entry, and sub-ledger transactions that fail to flow to the GL because of interface errors or chart-of-accounts mapping problems.
The sub-ledger closes first. Once the AR sub-ledger is closed and reconciled to the AR control account, the GL can be closed for the period. Trying to close the GL before the sub-ledger is reconciled is one of the most common reasons month-end runs late.
