Charging a customer once is straightforward. Charging them every month, for years, while they change plan, change card, add users, cancel, return and query an invoice — that is a system, and it is where subscription businesses lose money without noticing.
Failed payments are the biggest single leak
A meaningful share of subscription cards fail every month. Expiry, replacement after fraud, insufficient funds, a bank declining an unfamiliar recurring charge, a corporate card cancelled when someone left.
Almost none of these customers intended to leave. They are lost anyway, and businesses record it as churn.
What good handling looks like:
Warn before expiry. You know the card's expiry date. Email a fortnight ahead and make updating it a single click from the message.
Retry on a considered schedule. Not five times in a day — spread over one to two weeks, because many failures are temporary and resolve on their own.
Tell the customer early. The email that matters is the one after the first failure, not the one announcing suspension.
Make updating trivial. A link that goes straight to a card form. Requiring a login, a password reset and three clicks loses people who fully intended to pay.
Suspend late and reversibly. Cut access only after genuine attempts and clear warning, and restore instantly on payment.
Recovering failed payments is usually the cheapest revenue available to a subscription business, and it is almost always under-engineered.
Proration, and why customers complain about it
A customer upgrades on the 17th of a monthly cycle. What do they pay?
The mathematically correct answer is a credit for the unused portion of the old plan and a charge for the remainder of the new one. The resulting figure is a number nobody expected, arriving at a moment nobody expected, and it generates support tickets.
Three workable approaches:
- Prorate immediately. Correct, and requires a clear explanation on the invoice.
- Charge the new rate from the next cycle. Simple to understand, and you give away part of a month.
- Charge the full new plan now and reset the cycle. Simple, and feels unfair to the customer.
Whichever you pick, say so plainly at the point of change. The complaint is nearly always about surprise rather than about the amount.
Downgrades and cancellations
Downgrades should generally take effect at the end of the paid period rather than immediately — the customer paid for it. Immediate downgrades with refunds invite abuse and confuse accounts.
Cancellation deserves care. Let people cancel without contacting you; forcing a phone call generates complaints and, for consumer subscriptions, regulatory attention. Keep their data for a stated period so returning customers do not start from nothing, and say when it will be deleted.
Ask one optional question about why they left. It is the most valuable feedback you will get.
VAT, and where it gets awkward
Straightforward for UK customers. Less so once you sell abroad.
Digital services to consumers in other countries can attract VAT in the customer's country, at their rate, with registration obligations. Business customers may reverse charge, which requires a valid VAT number — and validating it is your responsibility.
Invoices must contain specific information to be valid, and your customers' accountants will notice if they do not.
This is an area where using an established billing platform earns its fee several times over, because they maintain the rules and you do not.
Usage-based charging
If you charge per user, per transaction or per gigabyte, everything above becomes harder.
You need accurate metering, agreement on when a unit counts, a decision about what happens when limits are exceeded — block, charge overage, or notify — and a way for customers to see current usage before the invoice arrives.
That last point prevents most disputes. A customer who can see they are at 80% of an allowance will not argue about the overage.
Do not build the billing engine
Use an established payment platform for subscriptions, retries, card storage and tax. Then build only three connections:
- Platform to product. When a subscription starts, changes or lapses, your product must reflect it — and it must handle those events arriving out of order or twice, because they will.
- Platform to accounts. Revenue into your accounting system without anyone retyping it. See connecting accounting to operations.
- Platform to your team. Someone needs to see who is failing, who is overdue and who cancelled this week, without opening three systems.
What to watch monthly
Recurring revenue and its movement. Failed payment rate and recovery rate. Involuntary churn — customers lost to payment failure — separated from voluntary churn, because they have completely different remedies. And time from failure to recovery.
Businesses that separate involuntary from voluntary churn frequently discover the majority of their losses were technical rather than a product problem, and technical problems are much easier to fix.
Our integration team connects billing platforms to products and accounting systems for UK businesses. Start a conversation if your subscription revenue is being reconciled by hand.
