What is the point of a subledger?
A subledger keeps the detail that explains one balance in the general ledger. The general ledger gives the close team a classified view by account. A subledger retains the invoices, receipts, payments, quantities or other transaction details behind one part of that view. This split supports scale: teams can review customers, suppliers, inventory or assets at the level where differences arise, then compare the detail with the control balance.
The relationship is a control, not an assumption that two reports agree. A balance may differ because of timing, an omitted posting, a mapping choice, currency treatment or a duplicate. The subledger helps locate the underlying item; the general ledger shows the amount carried into the financial statements. The applicable accounting process determines what to post or adjust.
Common types of subledgers
Organizations create a subledger wherever a single general ledger balance hides many individual items that need to be tracked one by one. The most common are:
- Accounts receivable, with open invoices, credit memos and payments by customer, behind the Accounts Receivable control account.
- Accounts payable, with vendor bills and payments by supplier, behind the Accounts Payable control account.
- Fixed assets, with cost, depreciation and disposals by asset.
- Inventory, with quantities and costs by item or location.
- Payments and customer balances in fintech and banking operations, where each payment, refund, fee or wallet movement needs its own record.
How to reconcile a subledger to the general ledger
- Define the population. Choose the control account, entity, period, currency, source and detail grain. State whether the population is invoices, customer balances, vendor bills, inventory movements or another documented set.
- Total the signed detail. Add the detail using the same sign convention and period basis as the control balance. Keep debit and credit movements visible so the total can be traced to the underlying entries.
- Compare the balances. Compare the subledger total with the general-ledger control account. If both are USD 40,000, the amounts tie for the selected scope. If they differ, record the amount and direction of the variance before investigating.
- Investigate and document. Trace the difference to a source document, posting date, mapping, duplicate, reversal or unresolved exception. Retain the reports and support, assign a reviewer and let the accounting team decide whether a correction is appropriate.
This comparison is one form of general ledger reconciliation: the control account is checked against the detailed record that is supposed to explain it, usually as part of the month-end close.
Subledger example: customer balances and accounts receivable
Assume an accounts receivable subledger lists Customer A at USD 18,400, Customer B at USD 9,600 and Customer C at USD 12,000. The detail totals USD 40,000. The general-ledger accounts receivable control account is also USD 40,000 at close, so the selected population agrees.
At a later reporting cutoff, a USD 2,000 credit memo is posted in the subledger for Customer B but has not transferred to the general ledger. The subledger total becomes USD 38,000 while the control account remains USD 40,000.
| Item | First cutoff (USD) | Later cutoff (USD) |
|---|---|---|
| Customer A | 18,400 | 18,400 |
| Customer B | 9,600 | 7,600 |
| Customer C | 12,000 | 12,000 |
| Subledger total | 40,000 | 38,000 |
| General ledger control account | 40,000 | 40,000 |
| Difference | 0 | 2,000 |
The variance is USD 2,000, with the detail lower than the control balance. That identifies a timing or transfer exception, not proof that the customer balance is wrong. Review the document, posting status and cutoff before the accounting team chooses an action.
For an illustrative invoice, the journal entry may debit Accounts Receivable and credit Revenue; a later customer payment may debit Cash and credit Accounts Receivable. The exact accounts, dimensions and posting timing depend on the transaction and the organization’s accounting process.
Subledger vs. general ledger: key differences
| Criterion | Subledger | General ledger |
|---|---|---|
| Scope | One area, such as customers, suppliers or fixed assets | Every account of the entity |
| Level of detail | Individual invoices, payments, assets or items | Postings and balances by account, in detail or in summary depending on the design |
| Main use | Explaining and managing one balance item by item | Producing the trial balance and financial statements |
| Link between them | Its total supports a control account | The control account carries the balance that the subledger must explain |
Subledger and subsidiary ledger often name the same kind of detailed record. A subledger can be maintained as an ERP module, a separate system, a report or a controlled schedule, depending on the design. Entries may reach the general ledger in detail or in summary according to the system setup. What makes the subledger useful is the defined relationship to a control account, population and period.
A detail export is not automatically a formal subledger. The team should identify which transactions belong in the population, how signs are handled and when the detail is expected to agree with the control account. Those choices make a reconciliation review reproducible, and they are the groundwork of preparing source data before any comparison.
What is a modern subledger?
A modern subledger, sometimes called an enterprise or accounting subledger, is a layer that records high-volume transaction data from operational systems, applies accounting logic and sends the resulting entries to the general ledger. Payment companies, banks and marketplaces often adopt this architecture when posting every payment, refund, fee or account movement one by one would make the general ledger hard to maintain and review. The design does not change the control principle: the entries that reach the general ledger still have to agree with the detail that produced them, and the accounting policy still belongs to the finance team.
Evidence for a subledger review
Keep the source population, extraction date, account mapping, signed total, general-ledger report, reconciliation and exception log together. The record should show the period and scope, the reason for each variance and who prepared, reviewed or certified the work. A clear evidence trail helps the next reviewer follow the balance without rebuilding the analysis.
How Simetrik supports subledger reconciliation
Simetrik, an AI-native financial control platform, works on the transaction and operational data that subledgers are built from: bank, processor and internal system records brought in through its no-code integrations. Its deterministic engine reconciles those records with configured rules before they feed the ledger, so a refund recorded on one side only or a settlement that arrives short because of fees stays open for review instead of surfacing later as an unexplained variance. With accounting automation from reconciled data, Simetrik can generate journal entries from verified results, validate each entry before it syncs to the ERP and reprocess errors with a full trail.
For the balance itself, Simetrik can support a subledger review by comparing the recorded control-account balance with the detailed subledger total and supporting evidence for the period. Its account certification workflows assign a preparer and a certifier to each account and keep traceability around configured controls. The accounting team decides the mapping, review criteria and treatment of exceptions.