What MRR, ARR, and Bookings Actually Mean (And Why Founders Mix Them Up)

What MRR, ARR, and Bookings Actually Mean (And Why Founders Mix Them Up)

A founder told an investor his company was "at $2M ARR." The investor asked to see the recognized revenue. It was $640,000.

He wasn't lying. He just didn't know the difference between four numbers that all look like "revenue" on a slide and mean wildly different things in reality. That's the whole reason MRR vs ARR vs bookings explained is a search anybody running a subscription business eventually makes — usually right before a raise, when the gap between the story and the GAAP statement suddenly matters.

Here's what each number actually means, where they diverge, and why mixing them up is the fastest way to look amateur in a data room. Consider this your plain-English set of SaaS metrics definitions — the four that matter most.

Bookings: cash you've been promised, not cash you've earned

A booking is the total contract value a customer commits to when they sign. If a customer signs a 2-year deal at $5,000 per month, that's a $120,000 booking the day the ink dries.

Notice what hasn't happened: you haven't delivered the software for 24 months, and you may not have collected a dollar. Bookings measure sales momentum — how much demand your sales team is closing. That's useful. It is also the single most misused number in SaaS, because $120,000 booked feels a lot like $120,000 earned, and it is not.

Bookings are a leading indicator. Revenue is the trailing reality. Confusing the two is how the $2M-that's-really-$640K conversation happens.

MRR and ARR: your recurring run-rate, normalized

MRR (Monthly Recurring Revenue) is the predictable, subscription-based revenue you'd collect in a given month if nothing changed. ARR (Annual Recurring Revenue) is just MRR times 12 — the same number wearing a yearly coat.

The word that does all the work here is recurring. A one-time $20,000 setup fee is real money, but it isn't MRR, because it doesn't repeat. If you have 100 customers each paying $500/month in subscription fees, your MRR is $50,000 and your ARR is $600,000. Clean.

MRR and ARR are run-rate metrics. They answer "at today's pace, what does a year look like?" — not "what did we actually earn last quarter?" That distinction matters more than founders expect, because run-rate assumes a stable world, and SaaS is not a stable world. Churn, downgrades, and upgrades move MRR every month.

GAAP revenue under ASC 606: the number MRR vs ARR vs bookings can't show you

Now the number your accountant and your auditor care about. Under ASC 606, the FASB revenue-recognition standard that governs contracts with customers, you recognize revenue as you satisfy the performance obligation — meaning as you actually deliver the service over time.

ASC 606 lays out a five-step model: identify the contract, identify the performance obligations, determine the transaction price, allocate that price to the obligations, and recognize revenue as each obligation is satisfied. For most SaaS, "satisfied over time" means you earn that subscription revenue ratably — a little each day the customer has access.

So that $120,000 two-year booking? Under ASC 606 you recognize roughly $5,000 a month for 24 months. In month one, your bookings say $120,000, your MRR says $5,000, and your recognized GAAP revenue says $5,000. Same contract. Three numbers. All correct. The other $115,000 sits on your balance sheet as deferred revenue — a liability, because you owe the customer service you haven't delivered yet.

MRR vs ARR vs bookings, explained by where founders mix them up

The confusion isn't stupidity. It's that every number is "true" from a different vantage point, and founders default to the biggest one.

Here's the pattern that gets people in trouble:

• Quoting bookings as ARR. You sign a $120,000 two-year deal and tell people you "added $120K of ARR." You didn't — you added $60K of ARR (the annualized run-rate) and booked $120K of total contract value. This is the most common way founders overstate their own growth.
• Counting one-time fees in MRR. Setup fees, implementation, professional services — real revenue, not recurring. Including them inflates the metric investors use to value you.
• Forgetting deferred revenue exists. Collecting a year upfront feels like a great month. On the GAAP statement, eleven-twelfths of it is a liability, not earnings.

The cost shows up in a diligence process. When an investor's analyst reconciles your ARR claim against your recognized revenue and finds a 3x gap nobody flagged, the issue stops being the gap. It becomes whether they can trust any number you gave them.

Get the definitions right before someone else checks them

Investors expect you to know this cold. The founders who raise cleanly aren't the ones with the biggest ARR slide — they're the ones whose bookings, MRR, ARR, and ASC 606 revenue all reconcile and who can explain the differences in one breath.

That reconciliation is exactly the kind of work a SaaS-specialized bookkeeper sets up before you need it. Deferred revenue schedules, ASC 606-compliant recognition, a clean bridge from bookings to MRR to GAAP revenue — built once, so the data room doesn't surprise you.

Find a bookkeeper who speaks SaaS, not just spreadsheets

Bookings vs revenue in SaaS isn't a quirk you can wing on the night before a raise. It's an accounting structure, and most generalist bookkeepers don't build it because most of their clients don't need it.

The SaaS Bookkeeper works specifically with technology and subscription companies — the practices where deferred revenue, ASC 606, and the bookings-to-ARR bridge are the everyday job, not a once-a-year scramble.

Read their verified reviews on Sam's List, then book an intro call. Walk in knowing which number you're actually quoting — and able to prove it.