MRR vs ARR vs Bookings vs Revenue: The Money Terms Untangled

Few things cause more confusion in a SaaS board meeting than four money terms that sound interchangeable but mean very different things. The MRR vs ARR vs bookings vs revenue tangle is where founders, finance, and investors talk past each other — someone celebrates a $600,000 quarter, someone else asks why the bank shows a fraction of that, and a third person quietly wonders which number goes in the model. All four can describe the same customer while producing wildly different figures.

This guide untangles them. We will define each term precisely, show why they almost never equal each other, walk through a single deal that produces four different numbers, and give you a rule for which one to use when. By the end, these words will stop being a source of arguments and start being a set of tools.

The four terms, quickly defined

Before the nuance, here is the one-line version of each in the MRR vs ARR vs bookings vs revenue lineup.

• MRR (Monthly Recurring Revenue): the normalized monthly value of your active recurring subscriptions. A forward-looking run rate at monthly scale.
• ARR (Annual Recurring Revenue):the same run rate annualized — MRR times twelve. A forward-looking run rate at annual scale.
• Bookings:the total contractual value a customer has committed to, recognized when the contract is signed — regardless of when you deliver the service or collect the cash.
• Revenue: the money you have actually earned by delivering the service, recognized over time under accounting rules like ASC 606. This is the GAAP number on your income statement.

For single-metric deep dives, see what MRR is and what ARR is. The two newcomers here are bookings and revenue, and they are where most of the confusion lives.

Run rate vs bookings vs earned: three different questions

The reason these numbers diverge is that each answers a different question about time.

MRR and ARR answer "what is the current run rate?"

They are snapshots of the recurring engine as it stands today, projected forward. They ignore contract length and cash timing entirely — a month-to-month customer and an annual prepay customer at the same price show identical MRR.

Bookings answer "what did the customer commit to?"

Bookings capture the full value of a signed contract up front. A three-year, $120,000-per-year deal books as $360,000 the day it is signed, even though almost none of that has been delivered or collected. Bookings measure sales momentum, not earned income.

Revenue answers "what have you actually earned?"

Revenue is recognized only as you deliver. That same three-year contract produces $10,000 of recognized revenue in its first month, with the rest sitting in deferred revenue as a liability until it is earned. Revenue is the conservative, GAAP-compliant truth.

One deal, four numbers: a worked example

Nothing makes the MRR vs ARR vs bookings vs revenue distinction click like a single transaction. Imagine you sign a customer on January 1 to a two-year contract at $2,400 per month, paid annually in advance.

• MRR: $2,400. The normalized monthly recurring value of the subscription.
• ARR:$28,800. That MRR annualized ($2,400 × 12).
• Bookings:$57,600. The full two-year contract value committed on signing ($2,400 × 24).
• Revenue (first month): $2,400. Only the service actually delivered in January is recognized, even though the customer just paid $28,800 in cash for the first year.

Four numbers — $2,400, $28,800, $57,600, and $2,400 — all describing the same customer on the same day. None is wrong. They answer different questions, and using the wrong one in the wrong context is how founders accidentally mislead their own boards.

Why bookings and cash never match revenue

The gap between what a customer commits (bookings), what they pay (cash), and what you have earned (revenue) is normal and healthy in SaaS. Annual-prepay contracts collect cash long before the revenue is recognized, which is fantastic for your bank balance and irrelevant to your income statement. That difference lives in deferred revenue, and it is why a growing SaaS company can show strong cash collections and a modest recognized-revenue line at the same time.

The danger is mixing them. Reporting bookings as if it were revenue overstates the business; treating recurring run rate as cash in the bank overstates liquidity. Keeping the four cleanly separated is what lets you trust each one.

The reporting traps that catch founders

Because these four numbers are all technically "how much money," it is easy to reach for the biggest one. A few specific mix-ups do real damage.

• Quoting bookings as revenue:Announcing a "$500,000 quarter" when that figure is signed contract value, not earned revenue, overstates the business to anyone who assumes GAAP. It also sets up an awkward reconciliation when the income statement shows a fraction of that.
• Treating ARR as cash: A $2M ARR run rate is not $2M in the bank. It is a forward projection that assumes nothing churns. Spending against it as though it were collected cash is how fast-growing companies run out of money.
• Multiplying volatile MRR into ARR: Annualizing a bouncy month-to-month base manufactures a precise-looking ARR that swings wildly. Only annualize revenue that is genuinely durable.
• Ignoring deferred revenue: When customers prepay annually, the cash arrives long before the revenue is earned. Forgetting that the unearned portion is a liability, not profit, flatters the picture.

The through-line is simple: never let the flattering number stand in for the honest one. Each metric is legitimate in its lane, and dishonest the moment it wanders into another's.

Which number to use, and when

Here is the practical rule for the MRR vs ARR vs bookings vs revenue choice: match the metric to the decision.

• Operating the business day to day: use MRR, because it reacts fast and breaks cleanly into new, expansion, contraction, and churn.
• Reporting to boards and investors: use ARR, the shared language of SaaS scale, and pair it with growth rate and retention.
• Measuring sales performance: use bookings, since it captures the full value your sales team committed in the period.
• Filing financials and understanding profitability: use recognized revenue, the GAAP figure that reflects what you have actually earned.

If you are only deciding between the two run-rate metrics, our focused comparison of MRR vs ARR covers that choice in detail.

Keeping all four straight automatically

The reason these terms get muddled in practice is that they usually live in different tools: run rate in a spreadsheet, bookings in the CRM, revenue in the accounting system. When nobody reconciles them, people quote whichever number flatters the moment.

StripeReport connects to Stripe with a read-only key and computes your MRR and ARR from live subscription data, broken into new, expansion, contraction, and churn, so the run-rate side of the picture is always accurate and consistent. Paired with your accounting system for recognized revenue and your CRM for bookings, it gives you a trustworthy anchor for the recurring-revenue metrics that drive most SaaS decisions. Our Stripe ARR tracking guide shows how to set it up, and if you want the foundational concept, start with recurring revenue.

Key takeaways

• MRR and ARR are forward-looking run rates; bookings is committed contract value; revenue is what you have actually earned under accounting rules.
• They diverge because each answers a different time question — current run rate, total commitment, or earned income.
• A single deal can produce four very different numbers, and none of them is wrong.
• Match the metric to the decision: MRR to operate, ARR to report, bookings for sales, recognized revenue for financials.
• Keep the four reconciled across tools so nobody quotes the flattering number by accident.