TL;DR
Booked ARR counts signed contracts. Billed ARR counts contracts that are actively invoicing. The gap between them reflects implementation time, future start dates, and ramp schedules. Sales teams usually celebrate booked ARR. Finance plans against billed ARR. Good forecasting requires both. Updated April 2026.
---
Why the Distinction Matters
Booked ARR is defined as the annualized contract value of signed deals in a period. Billed ARR is defined as the annualized contract value of contracts that are actively invoicing. The two numbers are rarely equal. A deal signed in January with a March 1 start date contributes to booked ARR in January and to billed ARR starting in March. Multiply that across an entire pipeline and the gap becomes material.Sales teams default to booked because it credits the quarter they closed the deal. Finance defaults to billed because it is closer to cash. Both are correct for their purposes. Problems start when leadership conversations use one number while planning is built on the other, and nobody realizes the gap until the revenue report shows a shortfall.
How the Numbers Differ in Practice
Consider a SaaS company that signed $10M in new contracts in Q1. Of those contracts:| Category | Booked ARR Contribution | Billed ARR Contribution (Q1) |
|---|---|---|
| Deals with immediate start | $6M | $6M |
| Deals with 60-day implementation | $2M | $0 (billed in Q2) |
| Deals with future start date | $1.5M | $0 (billed Q2-Q3) |
| Deals with ramp schedule | $0.5M | $0.1M (partial ramp) |
| Total Q1 | $10M | $6.1M |
Where the Gap Usually Comes From
Three structural causes account for most of the difference:First, implementation timelines. Enterprise deals often have 30-90 day implementation periods before billing starts. Larger deals correlate with longer implementations. Upmarket motion widens the gap.
Second, delayed start dates. Deals signed with a future commencement date. Common in replacement scenarios where the customer is exiting another contract.
Third, ramp schedules. Deals that bill a smaller amount in year one and step up in years two and three. The full ARR contribution does not show in billed until the ramp completes.
Each of these is legitimate. None should be hidden. The job of revenue operations is to surface the gap clearly enough that leadership can plan around it.
Why This Affects Forecasting
Pipeline forecasts based on booked ARR overstate near-term revenue recognition. If your Q2 revenue plan assumes $8M of recognized revenue from Q1 bookings, but $3M of those bookings will not start billing until Q3, the plan will miss. This is a surprisingly common pattern in companies that have not formalized the distinction.The fix is to build two views of the forecast. One tracks bookings, which is the operational sales number. One tracks billings, which is the cash and revenue number. Revenue forecasting that only produces a booked number leaves finance doing ad-hoc conversions that introduce error.
Net new ARR similarly comes in booked and billed flavors. The same discipline applies — know which version you are reporting and why.Common Mistakes
Conflating the two numbers in board reporting. Leadership decks that cite booked ARR alongside historical billed ARR create a false growth story. The trend line looks stronger than it is because recent periods are counting contracts that have not started invoicing. Always label the metric. Ignoring the gap in operating plans. If implementation timelines are growing, billed ARR will lag booked ARR more severely. That affects hiring plans, marketing spend capacity, and runway calculations. Tracking the gap as its own metric — days from signature to first invoice — is a useful leading indicator. Pair this with revenue variance tracking to catch drift early. Forgetting about cancellations pre-billing. Deals that are signed but cancel before billing starts contribute to booked ARR but never to billed. In mature SaaS finance, this is tracked separately as "booking cancellations" and is an important leading indicator of customer expectation-setting problems in sales.For a broader view of how ARR metrics fit together with pipeline and forecasting, see the ARR glossary entry and the revenue forecasting guide.
Frequently Asked Questions
What is the difference between booked ARR and billed ARR?
Booked ARR is the annualized contract value of deals that have been signed. Billed ARR is the annualized value of contracts where billing has started. The difference is the portion of booked revenue that has not yet begun to invoice, usually because of future start dates, implementation periods, or ramp schedules.
Why does the gap between booked and billed ARR matter?
The gap is a leading indicator of cash flow and a drag on reported revenue. A deal booked in Q1 that bills starting in Q3 contributes to bookings but not to cash or reported revenue until Q3. If the gap grows, you have either longer implementation timelines or more deals with delayed start dates, both of which affect forecasting and planning.
How is booked ARR calculated?
Booked ARR is the sum of annualized contract values for deals signed in a period, using the recurring portion of the contract only. A three-year deal worth $300K total with $100K per year of recurring value contributes $100K of booked ARR in the period the deal was signed.
How is billed ARR calculated?
Billed ARR is the sum of annualized recurring revenue from contracts that have active billing as of the measurement date. Deals with future start dates are excluded until the billing period begins. This is the number that most closely aligns with what finance is actually collecting.
Put these metrics to work
ORM builds custom revenue forecast models that turn concepts like booked arr vs. billed arr into prescriptive action for your team.
Schedule a Demo