MRR versus ARR in one sentence
Monthly recurring revenue (MRR) is the normalized monthly value of an active recurring revenue base. Annual recurring revenue (ARR) expresses that same recurring base on an annual basis.
When the same scope and accounting policy are used:
ARR = MRR × 12
and:
MRR = ARR ÷ 12
The arithmetic is easy. The difficult—and commercially important—work is deciding which customers, contracts, statuses, discounts, and revenue types belong in the recurring base.
MRR and ARR are management metrics, not cash balances. They are designed to remove billing-cycle noise so that a $1,200 annual subscription and a $100 monthly subscription each contribute $100 of MRR. They should not be confused with invoiced amounts, provider payouts, trailing revenue, bookings, or revenue recognized in financial statements.
A precise working definition of MRR
A practical contract-level formula is:
MRR = sum of recurring contract value ÷ months in each contract term
For a monthly snapshot, include the normalized value of eligible subscriptions active on the measurement date. Apply one documented policy consistently to:
- active, trialing, past-due, paused, canceled, and unpaid subscriptions;
- recurring discounts and credits;
- seat or quantity changes;
- usage charges and committed minimums;
- foreign-currency conversion;
- cancellations scheduled for the end of a paid term.
Provider definitions are not universal. Stripe defines MRR as the monthly-normalized value of active and past-due subscriptions, while excluding taxes, free plans, and metered products in its standard calculation; Stripe also lets users configure some discount and subscriber rules. See Stripe Billing analytics. That is a valid provider definition, but it may not match another analytics tool or a company’s board reporting policy.
ChartMogul defines MRR as normalized monthly subscription revenue and calculates a subscription item by dividing its amount by the number of months in the plan interval. Its SaaS metrics reference also distinguishes MRR from bookings, billing cycles, and one-time fees.
What normally belongs in MRR
- monthly subscriptions at their recurring monthly value;
- quarterly, annual, and multi-year subscriptions normalized to one month;
- recurring add-ons and additional seats while active;
- committed recurring minimums, if the policy treats them as contracted recurring value;
- recurring discounts, reflected consistently as gross or net MRR.
What normally does not belong in MRR
- implementation and setup fees;
- lifetime deals;
- consulting and professional services;
- one-time purchases and hardware;
- taxes collected for authorities;
- payment-processor fees;
- the full cash receipt from an annual invoice;
- uncommitted pipeline, unsigned renewals, or projected expansion.
Usage-based revenue needs an explicit policy. Pure, uncommitted usage fluctuates and may not belong in MRR at all; a recurring platform fee or contractual minimum may qualify. Never silently mix last month’s usage into a contract-based MRR figure.
What ARR means—and what it does not
For a business that manages revenue monthly, ARR is usually the current MRR snapshot annualized:
ARR = current MRR × 12
Alternatively, normalize each active contract directly to one year and sum those values. A two-year $24,000 subscription contributes $12,000 of ARR, not $24,000. A monthly $500 subscription contributes $6,000 of ARR while active.
ARR does not mean “revenue collected in the last 12 months.” That is trailing-twelve-month revenue. It also does not automatically mean annualized total revenue. Stripe’s guide to annual recurring revenue explicitly distinguishes recurring ARR from annualized run rate, which may extrapolate all revenue from a short period. The acronym is used inconsistently in practice, so a report should spell out whether ARR means annual recurring revenue or annualized run rate.
ARR is useful because it creates a common annual scale for recurring businesses and valuation discussions. SaaS Capital describes current recurring scale as a starting point for valuation while emphasizing that growth, retention, margins, customer acquisition, and other factors affect the multiple. ARR is not a valuation by itself, and it does not measure cash, profit, or runway.
The MRR waterfall
A single ending balance hides how the business changed. A recurring-revenue roll-forward separates the movements:
- New MRR: first-time recurring revenue from newly paying customers.
- Expansion MRR: increases from existing customers, such as upgrades, more seats, or additional subscriptions.
- Reactivation MRR: recurring revenue from customers returning after churn.
- Contraction MRR: decreases from existing customers that remain active, such as downgrades, fewer seats, or newly applied discounts.
- Churned MRR: recurring revenue lost when the customer’s final active subscription ends.
The basic waterfall is:
Ending MRR = Starting MRR + New + Expansion + Reactivation − Contraction − Churn
If the reporting currency changes the value of existing subscriptions, show foreign-exchange impact as a separate bridge:
Ending MRR = Starting MRR + operating movements ± FX adjustment
Do not hide FX gains inside expansion or FX losses inside churn. ChartMogul’s MRR movement documentation shows how event timing, discounts, multiple subscriptions, and churn-recognition settings can change movement classifications even when the ending balance remains correct.
Worked example: MRR, ARR, and cash diverge
Assume a SaaS company starts April with $18,000 of MRR. During April it records:
- $2,400 of new MRR;
- $900 of expansion MRR;
- $300 of reactivation MRR;
- $500 of contraction MRR;
- $1,200 of churned MRR;
- a $100 negative FX adjustment.
First calculate net operating movement:
$2,400 + $900 + $300 − $500 − $1,200 = $1,900
Then calculate ending MRR:
$18,000 + $1,900 − $100 FX = $19,800
At the April measurement date:
ARR = $19,800 × 12 = $237,600
Now suppose the provider collected $16,800 from monthly invoices, $18,000 in annual prepayments, and $3,000 in setup fees during the latest 30 days, then processed $1,000 of refunds:
Trailing-30-day provider-reported revenue = $16,800 + $18,000 + $3,000 − $1,000 = $36,800
The $36,800 trailing figure is not MRR. It includes annual cash billed upfront and non-recurring setup work, while MRR normalizes the current recurring base. The $237,600 ARR is also not a forecast that $237,600 will necessarily be collected or recognized over the next year: customers can churn, expand, fail to pay, or renew on different terms.
Use the MRR and ARR calculator to test the normalization and waterfall. Keep the subscription schedule beside the result so the formula remains auditable.
When you need to separate logo churn, GRR, and NRR for the opening cohort, use the SaaS churn and retention calculator.
Why RevenueBug’s headline number can differ
RevenueBug uses trailing-30-day provider-reported revenue as its cross-provider headline metric. That figure should not be interpreted as native subscription MRR. The cross-provider approach is necessary because connected systems expose different source records and business models: one may supply payment transactions, another store orders, and another app subscription analytics.
Provider scope also varies. A connection may represent an account, store, organization, project, app, or—in some cases—a narrower product view. Some accounts contain several products, and not every provider offers reliable product-level attribution. RevenueCat’s Charts and Metrics API, for instance, documents project revenue across all apps and chart-specific filters whose availability varies. Provider permissions also differ; do not infer that every credential is read-only from the existence of a verified connection.
Read the RevenueBug methodology and relevant integration documentation before comparing a profile with a native billing dashboard. Browse startup profiles using the visible metric label, period, scope, and freshness—not the superficial fact that each figure is denominated in dollars.
A practical MRR and ARR reconciliation
Use this framework monthly and whenever a metric moves unexpectedly.
1. Write the policy before calculating
Define the reporting date, time zone, eligible subscription statuses, discount treatment, usage policy, churn date, tax treatment, currency source, and whether MRR is gross or net of recurring discounts. Version the policy when it changes.
2. Build the opening balance
Retain the prior period’s customer- and subscription-level closing schedule. It should sum exactly to starting MRR. If it does not, record an opening adjustment rather than forcing the new month to balance.
3. Recalculate each active subscription
Normalize each eligible recurring line by its term. Confirm quantities, plan changes, pauses, cancellations, and annual renewals. Keep original currency alongside converted currency.
4. Classify every movement
Map the change from opening to closing as new, expansion, reactivation, contraction, churn, or FX. A customer moving between plans may have no net change; do not manufacture growth by recording a full churn and full new sale without disclosing the convention.
5. Maintain an exclusion register
List setup fees, services, one-time purchases, lifetime deals, taxes, uncommitted usage, test transactions, and duplicate records excluded from MRR. This prevents the same questionable item from being debated every month.
6. Reconcile—but do not equate—other ledgers
Bridge MRR separately to invoices, cash collections, trailing provider revenue, recognized revenue, deferred revenue, and bank deposits. Annual billing and payout timing create expected differences. A reconciliation is successful when every difference is explained, not when unlike metrics are forced to match.
7. Review exceptions and lock the snapshot
Investigate large movements, negative values, past-due accounts, unexpected plan intervals, missing currencies, and manual overrides. Save the source export, policy version, calculation, and approval date so later corrections can be traced.
For a founder preparing to list a startup, this monthly pack is more useful than a screenshot: it lets a buyer reproduce the recurring base and understand why it differs from the public trailing-revenue chart.
Common MRR and ARR mistakes
Counting annual cash upfront. A $12,000 annual subscription contributes $1,000 of MRR during its eligible term, not $12,000 in the billing month.
Annualizing a launch spike. Multiplying a strong month containing lifetime deals or setup work by 12 produces a revenue run rate, not recurring ARR.
Mixing snapshots and flows. MRR is a balance at a point in time; new MRR and churn are movements during a period. Adding all invoices in a month does not reproduce the ending snapshot.
Leaving the denominator undocumented. Customer counts, plan intervals, quantities, discounts, and currencies must correspond to the same date and policy as the MRR total.
Ignoring past-due and churn settings. One tool may retain a past-due subscription while another removes it. The difference is definitional until the policy and source status are compared.
Combining several products without disclosure. Account-level recurring revenue should not be presented as product-level MRR unless the source supports the allocation.
Changing definitions without restating history. A new discount or usage policy creates a break in the series. Either restate comparable periods or label the change clearly.
Frequently asked questions
Is ARR always MRR multiplied by 12?
Yes when ARR and MRR use the same scope, date, currency, and inclusion policy. If the ARR schedule includes contracts or adjustments absent from MRR, multiplying by 12 will not reconcile and the definitions must be explained.
Should an annual subscription count when it is paid or over the year?
For MRR, normalize it over the subscription term: a $1,200 annual subscription contributes $100 per month while eligible. Cash reporting records the collection when paid, and accounting revenue can follow a separate recognition schedule.
Are usage-based charges included in MRR?
There is no universal rule. A committed recurring minimum can reasonably be separated from variable overage; uncommitted usage is often excluded or reported as usage revenue. Document the policy and do not compare metrics built under different rules without adjustment.
Is RevenueBug’s trailing-30-day revenue the same as MRR?
No. RevenueBug’s headline figure is qualifying provider-reported revenue in a rolling 30-day window. It may include annual payments and non-recurring transactions, while MRR normalizes eligible active recurring subscriptions.
Can ARR be used as the value of a startup?
No. ARR is one input, not an appraisal. Growth, retention, customer concentration, gross margin, owner dependence, intellectual property, liabilities, and deal terms all affect value. Verified revenue also does not establish profitability or ownership.