Bookings vs billings vs revenue: the three numbers founders confuse

A customer signs a $12,000 annual contract on March 15. That same deal is worth three different numbers at once: $12,000, $1,000, and roughly $548. Each one is correct. Each one answers a different question, and founders mix them up constantly.

Bookings is what the customer committed to: the full contract value, counted the day they sign. Billings is what you invoice them, which depends entirely on your billing terms. Revenue is what you have actually earned by delivering the service, recognized one period at a time. The gap between billings and revenue has its own name: deferred revenue, the cash you have collected but not yet earned.

Bookings and billings are forward-looking. Recognized revenue is backward-looking and the only one of the three that hits your income statement under GAAP. They disagree on purpose. This piece traces one contract through all of them so the gaps stop being abstract.

The one-contract walkthrough

Take that $12,000 annual deal signed March 15, billed annually upfront. Here is what each number does on day one and over the following year.

Day 1 (signing): bookings = $12,000. The moment the customer commits, you book the full contract value. Nothing has been delivered, nothing has been invoiced. Sales counts this number the day the ink dries.

Invoice day: billings = $12,000. Because you bill annually upfront, you invoice the whole year at once. Had you billed monthly, billings would be $1,000 this month and $1,000 each month after. Same contract, completely different billings depending on terms.

End of March: recognized revenue = about $548. You only earned the days you actually delivered. The contract started March 15, so March had 17 days of service out of 31. Under ASC 606 daily proration, that is (17 / 31) x ($12,000 / 12) = (17 / 31) x $1,000 = about $548.

End of March: deferred revenue = about $11,452. You collected $12,000 but earned $548. The difference, $11,452, sits on your balance sheet as a liability. You owe the customer eleven and a half months of service.

Every month after: recognized revenue = $1,000, MRR = $1,000. From April through the following February you deliver a full month, so you recognize $1,000 each month, draining the deferred balance as you go. The contract is $1,000 of MRR the entire time, billed annually or not.

The “missing” $11,452 was never missing. It moved into deferred revenue and unwinds at roughly $1,000 a month until the contract finishes a year later, when all three numbers finally agree.

The reconciliation table

Here is the same single contract across every metric at four points in its life. Annual-upfront billing, daily ASC 606 proration.

Point in time	Bookings	Billings	Recognized revenue (cumulative)	Deferred revenue	MRR
Signing (Mar 15)	$12,000	$12,000	$0	$12,000	$1,000
End of month 1 (Mar 31)	$12,000	$12,000	$548	$11,452	$1,000
End of month 6 (Aug)	$12,000	$12,000	$5,548	$6,452	$1,000
End of month 12 (next Mar)	$12,000	$12,000	$12,000	$0	$1,000

Read the rows top to bottom. Bookings and billings are fixed the day you sign and invoice. Recognized revenue climbs one month at a time. Deferred revenue drains as the mirror image. They only reconcile at the bottom row, when the year is fully delivered.

One identity holds for the whole contract: bookings is greater than or equal to billings, which is greater than or equal to cumulative recognized revenue, at every point until the contract completes.

Bookings: what the customer committed to

Bookings is the total value of contracts signed in a period, counted in full on the signing date. It is a commitment, not cash and not earned revenue. A $12,000 annual deal is $12,000 in bookings the day it closes, even though you have delivered nothing.

Two flavors matter, and confusing them is the classic mistake.

TCV (total contract value) is the recurring value over the whole contract life. A three-year, $12,000-per-year deal is $36,000 of TCV.
ACV (annual contract value) is the recurring value for one year, so $12,000.

TCV behaves like bookings; ACV behaves like annualized revenue. Report a three-year deal at TCV, call it your annual number, and you have overstated growth by 3x. Bookings teams should always say which one they mean.

Bookings is non-GAAP and forward-looking, which is exactly why sales lives here. It tells you demand and pipeline conversion the instant a deal closes, long before any revenue shows up. It tells you nothing about cash or earnings. For the standard definition, see bookings in the glossary.

Billings: what you invoiced

Billings is the total dollar amount you invoice customers in a period, and it is the best near-term read on cash flow. Bill the $12,000 contract annually upfront and billings is $12,000 this month. Bill it monthly and billings is $1,000 at a time.

That single choice drives the size of your deferred-revenue balance.

Annual-upfront billing makes billings spike to the full contract value while revenue trickles in at one-twelfth a month. Big deferred balance.
Monthly billing keeps billings and revenue almost identical, because the service period and the billing period line up. Almost no deferred revenue.

The market leans heavily on annual. Roughly 45 to 50 percent of SaaS plans were billed annually across 2024 and 2025, against about 36 to 42 percent monthly, with the balance multi-year or usage-based. That mix is why deferred-revenue balances run so large industry-wide.

The incentive driving it is the prepay discount. Companies trade a price cut for a year of cash upfront.

Billing structure	Median discount vs monthly	Effect on deferred revenue
Annual prepay	About 18 percent	Large balance, unwinds over 12 months
Multi-year / tiered prepay	Up to 25 percent	Even larger, unwinds over the full term
Monthly	None	Near zero

Company size sorts the behavior cleanly. Firms under 50 employees bill monthly about 68 percent of the time. Enterprises over 1,000 employees bill monthly only about 28 percent of the time. Bigger deals skew annual, which widens the deferred balance. The mechanics behind billings are worth pinning down if your cash forecast depends on them.

Revenue and deferred revenue: what you earned

Recognized revenue is the portion of a contract you have actually delivered, recognized as you perform the service, not when you sign or collect. This is the GAAP number on your income statement, and it is the one auditors and investors treat as real.

ASC 606 governs how you recognize it. The five-step model in plain English:

Identify the contract with the customer.
Identify what you promised to deliver.
Set the transaction price.
Allocate that price across what you promised.
Recognize revenue as you deliver each promise.

For a flat annual subscription, step five does the work. You deliver access continuously, so you spread the $12,000 across the year. Two ways to spread it:

Straight-line: $12,000 / 12 = $1,000 per month, every month.
Daily proration (ASC 606 preferred for partial periods): (days of service in the period / total contract days) x contract value. This is why March earned $548, not $1,000. It had 17 service days, not 31.

Deferred revenue is the bridge between billings and revenue: deferred revenue = billings minus recognized revenue. Collect $12,000 upfront and all $12,000 starts as deferred revenue, a liability on your balance sheet. Each month about $1,000 moves out of deferred and into recognized as you deliver. Monthly-billed plans create almost none, because billing and delivery happen in the same period. We go deeper on this in the deferred revenue guide for SaaS.

How MRR and ARR tie in

MRR normalizes every billing interval to a monthly figure: MRR = ACV / 12. A $12,000-per-year customer is $1,000 of MRR whether you billed them monthly or annually upfront. Billing terms do not change MRR, which is the entire point of the metric.

ARR is MRR x 12, counting recurring subscription revenue only. One-time charges and non-recurring fees stay out.

So MRR and ARR sit alongside recognized revenue rather than replacing it. Recognized revenue is the GAAP truth of what you earned this period, including any one-time items. MRR strips out the noise to show the steady-state recurring run-rate the business operates at. A board wants both: the audited number and the run-rate. To model the run-rate forward, the ARR calculator runs the normalization for you.

Who should watch which number

Each number answers to a different audience, and pointing the wrong one at the wrong reader is how founders lose credibility in a board meeting.

Audience	The number they care about	Why
Sales	Bookings (TCV / ACV)	Measures deals closed and pipeline conversion the day they sign
Finance	Billings and cash	Best near-term proxy for cash in the door
Board and investors	Recognized revenue + MRR / ARR	GAAP earnings plus the recurring run-rate

The trap is treating bookings or billings as revenue. A founder who reports “$12,000 in revenue” the day a deal signs is off by a factor of roughly 22 for the first month. The deal earned about $548. Bookings and billings are also non-GAAP and non-standardized, so two companies calculate them differently and peer comparisons get unreliable fast. Recognized revenue is the only one with rules everyone follows.

This is where keeping the views connected matters. Mowt builds your MRR view and your recognized-revenue view from the same Stripe data, so the run-rate and the GAAP number reconcile instead of drifting apart in two spreadsheets. The three numbers stop surprising you because you can see, per contract, exactly where each one stands.

The takeaway in one contract

Same $12,000 deal, three honest answers. $12,000 of bookings the day it signs. $12,000 of billings when you invoice annually upfront, or $1,000 at a time if you bill monthly. About $548 of recognized revenue in the partial first month, then $1,000 a month after, with the balance parked in deferred revenue until you have earned it.

Know which question you are answering before you say the number out loud. If you are also deciding how to present the recurring run-rate, MRR versus ARR covers the next layer.

FAQ

What is the difference between bookings and revenue?

Bookings is the full value of a contract counted on the day it is signed, a commitment. Revenue is only the portion you have actually earned by delivering the service, recognized over time. A $12,000 annual deal is $12,000 in bookings immediately but $1,000 of recognized revenue per month over the next 12 months. Bookings is forward-looking and non-GAAP; revenue is the GAAP number on your income statement.

What are billings in SaaS?

Billings is the total dollar amount you invoice customers in a period, and it depends entirely on your billing terms. Invoice a $12,000 annual contract upfront and billings is $12,000; bill monthly and it is $1,000 at a time. Billings is the best near-term proxy for cash flow, but it is not revenue. The part you have billed but not yet earned becomes deferred revenue.

Why do bookings not equal revenue?

Because they measure different moments. Bookings counts the entire contract the instant it is signed; revenue counts only what you have delivered. Accrual accounting under ASC 606 forces you to recognize revenue as you perform the service, not when you sign or collect, so the full booking spreads across the contract term and only matches cumulative revenue once the contract fully completes.

How does deferred revenue fit in?

Deferred revenue is the bridge between billings and revenue: it equals billings minus recognized revenue. When you collect $12,000 upfront for an annual plan, all $12,000 starts as deferred revenue, a liability, and each month about $1,000 moves from deferred into recognized revenue as you deliver the service. Monthly billing creates almost no deferred revenue because billing and delivery happen in the same period.

Is bookings or billings the same as MRR?

Neither. MRR normalizes a contract to a monthly recurring figure (ACV / 12), so a $12,000-per-year customer is always $1,000 of MRR regardless of how they are billed. Bookings counts the whole contract value at signing and billings counts what you invoiced in the period, both of which move with contract length and billing terms in ways MRR deliberately ignores.