Review membership refunds and chargebacks by linking each case to its original charge, service period and actual settlement effect. Separate completed refunds, final dispute losses, recoveries and unresolved exposure. Reconcile gross receipts to net cash without duplicate deductions, then document closing responsibility under the agreed transaction terms rather than assuming the request date determines who pays.
- Track cases and cash movements separately.
- Link every adjustment to the original billing obligation.
- Preserve pending exposure and later recoveries.
- Check whether deductions already reduce reported earnings.
What does the acquisition review need to establish?
Establish what happened to collected member charges, what remains open and which party bears the agreed cost. Keep the case history, cash bridge and closing terms linked without treating them as the same question.
The buyer hub places this review in the wider purchase process. Recurring billings can differ from bank deposits because of refunds, disputes, fees and payout timing. Trace that gap before calling a monthly charge total dependable cash.
The failed-payment recovery guide starts with bills not initially paid. Here a successful charge may later be refunded or challenged. Keep those groups distinct so one loss rate does not hide different causes.
Build a register around each original charge and its linked events. An opened case, later deduction and final result are not three separate losses. Show refunds, fees, actual recoveries and unresolved amounts with dates, then assign an owner and next review date to each open item.
How are refunds and disputes different?
A merchant refund and a customer dispute use different processes and records. Identify the event before reading its status or effect on cash.
Stripe’s refund documentation shows pending, successful and failed outcomes. This provider example does not prove that the wash uses Stripe or that its refund reached a customer. Ask the installed provider for its records and status definitions.
Stripe’s dispute explanation describes a separate case process and related money movements. Opening a case is distinct from its final result. Do not call every opened case a permanent loss or assume that contesting it will return the money.
Keep complaints apart from financial cases. A complaint might lead to no adjustment, a concession or a dispute, so count the actual event. When both a refund and a dispute concern one charge, inspect the balance movements with the provider. Neither one automatically cancels the other or proves two final losses.
Which records should the buyer request?
Request records linking each original charge to refunds, disputes, fees and recoveries. Save IDs and dates so another reviewer can rebuild the case history and cash timing.
Useful fields include account and charge IDs, service period, plan amount, case ID, event type, date, status and amount. Add reason codes, balance transaction IDs and payout references where the system supports them. Flag missing fields rather than treating an export as complete merely because its totals agree.
Keep customer details inside the approved confidential review process. Sale materials generally need totals and definitions, not payment credentials. Use approved exports and access controls; this guide authorizes no refunds, live charges or responses to customer cases.
Save source files and their extraction date. A pending case can later close, changing the same group’s cash result at a new review date. Preserve both snapshots and explain the change instead of replacing the old history without a record of what happened.
What does a fictional cash bridge look like?
Start with successful gross charges and follow actual balance movements toward the payout amount. Show later money from the same cases as dated credits rather than assumed recoveries.
Suppose a fictional period has $40,000 of successful charges and $600 of completed refunds. Dispute deductions are $900, including $300 still open at the review date. Actual recoveries credited in the period are $200, while processing and case fees total $1,000. These invented figures illustrate a bridge, not this wash’s results.
| Item | Cash effect | Review point |
|---|---|---|
| Successful charges | +$40,000 | Original charge population |
| Completed refunds | −$600 | Matched refund transactions |
| Dispute deductions | −$900 | Includes $300 unresolved |
| Credited recoveries | +$200 | Actual credits, not forecasts |
| Processing and case fees | −$1,000 | Documented fee treatment |
| Net balance movement | $37,700 | Then reconcile settlement timing |
The net balance movement is $37,700 before payout timing differences. The open $300 is already inside the $900 deduction; subtracting it again creates a false shortfall. Its final outcome remains uncertain even though the deduction is observed cash movement.
If that money is later returned, record the credit when it occurs and link it to the original case. A possible recovery is not received cash. Keep the open amount visible without counting it again as another current deduction.
How does the bridge connect to bank deposits?
Match net balance movements to payouts, with support for timing, reserves and other items. Bank deposits may cover charges from a different period than the one being reviewed.
Stripe’s payout reconciliation guidance distinguishes account activity from payout reporting. Check the actual provider’s payout structure and report fields. Do not assume a deposit equals one day’s charges or that every report offers the same way to match them.
If the fictional $37,700 consists of $37,200 deposited and $500 supported as a later settlement, the amounts agree. The $500 still needs proof of its status and later receipt. Money said to be in transit without support stays an exception rather than a plug used to force agreement.
Keep held provider balances separate from customer losses. A documented reserve can delay access without being a refunded charge. Ask the provider and advisers to review restrictions, ownership and release terms before assigning that balance in the deal model.
How are earnings and cash kept from double counting?
Check how the books record each item before proposing an earnings adjustment. Cash and accounting reports can describe the same event from different views.
The profit-and-loss review guide connects this work to the wider earnings bridge. If revenue is already net of refunds, subtracting the refund register again repeats the deduction. If a chargeback is booked as an expense, have the accountant reconcile that treatment before reducing revenue as well.
Review dates and original service periods with the accountant. A later deduction may concern earlier billings, and cash-basis reports can differ from other accounting views. Explain those differences without calling every unusual case an add-back or treating its proximity to closing as proof it should be removed.
Trace the same charge through the register, ledger and payout report. Note where its effect is already included, with the supporting line or transaction ID. An open case may affect available cash while its final earnings treatment still needs review; show that limit explicitly.
What should the buyer investigate beyond the totals?
Investigate repeated causes and concentrations under stated definitions. A cash total alone does not show whether the operating problem behind it continues.
Possible categories include duplicate charges, unclear offers, missed cancellations and service-access faults. These are review questions, not claims about this wash. Match recorded reasons to customer messages, system changes and provider records while noting gaps in reason codes.
- Define the original charge population and measurement period.
- Link case events and balance movements without duplicate counting.
- Separate final outcomes, credited recoveries and pending exposure.
- Reconcile settlements and the accounting treatment.
- Investigate documented causes and assign unresolved transaction items.
Use the installed provider’s rules when reading a rate. There is no universal acceptable chargeback percentage in this guide. State the charge population, case count, dollar amount and dates so a changed reporting window cannot masquerade as an improved customer outcome.
Keep actions and financial outcomes separate in the review log. A promised fix does not show that later cases stopped or open money returned. Name who will check the next dated export and carry unresolved causes forward until evidence supports a different result.
How should closing responsibility be documented?
Use adviser-reviewed signed terms to assign costs, then track actual deductions and reimbursements against them. The account charged does not by itself settle responsibility between buyer and seller.
The membership transfer guide covers service continuity at handover. Refunds and disputes also need a named contact, evidence and an agreed process for resolution. Keep original charge dates, service periods and case status rather than assigning every later request to one party based only on its arrival date.
Show open items in the closing file and update them as outcomes arrive. Distinguish money already deducted, credits actually received and contractual responsibility still under review. An agreed allocation does not mean a reimbursement has already been paid.
Track any reimbursement separately from the provider’s refund or recovery. Match it to the assigned case and signed terms so it does not become a second earnings credit. A complete file lets reviewers follow both the customer event and the parties’ later settlement without guessing.