A direct debit collected on the due date reaches your bank account a few days afterwards, because Bacs clears every collection over a three day cycle. So an invoice paid perfectly can show up in your reports as paid three or four days late. If direct debit is most of what you collect, an average days-late figure is measuring that cycle instead of your customers.
In this article
The short version
- Bacs describes the collection process as taking "less than three days from start to finish", running from input day through to entry day.
- The debit hits your customer and the credit reaches you on the same day, the third one.
- Bacs publishes a processing calendar covering bank holidays, so the elapsed time stretches around them.
- Direct debit is 83.4% of the payments Adfin collects on its own rails, counted by number of payments and not by value, so a blended days-late average is dominated by settlement timing (Adfin platform data).
- Measure collection success and on-time rate by payment method, and compare direct debit only with direct debit.
Why the money arrives after the due date
Bacs sets out the cycle plainly. The whole process "takes less than three days from start to finish", and the three days have names: input, processing and entry.
On the input day you or your provider submit the payment file, in a window that runs from 07.00 to 22.30. On the processing day the files "reach recipient banks for individual payment processing". On the entry day, payments "are simultaneously debited from the recipients' accounts and credited to your account".
Nothing there has gone wrong. Your customer didn't delay anything, nobody chased anyone, and the money still landed after the date on the invoice. That's how the scheme works, and every UK business collecting by direct debit is on the same timetable.
Adfin settles direct debit to you on T+3, with payouts every weekday and the fee invoiced separately so the amount that lands matches the collection. Your provider's own settlement timing comes on top of the Bacs cycle, so the two together decide the date you see on your statement.
Are the three days working days?
Almost everyone writing about this says three working days, and you'll want to know how solid that is before you build a report on it.
Bacs itself doesn't say so in the material it publishes openly. The scheme's own description of the cycle uses "less than three days" without qualifying it. What Bacs does publish is a processing calendar, described as holding detailed processing and non-processing day information for every bank holiday, and a calendar of non-processing days only makes sense if non-processing days exist. Providers then state the working-day version directly: GoCardless describes it as the Bacs three working day cycle.
So the practical position is the one to plan around. Collections don't clear on weekends or bank holidays, and an Easter or Christmas run stretches accordingly. The full rulebook that would settle the wording is behind a login for registered service users, so nobody outside that group can quote it, us included.
For your own planning, the safe habit is to look up the processing calendar before you set collection dates in a month containing a bank holiday, and to expect a payout you were counting on for the Tuesday to arrive later that week.
Which dates are you comparing?
Most reporting confusion comes from four different dates being treated as one.
| Date | What happens | Who sets it |
|---|---|---|
| Notice date | Your customer is told the amount and the collection date | You, subject to the notice period |
| Due date | The date on the invoice, and normally the collection date | You |
| Input day | The file goes to Bacs, in the 07.00 to 22.30 window | You or your provider |
| Entry day | Your customer is debited and you're credited, on day three | Bacs |
| Payout date | The money reaches your business account | Your provider's settlement terms |
The Direct Debit Guarantee sets the notice period at "normally 10 working days" ahead of a change to the amount, date or frequency, "or as otherwise agreed". Add that to the front of the cycle and the gap between raising an invoice and having the cash can be a fortnight, all of it by design.
Bacs also lets you submit up to 30 days in advance of the payment date, and allows a recall after submission provided your bank hears from you before its cut off. Submitting early doesn't get you paid early, though. The entry day is what determines when the money moves.
What this does to your reporting
Take a simple example. You invoice 100 clients on the 1st, due on the 1st of the following month, all on direct debit. Every one of them pays without a hitch. Your report says the average invoice was paid three days late, and if the month contained a bank holiday, four or five.
Now scale that. Across all users, 83.4% of the payments Adfin collects on its own rails are direct debits, counting payments and not value (Adfin platform data). It's a similar share for a lot of accountancy practices and subscription businesses. When five sixths of the collections you make carry a built-in three day settlement lag, an average days-late figure across all methods is mostly reporting the Bacs cycle. Move a client onto direct debit and your average days late gets worse while your cash position improves.
That's why Adfin doesn't publish a blended days-late number, and why the guide to credit control metrics carries a caution about reading debtor days when bank debit is most of your book. This article is the longer version of that caution.
The same effect shows up in the other direction. A business that collects mainly by card and bank transfer will show a flattering days-late average and a worse collection rate, because customer-initiated payments arrive whenever the customer acts.
What to measure instead
Four measures survive the settlement lag, and each of them works straight out of your existing reporting.
- Collection success by method. On direct debit, 97.0% of requests clear on the first attempt and 98.7% are eventually collected (Adfin platform data, measured on 269,518 direct debit collections first attempted between July 2024 and mid-July 2026). That measures whether the money arrives, which is what days-late was standing in for.
- On-time rate for customer-initiated payments only. Where your customer chooses when to act, the number means something: 72.7% of Apple Pay payments and 57.9% of bank transfers arrive on or before the due date (Adfin platform data).
- Days late measured from the entry day, not the due date, if you want a lateness figure for direct debit at all. Anything beyond the entry day is a genuine failure and worth looking at.
- Mandate coverage. The share of your recurring revenue with a live mandate behind it predicts next quarter's collections better than any lateness average.
If your current figures report has a single days-late number in it, the least disruptive fix is to split it by method and show the two lines separately. Nobody has to relearn a metric, and the direct debit line stops dragging the average around every time you onboard a client.
What to tell a client who says they've paid
This comes up most often on the phone, and the sequence that resolves it fastest is to check the entry day before you check anything else.
Your client's statement will show the debit on the entry day, and your account shows the credit on the same day, plus whatever settlement terms your provider adds. So if they're looking at a debit dated Wednesday and you're looking at an unallocated invoice on Tuesday, you're both right and nothing needs fixing.
Where a collection has actually failed, you'll get a message from the bank rather than silence, carrying a reason code that tells you whether the account has closed, the mandate has been cancelled, or the balance wasn't there on the day. Until that message arrives, an invoice sitting just past its due date on a live mandate is usually mid-cycle.
Getting the language right in your reminders helps too. A chase that goes out on the due date to a client on direct debit reads as though you haven't noticed you're collecting from them automatically, so it's worth setting your reminder rules to leave collected invoices alone until the cycle has finished.
Common questions
Why has my direct debit not arrived on the due date? Bacs clears collections over a three day cycle of input, processing and entry days, and the money reaches you on the entry day. A collection taken on the due date credits your account a few days afterwards by design, and your provider's settlement terms sit on top of that.
Are Bacs days working days? Providers describe the cycle as three working days, and Bacs publishes a processing calendar covering bank holidays. The scheme's own public description says "less than three days" without stating that they're working days, so plan around the processing calendar and expect bank holidays to extend the run.
Should I count direct debit invoices as paid late? Not for the settlement gap alone. If a lateness figure is useful to you, measure it from the entry day, and compare direct debit only with direct debit so the settlement cycle isn't being read as customer behaviour.
Why did my average days late get worse after moving clients to direct debit? Because the settlement cycle became a larger share of your book. Direct debit is 83.4% of the payments Adfin collects on its own rails, counted by number of payments and not by value, and each of those collections lands a few days after the due date, so the average moves even though collection rates improve.
Can I get direct debit money faster than three days? Not through the Bacs cycle itself. What you can change is your provider's settlement terms and how promptly collections are submitted. For a payment you need today, an instant method like open banking or a card is the practical alternative.
How do I know whether a direct debit has failed rather than settled slowly? The bank tells you. A failed collection comes back with a reason code covering things like a closed account, a cancelled mandate or insufficient funds. No message and a live mandate usually means the collection is still mid-cycle.
Sources
- Bacs — Direct Debit, getting started (accurate as of August 2026)
- Bacs — processing calendar (accurate as of August 2026)
- Direct Debit — the Direct Debit Guarantee (accurate as of August 2026)
This article explains how direct debit settlement timing works and is not legal or financial advice. Last updated August 2026.
