Summary
You can recover most failed direct debits within a few days. Read the failure reason, contact the customer the same day, then retry once the account is funded, collect a new mandate, or take the payment another way. This guide is for the business that collects the debit, not the customer who pays it.
- Why debits fail: Not enough money in the account, a cancelled mandate, a closed or wrong account, or a bank that blocks direct debits. The reason code tells you which.
- What happens to the invoice: It stays unpaid in Xero or QuickBooks. In Paidnice a failed debit freezes the invoice, so no reminder or automatic late fee goes out until you fix it.
- Fees: Charge a fee only if your terms allow it. Paidnice never adds one automatically after a failed debit; you can charge it manually.
A customer who pays you by direct debit every month has just bounced. Stripe marks the payment as failed, the invoice in Xero still shows as unpaid, and the customer has not been in touch. You were relying on that money arriving without anyone chasing it.
Here is why a direct debit fails, what to do for each failure reason, what happens to the invoice and your reminders, and how the five main schemes differ.
Free: Payment reminder email templatesCopy the reminder emails for before, on and after the due date.Why does a direct debit fail?
A failed direct debit means the customer's bank refused or returned the payment, so the money never reached you. The customer's bank sends a reason with the failure, and that reason decides your next step. The common reasons are the same across schemes:
- Not enough money in the account. The most common reason. The mandate is still valid.
- Mandate cancelled. The customer, or their bank, stopped the instruction. You need a new mandate before you can debit again.
- Account closed or details wrong. The customer moved banks or typed the account number incorrectly.
- Debits blocked. The bank has restricted direct debits on the account.
- No reason given. Some banks return a failure without a code, so you have to ask the customer.
Stripe lists each code with a suggested next step. Its SEPA Direct Debit failure table is the clearest example, and the same reasons appear for Bacs, ACH, BECS and PAD.
A failure before the payment clears, or a return after it
A direct debit can fail in two places. Most failures arrive while the payment is still processing, within the scheme's normal clearing time. A few arrive after the payment has already shown as successful.
Stripe says that for Bacs, a bank can report a failure after the payment was marked successful, and Stripe then shows it as a dispute with a reason code. The same can happen with ACH and PAD. On top of that, customers can ask their bank to refund a debit for weeks or months afterwards under each scheme's guarantee.
So "paid" on a direct debit is not final on the day it clears. Keep the invoice reference against the payment so a late return goes back to the right invoice.
What to do, by failure reason
Contact the customer the same day the failure arrives. Most customers do not know their debit bounced, and a quick, plain message gets the payment back faster than a formal reminder a week later.
| Failure reason | What to do next |
|---|---|
| Not enough money | Tell the customer, agree a date the funds will be there, and retry on that date. The mandate still works. |
| Mandate cancelled or revoked | Ask why. If they still want to pay by debit, send a new mandate. If not, send a pay link for card or bank transfer. |
| Account closed or wrong details | Ask for the new account and collect a new mandate. Do not retry the old one. |
| Debits blocked by the bank | Ask the customer to lift the block with their bank, or take this payment another way. |
| Customer disputed the debit | Talk to the customer first. Disputes on bank debits are final, so the money comes back only as a new payment. |
| No reason given | Ask the customer what they see on their side before you retry. |
Do not retry blindly. A second failure on the same mandate can bring another failure fee from your payment provider, and it tells the customer's bank the account has a problem.
What happens to the invoice and your reminders?
The invoice stays unpaid in Xero or QuickBooks, because no money arrived. What your chasing does next depends on your setup.
In Paidnice, a failed direct debit freezes the invoice. A frozen invoice gets no reminders and no automatic late fee until you unfreeze it. That stops a customer who is already sorting out a bounced payment from also getting an overdue reminder about the same invoice.
Once you have fixed the payment, either the retry succeeds and the invoice is paid, or you unfreeze it and your normal reminder schedule picks it up again. A separate setting can also freeze invoices automatically when a payment is reversed in your ledger.
We see a related problem in support. Businesses that collect most customers by direct debit often want those customers out of reminders and statements altogether.
Some add a "Direct Debit" group in Xero or a tag in Paidnice and leave that group off their reminder policies. When a debit fails, that customer then gets no reminder at all, so the failed payment needs a person to pick it up.
Can you charge a fee for a failed direct debit?
You can charge a fee for a failed direct debit only if your terms of trade say so. Without that clause, a fee is hard to defend and it sours a customer who simply had a short month.
Paidnice never adds a late fee automatically after a failed debit. If your terms allow one, you can charge it manually from the invoice. Some businesses waive it the first time and charge it if the same customer bounces again.
How Bacs, SEPA, ACH, BECS and PAD differ
Each scheme has its own clearing time and its own window for customers to dispute a debit. These figures are from Stripe's documentation for each scheme.
| Scheme | Time to confirm the outcome | How long a customer can dispute |
|---|---|---|
| Bacs (UK) | About 4 business days, or 7 with a new mandate | No set time limit |
| SEPA (euro) | At least 6 business days | 8 weeks with no questions, up to 13 months if unauthorised |
| ACH (US) | Up to 4 business days | 2 business days for a business account, 60 days for a personal one |
| BECS (Australia) | Up to 2 business days | Up to 7 years |
| PAD (Canada) | Up to 5 business days | 10 business days for a business account, 90 days for a personal one |
Sources: Stripe's pages on Bacs, SEPA, ACH, BECS and PAD.
How Paidnice handles a failed direct debit
Paidnice collects direct debits through Stripe on all six schemes it supports: ACH, Bacs, SEPA, BECS, NZ bank debit and Canadian PAD. It charges no fee of its own for direct debit on invoices, on every plan.
- Payments page. Every payment attempt is listed in one place, from pending bank debits and failed payments to abandoned checkouts and payments that did not sync to your ledger. A failed debit shows there the day Stripe reports it.
- Frozen invoice. The invoice freezes, so no reminder or automatic late fee goes out while you sort it.
- Another way to pay. The customer payment portal lets the customer pay that invoice by card or by debit, or pay several invoices at once.
- Replies in one place. When the customer answers your message, the reply lands in the shared inbox, where a teammate can pick it up.
- Fee, if you choose. If your terms allow a fee, you add it manually. Your late fee policies stay as they are for every other invoice.
If the customer keeps missing payments after this, move them from direct debit back onto your normal escalation ladder of reminders, a call and a final notice.
💡 Paidnice insight
A failed debit is the one time a customer on autopay needs a person to talk to them. Freezing the invoice stops the automatic reminders, so make sure someone owns the follow-up call or email the same day.
Card payments fail in different ways, with different fixes. If the payment that failed was a card, read what to do when a Stripe payment fails. If the customer insists they have paid, start with checking where the money went.
Frequently asked questions
Will a direct debit try again on its own?
It depends on your payment provider and your setup. Some providers retry a debit that failed for lack of funds after a few days, and others wait for you. Before any retry, ask the customer whether the money is there, because a second failure can bring another fee.
What does a returned direct debit mean?
A returned direct debit is a payment the customer's bank sent back after first accepting it. The money leaves your account again, and the invoice is unpaid once more. Treat it like any other failure: read the reason and contact the customer.
Does a failed direct debit cancel the mandate?
Not always. A failure for lack of funds leaves the mandate in place. A cancelled instruction, a closed account or a dispute usually ends it, and you need a new mandate before you can debit that customer again.
Should I take a customer off direct debit after one failure?
Usually not. One failure for lack of funds is common and rarely repeats. If the same customer fails two or three times, ask them to pay each invoice by link instead, or put them on a payment plan.
Do I need to tell the customer their direct debit failed?
Yes. Stripe tells you, but the customer may not notice for days. A short message the same day, with the amount and a way to pay, gets the invoice settled faster than waiting for the next reminder.
Paidnice features in this article
- Direct debit Lets customers pay by direct debit through Stripe: ACH, Bacs, SEPA, BECS, NZ bank debit and Canadian PAD.
- Customer payment portal Shows customers every open invoice in one place, where they can pay.
- Late fees and interest Adds late fees and interest to overdue invoices when you turn them on.
About the editorial team
Ashley is a co-founder and lead developer of Paidnice and has built accounting software for more than 10 years. He builds the ledger connections that put reminders, late fees and payments into Xero, QuickBooks and ERPs such as NetSuite and Business Central. Before Paidnice he co-founded A2X, ecommerce accounting software for Xero and QuickBooks.
App of the Year