1 min lesson
Where the revenue subledger sits and why the GL alone is not enough
Match each case in "Where the revenue subledger sits and why the GL alone is not enough" to the signal and response that fit it.
Step 1 of 2
3. Where the revenue subledger sits and why the GL alone is not enoughThis separates engineers from configurators
A general ledger stores balances: it knows you have $4.2M of deferred revenue this month. It does not know which contract, which performance obligation and which schedule produced that number. Auditors and your own restatement-prevention instincts need that lineage.
Summarized, account-level balances by period.
One journal line can roll up thousands of contracts.
Cannot answer 'show me the rev schedule for contract 88421' without a subledger behind it.
Contract- and obligation-level revenue schedules.
Holds the allocation, the deferral and the recognition timing per PO.
Posts a summarized journal entry up to the GL and retains the detail for audit and re-allocation on modification.
“The GL tells you the balance; the subledger tells you the story behind it. With usage and frequent contract mods, you need a dedicated revenue subledger between billing and the GL so that a modification re-allocates schedules at the obligation level and posts a clean delta upward, instead of you hand-journaling adjustments at the account level and losing the audit trail.”
Learn more
Full explanation
Keeping usage, invoices and the GL reconciled at scale
4. Keeping usage, invoices and the GL reconciled at scaleThree-way tie-out
- Usage → invoiced. For each billing period, the sum of rated usage events must equal the usage charges on the invoice. Reconcile on a stable usage key with a tolerance threshold and alert on any drift.
- Invoiced → recognized. Recognized revenue ties to the rev subledger schedules; deferred plus recognized must equal billed plus any unbilled receivable.
- Subledger → GL. The subledger's posted journals must foot to the GL revenue and deferred-revenue accounts every period, with a documented reconciliation owner.
- Controls. Immutable usage ledger, idempotent ingestion and a daily three-way reconciliation job that fails loudly rather than silently absorbing variance.
Learn more
Full explanation
A build-vs-configure decision with real trade-offs
5. A build-vs-configure decision with real trade-offsHave one rehearsed
- Lever
- Speed to first value
- Configure the platform
- Fast; you inherit the vendor's model
- Build custom
- Slow; you own everything from scratch
- Lever
- Fit to Cursor's usage model
- Configure the platform
- Risky if metering or rating is non-standard
- Build custom
- Exact fit, including odd entitlement logic
- Lever
- Maintenance burden
- Configure the platform
- Vendor patches and upgrades
- Build custom
- Yours forever, including on-call
- Lever
- Audit / SOXSarbanes-Oxley Act. A US law that forces companies to keep auditable controls over any system that affects their financial reporting. Press Enter for the full definition. surface
- Configure the platform
- Vendor SOC reports help your assertions
- Build custom
- You must build and evidence the controls
| Lever | Configure the platform | Build custom |
|---|---|---|
| Speed to first value | Fast; you inherit the vendor's model | Slow; you own everything from scratch |
| Fit to Cursor's usage model | Risky if metering or rating is non-standard | Exact fit, including odd entitlement logic |
| Maintenance burden | Vendor patches and upgrades | Yours forever, including on-call |
| Audit / SOXSarbanes-Oxley Act. A US law that forces companies to keep auditable controls over any system that affects their financial reporting. Press Enter for the full definition. surface | Vendor SOC reports help your assertions | You must build and evidence the controls |
Pick a lane and name the condition that would flip you.
Default to configure for the commodity (subscriptions, dunning, tax) and build for the differentiator (Cursor's specific metering, rating and entitlement logic). Then state the flip condition: “I configure the billing platform's rating engine until our pricing needs a rule it cannot express without three layers of hacks; at that point the maintenance cost of fighting the tool exceeds the cost of owning a thin custom rater behind a clean interface.” That single sentence is the autonomy and pragmatism signal the solo role screens for.
QFor Cursor's pure pay-as-you-go token usage at a fixed rate per unit, which ASC 606The US revenue-recognition standard; cited as the canonical judgment-heavy accounting work to keep human-led rather than hand to an agent, because facts and circumstances vary deal to deal. Press Enter for the full definition. treatment is usually the cleanest and what breaks it?