ARR and MRR vocabulary for non-finance

Someone drops “ARR is up 18%” into a meeting, everyone nods, and then three people open three different slides. One chart shows monthly revenue. One shows contracted value. One shows a number that only matches finance if you squint and exclude trials. Nobody is lying on purpose. They are using adjacent words for different objects.

This is Part 1 of Finance analytics for non-finance, a short series for analysts, PMs, 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.

What you’ll learn

What MRR and ARR mean in plain language, and how they relate without magic
Which revenue pieces usually sit inside or outside “recurring”
How new, expansion, contraction, and churn movement explain period change
Questions that force a shared definition before the chart gets built
A worked SaaS example you can reuse when three dashboards disagree

Why non-finance people still need ARR and MRR

Recurring revenue is the language of subscription businesses, boards, investors, and many modern “usage-ish” products that still bill on a plan. Product teams care because packaging changes 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. Analytics owns the pipeline that turns invoices and subscriptions into slides.

Finance owns the official books. That remains true. The trap is assuming “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 have 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 the grain, name the time window, name the exclusions. ARR and MRR are metrics with strong social status. 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: often MRR times twelve, or a direct annualized view of the same contracts. Ops and product often live in MRR because months match billing and sprint calendars. Boards and many fundraising conversations live in ARR because annual language scales with company size stories.

Side by side cards comparing MRR for ops and monthly tracking versus ARR for annualized board language

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 different ARR if one annualizes list price and the other annualizes 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 MRR normalization is:

A: $100 MRR
B: $1,200 / 12 = $100 MRR
C: $300 / 3 = $100 MRR

Total MRR = $300. A common ARR view is $300 × 12 = $3,600. Cash collected in March might look totally different if B prepaid the year in January. Cash is not MRR. Booked invoices are not always MRR. 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 cadence under a subscription or contract, not a one-time project. Typical inclusions:

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 buckets (policy dependent):

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; 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 run-rate usage from the last N days and call that MRR. Both can be useful. Mixing them silently is how growth stories fall apart under diligence.

Point-in-time stock versus period movement

MRR and ARR are often treated as a stock: the recurring base at a moment (end of month is common). Growth language also needs a flow: how that stock changed between two moments. A simple bridge many SaaS teams use:

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 (a former customer comes back) sometimes sits with new, sometimes as its own line. Reactivation policy should be written next to the logo definition of “customer.” We will go deeper on churn and retention vocabulary in Part 2. For Part 1, 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 logo ARR only. Sometimes they mean new plus expansion minus contraction minus churn. Ask which. “Gross retention” and “net retention” are related cousins that we cover next post; for now, know that “net” almost always means “after something offset something,” and you must name the offset.

Discounts, free months, and other honesty tests

Discounts are where non-finance people get burned. A plan “list” of $200 per month sold at $100 is not $200 of MRR unless your policy says you report list (almost nobody serious does that for investor-facing recurring metrics). Free months create timing choices: do you recognize $0 MRR during the free period, or do you smooth the paid months across the whole term? Either answer can be defended. Neither answer is “obvious.”

Trials are similar. Some teams exclude trials until conversion. Some include trials at $0 and track a separate trial funnel. Including unpaid trials as if they were paying MRR is not a definition; it is wishful thinking.

Multi-year deals with heavy prepay create another fork: cash is early, service is long. MRR still usually reflects the ongoing monthly value of the subscription, not the cash pile that landed in the bank last Tuesday. Finance may also talk about revenue recognition under accounting standards. That is related and not identical. Your dashboard can be directionally right for product ops and still not equal GAAP revenue. Label which universe you are in.

Worked example: three dashboards, one company

Meet Northwind Tools, a fictional B2B SaaS shop. At the end of February, finance reports $500k ARR. Product’s growth dashboard shows $560k ARR. 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. Product is counting free users as if they paid list. Marketing is counting deals that have not started. Finance is counting paying customers who are live. All three might be useful for different jobs. Only one should be labeled “ARR” in the company-wide executive pack unless the pack has three clearly named metrics.

A tiny pseudo-calculation for finance-style MRR on one day might look like this in SQL sketch form (toy grain: one row per 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: how monthly_recurring_amount is built, whether seats are prorated mid-month, and whether end_date means cancel requested or access revoked. The point of the sketch is not production code. It is a checklist of predicates you can demand in a metric spec.

Definition care table agreeing logo churn means lost customers, revenue churn means lost dollars, and expansion means…

Even before Part 2, put “definition care” next to every finance-ish KPI: logo versus revenue, expansion versus new, and what each meeting means by those words. The result 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 this list out loud. Write answers. Do not settle for “standard SaaS definition.” There is no single global standard that every company implements the same way.

Population: Customers, accounts, subscriptions, or contracts?
Status: What statuses count as active? What about paused, delinquent, or pending cancel?
Money basis: List, booked, invoiced, collected, or recognized?
Cadence normalization: How do annual and quarterly plans become monthly?
Discounts and credits: Net of discount? Credits applied how?
Usage: Excluded, estimated, or actual last period?
Services and one-time: Explicitly out, or sneaking in through “total revenue”?
As-of timing: End of day, end of month, or live snapshot?
Currency: Reporting currency and FX policy if multi-country.
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 Slack threads.

Common mistakes

Calling total revenue ARR. Total revenue can include services, one-time fees, and non-recurring usage. ARR is a recurring concept with a policy.
Multiplying last month’s cash by twelve. Cash is lumpy. Annual prepay makes a single month look like a rocket or a crater.
Mixing bookings and live recurring base. Signed future deals are pipeline quality metrics, not the same as today’s recurring stock.
Reporting list price as if it were paid. Leadership likes big numbers. Diligence likes truth.
Changing the definition mid-year without a bridge. Growth can be pure methodology. Always show old and new side by side for a transition period.
Letting BI tools re-filter the official table differently per dashboard. Serve layer filters should not quietly rewrite finance policy. Path thinking from how data moves still applies: the transform should encode the definition once.
Assuming GAAP revenue equals MRR. Related, not identical. Label the universe.

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. Blanks are findings.
Reproduce the headline number from a raw-ish subscription table for one as-of date. Note every filter you needed.
Build a simple MRR bridge for one month: start, new, expansion, contraction, churn, end. If the bridge does not tie, you found a definition or data quality bug.
Schedule a 20-minute review with finance or rev ops. Ask only: “Which of these filters is official?” Capture the answer in the wiki, not only in chat.

Next in this series: churn and retention definitions that stick, including logo 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; ARR is usually the annualized cousin, often MRR × 12 under a written policy.
Recurring is not the same as cash, bookings, or total revenue.
Period change needs a bridge: new, expansion, contraction, churn.
Discounts, trials, usage, and multi-year prepay 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.

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
FASB. Accounting Standards Codification Topic 606 overview materials via FASB (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/