Direct Debit is a pull-based payment method where the customer signs a mandate authorising the supplier to collect funds directly from their bank account on agreed dates. The supplier initiates each collection, making cash flow predictable but requiring strict mandate management, pre-notification, and handling of returns under scheme rules such as SEPA, BACS, and ACH Debit.
Direct Debit is a payment collection method in which the customer pre-authorises the supplier to pull funds from their bank account on agreed dates. The customer signs a mandate once, and from that point the supplier initiates each individual collection through their bank, which routes it to the customer's bank for debit. There is no per-payment approval, no card to expire, and no manual transfer required.
This is the structural opposite of a credit transfer, where the customer pushes funds to the supplier when they choose. With Direct Debit, the supplier controls the timing. For AR teams running recurring B2B billing or subscription models, that single shift transforms working capital. Cash arrives on schedule rather than whenever the customer's accounts payable team gets to the invoice. DSO drops, forecasting improves, and the cost per collection sits well below cards or wire transfers.
The trade-off is operational. Every collection depends on a valid mandate, accurate scheme references, and compliance with pre-notification and refund rules that differ by country. Get the plumbing right and Direct Debit is the most predictable receivable a finance team can hold. Get it wrong and you face rejected collections, customer disputes, and regulatory scrutiny.
Direct Debit is not a single product. It is a family of national and regional schemes that share the pull-payment concept but differ in mandate format, pre-notification rules, refund rights, and return windows.
For any AR team collecting across borders, treating Direct Debit as one process is the fastest route to failed collections. Each scheme needs its own mandate template, pre-notification logic, and return-handling workflow.
The mandate is the legal instrument that authorises every collection. Without a valid mandate, the collection is unauthorised and the customer's bank will reject it or claw it back.
A compliant mandate typically carries a unique reference (the UMR, or Unique Mandate Reference, under SEPA), the creditor identifier, the debtor's IBAN or account number, the type of collection (one-off or recurring), and a signature. Signatures can be paper, electronic, or e-signature depending on what each scheme permits.
Mandates have a lifecycle. They are active from signature, lapsed after a defined period of inactivity (36 months under SEPA, shorter under some schemes), or cancelled by either party. Once lapsed or cancelled, the mandate cannot be used and a new one must be obtained. The most common AR failure mode is presenting a collection against a lapsed mandate and getting an instant rejection that the team only discovers days later in the bank statement.
The split between consumer and business Direct Debit is sharpest in SEPA, but the same logic applies across most schemes.
SDD Core is designed for consumer protection. The payer has an unconditional refund right for 8 weeks from the collection date, no questions asked. For unauthorised collections, the refund window extends to 13 months. The mandate sits with the supplier; the customer's bank is not required to verify it before settlement.
SDD B2B is designed for predictable business-to-business cash flow. Once a B2B collection has settled, there is no refund right. To balance that, the customer's bank must confirm the mandate before the first collection can be presented. This pre-validation step adds friction at onboarding but eliminates the dispute risk that B2C suppliers carry for months after each collection.
For AR teams billing other businesses on recurring contracts, SDD B2B (or its equivalent in other regions) is almost always the right choice. The 8-week refund window of consumer schemes is incompatible with revenue recognition and forecasting in a B2B context.
Returns are a normal part of Direct Debit, not an exception. A small percentage of collections will always fail because of insufficient funds, closed accounts, cancelled mandates, or customer disputes. SEPA codes these as R-transactions, with codes like AC01 (incorrect account), AM04 (insufficient funds), and MD01 (no valid mandate) driving the response logic.
Each R-code implies a different action. AM04 usually means retry in a few days. AC01 means stop and contact the customer to correct the account. MD01 means the mandate is gone and a new one is required before any further collection. Treating all returns the same is the second-most common AR failure mode after lapsed mandates.
Schemes also track return rates. Under SEPA, a return rate above 5 percent (or higher thresholds for unauthorised returns) triggers regulatory scrutiny and can lead to the creditor being suspended from the scheme. Keeping return rates low is a compliance issue, not just an operational one.
Direct Debit at scale is a data problem. A finance team running thousands of recurring B2B collections across multiple schemes cannot manually track mandate aging, pre-notification deadlines, and R-transaction responses. An AI-native AR platform solves this with a live mandate registry that monitors every mandate's status, flags ones approaching the lapse threshold, and triggers re-authorisation workflows before the next collection fails.
Agentic workflows handle R-transactions in real time. Insufficient-funds returns trigger predictive retry on the date the customer's cash position is most likely to clear. Mandate-cancelled returns route directly into a re-mandate flow with the customer. Disputed collections route to a human reviewer with the full context attached.
Most importantly, an AI-native system predicts collection failure risk per customer before the file is even submitted. Customers with rising risk scores get a pre-collection nudge or a payment-method conversation, rather than a blanket retry after the fact. That keeps return rates inside scheme tolerances and turns Direct Debit into the predictable, low-cost receivable it was designed to be.
Direct Debit is a pull payment: the supplier initiates the collection against a pre-signed mandate from the customer. A credit transfer is a push payment: the customer initiates the transfer of funds to the supplier when they choose. Direct Debit gives the supplier control over timing, which is why it is the preferred method for recurring B2B billing and subscription revenue.
It depends on the scheme. Under SEPA, a mandate lapses if no collection is presented for 36 months. BACS and ACH Debit have similar inactivity rules but with different thresholds. Once a mandate has lapsed, any collection presented against it will be rejected and a new mandate must be signed before further collections can be made.
SDD Core is the consumer variant and gives the payer an unconditional 8-week refund right after each collection, extending to 13 months for unauthorised collections. SDD B2B is the business variant: once a collection has settled there is no refund right, but the customer's bank must validate the mandate before the first collection can be presented. B2B suppliers should default to SDD B2B for predictable cash flow.
R-transactions are returned or rejected collections, typically because of insufficient funds, an incorrect account number, a cancelled mandate, or a customer dispute. Each return carries a code (such as AC01, AM04, or MD01 under SEPA) that tells the AR team why the collection failed and what action to take. Treating each code with the right response is essential to keeping return rates inside scheme tolerances.
Pre-notification is advance notice to the customer of an upcoming collection. SEPA SDD requires 14 calendar days notice before the first collection unless a shorter period is agreed in the contract for recurring collections. BACS requires 10 working days notice for any change in amount or date. ACH Debit does not have a separate pre-notification rule but does require prior authorisation. Missing pre-notification is grounds for the customer to dispute the collection.
An AI-native AR platform maintains a live mandate registry, alerts before mandates lapse, and routes R-transactions through agentic workflows that respond to each return code differently. It also predicts collection failure risk per customer before the file is submitted, so finance teams can take pre-emptive action with high-risk accounts rather than blanket-retrying after the fact. The result is lower return rates, fewer disputes, and more predictable cash flow.
