An annual subscription can create a large payment today and no payment next month. That does not mean the recurring business disappears between those moments. MRR expresses a monthly-normalised recurring base; payments describe movements of money. Keeping them separate helps you understand performance without presenting the billing calendar as an equivalent change in subscriptions. Begin by writing the question each figure is supposed to answer for your team.
Start with a simple example
Imagine ten subscriptions at €20 per month and two at €240 per year. If they all qualify under your chosen definition, their normalised monthly contribution is €200 plus €40: €240 MRR. This hypothetical example leaves out tax, discounts and special cases. If both annual plans are charged today, the money received that day differs from the normalised monthly figure. Multiplying that day's collections would not provide a sensible estimate of a typical month.
Document the provider's definition
Stripe documents its MRR calculation and offers configurable criteria for certain metrics. Before comparing its dashboard with another report, record which subscriptions, statuses and discounts each calculation includes. The official documentation is the reference for Stripe's calculation. Different definitions can produce different numbers without an arithmetic mistake. If a team changes its reporting convention, record the date and explain what that means for historical comparisons rather than silently presenting the new series as unchanged.
Investigate what drives the movement
For an internal review, separate new business, increases, reductions, reactivations and cancellations in the recurring base. This leads to more useful questions than whether MRR went up. Small net growth might combine many new subscriptions with several large cancellations. Inspect the cases before crediting a pricing change with the outcome. A temporal association does not establish that a particular campaign caused expansion or prevented churn. Keep unresolved explanations visible in the review notes.
Keep a separate collections view
Prepare another report for collected payments, refunds and their recording periods. Billing schedules can produce spikes in that view even when the subscription base changes little. Label both charts clearly and do not call either one profit: neither describes all business costs by itself. Use the appropriate records and criteria for accounting decisions. An operational metric card should not replace those records or become a shortcut for a financial statement it was never designed to represent.
End the discussion with specific cases
When MRR changes, identify the subscriptions behind the movement and assign a review to someone who knows those accounts. When collections change, investigate billing timing and individual operations. Retain currency, period and definition in the shared report. ClawStud lets you consult Stripe subscription metrics alongside the rest of the dashboard. To examine a calculation or resolve a discrepancy, return to Stripe's underlying records rather than assuming every tool applies precisely the same convention.
Official reference: Stripe: Billing analytics.
Read next: Traffic dropped: a checklist before you change anything.
