1 min lesson
The three-layer picture
Choose two examples from the table in "The three-layer picture" and explain what each teaches you to do.
Step 1 of 2
The three-layer picturebilling → subledger → GL
- Layer
- Billing engine
- Grain
- Invoice / usage line
- Owns
- What to charge, when, metering and rating
- Why it can't absorb the next layer
- Has no concept of performance obligations or deferral schedules
- Layer
- Revenue subledger
- Grain
- Contract obligation / schedule line
- Owns
- SSP allocation, recognition schedules, deferral, modifications
- Why it can't absorb the next layer
- Too detailed to be the GL; that detail is the point
- Layer
- General ledger
- Grain
- Account balance
- Owns
- Summarized journal entries, trial balance, financials
- Why it can't absorb the next layer
- Too coarse to track contract-level revenue over time
| Layer | Grain | Owns | Why it can't absorb the next layer |
|---|---|---|---|
| Billing engine | Invoice / usage line | What to charge, when, metering and rating | Has no concept of performance obligations or deferral schedules |
| Revenue subledger | Contract obligation / schedule line | SSP allocation, recognition schedules, deferral, modifications | Too detailed to be the GL; that detail is the point |
| General ledger | Account balance | Summarized journal entries, trial balance, financials | Too coarse to track contract-level revenue over time |
Each layer hands a summarized view up and keeps line-level detail for itself.
The subledger holds detail the GL is deliberately too coarse to track: every obligation, its schedule, its deferred balance and the history of any modification. It posts summarized journal entries up to the GL - a single deferred-revenue and recognized-revenue movement per period - while retaining the line-level traceability an auditor will ask for.
What the subledger reconciles
- Billings
- what was invoiced, tied back to orders and usage
- Deferred revenue
- the liability balance, drawn down on schedule
- Recognized revenue
- what hit the P&L this period, by obligation
- The tie-out
- opening deferred + billings − recognized = closing deferred, every period
If that roll-forward identity doesn't hold, the subledger is wrong before the GL ever sees it.