Skip to content
OperationsMetric 26 of 35

Dunning & Payment Recovery

The art of getting failed payments to succeed without losing the customer.

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 plan Stripe payment recovery right inside your Stripe MRR dashboard.

The process of recovering revenue from failed charges through retries, card updates, and customer outreach. FlowMRR measures it with a recovery rate on counts: an invoice paid after a failed attempt is a recovery, dated when the money arrives; a subscription that ended unpaid or canceled with its invoice still unpaid is a loss; cases still being retried are in neither. Recovery has no acquisition cost, which makes it one of the highest-return workstreams in SaaS.

Formula

Recovery Rate = Failed payments later collected ÷ (Failed payments later collected + Subscriptions lost with their invoice unpaid)

Worked example

100 monthly renewals fail and go past_due, at $80 each → $8,000 of at-risk MRR. 60 are paid after a retry or an email, 40 end unpaid → Recovery Rate = 60 ÷ (60 + 40) = 60%. If the 60 stay active at the same price, that protects $4,800 MRR, or $57,600 ARR; the recovered cash itself is not ARR.

Other definitions you will see

Recovery rate is also measured by amount (the share of failed revenue later collected) or on a cohort: of the invoices that failed in a month, the share later paid, however long it took. Some tools put payments still being retried in the denominator, which reads lower until those cases resolve; some count a subscription as recovered as soon as it is active again, even if the failed invoice was never paid.

Illustrative comparisons

Recovery rate

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.

Higher recovery
65–80%
Middle scenario
40–55%
Lower recovery
< 30%

Why it matters

Every $1 recovered through dunning is worth more than $1 of new acquisition because there's no acquisition cost. Stripe gives you most of the pieces (Smart Retries, automatic card updates, the customer portal); the work is to wire them together, reach the customer when a retry cannot succeed, and measure the result.

Common mistakes

  • Retrying with fixed intervals instead of using Stripe's adaptive Smart Retries.
  • Leaving Stripe's automatic card updates off, so expired or reissued cards fail at renewal.
  • Sending a single dunning email and stopping there: a customer who missed the first message gets no second chance.
  • Marking accounts as churned the moment a payment fails — give them the grace period and the retries first.

Calculating it from Stripe data

A failed renewal shows in Stripe as an open invoice with a failed payment attempt, and the subscription moves to past_due. Smart Retries, or a custom schedule, try the charge again over a period you configure; the invoice's attempt_count and next_payment_attempt show where it stands. When the retries run out, your subscription settings decide what happens: cancel the subscription, mark it unpaid, or leave it past_due, and the invoice can be marked uncollectible or left open. A first payment that fails on a brand-new subscription is different: the subscription is incomplete, never paid, and does not belong in dunning figures.

Keep the money figures apart. MRR at risk is the MRR of past_due subscriptions only, since they still count in MRR while Stripe retries. Unpaid subscriptions are already churned, as of the end of their last paid period, yet their invoice can still be collected: report them as churned but recoverable. The amount to recover is past_due plus unpaid. Count per subscription, so a multi-item subscription is one case and its open invoice is counted once, and age each case from its oldest unpaid invoice.

Recovered means money collected on an invoice after a failed attempt, dated when it arrived. A subscription that is active again while its failed invoice is still open or uncollectible collected nothing on that invoice and is not a recovery. FlowMRR's Recovery Rate counts outcomes: invoices recovered ÷ (invoices recovered + subscriptions that ended unpaid or canceled with their invoice unpaid); cases still in dunning stay out until they resolve. The other common measure follows a cohort by amount: the share of a month's failed invoices later paid. FlowMRR's Recovery page applies these rules: past_due as MRR at risk, unpaid shown separately, the amount to recover, six ageing buckets from under 7 days to over 60, decline codes and a trend of invoices recovered after a failure, with the same figures in the weekly review, emails, investor PDF and Excel export.

Reading the result

Split the population by decline type before acting. Soft declines, such as insufficient funds or a temporary issuer refusal, often succeed on a later retry. Codes that mean the card itself can no longer be charged, such as an expired, lost or stolen card, will not be fixed by another retry; the customer has to update the payment method, so an email with a direct link to do so is the lever.

Prioritise by amount and age. Large subscriptions deserve a personal message, and cases that have aged past the first weeks tend to be harder to collect, so act on new failures quickly. A rising share of MRR at risk with a flat number of failures means larger accounts are failing; a growing unpaid backlog means retries end without anyone following up.

Frequently asked questions

What is a good failed payment recovery rate?

It depends on your mix of decline reasons, payment methods and customers, and on how long you keep retrying. A book dominated by expired cards recovers differently from one dominated by insufficient funds. Compare rates only when they are measured the same way, on the same cohort of failed invoices, and watch your own trend after each change to retries or emails.

What is the difference between MRR at risk and the amount to recover?

MRR at risk covers past_due subscriptions only: customers still counted in MRR while Stripe retries. The amount to recover adds unpaid subscriptions, which have already churned but whose invoices can still be paid. The first measures revenue you could still lose; the second, the work left to collect.

Are Smart Retries enough without dunning emails?

Usually not. Retries can only succeed when the card can still be charged, for example once funds are available. When the card has expired or been replaced, no retry will work until the customer enters new details, and that takes an email or an in-app prompt with a link to update the payment method.

How do I calculate payment recovery rate?

FlowMRR counts outcomes: failed payments later collected ÷ (those payments + subscriptions that ended unpaid or canceled with their invoice unpaid), leaving out cases still in dunning. With 60 failed renewals paid and 40 lost, the rate is 60%. Another common method follows a cohort by amount: of $8,000 that failed in May, $4,800 collected by the end of the retry window gives 60% for May. The two can differ when large and small invoices recover at different rates.

Contact us
FlowMRR

Let's talk

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