In this article
A recurring invoice raises the same charge on a schedule, so it solves the raising and not the paying. Your customer still has to pay each one unless a mandate is collecting it. Invoices set to collect automatically are paid 98.0% of the time, against 90.8% collected on demand.
The distinction between a recurring invoice and a recurring payment is the whole subject, and most software blurs it.
The short version
- A recurring invoice automates your paperwork. A mandate automates the money.
- Set to collect automatically: 98.0% paid, 0.9% overdue. Collected on demand: 90.8% paid, 5.3% overdue (Adfin platform data).
- Each issue is a separate supply with its own invoice number, supply date and tax point.
- Agree the schedule and the amount in writing before the first one goes out.
- A failed collection is normal, and what you do next decides whether the arrangement survives.
The short answer
Use a recurring invoice for anything you bill on a rhythm, and put a direct debit mandate behind it wherever your client will agree to one. Without the mandate you've automated your own admin and left your customer's decision untouched, and that's the half that costs you.
Recurring invoice or recurring payment
Two different things, and they're often sold to you as one.
| What it automates | What still has to happen | |
|---|---|---|
| Recurring invoice | Raising and sending the document on a schedule | The customer decides to pay, every time |
| Recurring payment by mandate | Collecting the money on the due date | Nothing, unless the collection fails |
The gap between them is measurable. Across Adfin, invoices set to collect automatically are paid 98.0% of the time and 0.9% go overdue. Invoices collected on demand are paid 90.8% of the time and 5.3% go overdue (Adfin platform data, requests created in the seven months to the end of January 2026).
Be careful how you read that. Invoices set to collect automatically usually have a mandate behind them, so automation isn't doing the work on its own. What you're looking at is the difference between having agreed how you get paid and asking each time.
Setting one up so it holds
There are five decisions to make before the first one goes out, and each is easier to make now than to unpick in month four.
- Agree the amount and the rhythm in writing. Monthly or quarterly, on a day of the month, in advance or in arrears. A recurring charge nobody remembers agreeing to is the usual cause of a first-time dispute.
- Capture the mandate at the same moment, while your client is already saying yes to the work. Ask a month later and you're asking for bank details out of context. Practices that capture a direct debit mandate as the engagement letter is signed see fee notes collect themselves.
- Give each issue its own number. Each one is a separate document, and reusing a number with a new date won't do.
- Decide what happens when the amount changes. A price rise on a recurring arrangement means telling your customer before the collection, not after it.
- Decide who gets told. If your invoice lands in the same ignored inbox for twelve months, that's twelve months of nobody reading it.
What breaks a recurring arrangement
Four things break these arrangements, and each one is mundane enough to miss.
Collections fail. Your customer's bank details change, accounts close and balances run short, and the failure itself doesn't break the arrangement. Nothing sensible happening afterwards does. A retry, then an alternative method, then a person, in that order.
A silent price change almost always becomes a dispute with your customer, and often a cancelled mandate.
Scope drift is the quiet one. The recurring amount stays the same while the work grows, so the arrangement holds and your margin goes instead.
And there's renewal blindness. An annual arrangement nobody reviews for three years is usually mispriced by the time you look at it.
The VAT and record-keeping side
Each issue you send is its own supply, and it carries its own invoice number, supply date and tax point. A recurring arrangement doesn't create one long supply with twelve payments attached to it.
The required fields don't change either, so every issue needs everything a one-off invoice needs. What does change is that you're now producing twelve chances to get the same detail wrong, and an error in your template repeats until somebody notices.
Common questions
What is a recurring invoice? An invoice raised automatically on a schedule, for the same charge, without somebody creating it each time. It automates the document, not the payment.
Is a recurring invoice the same as a direct debit? No. A recurring invoice is a document issued on a schedule. A direct debit is a mandate that collects the money. Used together, the invoice is raised and the payment arrives without anyone deciding.
Does each recurring invoice need its own number? Yes. Each issue is a separate document and needs its own unique identification number, its own supply date and its own invoice date.
Can I change the amount on a recurring invoice? Yes, but tell your customer before the next collection rather than after it. An unannounced change on a recurring arrangement is the most reliable way to lose the mandate.
What happens if a recurring payment fails? A failure is normal and recoverable. What matters is the sequence afterwards: a retry, then an alternative payment method, then a human. Adfin retries at no charge and can fall back to card if a direct debit fails.
Should I invoice in advance or in arrears for recurring work? In advance where your client will accept it, because it removes the gap between doing the work and being paid for it. In arrears is more common for time-based work, and then the mandate matters more.
Sources
- GOV.UK — invoicing and taking payment from customers (accurate as of August 2026)
Reviewed by the Adfin team. This article explains how invoicing works and is not tax or legal advice. Last updated August 2026.
