Monthly Recurring Revenue

What is monthly recurring revenue?

Monthly recurring revenue, or MRR, is a SaaS metric that measures predictable monthly income from active software subscriptions. It converts monthly, quarterly, and annual plans into one monthly amount, making subscription growth easier to track. MRR is an operational metric, not formal GAAP or IFRS revenue recognition.

How do you calculate monthly recurring revenue?

Calculate MRR from the subscriptions active on a consistent reporting date.

1. Choose an as-of date, such as the last day of the month.
2. List active paid subscriptions and their recurring prices after discounts.
3. Normalize each plan to a monthly value. Divide quarterly plans by three and annual plans by 12.
4. Exclude canceled subscriptions, unpaid trials, and one-time charges.
5. Add the normalized subscription values to find total MRR.

Monthly recurring revenue example

A software product has 40 customers paying $50 monthly, 12 customers paying $1,200 annually, and five customers on a discounted $30 monthly plan. Its MRR is $2,000 + $1,200 + $150, or $3,350. Although annual customers paid $1,200 upfront, each contributes $100 to MRR because the subscription value is spread across 12 months. A canceled subscription contributes nothing after its end date.

What counts in MRR and what does not?

Clear, consistent inclusion rules prevent misleading month-to-month comparisons.

Benefits of tracking MRR in SaaS

MRR gives product and finance teams a shared view of the subscription base.

• Shows whether recurring revenue is growing, flat, or shrinking.
• Supports near-term forecasting and pricing-change analysis.
• Separates new, expansion, contraction, and churned MRR to reveal retention trends.
• Complements churn, ARPU, ARR, net new MRR, and revenue growth rate.

Limits of monthly recurring revenue

MRR is useful, but it is not a complete financial-health measure.

• It does not equal cash flow, recognized revenue, or profitability.
• Annual prepayments can improve cash without changing normalized MRR.
• Failed payments, credits, and inaccurate subscription statuses can distort results.
• It cannot alone show customer satisfaction or future collections.

MRR reporting practices for software products

Set one as-of date, retain subscription history, document inclusion rules, and reconcile totals with billing records. Report new, expansion, contraction, churned, and reactivated MRR separately rather than relying only on a net total. Teams can create a revenue dashboard or build a subscription product with an AI SaaS builder to make these movements visible. Track SaaS revenue with apps built on Emergent.