SEPA direct debit is an effective way to collect customer payments, particularly for recurring invoices. Unlike a bank transfer, the payment instruction is initiated by the supplier, based on a mandate signed by the customer. This gives the creditor greater control over the collection timetable and makes reconciliation easier.
It is not, however, a payment guarantee. A debit may be rejected because the customer's account lacks funds, and refund rights depend on the SEPA scheme used. These distinctions matter in B2B credit management.
Why use SEPA direct debit?
For a supplier, the main advantage is the ability to initiate collection on the agreed payment date instead of waiting for the customer to issue a bank transfer. When the customer's bank account has sufficient funds and the debit is accepted, this helps reduce late payments.
It is particularly useful for subscriptions, maintenance agreements, service contracts and other recurring business relationships. For customers, it removes repetitive payment administration while retaining visibility over the amounts and dates collected.
- More predictable cash receipts: the creditor schedules the payment instruction.
- Less administration: recurring payments can be managed without requesting a new transfer for every invoice.
- Easier reconciliation: payment references can be associated with the relevant customer account and invoices.
- Better customer experience: fewer manual steps and fewer forgotten due dates.
SEPA direct debit is available across the SEPA geographical area, which extends beyond the euro area. The transaction is denominated in euros, and participating banks must support the relevant scheme.
Important: direct debit does not eliminate credit risk. Insufficient funds, incorrect bank details, invalid mandates and scheme-specific refunds or returns can still result in non-payment.
Understand the difference between SEPA Core and SEPA B2B
The distinction between the two main SEPA direct debit schemes is essential. A business customer is not automatically using the SEPA B2B scheme simply because the transaction is between companies.
| Feature | SEPA Core | SEPA B2B |
|---|---|---|
| Who can pay? | Consumers and businesses | Business payers only; not consumers |
| Refund of an authorised debit | The payer generally has an unconditional refund right for eight weeks from the debit date | No equivalent unconditional refund right for an authorised debit under the scheme |
| Unauthorised debit | Can generally be challenged for up to 13 months under applicable payment-services rules | Subject to the B2B scheme rules and applicable law; absence of an unconditional refund does not validate an unauthorised debit |
| Mandate verification | The creditor retains the mandate; the debtor's bank does not routinely verify it before each collection | The debtor's bank must verify mandate information before accepting B2B collections |
| Bank availability | Widely supported | Requires the debtor's bank to offer the B2B scheme |
For suppliers seeking greater certainty on recurring business collections, SEPA B2B can be attractive. But it requires the customer's cooperation, the correct mandate registration and bank support. A failed or rejected debit remains possible.
How to set up SEPA direct debit: step by step
- Choose the appropriate scheme with your bank. Check whether SEPA Core or SEPA B2B is suitable for the customer and whether both banks support the selected scheme.
- Obtain a SEPA Creditor Identifier (SCI). Your bank explains the application process in your country. The identifier is assigned through the relevant national arrangements; it is not necessarily issued directly by the central bank.
- Assign a Unique Mandate Reference (UMR). Each mandate needs a unique reference, up to 35 characters, used together with the creditor identifier to identify the authorisation.
- Obtain the customer's signed mandate. Include the creditor details, SCI, UMR, payer details and IBAN, along with the scheme-specific mandate wording. Keep evidence of the authorisation securely.
- For SEPA B2B, ensure the customer registers or confirms the mandate with its bank. Otherwise the bank may reject the first debit.
- Provide the required pre-notification. Inform the payer of the amount and collection date within the agreed notification period. The standard period is 14 calendar days unless another period has been agreed.
- Submit the collection instruction. Send the payment file through your bank using the appropriate scheme and the bank's submission deadlines. For recurring invoices, automate the process where possible.
- Monitor settlement, returns and reconciliation. Match collections to invoices, investigate rejections promptly and follow up on any amount that remains unpaid.
The process is simple in principle, but successful deployment requires coordination between credit management, accounting, treasury, IT and the customer.
The SEPA direct debit mandate
The mandate formalises the customer's authorisation for the supplier to initiate collections and for the customer's bank to debit the designated account. It may cover a single payment or recurring collections, depending on the arrangement.
A properly managed mandate process should include:
- The correct SEPA Core or SEPA B2B mandate wording.
- The creditor's name and SEPA Creditor Identifier.
- The payer's identification and IBAN.
- A Unique Mandate Reference and the mandate signature or valid electronic authorisation.
- Secure storage, traceability and management of changes, cancellations and inactive mandates.
- Clear customer communication about invoices, amounts and debit dates.
Mandate templates should come from the bank or a reliable provider implementing the current scheme requirements. The mandate is normally retained by the creditor rather than systematically transmitted to the creditor's bank; the specific verification process differs under the B2B scheme.
SEPA direct debit from a Credit Manager's perspective
Direct debit is an excellent operational tool when the customer relationship is sound. It helps reduce payment delays caused by forgetfulness or slow administrative processes and makes receipts more predictable.
Nevertheless, control over the payment instruction is not the same as certainty of payment. A customer experiencing financial difficulties may have insufficient funds; a collection can also be rejected or returned for technical or mandate-related reasons.
This is why the method is particularly suitable for customers whose payment behaviour and financial position are well understood. For higher-risk exposures, it can be combined with appropriate protections such as trade credit insurance or a bank guarantee, subject to the terms of those instruments.
In addition, payment incidents should be integrated into the collection process. A rejected debit requires immediate investigation: was it caused by a missing mandate, incorrect IBAN, insufficient funds or a customer objection? The response should address the real cause rather than simply repeating the same collection instruction.
Conclusion
SEPA direct debit is a practical way to improve collection efficiency, particularly for recurring B2B invoices. It reduces administrative friction and allows the supplier to initiate payment on the agreed date. The choice between SEPA Core and SEPA B2B, the quality of the mandate process and the monitoring of rejected collections are decisive.
As with any collection method, technology supports credit management expertise; it does not replace customer risk assessment or the need to resolve payment problems.