1 min lesson
From rated event to recognized revenue
Start at the first move in "From rated event to recognized revenue" and carry it through to the proof.
Step 1 of 2
From rated event to recognized revenuethe audit trail that has to survive
The piece that separates a finance systems engineer from an accountant is owning the data path. Every rated usage event has to map to a recognition entry that an auditor can trace back to the metered fact.
- 1Metering captures the raw consumption event with a timestamp, customer and quantity.
- 2Rating applies the price book to produce a dollar amount and a rated-event id.
- 3Recognition ties that rated amount to the contract, draws down any prepaid balance and writes a revenue schedule line for the period.
- 4Reconciliation confirms that rated usage, drawn-down deferred revenue and recognized revenue tie out for every contract.
Late-arriving usage events are the classic trap. If consumption for the last day of the period lands after subledger cutoff, you either accrue it or you understate revenue. Your design needs an explicit cutoff and accrual rule, not an implicit "whatever was in the table when the job ran."
Asked how to recognize Cursor-style usage revenue, lead with the right-to-invoice expedient for pure pay-as-you-go, then immediately distinguish prepaid credits and committed spend, which are deferred revenue drawn down by consumption with breakage on the tail. That sequence shows you know which case is easy and exactly where the judgment lives.
Learn more
Optional practice