Evaluate failed membership payments by linking each original billing obligation to its attempts, later collections and unresolved balance. Measure recovery on unique obligations or dollars at a stated date, then reconcile the cash to settlements. Scheduled retries, active account labels and recovered old billings must not inflate member growth or recurring collections in the acquisition model.
- Count unique billing obligations separately from retry attempts.
- Keep voluntary cancellation, payment failure and recovery distinct.
- Compare recovery cohorts at the same observation age.
- Reconcile successful charges through refunds, fees and bank timing.
What problem does the recovery review solve?
The review shows which failed bills later became collected cash and which remain unpaid. An account status or retry total cannot answer that question alone, so follow the original bill through its later outcomes rather than valuing a dashboard label.
The buyer hub frames the wider purchase review. Recurring revenue needs proof of repeat collections as well as enrollment. An active-member dashboard may include people in a recovery period, so learn its definition before multiplying the count by the advertised plan price.
The membership churn guide explains the member movement bridge. Here, trace the bills behind payment failure and recovery. A failed payment is not the same event as a voluntary cancellation, and a later receipt is not automatically new member growth.
State the site, period and question being tested. Keep account counts, billed dollars and actual collections distinct. The goal is a review another buyer can reproduce, not a promise that one processor setting will raise the wash’s value.
Which records should be requested?
Request a dated export that links each original bill to its eventual payment outcome. Confirm what the installed provider can produce, keeping missing fields visible instead of inventing bill-level precision from a summary dashboard.
Useful fields include stable account and bill identifiers, original due date, amount, plan, attempt dates, outcome, collected amount and unpaid balance. Add refunds, reversals and settlement references where available. Use controlled IDs rather than unnecessary card or personal data in a general diligence workbook.
Sonny’s POS and back-office specification describes member management and reporting features. It is a published product description, not proof that the target’s version exports every requested field. Ask the actual provider to confirm report definitions, available exports and authorized access.
Retain the export date, filters and source totals. Note any summary-only records and which facts cannot yet be verified. Check that the selected site and date range match the proposed analysis before joining files from different reports.
Why are attempts different from obligations?
One unpaid monthly bill can create several scheduled or executed attempts. Counting each attempt as a separate lost member or a chance to collect another full bill distorts the review, because the original debt remains one obligation.
Stripe’s retry documentation gives a provider-specific example of recovery settings and failures that need a new payment method. Some retries can remain scheduled without an executed charge. Confirm how the wash’s provider reports these events rather than assuming every system behaves like Stripe.
For a fictional customer owing $30 for one period, four failed attempts relate to one $30 bill. A later $30 collection resolves it once. It does not create four recovered sales or prove four customers stayed.
Keep counts and amounts in separate columns. One customer may have several unpaid periods, each with its own bill. Account-level and bill-level recovery can yield different rates, so name the unit and avoid switching it midway through a comparison.
How do you build a billing cohort bridge?
Group bills by their original billing period and follow each group’s outcome to a stated review date. Keep the actual cash date beside that original period so later receipts can be traced without being counted as a second sale.
| Outcome | Unique obligations | Amount |
|---|---|---|
| Originally due | 1,200 | $36,000 |
| Paid on first attempt | 1,000 | $30,000 |
| Initially failed | 200 | $6,000 |
| Later recovered by review date | 120 | $3,600 |
| Still unresolved | 80 | $2,400 |
The 1,200 original bills divide into 1,000 first successes and 200 initial failures. Of those failures, 120 recover and 80 remain unpaid. Collected cash is $33,600 from 1,120 paid bills. The example excludes partial payments, taxes and differing plan prices.
Observed count recovery at the review date is 120 divided by 200, or 60%. This is math for fictional inputs, not a benchmark or another wash’s forecast. Do not mark all 1,200 bills paid because the accounts still appear on a member list; actual records may need extra outcome categories.
Why does the observation date matter?
A recent group of failed bills has had less time to recover than an older group. Compare groups at similar ages, rather than reading the difference as an improvement or decline without checking how long each has been observed.
Set review ages that fit the provider’s actual process. Show the review date and unpaid aging, without assuming every pending charge will succeed. A receipt after the first cutoff updates the original group’s history and also appears on its actual cash date.
For illustration, 20 of the unpaid $30 bills might pay the next month, adding $600 to cash then. They remain part of the earlier group. Counting that $600 as both an earlier recovery and a new member sale would overstate the combined result.
Use the profit-and-loss review guide to reconcile the reporting basis with the accountant. Keep cash dates, service periods and accounting treatment consistent. The diligence bridge should explain the reports without replacing the business’s accounting policy by assumption.
How should paid statuses and settlements reconcile?
Trace reported paid bills through the payment evidence to settlements and bank receipts. A status alone is not a bank reconciliation, so keep gross collections, refunds, fees and pending transfers as separate lines in the bridge.
Stripe’s invoicing documentation distinguishes processing from completed outcomes and explains that a paid event can include out-of-band treatment. It shows why underlying payment evidence matters. It does not prove the target uses Stripe or that every paid event is suspect.
Remove duplicate exports and identify reversals, refunds and manual adjustments. Match charges to processor batches and bank receipts. Where IDs do not link directly, state the method and remaining uncertainty instead of forcing an exact match.
In the fictional case, $33,600 gross less $300 refunds and $1,000 processor deductions gives $32,300 expected net settlement. Bank receipts of $31,800 plus $500 verified later reconcile to it. The later receipt needs proof; timing is not a permanent balancing plug.
A refund differs from an unpaid bill. A charge can succeed and later be returned, reducing net cash without changing the initial failure count. Keep disputes and reserves in their own supported lines where they affect settlement amount or timing.
What improvement assumptions can enter the buyer case?
Include only supported changes with a defined process and cost. Recovery opportunity is not automatically collectible revenue, so keep demonstrated collections apart from a proposed gain that still requires customer action or a different provider setting.
Identify causes of failure, current capabilities, needed customer actions and existing communications. Review settings and customer handling with the provider and advisers. More scheduled attempts do not guarantee proportionally more successful charges, and some failures cannot be resolved by repeating a charge.
Include provider fees, staff effort, refunds and complaints where relevant. Compare groups at like ages after a defined change. Keep other explanations, such as plan mix or seasonal enrollment shifts, visible before assigning a gain to the new policy.
Preserve the baseline and the date each change took effect. Explain which original bills are eligible for the comparison and why. A change should be tested within applicable requirements, not booked as acquisition upside simply because software offers a retry option.
What should the diligence conclusion contain?
State what was verified, what remains unpaid and how the findings affect recurring revenue. Keep the conclusion reproducible from retained records, with the unit, review date and unresolved evidence gaps visible beside any reported recovery rate.
- Document report definitions, identifiers and the measurement cutoff.
- Reconcile original obligations, first successes, recoveries and unresolved balances.
- Compare like-aged cohorts and separate counts from dollars.
- Trace collected amounts through refunds, deductions and settlements.
- Keep proposed recovery improvements separate from the supported base case.
The first-90-days guide helps preserve these controls during handover. Assign responsibility for open balances and later receipts. A buyer should leave with better cash evidence, not a larger member count created by repeating the same bill.
Retain the original export and each later dated update. New cash may change the recovery result without changing the first failure count. Keep member movements, old-bill collections and new paid periods distinct so operating reports and the buyer’s cash model stay aligned as the review matures.