The difference a signature creates
Bookings represent what the customer has agreed to pay; recognized revenue is what the company has earned under its obligations. These numbers can diverge by quarters or years, depending on contract structure, implementation timelines, and how the company defines its performance obligations under ASC 606.A practical example: if you close a two-year SaaS contract in December, you may book the full annual contract value in that quarter. But if the product does not go live until February, recognized revenue in Q4 is zero or limited to setup fees. The income statement and the CRM tell completely different stories about the same deal.
The four levers that create a gap
| Factor | Effect on gap |
|---|---|
| Long implementation cycles | Delays recognition of full ACV until delivery |
| Multi-element contracts | Each performance obligation recognized separately |
| Usage-based pricing | Revenue recognized as consumption occurs |
| Upfront annual billing | Cash received early; revenue earned over the term |
| Contract start date late in quarter | Full-period revenue recognized only in next period |
Why RevOps needs both numbers in every forecast
A bookings-only forecast overstates revenue when the pipeline is weighted toward complex, late-starting deals. A recognized-revenue-only forecast understates the commercial momentum the sales team is generating. RevOps leaders should maintain both forecasts and a bridge between them that accounts for deals closing late in the period, deferred revenue from prior periods unwinding, and contract modifications.
The bookings-to-revenue bridge is also where churn appears in its truest form. A high-bookings quarter paired with rising customer cancellations will show flat recognized revenue before it shows up in the ARR waterfall.
The RevOps operating model
Track bookings vs. revenue as separate line items in every board and investor package. Use deferred revenue as the reconciling account that explains the timing gap. Keep the ARR formula grounded in contracted recurring value, not recognized revenue, so scaling teams do not mistake delivery lag for business slowdown.
Frequently Asked Questions
Why does booked revenue not equal recognized revenue?
Because revenue recognition follows delivery, not signature. Under ASC 606, a company can only recognize revenue as it satisfies performance obligations to the customer. A deal signed on the last day of a quarter may book the full contract value but recognize only a fraction of it in that same period.
Which number should appear in a sales forecast?
Both, tracked separately. Bookings tell the sales org whether the team hit its targets for new contracted value. Recognized revenue is what appears in the income statement and determines whether the company meets external guidance. A forecast that conflates them will mislead both the CFO and the board.
How does the bookings-to-revenue gap affect ARR?
ARR is calculated from contracted recurring value, not recognized revenue, so ARR can grow in a period when recognized revenue is flat or even declining. This is common during a fast ramp phase where new bookings outpace delivery. RevOps teams need to track both to avoid presenting ARR growth as a revenue growth substitute to finance stakeholders.
Put these metrics to work
ORM builds custom revenue forecast models that turn concepts like booked revenue vs. recognized revenue into prescriptive action for your team.
Schedule a Demo