Annual recurring revenue (ARR) and monthly recurring revenue (MRR) are the money your customers pay you again and again, counted per year or per month. They sound simple, but in a meeting they often mean different things to different people. Write down one shared definition before anyone compares numbers, and this post gives you the plain words to do it.
Say someone drops “ARR is up 18%” into a meeting and everyone nods. Then three people open three different slides. One chart shows monthly revenue, one shows contracted value, and one shows a number that only matches finance if you squint and exclude trials. Nobody is lying on purpose. They are using neighboring words for different things.
This post opens Finance analytics for non-finance, a short series for analysts, product managers, marketers, and operators who live next to subscription numbers without owning the general ledger. You do not need to become a controller. You do need a vocabulary that survives a definition fight.
Why non-finance people still need ARR and MRR
Recurring revenue is the language of subscription businesses, boards, investors, and many modern products that bill on a plan even when usage varies. Product teams care because changes to packaging move the number. Marketing cares because acquisition campaigns get judged against it. Customer success cares because retention and expansion sit inside the same family of metrics, and analytics owns the pipeline (the automatic steps) that turns invoices and subscriptions into slides.
Finance owns the official books, and that remains true. The trap is assuming that “official” means everyone already knows what we mean when we say ARR. Official usually means this number reconciles under a written policy. Your warehouse may hold five almost-ARR fields built by five almost-policies.
If you have worked through the metrics series on Analytics Made Simple, this will feel familiar. Name the object, name what one row means, name the time window, and name the exclusions. ARR and MRR are metrics with strong social status, but status does not replace a definition.
Rule of thumb: If two people can both be “right” about ARR and still disagree by double digits, you do not have a math problem. You have a dictionary problem.
MRR and ARR in one picture
Start simple. MRR is monthly recurring revenue, the normalized monthly value of active recurring subscriptions at a point in time, or for a period, depending on policy. ARR is annual recurring revenue, which is often MRR times twelve, or a direct annualized view of the same contracts. Operations and product teams often live in MRR because months match billing and sprint calendars. Boards and many fundraising conversations live in ARR because annual language scales with the story of a company’s size.
The conversion is not always “multiply by twelve and stop thinking.” Annual plans, multi-year deals, prepaid discounts, and mid-month changes force policy choices. Two healthy teams can both annualize correctly and still land on different ARR, if one annualizes list price and the other annualizes the cash collected after discount.
A normalization example you can hold in your head
Imagine three active customers on the last day of March.
- Customer A pays $100 per month on a monthly plan.
- Customer B pays $1,200 once per year up front for the same product.
- Customer C pays $300 per quarter.
A common way to normalize each one to a monthly figure looks like this.
- A: $100 MRR
- B: $1,200 / 12 = $100 MRR
- C: $300 / 3 = $100 MRR
Total MRR is $300, and a common ARR view is $300 × 12 = $3,600. Cash collected in March might look totally different if customer B prepaid the year in January. Cash is not MRR, booked invoices are not always MRR, and deferred revenue on the balance sheet is not MRR either, even though all of these numbers are about money and time.
What usually counts as recurring
Recurring means the business expects the charge to continue on a known schedule under a subscription or contract, and not as a one-time project. Typical inclusions are simple.
- Base subscription fees for software, seats, or plans
- Contracted platform fees billed monthly or annually
- Sometimes minimum commitments that behave like a floor subscription
Typical exclusions, or separate groupings, depend on policy.
- One-time implementation or onboarding fees
- Professional services projects
- Hardware sales
- Purely usage overage that is not contractually recurring (some teams still model expected usage, so write that down)
- Non-recurring marketplace take rates, unless you deliberately redefine the metric
Usage-based pricing is where meetings get spicy. Some companies report “recurring” as the subscription minimum only. Others estimate a run rate from the usage of the last N days and call that MRR. Both approaches can be useful, and mixing them silently is how growth stories fall apart under diligence, the deep check an investor or buyer runs on your numbers.
Point-in-time stock versus period movement
MRR and ARR are often treated as a stock, meaning the recurring base at one moment, with the end of the month being common. Growth language also needs a flow, which is how that stock changed between two moments. Many subscription software teams use a simple bridge with six parts.
- Starting MRR
- Plus new MRR from newly acquired customers
- Plus expansion MRR from existing customers buying more
- Minus contraction MRR from downgrades
- Minus churned MRR from customers who left
- Equals ending MRR
Reactivation, when a former customer comes back, sometimes sits with new and sometimes gets its own line. Write the reactivation policy next to your definition of who counts as a customer. The next post in this series goes deeper into churn and retention vocabulary. For now, remember that a single ARR headline hides a four-way tug of war between new, expand, contract, and leave.
Gross versus net language
People say “net new ARR” in at least two ways. Sometimes they mean new-customer ARR only, and sometimes they mean new plus expansion minus contraction minus churn. Ask which one they mean. “Gross retention” and “net retention” are related cousins that the next post covers, and for now you only need to know that “net” almost always means “after something offset something,” so you must name the offset.
Discounts, free months, and other honesty tests
Discounts are where non-finance people get burned. A plan with a list price of $200 per month that sells at $100 is not $200 of MRR, unless your policy says you report list price, and almost nobody serious does that for investor-facing recurring metrics. Free months create timing choices. You can recognize $0 MRR during the free period, or you can smooth the paid months across the whole term. Either answer can be defended, and neither is obvious.
Trials are similar. Some teams exclude trials until the customer converts, and some include trials at $0 and track a separate trial funnel. Including unpaid trials as if they were paying MRR is wishful thinking and does not count as a definition.
Multi-year deals with heavy prepayment create another fork, because the cash arrives early while the service runs long. MRR still usually reflects the ongoing monthly value of the subscription, and not the cash pile that landed in the bank last Tuesday. Finance may also talk about revenue recognition under accounting standards. That is related to MRR and is not identical to it, so your dashboard (a screen of charts that tracks key numbers) can be directionally right for product and operations and still not equal revenue under generally accepted accounting principles (GAAP). Label which universe you are in.
Worked example: three dashboards, one company
Imagine a fictional business-to-business software company that sells tools to other companies. At the end of February, finance reports $500k ARR. The product team’s growth dashboard shows $560k ARR, and marketing’s “booked” board shows $610k ARR. Leadership wants one number by Friday.
You interview the three builders and write a definition card.
| Source | Includes | Excludes | Timing |
|---|---|---|---|
| Finance ARR | Paid active subscriptions, annualized after discount | Services, trials, one-time fees | End-of-month active status |
| Product ARR | Paid + free-tier accounts valued at list plan price | Services only | Live snapshot whenever the job ran |
| Marketing ARR | Signed contracts including future start dates | Nothing much | Signature date, not start date |
Now the gaps make sense. The product team is counting free users as if they paid list price, and marketing is counting deals that have not started yet. Finance is counting paying customers who are live today. All three numbers might be useful for different jobs, but only one should carry the label “ARR” in the company-wide executive pack, unless the pack shows three clearly named metrics.
A tiny pseudo-calculation for finance-style MRR on one day might look like the SQL (the standard language for asking a database for data) sketch below, where each row is one subscription.
SELECT
DATE '2026-02-28' AS as_of_date,
SUM(monthly_recurring_amount) AS mrr,
SUM(monthly_recurring_amount) * 12 AS arr
FROM subscriptions
WHERE status = 'active'
AND plan_type = 'recurring'
AND trial_flag = FALSE
AND as_of_date BETWEEN start_date AND COALESCE(end_date, DATE '9999-12-31');That sketch still hides hard choices, such as how monthly_recurring_amount is built, whether seats are prorated mid-month, and whether end_date means a cancel was requested or access was actually revoked. The point of the sketch is not production code. It is a checklist of conditions that you can demand in a metric spec.
Even before the next post, put a “definition card” next to every finance-flavored KPI (key performance indicator, a number the team is judged on), covering customers versus revenue, expansion versus new, and what each meeting means by those words. The card above is a mini contract you can paste into a metric wiki.
A definition checklist you can run in a meeting
When someone says ARR or MRR, walk through this list out loud and write down the answers. Do not settle for “standard SaaS definition,” because there is no single global standard that every company implements the same way.
- Population: are we counting customers, accounts, subscriptions, or contracts?
- Status: which statuses count as active, and what about paused, delinquent, or pending cancel?
- Money basis: do we use list price, booked, invoiced, collected, or recognized amounts?
- Cadence normalization (converting every plan to the same monthly amount): how do annual and quarterly plans become monthly?
- Discounts and credits: is the figure net of discount, and how are credits applied?
- Usage: is it excluded, estimated, or the actual amount from last period?
- Services and one-time fees: are they explicitly out, or sneaking in through “total revenue”?
- As-of timing: do we measure at end of day, end of month, or a live snapshot?
- Currency: what is the reporting currency, and what is the exchange-rate policy if you sell in several countries?
- Owner: who can change the definition, and where is it documented?
If your company already maintains metric contracts, put ARR and MRR next to the rest of your data quality and stewardship habits. The data stewardship series is a useful companion when definitions keep living only in chat threads.
Common mistakes
- Calling total revenue ARR. Total revenue can include services, one-time fees, and non-recurring usage, while ARR is a recurring concept with a policy.
- Multiplying last month’s cash by twelve. Cash is lumpy, and an annual prepayment makes a single month look like a rocket or a crater.
- Mixing bookings with the live recurring base. Signed future deals measure the quality of your pipeline, and they are not the same as today’s recurring stock.
- Reporting list price as if it were paid. Leadership likes big numbers, but diligence likes truth.
- Changing the definition mid-year without a bridge. Growth can be pure methodology, so always show the old and new definitions side by side for a transition period.
- Letting business intelligence (BI) tools filter the official table differently on every dashboard. The layer that serves data should not quietly rewrite finance policy, so the transform should encode the definition once.
- Assuming GAAP revenue equals MRR. They are related and not identical, so label the universe you are in.
How to practice
- Pick one live ARR or MRR chart in your company, or invent a toy subscription table if you are learning solo.
- Write a one-page definition answering the ten checklist questions above. Leave blanks where you do not know, because blanks are findings.
- Reproduce the headline number from a raw-ish subscription table for one as-of date, and note every filter you needed.
- Build a simple MRR bridge for one month with start, new, expansion, contraction, churn, and end. If the bridge does not tie out, you found a definition or data quality bug.
- Schedule a 20-minute review with finance or revenue operations and ask only “which of these filters is official?” Capture the answer in the wiki, and not only in chat.
The next post in this series covers churn and retention definitions that stick, including customer churn versus revenue churn, and why net retention can look healthy while customers quietly leave. For broader paths, see the Learn hub. If your recurring metrics sit on messy event data, pair this with solid SQL and quality habits from the SQL series and data quality series.
Quick recap
- MRR is the monthly recurring base, and ARR is usually the annualized cousin, often MRR × 12 under a written policy.
- Recurring is not the same as cash, bookings, or total revenue.
- Change over a period needs a bridge of new, expansion, contraction, and churn.
- Discounts, trials, usage, and multi-year prepayment force explicit choices.
- When dashboards disagree, build a definition card before you rebuild charts.
- Non-finance partners do not need ledger mastery. They need shared words and an owner for the dictionary.
Series notes
This is Part 1 of the Finance analytics for non-finance series. Related: metrics and data stewardship.
Sources
- Stripe. “Recurring payments” product docs (how subscription billing objects behave in a common processor). https://docs.stripe.com/billing/subscriptions/overview
- ChartMogul. “SaaS metrics” knowledge base (practical ARR/MRR and related metric definitions used by many subscription teams). https://blog.chartmogul.com/saas-metrics/
- ProfitWell (Paddle). “SaaS metrics” guides (MRR components and retention-related vocabulary for operators). https://www.paddle.com/resources/saas-metrics
- Financial Accounting Standards Board (FASB). Accounting Standards Codification Topic 606 overview materials (revenue recognition is related to, not identical with, MRR). https://www.fasb.org/page/PageContent?pageId=/standards/accounting-standards-codification.html
- OpenView. “SaaS benchmarks” and metric explainers (industry usage of ARR language in growth contexts; treat benchmarks as context, not law). https://openviewpartners.com/blog/
Keep going
Same lessons in your feed
Short diagrams, hooks, and weekly tutorials on Substack, Instagram, X, and Facebook.
