Blog · Board and management reporting · Software
Passive churn is customer loss caused by unresolved payment problems rather than a deliberate cancellation. Measure the final outcome of a billing cohort and reconcile recovered, lost and unresolved customers before comparing periods.
Passive churn is customer loss caused by unresolved payment problems rather than a deliberate cancellation. The first failed charge is a warning, not the loss itself. Measure the customer's final outcome at a stated cutoff, keeping recovered payments and unresolved cases separate from confirmed exits.
A subscription can be past due while the business is still attempting collection or honoring an approved grace period. Stripe's subscription lifecycle documentation distinguishes past-due, unpaid and canceled statuses, and explains that the outcome after unsuccessful retries depends on the configured settings. A status label therefore needs the business's reporting rule beside it.
For analysis, define passive churn as a confirmed payment-related end to an eligible opening customer relationship. Require evidence of the payment failure, the final effective end and the recorded reason. A voluntary cancellation belongs in a separate bucket even if an invoice also failed; conflicting records need review before attribution.
If a customer has several subscriptions, a single failed or canceled subscription does not necessarily mean the customer relationship ended. The churn definition sets the general customer denominator. Here the additional work is classifying the reason and payment outcome correctly.
Use the customers active at the opening of the observation period. Export customer ID, subscription ID, renewal due date, first qualifying failure date, recovery date, final status, effective end date, termination reason and opening recurring revenue. Record the extract cutoff with the file.
Keep one customer outcome per cohort. Aggregate repeated attempts under the relevant invoice and customer before counting people. Failed first payments for customers who never activated belong in an activation analysis, outside an established active-customer cohort.
Decide in advance how to handle grace periods, delayed payment confirmation and later reactivation. An unresolved customer remains visible as unresolved until the loss rule is satisfied. The distinction resembles churn versus dormancy: a risk signal and a confirmed ending serve different decisions.
Passive customer churn rate = Confirmed payment-related losses from the opening cohort / Eligible opening customers
This differs from the payment failure rate, which can count invoices or attempts. It also differs from the recovery rate, whose denominator contains only customers with qualifying failures.
A hypothetical US SaaS business starts September 2026 with 200 active customers, each with one subscription and $100 of opening monthly recurring revenue. All subscriptions renew at the beginning of the month. The reporting cutoff is September 30, 2026; two customers have approved extensions that remain unresolved at that date.
Every customer appears in exactly one outcome row. Opening monthly recurring revenue is a normalized subscription measure, not cash received or recognized revenue.
| Outcome at cutoff | Opening customers | Opening monthly recurring revenue (USD) | Counted as lost? |
|---|---|---|---|
| Retained, no qualifying payment failure | 160 | 16,000 | No |
| Failed payment, subsequently recovered | 24 | 2,400 | No |
| Confirmed payment-related exit | 8 | 800 | Yes, passive |
| Deliberate cancellation | 6 | 600 | Yes, voluntary |
| Failure unresolved, extension still open | 2 | 200 | No, unresolved |
| Total | 200 | 20,000 |
The eight payment-related exits have effective termination records and no conflicting voluntary cancellation reason. The six deliberate cancellations had no qualifying payment failures and are classified separately. The example assumes no price changes, expansion or contraction among customers retained at the cutoff.
| Measure | Calculation from the outcome rows | Result |
|---|---|---|
| Passive customer churn | 8 / 200 | 4.0% |
| Voluntary customer churn | 6 / 200 | 3.0% |
| Total customer churn | (8 + 6) / 200 | 7.0% |
| Passive share of confirmed customer losses | 8 / (8 + 6) | 57.1% |
| Passive lost opening recurring revenue | 800 / 20,000 | 4.0% |
Percentages are rounded to one decimal place. Passive churn and the passive share of losses describe the same eight customers against different denominators; label both clearly. The recurring revenue rate matches the customer rate here only because every opening subscription has the same value.
The qualifying failure population contains 24 recovered customers, 8 payment-related exits and 2 unresolved customers: 34 in total. That population reconciles as follows:
| Failure-cohort result | Customers | Share of qualifying failures |
|---|---|---|
| Recovered | 24 | 70.6% |
| Confirmed payment-related exit | 8 | 23.5% |
| Unresolved | 2 | 5.9% |
| Total | 34 | 100.0% |
The full opening cohort also ties: 160 + 24 + 2 = 186 customers retained at the cutoff, and 186 + 8 + 6 = 200. Its opening recurring revenue bridge is 20,000 − 800 − 600 = 18,600. This bridge says nothing about invoice cash collection; outstanding receivables need their own reconciliation.
Call this a cutoff snapshot while extensions remain open. Compare another cohort at the same follow-up age and show unresolved cases on both sides. A later snapshot can change the outcome classification; retain the reporting date so readers can understand the revision.
Billing operations should review where payment-related cases end unresolved and whether the recorded status matches the actual service relationship. Stripe's revenue recovery documentation describes payment retries and customer notifications as billing recovery tools. The reporting analysis measures the exported results of those processes; the responsible billing team operates them.
Customer success should separately review the deliberate cancellations. Finance should compare the lost opening recurring revenue and verify that the cohort ties to its subscription reporting file. A larger recovery percentage alone does not prove that a process change caused improvement: payment methods, customer mix and observation time can differ. Keep those definitions with the other sales analytics KPI definitions.
Covirage is not affiliated with Stripe.
Upload billing and customer-status exports with payment outcomes, end reasons and opening recurring revenue. Covirage maps the columns, its tools compute and check the cohort split, and the external AI model explains the result with every figure traced to its rows. Create a free Covirage account and bring a sample of your own export.
See Covirage for SaaS sales for the supporting workflow.
The terms commonly describe payment-related losses that occur without a deliberate cancellation. Keep the local definition explicit: count a customer only after the qualifying relationship has ended under the reporting policy, rather than at the first failed charge.
No. A failed attempt can later succeed, remain unresolved or belong to a customer who still has another active product. Use the final customer outcome at the reporting cutoff and distinguish lost customers from failed invoices and individual charge attempts.
Choose a billing cohort and follow customers from their first qualifying payment failure to a fixed cutoff. Divide recovered customers by customers with qualifying failures. Show unresolved cases alongside the result, because different follow-up periods change the apparent recovery rate.
Finance validates the opening recurring revenue and revenue bridge. Billing or payments operations validates failures, recoveries and final status. Customer analytics maintains the cohort and classification rules so deliberate cancellations, unresolved accounts and confirmed payment losses remain separate.