Subledger

Subledger meaning in accounting: the transaction-level detail behind a general ledger balance, and why it matters for contract audits. Read the full guide.

Twitter LinkedIn WhatsApp
Ask AI: ChatGPT Claude Gemini Grok
Subledger

A subledger is a detailed accounting record that holds the individual transactions behind a single general ledger balance, such as accounts payable or accounts receivable. Finance teams use it every day without naming it: it is the vendor-by-vendor, invoice-by-invoice detail that a general ledger total summarizes but does not show. For a margin drift review, the subledger is where the audit actually happens, because the general ledger only shows a number and the subledger shows the invoice.

1. What is a subledger?

A subledger is a detailed ledger that records every individual transaction rolling up into one general ledger control account. The accounts payable subledger, for example, holds every vendor invoice, credit memo and payment. The general ledger shows the total balance owed to vendors; the subledger shows which vendor, which invoice, which purchase order and which amount make up that total.

Most ERPs maintain several subledgers at once: accounts payable, accounts receivable, fixed assets, inventory. Each feeds a single control account in the general ledger.

2. How does a subledger differ from the general ledger?

The general ledger holds summary balances by account, updated as subledger activity posts to it. The subledger holds the transaction detail that produced that balance. A controller reading the general ledger sees one accounts payable figure; reading the subledger, they see every open invoice by vendor, due date and amount that adds up to it.

The two should always reconcile. A mismatch signals a posting error or a timing gap that needs resolution before the balance can be trusted.

3. Why does subledger detail matter for a contract compliance audit?

A contract compliance audit checks invoice lines against a rate card, a volume tier or a not-to-exceed cap. That check needs line-level detail: vendor, invoice number, purchase order, unit price, quantity. The general ledger cannot supply it because it only carries a posted total. The subledger is the only place that detail exists in the system of record.

Pulling clean subledger extracts by vendor and date range is usually the first working step in any audit of this kind, before any comparison against contract terms begins.

4. What does a subledger export typically include?

A usable subledger export includes the invoice number, vendor ID, purchase order reference, line-level amount, quantity, unit price and posting date. Without all of these fields, matching an invoice back to a contract rate or a volume tier is not possible, because the comparison requires the same level of detail on both sides.

Missing fields are a common early blocker in an audit and are worth confirming before an extract is treated as complete.

  • Invoice and PO number: Ties the transaction to the order that authorized it.
  • Vendor identifier: Groups transactions for rate card and tier comparison.
  • Line amount and quantity: Lets a unit price be recalculated and checked.
  • Posting date: Places the transaction in the correct contract period.

For the wider pattern this sits inside, start with the margin drift guide. See also margin drift vs. legitimate price increases: how to tell them apart and accessorial charge audit: the surcharges nobody validates.

5. Frequently Asked Questions (People Also Ask)

Is a subledger the same as the general ledger?

No. The general ledger holds summary balances by account. A subledger holds the transaction detail behind one of those balances, such as every open vendor invoice behind the accounts payable account. The general ledger total should reconcile back to the sum of its subledgers.

What is the accounts payable subledger used for?

It stores every vendor invoice, credit memo and payment, tied to a purchase order and vendor record. AP teams use it to track open balances by vendor and to support the audit trail a contract compliance review depends on.

Why does subledger detail matter for a contract compliance audit?

A contract compliance audit checks invoice lines against rate cards, tiers and caps. The general ledger only shows a posted total. The subledger holds the line-level detail, vendor, PO and date, needed to run that check at all.

Can subledger data be exported for an audit?

Most ERPs support an export of subledger detail by vendor, date range and account. The export should include invoice number, PO reference, line amount and posting date, the minimum detail needed to match against a contract.

What happens when the subledger and general ledger do not reconcile?

An unreconciled subledger points to a posting error, a timing difference, or a transaction recorded in one ledger and not the other. It has to be resolved before the balance can be trusted for reporting or for an audit.

Does every ERP call it a subledger?

The concept is standard across ERPs even where the label varies. Some systems call it a sub-ledger module or a vendor detail table, but the function is the same: transaction-level detail rolling up to a general ledger control account.

1. What is a subledger?

A subledger is a detailed ledger that records every individual transaction rolling up into one general ledger control account. The accounts payable subledger, for example, holds every vendor invoice, credit memo and payment. The general ledger shows the total balance owed to vendors; the subledger shows which vendor, which invoice, which purchase order and which amount make up that total. Most ERPs maintain several subledgers at once: accounts payable, accounts receivable, fixed assets, inventory. Each feeds a single control account in the general ledger.

2. How does a subledger differ from the general ledger?

The general ledger holds summary balances by account, updated as subledger activity posts to it. The subledger holds the transaction detail that produced that balance. A controller reading the general ledger sees one accounts payable figure; reading the subledger, they see every open invoice by vendor, due date and amount that adds up to it. The two should always reconcile. A mismatch signals a posting error or a timing gap that needs resolution before the balance can be trusted.

3. Why does subledger detail matter for a contract compliance audit?

A contract compliance audit checks invoice lines against a rate card, a volume tier or a not-to-exceed cap. That check needs line-level detail: vendor, invoice number, purchase order, unit price, quantity. The general ledger cannot supply it because it only carries a posted total. The subledger is the only place that detail exists in the system of record. Pulling clean subledger extracts by vendor and date range is usually the first working step in any audit of this kind, before any comparison against contract terms begins.

4. What does a subledger export typically include?

A usable subledger export includes the invoice number, vendor ID, purchase order reference, line-level amount, quantity, unit price and posting date. Without all of these fields, matching an invoice back to a contract rate or a volume tier is not possible, because the comparison requires the same level of detail on both sides. Missing fields are a common early blocker in an audit and are worth confirming before an extract is treated as complete. - Invoice and PO number: Ties the transaction to the order that authorized it. - Vendor identifier: Groups transactions for rate card and tier comparison. - Line amount and quantity: Lets a unit price be recalculated and checked. - Posting date: Places the transaction in the correct contract period. For the wider pattern this sits inside, start with the [margin drift](/insights/margin-drift-spend-leakage-guide) guide. See also [margin drift vs. legitimate price increases: how to tell them apart](/guides/margin-drift-vs-legitimate-price-increases-how-to-tell-them) and [accessorial charge audit: the surcharges nobody validates](/guides/accessorial-charge-audit-the-surcharges-nobody-validates).

Questions & Answers

Is a subledger the same as the general ledger?

No. The general ledger holds summary balances by account. A subledger holds the transaction detail behind one of those balances, such as every open vendor invoice behind the accounts payable account. The general ledger total should reconcile back to the sum of its subledgers.

What is the accounts payable subledger used for?

It stores every vendor invoice, credit memo and payment, tied to a purchase order and vendor record. AP teams use it to track open balances by vendor and to support the audit trail a contract compliance review depends on.

Why does subledger detail matter for a contract compliance audit?

A contract compliance audit checks invoice lines against rate cards, tiers and caps. The general ledger only shows a posted total. The subledger holds the line-level detail, vendor, PO and date, needed to run that check at all.

Can subledger data be exported for an audit?

Most ERPs support an export of subledger detail by vendor, date range and account. The export should include invoice number, PO reference, line amount and posting date, the minimum detail needed to match against a contract.

What happens when the subledger and general ledger do not reconcile?

An unreconciled subledger points to a posting error, a timing difference, or a transaction recorded in one ledger and not the other. It has to be resolved before the balance can be trusted for reporting or for an audit.

Margin Drift Resources