Track and grow your ARR →
Unlock CFO-grade clarity into your SaaS metrics with Equals.
Mistakes happen. That’s what refunds are for.
As an analyst, the problem is that refunds are often used as a catch-all for many things like:
They also restate historicals, which can drive you crazy when trying to reconcile performance data. Rather than walking through each permutation, we’ll share our guiding principles on refunds.
Always work to fix the underlying issue in the correct upstream source (usually the subscription) and make the best effort to record the refund on the date it was processed instead of applying it retroactively (i.e., avoid historical restatement). The one exception to the latter point is if the refund amount is so high that it materially impacts performance or creates misleading results. For example, when a customer expands by $1M and your total ARR pre-expansion is only $200K. In those cases, applying it retroactively makes more sense.
Next topic