Refunds are rarely large enough to change a valuation, and that is exactly why the claim is worth checking: it is cheap to verify and the distribution tells you things nothing else in the export will. Early refunds indicate an expectation gap in the sales process. Chargebacks indicate the health of a payment account you are about to inherit.
TL;DR: Refunds are usually small in aggregate and highly informative in distribution. Here is how to check the refund rate, the timing, and what a chargeback rate implies about the payment account you are inheriting.
Sellers say this because it is usually true in aggregate, and because refunds are netted out of the revenue figures they look at, so the gross amount is genuinely not visible to them day to day. The information that matters is not the total but the shape: when refunds happen relative to sign-up, which plans they cluster in, and whether the chargeback rate is anywhere near the level at which a payment processor takes an interest.
Four mechanisms account for most of the gap between this claim and what the raw rows show. They are not mutually exclusive and they compound.
A high early-refund rate means customers are arriving with the wrong expectation. That is a marketing and onboarding finding, and it usually correlates with elevated first-cycle churn among the customers who do not ask for their money back.
Chargeback rates above the thresholds payment processors monitor can trigger reserves, higher fees or account review. You are inheriting that account and its history. This is an operational risk that does not appear anywhere in the revenue analysis.
A business that resolves complaints by extending the subscription for free shows almost no refunds and carries the cost in unbilled revenue. Look for zero-amount or heavily discounted periods on otherwise paying accounts.
One incident, one bad launch or one broken migration can produce a refund cluster in a single month. That is a service-failure signal, and the accounts involved are the ones most likely to churn in the following cycles.
Every step below runs on a subscription-level export in a spreadsheet. None of it needs access to the seller's live billing account, which matters, because as a buyer you will not get one.
These are the thresholds we use in our own reports. They are working thresholds rather than industry standards, and the right line for a given deal depends on contract length, tenure and how transferable the customer relationships are.
| What you find | Verdict | What to do about it |
|---|---|---|
| Refunds under 2% of gross revenue, spread across tenure | Green | Genuinely negligible. Note it and move on. |
| Refunds 2–5% of gross revenue | Investigate | Not alarming, but worth understanding. Check the tenure distribution before accepting it. |
| More than half of refunds inside the first 30 days | Investigate | An expectation gap between what is sold and what is delivered. Expect it to show up in first-cycle churn too. |
| A single month above 3× the trailing average | Investigate | A service or product event. Identify it and check churn among the affected accounts in the following cycles. |
| Chargeback rate near processor monitoring thresholds | Price it in | This is a payment-account risk you inherit, including reserves and fees. Verify the account standing directly with the processor before close. |
Ask for these before the LOI. After the LOI you are renegotiating rather than negotiating, and a seller who will not produce subscription-level rows has told you something useful either way.
Illustrative. Refunds are 1.4% of gross revenue, which supports the claim. But 68% of refunded dollars are refunded within twenty-one days of sign-up, and 80% of those come from one paid acquisition channel. The aggregate is negligible and the distribution says the channel is buying customers who did not want the product. Those customers are also 3× more likely to churn in the first ninety days if they do not request a refund, so the refund line is a visible corner of a much larger acquisition-quality problem. The aggregate answer was true and uninformative.
Refund analysis rarely moves a price and often changes what you do in the first quarter, which is why it is worth the twenty minutes. Early-refund clustering tells you which acquisition channels to turn off before you scale spend. Chargeback standing tells you whether the payment account you are inheriting is in good order, and that is a question best answered by the processor rather than by the seller.
The relevant tool on this site is the free SaaS health score, which runs the arithmetic above on a file you paste in. The full method is documented in the 5-risk buyer-side method and the due-diligence checklist.
Every check on this page can be run by hand in a spreadsheet, and if you have the time you should. If you would rather not: send us the target's subscription export and we run the full human-reviewed analysis — logo churn, revenue churn, customer concentration, annual-plan decay, zombie MRR and an A–F revenue-quality grade. The free Starter tier covers one CSV per month, which is enough to check a single deal.
See a sample report → · Get the free 23-point checklist →
As a working guide we treat under 2% of gross revenue as unremarkable and above 5% as worth a specific explanation. Those are our thresholds rather than an industry standard, and the distribution matters more than the level: 1% concentrated in the first two weeks is more informative than 3% spread evenly across tenure.
A refund is a decision the business made; a chargeback is a dispute the customer escalated to their card issuer. Processors monitor chargeback rates and can impose reserves, higher fees or account review. Because you inherit the payment account, chargeback history is an operational risk that does not appear in any revenue metric.
That customers are arriving with a different expectation than the product delivers, which is a sales and onboarding problem rather than a product-quality one. It usually travels with elevated first-cycle churn among the customers who do not ask for a refund, so the visible refund line understates the size of the issue.