Booked vs invoiced vs recognized revenue: what SaaS RevOps teams need to know
Every RevOps leader eventually has a conversation with finance that goes like this:
RevOps: We booked $340K in new revenue this month. Finance: Revenue was $120K last month. RevOps: I'm talking about this month. Finance: I'm talking about recognized revenue. RevOps: Oh.
Booked, invoiced, and recognized revenue are three different numbers. For a cash-sale business (transactional e-commerce, consumer subscriptions) they're similar enough that the distinction doesn't matter. For B2B SaaS, especially with multi-year contracts and annual upfront billing, they can differ by a factor of three or more at any given moment.
This post is a practical walkthrough of what each one means, where they diverge, and how to build reporting that doesn't create monthly arguments with your CFO.
The definitions
Booked revenue
The total contract value of deals signed in a period. If a customer signs a 2-year contract for $100K/year with $12K paid upfront and monthly billing thereafter, booked revenue for that month is the full $200K (the contract value).
Booked = what you sold, measured at the moment of sale.
Invoiced revenue
The amount billed to customers in a period. From the same example, invoiced revenue depends on the billing schedule. If they paid $12K upfront and then $7,333/month thereafter, month 1 invoiced is $12K + $7,333 = $19,333. Month 2 onward is $7,333.
Invoiced = what you billed, measured when the invoice went out.
Recognized revenue
The amount of revenue recognized in a period according to accounting rules (US GAAP ASC 606 or IFRS 15). For subscription businesses, this is usually the contract value divided across the service period, ratably.
From our example, $200K of contract across 24 months = $8,333 per month of recognized revenue, regardless of when the cash came in.
Recognized = what accounting allows you to count as revenue that period.
Why they diverge
Three different timing models:
- Booked: when the contract is signed
- Invoiced: when the invoice is issued
- Recognized: when the service is delivered (monthly, ratably, or by usage)
In a steady-state business, they roughly correlate. In a growing business, they diverge significantly — the faster you grow, the bigger the delta.
Example: imagine you sign $1M of new contracts this month, all annual commits paid upfront.
- Booked: $1,000,000
- Invoiced: $1,000,000 (paid upfront this month)
- Recognized: $83,333 (1/12 of the annual contract)
The CFO is looking at $83K of recognized revenue growth. You're celebrating $1M of bookings. Both of you are right. Neither of you is wrong. You're talking about different numbers.
When each one matters
Booked revenue: commercial teams
Sales leadership cares about bookings because bookings = what sales closed. Quota is typically measured in bookings. Commission is typically paid on bookings. Pipeline coverage and sales forecasting operate in bookings.
Use booked revenue when:
- Measuring sales performance (quota attainment, rep productivity)
- Planning capacity (how many AEs do we need to hit the bookings target?)
- Setting targets with the sales team
- Any real-time operational view
Invoiced revenue: cash flow
Finance cares about invoiced revenue because invoiced = cash that will (hopefully) come in the door. Collections, DSO (days sales outstanding), and working capital are all driven by invoicing.
Use invoiced revenue when:
- Cash flow forecasting
- Understanding billing friction ("why was $200K of bookings only $80K of invoicing?")
- Collections reporting
- Credit and payment terms analysis
Recognized revenue: GAAP reporting and investors
Investors, banks, and auditors care about recognized revenue. It's the number that shows up on the income statement. It's what you report in financials. It drives EPS, margins, and valuation multiples.
Use recognized revenue when:
- Board reporting (outside the internal operating section)
- Investor updates
- Any external financial reporting
- Margin calculation
The three biggest divergence triggers
1. Multi-year contracts
A 3-year contract dramatically inflates booked revenue relative to recognized. Sign $360K total for 3 years? Booked: $360K this month. Recognized: $10K this month, and $10K every month for 35 more months.
Teams growing via multi-year deals will always have booked >> recognized. That's not a problem to solve — it's a characteristic of the business model. But it requires disciplined reporting so nobody thinks the business grew by 3×.
2. Annual prepay
Prepaid annual contracts inflate invoiced >> recognized even for single-year deals. Customer pays $60K upfront for a 12-month commit? Invoiced: $60K this month. Recognized: $5K this month.
This is why fast-growing SaaS often has cash on hand wildly larger than recognized revenue — the annual prepays front-load billings.
3. Usage-based pricing
Usage-based contracts complicate all three measures. Booked might be "up to $120K/year" (the cap), but actual recognized revenue depends on usage. Invoicing could be monthly in arrears.
For pure usage businesses, recognized ≈ invoiced ≈ consumption. But hybrid models (commit + usage) diverge in messy ways. Finance and RevOps should align on how to report "bookings" for usage contracts before the first report goes out.
The reporting pattern that works
A clean RevOps revenue report has three columns, labeled clearly, for each period:
| Period | Booked (new ACV + expansion) | Invoiced (cash billed) | Recognized (GAAP) | |--------|------------------------------|------------------------|-------------------| | Q1-2026 | $1,240K | $890K | $620K | | Q2-2026 | $1,480K | $1,120K | $780K |
Three columns, one table. Everyone reads what they need. Commercial teams track the first column. Finance tracks the third. Cash-flow people track the middle. No one is surprised.
The addition that brings it together: attribution. Each of the three columns breaks down by channel, so you can see what drove bookings, what converted to invoicing, and what ended up as recognized revenue. That's when attribution gets genuinely useful — not just "what drove the lead" but "what drove the revenue that the CFO is reporting."
ARR vs bookings — a related confusion
Annual Recurring Revenue (ARR) gets confused with bookings all the time. They're different:
- ARR = the annualized run rate of recurring revenue at a point in time
- New bookings ARR = new ARR added in a period (from new customers + expansion)
- Total bookings = new bookings ARR + services/one-time revenue
Most RevOps teams should report new bookings ARR monthly — it's the cleanest apples-to-apples commercial number. Services and one-time bookings go in a separate line. Finance typically cares about total bookings for their calculations.
Mistakes I see
Mistake 1: celebrating booked in the all-hands while finance reports recognized in the board deck. Two different growth stories in one company. Investors notice.
Mistake 2: computing CAC using recognized revenue numerator. CAC is paid once, at acquisition. The bookings paid it. Use bookings — or better, LTV — for unit economics.
Mistake 3: forecasting cash flow from recognized revenue. Cash is invoicing, not recognition.
Mistake 4: reporting "revenue" without specifying which. The vaguest word in RevOps. Never use "revenue" alone in a report.
Connecting to broader RevOps
This post ties directly into our Monday morning revenue dashboard, where booked and invoiced each earn their own tile. Revenue without qualifiers is too ambiguous for operational reporting.
It also connects to CAC by channel — CAC computations should use bookings, not recognized, to avoid the denominator drift that comes from GAAP timing.
Where Elir fits
Elir reports booked, invoiced, and (via connected accounting data) recognized revenue side by side, each broken down by channel and campaign. No more "which revenue are we talking about?" — the answer is "all three, at the same time, on the same screen." If that sounds like it would shorten your finance meetings, book a walkthrough.
TL;DR
Booked = contract signed. Invoiced = bill sent. Recognized = GAAP-allowed on the income statement. They diverge meaningfully in SaaS with multi-year contracts, annual prepays, or usage pricing. RevOps defaults to booked; finance defaults to recognized; cash flow uses invoiced. Never report "revenue" without the qualifier — it's the one-word way to create monthly arguments with your CFO.