Monthly Recurring Revenue (MRR): Formula, Examples and Stripe Checks
Published November 1, 2026 · Written by Aanart

Monthly recurring revenue (MRR) is the monthly value of the subscriptions included in your reporting policy. A $1,200 yearly subscription contributes $100 to MRR, even if the customer pays the whole amount on one day. Normalising billing intervals lets you compare recurring value across monthly and annual plans.
Use SourcetoMCP’s Stripe connector to check a current list-price snapshot alongside Stripe Billing analytics. This guide covers the MRR formula, a monthly change breakdown and the rules to check when two reports disagree.
Calculate MRR from recurring subscription prices
For a fixed-price subscription item, multiply its recurring price by its quantity and divide by the number of months in the billing interval. Sum the resulting monthly amounts for the items included in the metric. A two-month plan priced at $180 per interval contributes $90 per month. For weekly or daily billing, document the average-month convention so another analyst can reproduce the calculation.
This hypothetical example uses one currency, fixed prices before discount and an explicit policy excluding trials and one-time charges.
| Subscription group | Quantity | Price and interval | MRR contribution |
|---|---|---|---|
| Starter | 30 | $60 monthly | $1,800 |
| Pro | 8 | $1,200 annually | $800 |
| Team seats | 20 | $180 every two months | $1,800 |
| Free trials | 5 | $60 monthly after trial | $0 under this policy |
| One-time onboarding | 2 | $250 once | $0 |
| Total | $4,400 |
Using 12 times this snapshot, the annualised run rate is $52,800. That expresses the present run rate in annual terms. It does not forecast renewals or cash collections. For cash activity, see the Stripe reporting guide.
Write down what belongs in MRR
Decide which subscription statuses count, how discounts apply, whether prices include taxes and how to handle usage-based charges. Record what happens when a customer schedules cancellation, goes past due or starts a trial. Keep one-off invoices out of a recurring subscription calculation. Report different currencies separately or give your conversion rate and date.
Stripe Billing analytics normally includes monthly-normalised active and past-due subscription value and excludes taxes and metered products from standard MRR. Stripe’s dashboard settings can affect how discounts are handled, and item-level trial offers can affect which subscription items contribute. Check the actual configuration before comparing the dashboard with a list-price calculation.
Explain the change from opening to closing MRR
Use matching snapshots or a Billing analytics movement export to account for gains and losses. Give each change a category: new subscriptions, reactivations, expansions, contractions or churn. Compare like currencies and definitions first. If you consolidate across currencies, show exchange-rate impact separately.
| Movement | Hypothetical amount |
|---|---|
| Opening MRR | $4,400 |
| New and reactivated | +$360 |
| Expansion | +$240 |
| Contraction | −$100 |
| Churn | −$300 |
| Closing MRR | $4,600 |
The increase is $200, or about 4.5% of opening MRR. New and expanded business contributed $600, and contraction and churn removed $400. If the $360 came from new or reactivated customers outside the starting cohort, net revenue retention for the opening cohort in this example is ($4,400 + $240 − $100 − $300) ÷ $4,400, about 96.4%. Ending MRR can grow while the original cohort shrinks.
Compare the Stripe dashboard with a connected snapshot
The connected Stripe subscription metrics report calculates a current snapshot at list price, before discounts and tax. It includes active and past-due subscriptions, and separates subscriptions in trial status. A subscription marked to cancel at period end still contributes while it remains billable under that definition. The snapshot does not model every item-level trial or discount rule from the Dashboard. Unpriced items are counted and excluded rather than assigned a guessed amount.
The operation can read up to 5,000 subscription records and reports a warning when the list is cut short. A request for today’s snapshot cannot recreate a past month’s subscriber state. For historical movement, use the Stripe Billing export or snapshots taken under a consistent policy. Save the capture time, status rules and currency along with each snapshot. A price breakdown helps locate a difference, but the connector returns the top ten prices per currency rather than a full item ledger.
Ask AI to reconcile an MRR difference
Read the current Stripe subscription snapshot for [account]. Confirm the live or test connection, capture time and currencies. Return list-price MRR, annual run rate, active, past-due, trial and cancelling counts, top price contributions, unpriced items and coverage warnings. Compare with my supplied Billing Analytics export only after aligning date and currency. Check discounts, trial handling, status, billing intervals and missing subscriptions. For historical movement use the exports or snapshots I provide. Show any unexplained difference. Make no changes.
Keep the report’s basis beside every total. If you choose list-price MRR for an operating review and discounted MRR for another report, label both so the same change is interpreted consistently. Follow Stripe for Claude to set up the connection.
Platform guidance and SourcetoMCP capabilities checked on 14 November 2026. Worked figures are hypothetical examples.