Revenue recognition
Revenue recognition is the determination of when earned revenue may be recorded, governed by performance obligations rather than by cash timing.
Under a performance-obligation model, the contract is decomposed into distinct promises, the transaction price is allocated across them, and each is recognized as it is satisfied. This is why offer structure is a finance concern: a bundle whose components cannot be separated cannot be allocated cleanly.
The operational consequence for RevOps is that commercial structure decisions made at the deal desk, bundling, discounting across components, milestone-based delivery, determine the recognition schedule. Recognizing that upstream is what prevents a quarter of clean bookings from producing a messy revenue statement.
Where it breaks
A bundled discount is applied at the total level, forcing manual allocation across performance obligations at close.
Related terms
- Performance obligation
- A performance obligation is a distinct promise in a contract, and it is the unit revenue recognition is measured against.
- Deferred revenue
- Deferred revenue is a liability representing cash collected or invoiced for obligations not yet satisfied.
- Bookings
- A booking is the contractual commitment a customer has made, distinct from billings, which is what has been invoiced, and from revenue, which is what has been earned.
- Billing schedule
- A billing schedule is the sequence of invoices a contract generates, timing, amounts and triggers, derived from contract shape rather than chosen at invoicing time.
Field notes on this
- Four clocks: bookings, billings, revenue, and cash
Commercial commitment, invoicing, recognition, and collection answer different questions. Reconcile the clocks without treating them as one metric.