Refunds and write-offs: money out, with guardrails

What does the capability do?

It makes the two ways money exits a billing system (giving it back, and giving up on it) as disciplined as the way it came in, so the days when things go wrong are handled as reliably as the days when they do not.

• Validated refunds. A refund request checks the payment is in a refundable state and computes the refundable balance as the amount paid minus what was already refunded. Anything over that is rejected at the API, which is what makes partial refunds safe to offer.
• Mandatory reasons. Refunds and write-offs both require a reason, enforced by validation with a sensible length limit. The record carries its own justification.
• Typed and tracked. Each refund records its type, method, and status, moving from pending submission through submitted, confirmed, failed, cancelled, or rejected, and belongs to a refund batch for processing, consistent with the platform’s batch-based collection.
• Guarded write-offs. A charge can only be written off from pending, charged, overdue, or partially paid. The write-off cancels the charge, sets the remaining amount to zero, and records a void event, all inside one audited transaction.
• Attributed like everything else. Refunds carry the same site-level attribution as charges and payments, so reporting nets them against the right location.

Built for the days that go wrong

A double charge, a failed collection retried at the wrong moment, a cancelled session, a goodwill gesture: every operator meets these weekly, and they arrive as customer service queries, not finance tickets. Bulletproof support for those moments means the front-line team can see exactly what was paid, refund precisely what is refundable, or write off what will never be collected, in one contact, with the system guaranteeing the result is correct. The member gets a fast answer; finance gets a clean record; nobody escalates a £15 dispute through three departments.

Why guardrails beat goodwill

Refunds are where billing systems meet human judgement under pressure: an unhappy member at the desk, a manager who wants the problem gone. Systems that allow free-form negative adjustments accumulate mystery money movements that finance teams spend days unpicking. Putting the rules in the API (refundable balance, valid states, required reasons, audited commits) lets staff be generous quickly, without creating month-end archaeology.

Why it matters

An operator’s refund and write-off discipline is visible in its accounts. Validated amounts, mandatory reasons, guarded transitions, and per-record audit mean every outbound pound is explainable, which regulated and multi-site organisations need, and every debt given up on is an explicit decision rather than a quiet leak. It is the same principle the Billing Engine applies across mandates, charges, and collections: financial state changes are events with evidence.