Revenue Subledger
Revenue Subledger Definition
A revenue subledger is a detailed, transaction-level system of record that tracks every billing and revenue event — usage, invoices, overages, deferred revenue, and recognized revenue — at the individual contract and customer level, then reconciles and summarizes those events before they post to the general ledger. Where the general ledger holds the summarized, period-level balances an auditor signs off on, the revenue subledger holds the granular detail behind each balance and the audit trail that explains how it was calculated.
For B2B SaaS, the revenue subledger is where ASC 606 and IFRS 15 actually happen: it estimates and constrains variable consideration, builds deferred-revenue waterfalls, and recognizes revenue as performance obligations are satisfied. Unlike a billing engine, which meters usage and produces charges, a revenue subledger verifies that every unit was billed correctly and that the resulting revenue is recognized and reconciled — making it the control layer between billing and the books.
Also referred to as: revenue sub-ledger, revenue subsidiary ledger, rev rec subledger, billing subledger.
How a revenue subledger works
A revenue subledger takes in the signed contract terms, metered usage, invoices, and payments, then reconciles them against each other at the contract level. It confirms that what was billed matches the contract, catches under-billing and unbilled usage, and applies the ASC 606 / IFRS 15 policy to determine how and when each dollar is recognized — drawing down prepaid credits, recognizing usage as consumed, and spreading subscription fees over the term.
The output is a set of recognition schedules and deferred-revenue balances, plus summarized journal entries that post to the general ledger. Because the detail lives in the subledger, finance can answer "what makes up this revenue number?" and "why did deferred revenue change?" down to the individual contract — which is exactly what auditors and investors ask for.
Revenue subledger vs. general ledger
The general ledger (GL) is the book of record for the whole business: it holds summarized account balances — total revenue, total deferred revenue — for a period. A subledger is a subsidiary ledger that holds the line-item detail behind one of those GL accounts and rolls up into it. The revenue subledger is the subsidiary ledger for revenue and deferred revenue.
Keeping that detail out of the GL keeps the GL clean while preserving a full audit trail. The subledger reconciles to the GL control account, so the granular contract-level activity always ties back to the summarized number leadership and auditors review.
Revenue subledger vs. billing engine
A billing engine (Stripe Billing, Orb, Metronome, Chargebee) meters usage and produces charges and invoices. It answers "what do we bill this customer?" A revenue subledger answers a different question: "was that billed correctly against the contract, and how should the revenue be recognized?" The two are complementary — most companies keep their billing engine and add a revenue subledger on top.
The gap matters most for usage-based and hybrid pricing, where billing varies every period and recognition follows consumption rather than the invoice. A billing engine that meters perfectly can still leave revenue under-billed or mis-recognized; the subledger is the reconciliation and recognition layer that closes that gap.
When you'd use this
- Deciding whether you need a dedicated rev-rec system on top of your billing engine.
- Preparing audit-ready revenue schedules for a Series B, audit, or IPO.
- Explaining where ASC 606 / IFRS 15 recognition actually happens in your stack.
- Reconciling billed revenue to recognized revenue at month-end close.
Related Guides
How a revenue subledger recognizes usage revenue under ASC 606 — with worked journal entries.
The five-step model the revenue subledger applies to subscription, milestone, and usage contracts.
How LedgerUp runs your revenue subledger and posts audit-ready schedules to your ERP.
Revenue Subledger FAQ
What is a revenue subledger?
A revenue subledger is a detailed, contract-level system of record for billing and revenue events — usage, invoices, deferred revenue, and recognized revenue — that reconciles and summarizes them before they post to the general ledger. It is where ASC 606 / IFRS 15 recognition and the supporting audit trail live.
What is the difference between a revenue subledger and the general ledger?
The general ledger holds summarized, period-level account balances for the whole business. A revenue subledger holds the line-item detail behind the revenue and deferred-revenue accounts and rolls up into them, so the granular contract-level activity always reconciles to the summarized GL number.
Is a revenue subledger the same as an ERP?
No. An ERP (NetSuite, Sage Intacct) contains the general ledger and may include a native rev-rec module, but for complex or usage-based contracts many companies use a dedicated revenue subledger that reconciles billing to the contract and posts summarized journal entries into the ERP's GL.
Do I need a revenue subledger if I have a billing engine?
Often yes. A billing engine meters usage and produces charges, but it does not reconcile billing to the contract or run full ASC 606 recognition. A revenue subledger adds that control and recognition layer on top, which matters most for usage-based, hybrid, and committed-use contracts.