The SEPA direct debit scheme is the shared set of rules that lets a business collect euro payments from bank accounts across the Single Euro Payments Area using one process. SEPA, short for Single Euro Payments Area, covers the euro-area countries and a number of other European states that have joined the arrangement.
Before SEPA, each country ran its own domestic direct debit system with different forms and formats. Common standards now let a gym in Spain collect from a member’s account in Belgium much as it would locally. This guide explains how the scheme is structured and what it means for payers and collectors.
Why a Single Scheme Changed Euro Collections
The main achievement of SEPA is that a cross-border euro direct debit inside the area follows the same rules as a domestic one. A collector does not need a separate agreement with a bank in every country where its customers live. One mandate format and one file standard cover them all.
The rules are written by the European Payments Council, known as the EPC, which publishes rulebooks for each scheme. Banks that want to offer SEPA direct debits must adhere to those rulebooks. European Union regulation also requires that payments in euro be processed without discrimination based on where in the area an account is held.
For a customer, this means a euro account in one SEPA country can generally be used to pay bills from another. In practice, some collectors still ask for a local account, which raises questions that the article on international payments explores further.
Core and B2B: Two Schemes With Different Rules
The SEPA direct debit scheme is actually two schemes. They share the same basic message formats, but they offer very different levels of protection, so it matters which one a mandate uses.
SEPA Direct Debit Core
The Core scheme is designed for consumers, although businesses can use it too. Its defining feature is a generous refund right. A payer can typically ask their bank to refund an authorised debit within a set period without giving a reason, and has a longer period to claim for a debit that was never authorised.
The exact periods are set in the rulebook and in EU payment law, and payers should confirm the current figures with their bank.
SEPA Direct Debit B2B
The B2B scheme is only for payers that are not consumers, such as companies. It offers faster certainty for the collector because the payer cannot claim a no-questions refund for an authorised debit. To balance that, the payer’s bank must check each B2B mandate against the payer’s own confirmation before accepting debits.
This makes B2B suited to larger commercial invoices, where both sides want finality and the payer has controls in place.
Choosing Between Them
A business collecting from households will normally use Core, since consumers cannot be placed on B2B. Between companies, the choice depends on whether the collector values protection from refunds and whether the payer is willing to register mandates with its bank.
Some payers’ banks do not offer B2B at all, so the collector should confirm availability before relying on it.
The Mandate and Its Key Identifiers
Every SEPA direct debit rests on a mandate, the payer’s signed or electronically confirmed permission for the collector to take payments. The mandate also authorises the payer’s bank to honour those debits. It is held by the collector, which must be able to produce it if a payment is questioned.
- Unique mandate reference: a code the collector assigns, which identifies that specific mandate and appears with each debit.
- Creditor identifier: a code that identifies the collector across the scheme, issued through a national authority or bank.
- Payer’s IBAN: the International Bank Account Number that identifies the account to be debited.
- Payment type: whether the mandate is for recurring collections or a single one-off payment.
- Date and signature or electronic confirmation of the payer’s agreement.
Together, the mandate reference and creditor identifier let a payer recognise who is collecting and under which permission. If a debit shows an unfamiliar creditor identifier, that is a good reason to contact the bank before the refund window closes.
Pre-Notification Before Each Collection
The SEPA direct debit scheme requires collectors to tell payers in advance about the amount and date of upcoming debits. This message is called pre-notification. It can be a single schedule for fixed recurring payments or a separate notice before each variable payment.
The rulebook sets a default minimum notice period, but the collector and payer can agree a different period in their contract. The notice can arrive by email, letter, invoice or within a customer account, depending on what was agreed when the mandate was signed.
For payers, pre-notification is the moment to check that the account has enough money and that the amount is correct. Suppose an energy supplier notifies a debit of €120 for a quarter, but the payer expected €90. Querying it with the supplier before the collection date is far easier than reversing it afterwards.
How a Collection Moves Through the System
The collector sends its bank a file of debits in the ISO 20022 XML format, a global standard for payment messages. Each debit carries the mandate data, the amount and the due date. The collector must submit the file within the time limits the rulebook and its bank set before that due date.
The collector’s bank passes the file through a clearing and settlement mechanism, which routes each debit to the payer’s bank. On the due date, the payer’s bank debits the account and funds settle between the two banks.
The payer’s bank can refuse a debit before settlement if, for example, the account is closed or the payer has blocked direct debits. That makes the collection a rejected item rather than a completed payment, so no money leaves the payer’s account.
R-Transactions: When a Debit Does Not Complete
SEPA groups every exception under the label R-transactions, since each type begins with the letter R. Each one carries a reason code that tells the collector what happened, so it can decide whether to try again, contact the customer or close the mandate.
- Reject: the debit is refused before settlement, often because of invalid data.
- Refusal: the payer asks their bank not to pay a specific debit before it is collected.
- Return: the payer’s bank sends back a settled debit, for example for insufficient funds or a closed account.
- Refund: the payer claims money back after the debit was paid, under the refund rights of the scheme.
- Reversal: the collector itself reverses a debit it sent in error.
Time limits apply to each type and are set in the rulebook. Collectors should design their systems to read reason codes accurately, since retrying a payment the payer has refused can damage trust and may breach the agreement.
Payer Rights and Protections Under SEPA
A consumer in the Core scheme has strong protections. Beyond the no-reason refund right for authorised debits, a payer can claim back an unauthorised debit for a much longer period, and the bank must investigate. These rights come from both the scheme rulebook and EU payment services law.
Payers can also instruct their own bank to limit direct debits. Banks may let customers block all direct debits, allow only listed creditors, block specific creditors, or cap the amount or frequency of collections. The exact options available depend on the bank and the country.
Cancelling a mandate is normally done with the collector, but telling the bank as well adds a safety layer. Keeping the mandate confirmation and pre-notifications on file helps prove what was agreed if a dispute arises later.
What Collectors Need Before Joining the Scheme
A business that wants to collect through the SEPA direct debit scheme must first obtain a creditor identifier and open a collection arrangement with a bank that participates in the scheme. The bank will usually assess the business’s risk profile, because it carries exposure if collections are later refunded.
The business then needs compliant mandate forms, whether paper or electronic, along with a process for storing mandates and sending pre-notifications. Software or a payment service provider normally builds the XML files and handles returns, but the legal responsibility for valid mandates stays with the collector.
Contracts with the bank set fees, limits and timelines, and these vary widely. Reading the agreement closely and asking about R-transaction handling before launch prevents many common operational surprises.
Common Mistakes That Cause Problems
Many SEPA collection problems trace back to a few avoidable errors. On the payer side, the most frequent is giving a mistyped IBAN, which leads to a rejected first debit and sometimes a late-payment charge from the collector under its own terms.
Another payer mistake is closing an account or switching banks without updating mandates. The old mandates do not move automatically in every case, so debits may fail. Listing every active mandate before a switch, and contacting each collector, avoids gaps in payments for rent, insurance or utilities.
Collectors run into trouble when they change the amount without proper pre-notification, reuse a mandate reference for a different agreement, or keep collecting after a customer cancels. Each of these can trigger refunds and complaints. Clear internal records and a single owner for mandate changes reduce the risk considerably.
Making Good Use of SEPA Direct Debits Going Forward
The SEPA direct debit scheme continues to be updated through regular rulebook releases from the EPC. Changes may cover data fields, timelines or the treatment of electronic mandates, so payers and collectors benefit from checking the current version rather than relying on older guides.
Payers can get the most from the scheme by keeping mandate references, reading every pre-notification, and reviewing statements soon after each collection. Doing so keeps the refund rights usable when they are needed.
Collectors that plan ahead, choose the right scheme for each customer type, and handle R-transactions promptly can use SEPA to serve customers across many countries with one process. Asking the bank about upcoming rulebook changes once a year is a simple way to stay compliant.