Skip to content
Churn & retentionMetric 32 of 35

At-Risk MRRPast-Due Subscriptions

Revenue that hasn't churned yet, but is one failed retry away from it.

Abderrahim Ben Jazia, PhDBy · Founder of FlowMRR, previously built and sold AIS (Avance Immédiate Services), French tax-credit softwareUpdated:

Ready to act on this metric? See how FlowMRR helps you recover failed Stripe payments right inside your Stripe MRR dashboard.

Monthly subscription value exposed to payment failures while Stripe is still retrying: subscriptions in the past_due state, which remain in active MRR. Unpaid subscriptions are not at risk any more: they churned at the end of the last period they paid for, and are reported separately as churned but recoverable. The amount to recover is past_due plus unpaid, so the recovery queue and the at-risk figure are not the same population.

Formula

At-Risk MRR = MRR on subscriptions currently past_due in Stripe

Worked example

$60,000 MRR, including $2,400 past_due for 3 days and $1,500 past_due for 20 days → $3,900 at risk (6.5% of MRR). Stripe unpaid means retries are exhausted, not that another retry is pending; in FlowMRR an unpaid subscription is already out of MRR and appears as churned, recoverable.

Other definitions you will see

Some dashboards count past_due and unpaid together as at risk, or use open invoice amounts rather than MRR; both give a larger figure than FlowMRR's past_due-only MRR. FlowMRR shows that wider total as the amount to recover.

Illustrative comparisons

At-risk share of MRR

These unsourced ranges are illustrative scenarios, not measured industry benchmarks, percentiles or recommended targets. Their qualitative labels are editorial interpretations. Compare your own cohorts using the same segment, period, currency and measurement basis.

Healthy
< 2%
Middle scenario
2–5%
Dunning falling behind
> 5%

Why it matters

At-risk MRR is a leading indicator of possible involuntary churn. Segment by time since payment failure: fresh past-due accounts may respond to automated retries, while older cases need outreach. Unpaid accounts have exhausted retries and may need a manual payment or reactivation. Keep recoverable value separate from the active MRR base when reporting the ratio.

Common mistakes

  • Treating all at-risk MRR the same regardless of aging — a day-2 past-due and a day-25 past-due need very different playbooks.
  • Counting unpaid subscriptions as at risk: they have already churned, so they belong in the amount to recover, not in at-risk MRR.
  • Waiting for Stripe's default retry schedule instead of prioritising manual outreach on your highest-value at-risk accounts.
  • Not reporting at-risk MRR to the board — it's a truer picture of near-term revenue health than the churn number reported last month.

Calculating it from Stripe data

Two Stripe statuses are involved, and they should not be added into one at-risk figure. A past_due subscription has a failed payment that Stripe is still retrying; the customer has not left and the subscription is still in MRR. When the retries run out, Stripe does what your settings say: cancel the subscription, mark it unpaid, or leave it past_due. An unpaid subscription has stopped paying and is already churned, as of the end of the last period it actually paid for. At-risk MRR is therefore the MRR of past_due subscriptions only. Unpaid MRR is reported beside it as churned but still recoverable, and the amount to recover is past_due plus unpaid.

Value each subscription on the same basis as headline MRR (list price × quantity, normalised to a month, net of forever discounts) and sum all its items, so a base plan with seats counts once. Count subscriptions, not invoices: a subscription with three open invoices is one subscription at risk. Disputes are charges contested by the cardholder, not MRR, and do not belong in this figure. On a multi-currency account, convert at one rate date so the at-risk share is comparable with MRR.

Age each case from the date payment first failed: the subscription's oldest open invoice or, failing that, the customer's open invoices that belong to no subscription, then the end of the last paid period. FlowMRR sorts the amount to recover into six buckets of days in dunning (under 7, 7–14, 14–21, 21–30, 30–60, over 60) that together sum to the total, and separates cases Stripe is still retrying from cases that need you, such as a hard decline that no retry will fix. Customers you archive from recovery are left out of every figure.

Reading the result

Track the at-risk share of MRR over time together with its decline codes. A rise driven by soft declines, such as insufficient funds, is often recovered by retries and reminders; a rise in hard declines, such as lost, stolen or expired cards, needs the customer to update their payment method, and retrying alone will not help. Many subscriptions moving from past_due to unpaid means your retry window is short compared with how fast customers respond.

Work in order of value and age: high-MRR subscriptions early in dunning first, because they are worth the most and are still the easiest to save. Unpaid subscriptions are not lost for good: a customer who pays the open invoice can be reactivated, which is why they stay in the recovery worklist. Report at-risk MRR to the board as part of revenue quality, and report recovered payments as collected cash, not as new MRR.

Frequently asked questions

What does past_due mean in Stripe?

A subscription is past_due when payment on its latest invoice failed or was not attempted, and Stripe is still trying to collect. It keeps that status until the invoice is paid, or until retries run out and your settings cancel the subscription, mark it unpaid or leave it past_due.

What is the difference between past_due and unpaid in Stripe?

past_due means Stripe is still retrying the payment. unpaid means retries are over: the subscription stays in place and invoices are still created, but no payment is attempted automatically. For revenue reporting, past_due MRR is still in MRR and at risk; unpaid MRR has churned but remains recoverable if the customer pays.

How do you calculate MRR at risk?

Sum the monthly-normalised MRR of subscriptions currently past_due, each counted once across its items, and divide by total MRR to get the share. Report unpaid subscriptions separately: they are no longer in MRR, but their value is still recoverable, and past_due plus unpaid gives the total amount to recover.

How long does Stripe retry a failed subscription payment?

It depends on your settings. With Smart Retries, Stripe picks the retry times within a window and a number of attempts that you configure; with a custom schedule, you choose the days. When the last attempt fails, the subscription is cancelled, marked unpaid or left past_due, as your settings specify.

Contact us
FlowMRR

Let's talk

A question, a technical issue or an idea for a partnership? Write to the FlowMRR team.