SEPA Direct Debit
The SEPA Direct Debit is a standardised payment method within the Single Euro Payments Area (SEPA) in which the payee collects a due amount directly from the payer's account based on a mandate granted by the payer.
The SEPA Direct Debit is a unified European payment method in which the payer does not transfer money; instead, the payee actively collects the due amount from the payer's account. The legal basis for every collection is a SEPA direct debit mandate: the payer authorises the payee, once or on a recurring basis, to debit amounts from their account and at the same time instructs their bank to honour these debits. The scheme applies uniformly across all SEPA member countries and, since 2014, has replaced the former national direct debit schemes such as the German "Einzugsermächtigung".
SEPA stands for the "Single Euro Payments Area", the unified euro payment area. Within this area, euro payments are processed according to the same rules, formats and deadlines, regardless of whether they take place within a single country or across borders. For the direct debit, this means: standardised account identifiers via the IBAN, a machine-readable XML data format for submission to the bank, and a Europe-wide set of rules for mandates, pre-notification and return deadlines. For companies, the SEPA Direct Debit is thus the central instrument for collecting recurring or agreed receivables automatically and on schedule.
At a glance
- The payee collects the amount – the payer does not transfer it
- Every collection requires a valid SEPA mandate from the payer
- Two variants: Core direct debit for consumers, B2B direct debit for businesses
- Prerequisite: creditor identification number (creditor ID) and mandate reference
- Submitted to the bank as an XML file (pain.008 format), amount in euros
What is a SEPA Direct Debit and how does it work?
With the SEPA Direct Debit, the payee – the creditor – initiates the payment. They submit the collection through their bank, which requests the amount from the payer's account; the payer's bank debits the amount and makes it available to the creditor as a credit. This reverses the direction compared to a credit transfer: instead of waiting for the payment to arrive, the payee actively collects the due amount. A valid mandate, with which the payer has expressly authorised the collections, is always a prerequisite.
The process follows a fixed pattern. The creditor concludes a payment agreement with the customer, obtains the mandate and announces every debit in advance (pre-notification). On the due date they generate a direct debit file and submit it to their bank on time. The bank forwards the individual items via interbank clearing to the payer's bank, which debits the account. If the payer's bank does not honour the direct debit – for example due to insufficient funds or an objection – a return debit occurs, and the amount is deducted from the creditor again.
Components: mandate, creditor ID and mandate reference
Three elements are what make a collection valid in the first place. The SEPA mandate is the payer's written or electronic authorisation and must contain the mandatory details. The creditor identification number (creditor ID) uniquely identifies the payee across Europe; in the DACH region it is issued in Germany by the Deutsche Bundesbank and in Austria by the Oesterreichische Nationalbank. Finally, the mandate reference is an identifier assigned by the creditor that uniquely designates a specific mandate. Together, the creditor ID and mandate reference identify each individual direct debit and accompany it throughout the entire process.
Core and B2B direct debit: the two variants
The SEPA rulebook defines two direct debit schemes that differ in target group, deadlines and refund rights. The SEPA Core Direct Debit is open to everyone and is the standard scheme for payments by consumers. It is deliberately designed to be customer-friendly: the payer can object to an authorised debit within eight weeks of the debit date without giving reasons and is refunded the amount. For an unauthorised direct debit – for example without a valid mandate – this deadline extends to thirteen months.
The SEPA Business-to-Business Direct Debit (B2B) is intended exclusively for payments between businesses; the payer may not be a consumer. Here the payer waives the right to a refund: once a B2B direct debit has been honoured, it can no longer be reclaimed. In return, the payer's bank checks before honouring it whether a valid mandate exists – for this the payer must also report the mandate to their own bank. The B2B direct debit therefore offers the creditor greater planning certainty, but is more complex to handle.
One-off and recurring direct debits
A mandate can apply to a one-off payment or to a series of recurring payments. For recurring direct debits – such as subscriptions, rents or instalment payments – the first collection is marked as "FRST" or "RCUR", and subsequent collections as "RCUR". A mandate expires if it has not been used for 36 months. If a one-off direct debit is collected, the mandate lapses with the collection. This marking controls deadlines and checks in the clearing process and is carried along automatically by the ERP or payment system.
Why the SEPA Direct Debit matters for companies
The SEPA Direct Debit shifts the initiative for the payment from the customer to the company, making incoming payments predictable. Instead of hoping for punctual transfers and chasing overdue customers with reminders, the creditor collects due amounts itself on the agreed date. This shortens the time between invoice and payment receipt, reduces the share of open items and improves liquidity planning – especially for recurring revenue such as subscriptions, maintenance contracts or instalment purchases.
Added to this are low transaction costs and a high degree of automation. Once set up, mandates can be used for any number of collections; a single payment run bundles hundreds of receivables into one file. Compared with credit cards or payment service providers, percentage-based fees are largely eliminated. The residual risk of a return debit does remain, but it is calculable and can be managed through credit checks and dunning processes.
SEPA Direct Debit in the ERP system
In the ERP or merchandise management system, the SEPA Direct Debit is closely interlinked with accounts receivable, open items and payment processing. Per customer, the system manages the stored mandates with creditor ID, mandate reference, signature date and sequence type, and links them to the debtor's bank details. On the due date, a payment run selects all collectible open items, checks the mandates and generates the SEPA XML file in pain.008 format, which is transmitted to the bank.
After submission, the system tracks the returns: honoured direct debits clear the open items, while return debits are automatically re-posted as receivables and, where applicable, trigger a dunning process or a return debit fee. The end-to-end mapping of mandate, pre-notification, collection and return ensures audit-proof documentation and saves manual maintenance in banking software and spreadsheets. How deeply individual products map SEPA and mandate management varies; examples can be found under "Related systems".
Distinctions: SEPA Direct Debit vs. credit transfer and standing order
The SEPA Direct Debit is often confused with the SEPA Credit Transfer, even though the direction of payment runs the opposite way. With the credit transfer, the payer initiates the payment and actively pushes the money to the payee; with the direct debit, the payee pulls the amount based on a mandate. Control over the timing therefore lies once with the payer and once with the creditor. For the creditor, the direct debit is thus the more predictable instrument; for the payer, the credit transfer is the more controlled one.
From a standing order, the direct debit differs in the flexibility of the amount. A standing order transfers a fixed amount at a fixed interval from the payer's account and is set up by the payer – it is only suitable for constant sums. The direct debit, by contrast, can collect varying amounts, such as usage-based invoices, and is controlled by the payee. A further distinction is the payment service provider collection (for example via payment providers in online retail), which technically bundles the SEPA Direct Debit as one of several payment methods but is fundamentally built on the same scheme.
Example
Example: subscription billing in e-commerce
A retailer sells a monthly consumables subscription. At checkout the customer stores their IBAN and grants a SEPA Core direct debit mandate; the ERP saves the mandate reference, creditor ID and sequence type "FRST" for the first debit. Two days before each due date, the system sends the pre-notification by email with the amount and debit date. On the due date, the payment run bundles all due subscriptions into a pain.008 file and transmits it to the house bank.
With 3,000 subscribers, this results in a single payment run instead of 3,000 individual incoming transfers. The honoured direct debits clear the open items automatically. The system re-posts twelve return debits due to insufficient funds as receivables and triggers the dunning run plus a return debit fee for the affected customers – without accounting having to manually maintain a single item.
Frequently asked questions
Related services
Sources
Questions about SEPA Direct Debit in your ERP project?
We advise vendor-neutrally – and implement it ourselves on request.