You marked number 14 done on Tuesday. You collected the £15. On Friday the money is not there, and there is nothing in your inbox telling you why.
This is the bit nobody explains before you start collecting by Direct Debit. The sign-up is smooth, the first few collections land, and then one does not, and you find out that you never really understood what was happening between marking a clean done and the money turning up.
Here is what is actually going on, why collections fail, and what to do about each kind.
Direct Debit is a pull, and it takes days
Almost every misunderstanding starts here.
A bank transfer is a push. Your customer decides, their bank sends it, and it lands. A Direct Debit is a pull. You tell the scheme to take money from their account, the request goes into a queue, and several working days later either the money arrives or a failure comes back.
So a Direct Debit is never instant, and it cannot be. There is a window between you asking and finding out, and everything awkward about failed payments lives in that window. You have already done the work, you have already ticked the clean off, and the answer arrives later.
That is not a flaw. It is the trade you make for not having to ask. But it means "collected" in your app on Tuesday and "money in the bank" are two different events, and you want software that knows the difference.
The failures you will actually see
Most of the reasons sound dramatic and mean something ordinary.
Not enough money in the account. By a distance the most common one, and almost never personal. They get paid on the 28th and your collection went out on the 26th. It says nothing about whether they intend to pay you, and if you clean for a lot of people paid monthly, you will see the same handful fail in the same week every month until you move your collection day.
The mandate has been cancelled. Your customer can cancel a Direct Debit at their bank, without telling you, in about four taps in a banking app. Sometimes that is deliberate because they are leaving. More often they were clearing out old Direct Debits on a Sunday evening and yours did not look like anything they recognised.
This one is worth dwelling on, because there is a specific trap. Depending on how your collection service is set up, the entry on your customer's statement may carry the payment company's name rather than yours. So Mrs Hartley, who thinks she pays Dave for the windows, is looking at a line item from a company she has never heard of, for £15, every four weeks. Most providers sell an option to put your own trading name on the statement instead, and it is usually the single cheapest thing you can do to stop mandates being cancelled by mistake. Check what yours shows before you sign up fifty people, not after. Whatever the arrangement costs, it is on your provider's pricing page rather than in this post, because those things change.
The account is closed or the details changed. They switched banks. The switching service moves most things across, but not always cleanly and not always quickly.
The payer disputed it. Rarer, and the one worth understanding properly, so it gets its own section below.
There is one more thing that causes queries rather than failures, and it catches people out. If a customer is three cleans behind and you collect the lot in one go, the amount landing on their statement is £45, not the £15 they have got used to seeing. That is the collection that gets rung about. Either collect them separately, or tell them first.
The useful habit is to read the reason before you react, because the right response to each of these is completely different. Chasing somebody who got paid two days late is a good way to lose a customer who was always going to pay you.
A failed collection should put the clean back on the bill
This sounds obvious. It is the thing to check before you trust any app with your money.
The clean happened. You did the work. If the collection fails, the money is still owed, and the clean needs to go back to unpaid so it turns up in your total and in that customer's balance. What you do not want is a clean that is marked paid because you pressed collect, sitting there looking settled while the money never arrived.
That is how people end up months down the line with a book that does not match their bank. Not through fraud or bad luck, just through software that treated "I asked for the money" and "I got the money" as the same event.
Whatever you use, test this deliberately. Get a failure to happen and watch what the clean does.
Do not just retry it
The temptation, when something fails, is to fire it straight back in. Resist.
If the reason was no money in the account, a same-week retry is quite likely to fail again, and every failure is another notification to your customer that a payment they authorised did not work. Do it twice and you look disorganised to somebody who has done nothing wrong.
If the reason was a cancelled mandate, a retry cannot work at all. There is no authority to collect against any more. You need them to set it up again, which means a conversation, not a button.
The better pattern is boring. See the failure, read the reason, decide, then act. If it was timing, collect again after payday or roll it into the next clean. If the mandate has gone, send them a fresh link, or a one-off payment link for what they owe now and sort the mandate out at the next visit.
The Direct Debit Guarantee, and what it means for you
Every Direct Debit in the UK is covered by the Direct Debit Guarantee. Your customer can go to their bank, say the payment was wrong, and get it back. The bank refunds them, then reclaims it from you.
Read that as a feature rather than a threat, because it is the reason your customers will agree to it at all. You are asking somebody to let you take money out of their account, repeatedly, for an amount that varies. Nobody would do that without a way back out. The Guarantee is what makes it a normal thing to say yes to.
In practice, for a window cleaning round, it comes up rarely. The amounts are small, the work is visible, and people who wanted rid of you cancel the mandate instead. But you should know it exists, and you should not treat a Direct Debit as untouchable money the moment it lands. If you ever have a customer who feels hard done by, they have a lever, and so they should.
Two things reduce it to almost nothing. Collect after the work, not before, so the payment always matches something they can see. And make sure the name on their statement is one they recognise.
Advance notice is your friend, not a formality
Before each collection your customer gets told what is coming and when. That is a scheme requirement, not an optional courtesy.
It reads like admin. It is actually the single biggest thing standing between you and the "what is this on my statement?" phone call. A customer who has been told £15 is coming out on the 26th does not ring their bank about an unfamiliar payment on the 26th.
So do not think of it as paperwork. It is the thing quietly preventing disputes you would otherwise have to handle.
The part most software gets wrong
This one is technical, and it is worth knowing because it decides whether your numbers can be trusted.
Payment providers tell your app what happened using webhooks, which is a message sent from them to your software the moment something changes. Usually it arrives in seconds. Occasionally it does not arrive at all. A server hiccups, a deploy happens at the wrong moment, a message gets dropped.
If the app only ever listens for those messages, a dropped one means a payment that silently stays in the wrong state for ever. The collection succeeded, the money is in your account, and your app still shows the clean as unpaid. Or worse, the other way round.
The fix is unglamorous: something has to go back and check, on a schedule, comparing what the app thinks against what the provider says. If you are choosing between apps and you want one question that separates the careful ones from the rest, it is this. Ask what happens when a webhook goes missing.
What good looks like
If you are collecting by Direct Debit, whatever you use to run the round should do this much:
- Tell you a payment failed, in plain words, without you going looking
- Say why, in language you can act on rather than a code
- Put the clean back on the bill, so your total is right
- Let you collect again when the moment is right, from the customer's own record
- Never charge twice for the same clean, even if you tap collect twice
- Show you the money that is in flight separately from the money that has landed
None of that is exotic. It is just the difference between software that tracks your money and software that tracks your intentions.
A note on what this replaces
The reason to put up with any of the above is what it removes. No going back on a Saturday. No envelope behind the plant pot. No evening spent matching bank transfers to names, working out that the payment from "J Waters" is the Hardys at number 9 because their daughter set it up.
Failures are the small print of a system that mostly means you stop thinking about getting paid. Worth understanding, not worth being frightened of.
RoundWiz collects by Direct Debit through your own GoCardless account, and the failure handling above is how it behaves: the reason in plain words, the clean back on the bill, and a retry when you decide rather than automatically. See how Direct Debit works, or for the customers who will never set one up, send a one-off payment link instead. £7.99 a month, 30 days free, no card needed.