You're never told that it did. Bacs publishes nine kinds of report and not one confirms a successful collection: they confirm that a payment file was submitted, or they tell you which collections came back unpaid. So you learn about failure, and success is what you infer once the return window has passed without a rejection.
The short version
- Bacs lists nine report types and not one of them is a success advice.
- Its reports "can confirm a payment file has been successfully submitted", covering your file and nothing beyond it.
- Unpaid collections come back by ARUDD, "available within 1 to 2 PSP working days after the payment / collection date".
- Action on an ADDACS advice "must be taken within 3 working days of the advice being made available".
- A collection marked confirmed can still fail. GoCardless calls that a late failure and publishes no date after which it can't happen.
- Our own rule: treat a collection as good once the ARUDD window has closed, and keep the residual risk in view on anything large.
The reports Bacs sends you
Bacs publishes the reports you can collect as a service user: input reports for live and test submissions, arrival reports, withdrawal reports, and six kinds of advice, ARUCS and ARUDD and AUDDIS and ADDACS and AWACS and DDIC. Nine types, and not one of them is a confirmation that a payment cleared. Each tells you either what happened to your submission or what came back.
The Little Bacs Guide is careful about this. Under its heading about checking your submissions have been successful, it points you to reports "which can confirm a payment file has been successfully submitted or can alert you if there is an error".
A file, then. Your file reached Bacs, it was formatted properly and it entered the cycle. Whether the money left your customer's account three days later is something no report addresses.
That leaves you one signal. ARUDD, in Bacs's words, is the "automated system used by the banks to return unpaid Direct Debit payments", and "the ARUDD report lists the unpaids". Silence there is the nearest thing to a yes the scheme gives you.
The windows you can time against
Two published timings turn that silence into something usable.
| Report | What it tells you | Bacs's published timing |
|---|---|---|
| ARUDD and ARUCS | Collections and credits the payer's bank returned unapplied | "Available within 1 to 2 PSP working days after the payment / collection date" |
| ADDACS | A mandate has been amended, cancelled or reinstated | No transmission time published. Action "must be taken within 3 working days of the advice being made available" |
Both quotations are Bacs's own: the window from the Little Bacs Guide, the deadline from the ADDACS page. That page also recommends applying changes immediately.
The ARUDD figure is the one your ledger needs, and it's oddly hard to find: it's buried in a PDF guide and never appears on the ARUDD description page. One to two working days after the collection date is when a rejection can be expected, so a collection still unrejected after that has a decent claim to be good.
The ADDACS deadline works the other way round. Bacs doesn't say when the advice reaches you, only that you have three working days to act once it's available. An advice on a live mandate also tells you the next collection won't work even when the last one did. The codes are in our guide to AUDDIS and ADDACS reason codes.
Why "confirmed" in your dashboard can still be wrong
Providers show a status, and it's easy to read that as a fact about your bank balance. GoCardless publishes the exception plainly: "late failures occur when a paying customer's bank fails to inform us that a payment could not be collected and so the payment gets marked as confirmed, but without the funds having been received".
The bank then sends a delayed report, "usually within 1 additional business day". If your payout has already gone out, the amount comes back off a later one, because GoCardless rebalances a negative account against a subsequent payout. So a collection you were paid for in March can be debited in April.
What nobody publishes is a point of irreversibility. GoCardless gives no period after which a UK Bacs collection is definitively safe, and neither does Stripe or the scheme. For SEPA, where late reports are more common, GoCardless recommends allowing "a minimum of 7 business days following confirmation of a payment being successfully charged, before processing a refund", which shows the shape of the thinking without giving you a UK number. So any article offering you a specific number of days for Bacs has invented it, and we can't give you one either.
What you can rely on, and when
Verified and safe to work from: no Bacs report confirms an individual collection, ARUDD returns arrive within one to two working days, and a status of confirmed can turn out to be wrong. Our own operational rule follows from those, and it's ours rather than the scheme's: treat a collection as good once the ARUDD window has closed, so two working days after the collection date if you want the safer end. Before that, call it expected and hold off. After it, accept that the late-failure route stays open and size your exposure accordingly on anything large.
One caveat covers all of it. The Bacs Direct Debit and Bacs Direct Credit Guide and Rules and the Service User's Guide are held on password-protected microsites for registered service users, so the scheme rules aren't public. Everything here comes from Bacs's public pages and its public Little Bacs Guide: better sourcing than this subject usually gets, and still not the rulebook.
What that means for your ledger
Four habits follow from a system that reports failure and stays quiet about success.
- Mark a collection as received when your provider's payout lands, and use the ARUDD window instead of the collection date to decide when a reversal stops being likely.
- Hold anything irreversible until the window has closed. Late failures tend to cause the most trouble where goods have been released, or an overpayment refunded, on the strength of a same-day confirmed status.
- Read every advice the day it arrives. A cancellation you act on today can save a collection that would otherwise have failed, and an attempt against a mandate the bank has already told you about can turn into an indemnity claim.
- Reconcile the deduction as well as the credit. If your provider nets a late failure off a later payout, your invoice needs reopening, and a smaller payout may be the only place you'll see it.
Adfin applies advices to the mandate automatically, retries a failed collection for free and can fall back to a card, so a late failure updates your records without anyone opening a report.
Common questions
Does Bacs confirm that a direct debit has been paid? No. Bacs lists nine report types and not one confirms a successful collection. Its Little Bacs Guide describes reports that "can confirm a payment file has been successfully submitted", which is about your submission rather than the money. You learn about failures and infer success from their absence.
How long does it take to know a direct debit has failed? Bacs publishes that ARUDD and ARUCS reports are "available within 1 to 2 PSP working days after the payment / collection date", so a rejection normally reaches you within two working days. GoCardless says failure reports typically arrive one working day after the charge date.
Can a direct debit fail after it shows as successful? Yes. GoCardless calls it a late failure: the payer's bank doesn't tell them a payment couldn't be collected, so it gets marked confirmed "without the funds having been received". The delayed report usually follows within one more business day, and the amount can come off a later payout.
When is a direct debit irreversible? Neither Bacs nor any provider publishes a point at which a UK Bacs collection becomes irreversible, so any number of days you see quoted is somebody's estimate. The risk drops sharply once the ARUDD window closes, and it doesn't reach zero.
Should I wait before refunding a customer who has paid by direct debit? For anything material, yes. GoCardless recommends allowing at least 7 business days after a confirmation before refunding a SEPA payment, and publishes no UK equivalent. Waiting for the ARUDD window avoids refunding money that comes back off your next payout.
Where do I see whether a collection was returned? On the ARUDD report, collected through the Bacs payment services website or your Bacs software, or in your provider's dashboard and webhooks if you use one. Bacs says advices "contain time-critical information" and need accessing promptly.
Sources
- Bacs — collecting reports (accurate as of August 2026)
- Bacs — ADDACS (accurate as of August 2026)
- Bacs — the Little Bacs Guide (PDF) (accurate as of August 2026)
- GoCardless — late failures (accurate as of August 2026)
This article explains how Bacs reporting works and is not legal or financial advice. The scheme rulebook is not publicly available. Last updated August 2026.
