Bookings to Revenue Lag Calculator
SaaS bookings ≠ revenue. Under ASC 606, you recognize revenue ratably over the subscription term — meaning a $120K annual bookings deal produces $10K monthly revenue. Calculate your bookings-to-revenue lag and ARR roll-forward.
| Quarterly bookings | — |
| Monthly revenue per deal (over term) | — |
| Revenue recognized — Quarter 1 | — |
| Revenue recognized — Quarter 2 | — |
| Revenue recognized — Quarter 3 | — |
| Revenue recognized — Quarter 4 | — |
| Total 12-month revenue from this cohort | — |
| Deferred revenue balance — end of Q1 | — |
SaaS bookings — total contract value signed — is different from recognized revenue under ASC 606. Revenue must be recognized ratably over the performance period (subscription term). A $120K annual contract produces $10K/month of revenue over 12 months. This creates a structural lag between bookings growth and reported revenue growth.
Bookings vs Revenue vs Cash
Bookings: total contract value signed in the period. Revenue: ratably recognized portion of bookings during the period (typically 1/term per month). Cash: actually collected, depends on billing cadence. Annual prepay → cash day 1, revenue over 12 months, leaves deferred revenue liability.
Why It Matters
(1) Bookings is the LEADING indicator of future revenue. (2) Revenue lags 1-2 quarters behind bookings growth. (3) Cash flow leads revenue 3-9 months for annual prepay companies. (4) Layoff/hiring decisions based on P&L are 6+ months delayed reactions. (5) RPO (Remaining Performance Obligations) on balance sheet shows committed future revenue.
ASC 606 Compliance
ASC 606 (effective 2018 for public, 2019 for private) requires ratable recognition over the performance period. Implementation/setup fees are recognized over contract period (not upfront). Multi-element arrangements (subscription + services + hardware) require Standalone Selling Price (SSP) allocation. Most SaaS companies use ratable recognition for simplicity.
Last updated May 2026. Sources: FASB ASC 606, Bessemer Cloud 100.