Key points
A subledger holds the transaction-level detail behind a single general ledger balance, called the control account.
At startups, subledgers are usually operational systems: billing for AR, a spend tool for AP, payroll for accrued payroll.
Subledger totals must equal the control account every period end; differences are timing items or errors to fix.
A billing system is an AR subledger, not a revenue subledger, because invoices show what was billed, not what was earned.
Manual journal entries straight to a control account are the most common cause of permanent subledger breaks.
What a subledger is
A subledger, or subsidiary ledger, holds the transaction-level detail behind one balance in the general ledger. The accounts receivable subledger lists every open invoice by customer. The general ledger holds one number: the AR control account. The two must agree at every period end.
The split keeps the general ledger readable. A company with 400 customers does not want 400 receivable accounts in its chart of accounts. It wants one control account, plus a subledger that can answer "who owes us what, and since when."
Subledgers at a usage-based company
At a startup, most subledgers are not called subledgers. They are the systems where operational detail already lives. The table maps the common ones.
Subledger | Typical system of detail | GL control account | Reconcile against |
|---|---|---|---|
Accounts receivable | Billing system, such as Stripe | Accounts receivable | Open invoice aging report |
Accounts payable | Spend or bill-pay tool, such as Ramp | Accounts payable | Open bills by vendor |
Payroll | Payroll provider, such as Rippling | Accrued payroll and payroll taxes | Payroll register |
Fixed assets | Asset register | PP&E and accumulated depreciation | Register net book value |
Deferred revenue | Revenue schedule by contract | Deferred revenue | Remaining unearned balance by contract |
Unbilled usage | Metering or usage database | Unbilled receivables | Priced usage not yet invoiced |
One caution. A billing system is an AR subledger, not a revenue subledger. Invoices tell you what was billed, not what was earned. The gap is covered in billings vs revenue, and the revenue-side detail usually lives in a deferred revenue waterfall.
Worked example: tying AR subledger to the GL
Fieldnote AI, a fictional Series B company with usage-based pricing, closes October. Its Stripe aging report totals $612,400. The AR control account in the general ledger shows $618,400. The figures are illustrative.
Item | Amount |
|---|---|
AR per general ledger | 618,400 |
Less: invoice voided in Stripe on Oct 31, after the GL sync ran | (9,000) |
Add: customer wire recorded in the GL, not yet applied to the invoice in Stripe | 3,000 |
Adjusted AR per general ledger | 612,400 |
AR per subledger (Stripe aging) | 612,400 |
Unexplained difference | 0 |
The two items need different fixes. The voided invoice was a billing error, so the GL needs an entry. The wire needs no GL entry; someone applies the payment to the invoice in Stripe, which lowers the subledger by $3,000.
Account | Debit | Credit |
|---|---|---|
Usage revenue | 9,000 | |
Accounts receivable | 9,000 |
After both fixes, the GL and subledger each show $609,400. Ties like this are the core of account reconciliation for control accounts.
Subledger vs general ledger
Subledger | General ledger | |
|---|---|---|
Level of detail | Each invoice, bill, asset, or employee | One balance per account |
How many | Several, one per area | One per legal entity |
Who uses it daily | AR, AP, payroll, operations | Accounting and reporting |
Feeds | The GL, via summary or detailed postings | Trial balance and financial statements |
What auditors do with it | Sample items and trace them to support | Tie balances to subledgers and statements |
When a balance needs its own subledger
More than a few dozen open items sit in the balance at month end.
Someone outside accounting needs item-level answers, such as collections or vendor support.
The balance drives a metric investors watch, such as deferred revenue or unbilled usage.
An auditor would need to sample from it. If you cannot produce a list of items that sums to the GL, you will be asked to build one.
Common mistakes
Manual entries to control accounts. A journal entry straight to AR control, with no matching subledger change, creates a permanent break. Lock control accounts to subledger postings where your system allows it.
Summary postings with no drill-down. One monthly lump sum from billing to the GL hides which invoices it contains. Post at a level you can trace.
Sync timing. Integrations run on schedules. Voids, credits, and refunds near midnight on the last day are the usual cause of breaks.
Carrying an unexplained difference forward. A small break left alone becomes a large one nobody can explain.
How Quanta handles subledgers
Quanta builds integrations into the systems that hold the detail: the customer's usage database, Stripe, Ramp, Rippling and cloud bills. The in-house accounting team keeps the ledger and ties control accounts back to that detail. Because numbers trace to journal entries, a balance can be followed from the statement down to the items behind it.
Quanta perspective
Most startups already have good subledgers; they just never tie them to the ledger. Stripe knows every invoice and the usage database knows every unit consumed, but if those totals do not match the control accounts each month, the detail is useless in an audit. The tie-out is the work.
Frequently asked questions
What is the difference between a subledger and a general ledger?
The general ledger holds one balance per account and produces the financial statements. A subledger holds the individual items behind one of those balances, such as each open customer invoice behind accounts receivable.
Is accounts receivable a subledger?
Accounts receivable is a general ledger control account. The list of open invoices by customer that supports it is the AR subledger.
What is a control account?
A control account is the general ledger account whose balance should equal the total of a subledger. Accounts receivable, accounts payable, and fixed assets are common examples.
How often should subledgers be reconciled to the general ledger?
At least every month as part of the close. High-volume subledgers like AR and AP are often checked more often so breaks are caught while the cause is still easy to find.
Can a spreadsheet be a subledger?
Yes, if it lists every item, totals to the control account, and is kept under change control. Prepaid and fixed asset schedules are often spreadsheets at early-stage companies.