Bookings vs Revenue vs Billings: Key Differences

A CEO tells the board "we closed $4 million this quarter." The CFO's revenue line shows $900,000. Neither number is wrong. They're measuring different moments in the same set of deals, and a board that doesn't know which moment it's looking at will either panic over a number that was never supposed to match, or walk away thinking the business is bigger than it actually is.

Bookings, billings, and revenue are the three numbers every subscription business needs to keep straight. Bookings is what sales signed. Billings is what finance invoiced. Revenue is what accounting is allowed to recognize under the rules that govern public and audited financial statements. This guide defines each one, walks a single contract through all three so you can see exactly where they diverge, and tells you which number belongs in a board deck, a comp plan, a forecast, or a cash planning conversation.

Key Facts

• ASC 606, issued jointly by the FASB and the IASB in May 2014, took effect for public companies' annual reporting periods beginning after December 15, 2017, and for private companies a year later, per FASB's own project summary.
• Under IFRS 15, "an entity recognises revenue to depict the transfer of promised goods or services to the customer in an amount that reflects the consideration to which the entity expects to be entitled," applied through a five-step model, per the IFRS Foundation.
• ASC 606's five-step model requires identifying the contract and its performance obligations, then determining and allocating the transaction price, before revenue can be recognized as those obligations are satisfied, according to BDO's 2026 revenue recognition guide.
• Salesforce's current remaining performance obligation (the contracted, not-yet-recognized revenue it expects to recognize within a year) was $33.5 billion for the quarter ended July 31, 2026, nearly three times its $11.3 billion in quarterly revenue, per Salesforce's Q2 FY27 results.
• HubSpot's calculated billings, which it defines as "total revenue recognized in a period plus the sequential change in total deferred revenue," were $971.4 million against $846.7 million in revenue for the quarter ended December 31, 2025, per HubSpot's Q4 2025 results.

This article is about definitions and mechanics, not about setting a target or designing a payout curve. To build the target number itself, see sales quota. To design what a rep earns against that target, see sales compensation. This article assumes you already close deals and need a shared vocabulary for what actually happened when one of them closes.

Bookings: the sales number

Bookings is the total value of a contract a customer has signed. It's recorded the moment the deal closes, regardless of when the customer pays or when the company is allowed to count the revenue. Bookings lives in the CRM and the sales comp plan. It does not appear on the income statement, and it isn't governed by any accounting standard, because it isn't accounting. It's a measure of sales output.

That distinction matters more than it sounds. A deal can be fully booked and generate zero revenue for months, if the service hasn't started yet or the contract term hasn't begun. A rep who closes a $500,000, three-year deal on the last day of the quarter has done their job: the bookings number reflects it immediately. Finance won't recognize a dollar of that $500,000 until the service is actually delivered, which could be a full quarter or more away.

TCV vs ACV

Not all bookings are annual, so a single "bookings" number needs a second dimension: over what period.

TCV and ACV tell you different things and both are legitimate, as long as you label which one you're using. TCV is the right number for understanding how much total value a rep closed. ACV is the right number for comparing deal sizes across contracts of different lengths, and it's the number most sales comp plans and revenue quotas should use, because paying full commission on a three-year TCV the moment it's signed rewards length over annual value. A one-year, $120,000 deal and a three-year, $360,000 deal represent the same annual commitment; treating the second as three times the bookings of the first is the single most common bookings-reporting mistake in this article.

New, renewal, and expansion bookings

Bookings also needs a source tag, the same way ARR breaks into new, expansion, contraction, and churned components. A company that only tracks total bookings can't tell whether growth came from new logos, from existing customers renewing at the same level, or from existing customers buying more.

Blending these three into one "total bookings" figure hides the same thing blending ARR components hides: whether the business is growing because it's winning new customers or because it's growing the ones it already has. A company reporting strong bookings growth that's 90% renewal and expansion, with flat new logos, has a very different growth story than one where new logos are carrying the number. See net revenue retention for how the renewal and expansion side of this gets measured once a contract moves from a bookings event to an ongoing revenue base.

Billings: the invoicing number

Billings is what actually gets invoiced to the customer in a given period. Where bookings is a sales event that happens once, billings is a finance event that can happen repeatedly across a contract's life, once for every invoice the contract's terms call for.

Billing terms drive when those invoices go out, and they don't have to match how the service is delivered. A customer can sign a one-year contract and be billed monthly, quarterly, or in a single annual payment upfront. The service is delivered continuously either way; only the invoicing schedule changes.

Billing terms are a negotiating lever independent of price. A vendor that offers a discount for annual upfront payment isn't discounting the service, it's paying for the cash flow benefit of collecting a year's revenue on day one instead of over twelve invoices. That's also why billing terms show up in deal size optimization conversations: a deal desk comparing two otherwise-identical offers should weigh the cash timing difference, not just the headline ACV.

Billings connects directly to two numbers that live on the balance sheet: accounts receivable (billed but not yet collected) and deferred revenue (collected or billed but not yet recognized). The identity that ties billings to revenue is simple and worth memorizing: billings = revenue recognized in the period, plus the change in deferred revenue over that period. That's the exact formula HubSpot uses to calculate its own publicly reported "calculated billings" figure, and it's the cleanest way to understand why a period's invoiced total and its recognized revenue almost never match.

Revenue: the accounting number

Revenue is what a company is allowed to recognize on its income statement, governed by ASC 606 in the US and IFRS 15 internationally. It's the only one of the three numbers that GAAP and IFRS actually define, and it's the one that gets audited.

Both standards apply the same five-step model, since ASC 606 and IFRS 15 were issued as a converged standard by the FASB and the IASB together:

For a standard SaaS subscription, step 5 is what matters most day to day: revenue is recognized ratably, in equal monthly amounts, over the service period, regardless of how or when the customer was billed. A 12-month, $120,000 contract recognizes $10,000 of revenue every month it's active, whether the customer was billed once, quarterly, or monthly. This is what makes revenue the slowest-moving and most delayed of the three numbers, and also the one that's the hardest to inflate or accelerate through a clever contract structure.

One contract, three numbers: a worked example

Here's a single deal, followed through all three numbers plus cash and the deferred revenue balance it creates. A customer signs a 3-year contract for $360,000 total (TCV), an ACV of $120,000, billed annually in advance at the start of each contract year, with revenue recognized ratably at $10,000 per month over the full 36-month term.

Four things to notice in that table. First, bookings fires exactly once, in Month 1, for the full $360,000. It never appears again in this contract's life, which is exactly why a bookings number can't be added up across future months to estimate revenue. Second, billings and cash spike three times, once at the start of each contract year, and sit at zero the rest of the time. A finance team looking only at a monthly cash chart would see two enormous flat quarters of nothing between three sharp spikes, even though the customer is receiving continuous service every single month. Third, revenue recognized is the only number in the table that moves in smooth, equal, monthly steps, precisely because ASC 606 requires ratable recognition over the service period regardless of the invoicing schedule. Fourth, and this is the reconciling fact worth sitting with: by the end of Month 36, cumulative revenue recognized ($360,000) exactly equals the original bookings number ($360,000, the TCV). Bookings and lifetime revenue always converge for a contract that runs its full term without expansion or contraction. They just get there on completely different timelines, which is precisely why a snapshot at any single point in between, like a quarter or a fiscal year, shows three different numbers for the same deal.

Deferred revenue and the balance sheet

Deferred revenue (also called unearned revenue, or a contract liability under ASC 606 terminology) is the amount a company has billed or collected but hasn't yet recognized as revenue. It sits on the balance sheet as a liability, because the company owes the customer service it hasn't delivered yet. In the worked example above, deferred revenue peaks at $110,000 right after each annual invoice and drains to $0 by the time the next year's service is fully delivered.

Deferred revenue is one of the most useful lines on a subscription company's balance sheet precisely because it's forward-looking: a growing deferred revenue balance means customers have already committed to (and often paid for) service the company hasn't delivered yet, which is a much stronger signal than revenue alone. Public SaaS companies increasingly disclose a related, larger figure for exactly this reason: remaining performance obligation (RPO), the total contracted revenue across a customer's full term that hasn't been recognized yet, whether or not it's been billed.

Salesforce's total RPO of $66.3 billion sitting against $11.3 billion of quarterly revenue is the same gap the worked contract example shows at the level of a whole company: an enormous amount of already-signed, already-contracted value that simply hasn't reached the income statement yet, because ASC 606 won't let it. A shrinking deferred revenue or RPO balance, without a corresponding wave of new bookings behind it, is an early warning sign for a renewal problem, often weeks or months before it shows up in churn rate or a revenue miss.

Where ARR and MRR fit

Annual recurring revenue and monthly recurring revenue are neither bookings, billings, nor revenue in the strict sense used above. They're normalized, run-rate snapshots of the active recurring contract base at a point in time, built from the ACV of every contract currently in force.

ARR and MRR are closer in spirit to a recognized-revenue run rate than to bookings or billings; both explicitly exclude one-time fees and non-recurring charges, the same exclusion revenue recognition applies. The practical difference is timing: revenue is what got recognized in a period that already happened, while ARR and MRR describe what the current book of business would generate over the next year or month if nothing changed. A big new booking shows up in ARR the moment the contract starts, well before most of its lifetime revenue has been recognized, which is one more reason ARR, bookings, and revenue can all move in different directions in the same quarter without anything being wrong.

Why sales gets comped on bookings and finance reports revenue

Sales compensation runs on bookings for a practical reason: a rep who closes a three-year deal shouldn't have to wait three years, recognized ratably a little at a time, to get paid. Sales compensation plans are typically built to pay commission as a percentage of a result, and that result is usually bookings (often ACV, since a straight TCV-based plan overpays for length), sometimes revenue, sometimes gross margin. Finance, by contrast, has no choice: it reports revenue, because that's the number ASC 606 and IFRS 15 govern and the number an auditor signs off on. Neither team is wrong. They're optimizing for different jobs: sales needs to reward closing behavior the moment it happens, finance needs a number that means the same thing quarter over quarter and holds up to an audit.

The friction shows up when the two numbers get mixed up in a single report or, worse, compared to each other as if they should match.

Note that "revenue quota" in most sales organizations is itself explicitly defined as total bookings or recognized revenue closed in the period, depending on the company. That's a legitimate design choice as long as everyone knows which one the quota actually uses; the failure mode isn't picking bookings over revenue for quota, it's letting the two get blurred together in the same conversation without saying which one is on the table. The same discipline applies to on-target earnings: OTE is calculated against a quota, and that quota needs the same bookings-or-revenue clarity before anyone can calculate what a rep should actually earn.

Which number belongs in which conversation

Different audiences need different numbers, and handing someone the wrong one, even an accurate one, creates confusion rather than clarity.

Pipeline and forecasting work sits downstream of all three. A sales forecast predicts bookings that haven't happened yet, and forecasting fundamentals assumes you already know which of the three numbers your forecast is actually trying to predict. And because revenue predictability depends on a clean recognized-revenue baseline, a company that can't cleanly separate bookings, billings, and revenue in its own reporting will struggle to forecast any of them accurately.

The three numbers describe the same deal at three different moments: the moment it's signed, the moment it's invoiced, and the moment it's earned. None of them is more "true" than the others; they're just answering different questions. Keep them separate in how you report, comp, and forecast, and the board, the bank, and the sales team stop arguing over whose number is right, because they were never supposed to be the same number in the first place.

Related reading

• Annual Recurring Revenue
• Monthly Recurring Revenue
• Sales Quota
• Sales Compensation
• On-Target Earnings
• Net Revenue Retention
• Quota Attainment
• Sales Forecasting Methods
• Revenue Predictability