SEPA explainer General SEPA knowledge

SEPA Direct Debit mandates explained

Last updated: 25 October 2026 · Official sources checked: 25 October 2026

A SEPA Direct Debit lets a business (the creditor) collect euro payments from a customer’s account (the debtor) anywhere in the SEPA area. It only works with the debtor’s prior authorisation: the mandate. This guide explains the mandate rules of the two European Payments Council (EPC) schemes, SEPA Direct Debit Core and Business to Business (B2B), as they stand in the 2025 rulebooks.

This is a summary for orientation, not legal advice. The rulebooks are binding on banks, and your bank’s creditor agreement sets the conditions that apply to you. Where we quote a rule, the source is listed at the end.

What a mandate is

The EPC defines the mandate as the debtor’s consent and authorisation, given to the creditor, to initiate collections from the debtor’s account, and to the debtor’s bank to comply with those collections.

In practice that means:

• the creditor obtains the mandate before the first collection, usually by a paper form or an electronic process;
• the creditor stores it and must provide a copy when the bank asks, for example when a customer disputes a collection;
• each collection carries the mandate data — the unique mandate reference, the date of signature and the creditor identifier — so the banks can link the debit to the authorisation.

For a standard paper mandate in the Core scheme, the debtor’s bank does not receive or check a copy of the mandate. The scheme also has an optional e-mandate service, in which the debtor’s bank takes part in the electronic signature process and in storing the mandate data.

What a mandate must contain

The rulebooks list the mandatory content. In summary:

Element	Notes
Title	”SEPA Direct Debit Mandate”; a B2B mandate must be identified as “SEPA Business to Business Direct Debit Mandate”.
Unique mandate reference	Chosen by the creditor, unique per creditor. The XML message limits it to 35 characters.
Creditor name, address and creditor identifier	See creditor identifier below.
Debtor name and IBAN	The debtor’s address is mandatory only when a bank involved is outside the EEA.
Debtor bank BIC	Only in specific cases involving non-EEA SEPA countries.
Type of payment	Recurrent or one-off.
Date and place of signature, signature	Paper or a legally binding electronic signature.
Standard text	The authorisation and, for Core, the refund-right statement.

The EPC also publishes guidelines on the appearance of the mandate form.

The creditor identifier

To collect by SEPA Direct Debit, a creditor needs a creditor identifier (CI). It starts with an ISO country code and check digits, followed by a national identifier defined in each country. How you obtain one varies by country — in some countries your bank requests it for you, in others a national body issues it — so ask your bank. The EPC’s Creditor Identifier Overview lists the format used in each SEPA country.

CORE versus B2B

	SDD Core	SDD B2B
Debtor	Consumers and businesses	Businesses only (non-consumers)
Refund of an authorised collection	Debtor can ask for a refund within 8 weeks of the debit, without giving a reason	No refund right for authorised collections
Unauthorised collection (no valid mandate)	Refund claim within 13 months	The debtor’s bank checks the mandate data before debiting (next row)
Debtor’s bank and the mandate	Does not check the mandate (paper mandates)	Must obtain the debtor’s confirmation of the mandate data before the first debit, and checks each later collection against it
Latest presentation to the debtor’s bank	1 interbank business day before the due date (D-1)	D-1

Both schemes use the same message type (pain.008 from customer to bank), but a file contains collections of one scheme only, and the bank must offer the scheme to you. A B2B collection will be refused if the debtor has not confirmed the mandate with their bank, so plan this step with your business customers.

Your bank usually sets an earlier deadline than D-1 for receiving your file. The older Core option with a shortened timeline (code COR1) no longer exists since the timelines were harmonised in 2016.

Pre-notification

Before each collection, the creditor must inform the debtor of the amount and the due date. The default is at least 14 calendar days before the due date, unless creditor and debtor have agreed a different period — many contracts agree a shorter one, or a single schedule for recurring fixed amounts.

Sequence types: FRST, RCUR, OOFF, FNAL

Each collection states where it sits in the life of the mandate:

Code	Meaning
OOFF	One-off collection under a one-off mandate.
FRST	First collection of a recurrent series. Optional since November 2016.
RCUR	Recurrent collection. Can also be used for the first collection.
FNAL	Last collection of a recurrent series.

Since November 2016, a first collection can be sent as RCUR; a collection marked FRST is processed as a recurrent collection. Some banks and older systems still expect FRST, so check your bank’s guidance. A one-off mandate cannot be used again after its collection, and a series ended with FNAL should not be collected again.

Changes and expiry

• Amendments. If the creditor changes the mandate reference or its creditor identifier, the next collection must flag the amendment and carry the original values. Other changes, such as a new debtor account, are also signalled in the collection; your bank’s format guide explains how.
• Expiry after 36 months. If no collection is presented under a mandate for 36 months (counted from the latest collection presented, even if it was rejected, returned or refunded), the creditor must cancel the mandate and obtain a new one before collecting again. Banks do not have to check this; it is the creditor’s obligation.
• Cancellation. A debtor can revoke a mandate. Stop collecting under it, and keep the records your local law requires.

Practical checklist for a creditor

1. Agree SEPA Direct Debit collection with your bank (Core, B2B or both) and obtain a creditor identifier.
2. Use a mandate form with all mandatory content and a unique reference.
3. For B2B, ask the customer to confirm the mandate with their bank.
4. Store signed mandates safely and be able to provide a copy.
5. Pre-notify amounts and dates.
6. Send each collection in time with the correct mandate data and sequence type, and test your first file with your bank.
7. Retire mandates that are revoked or unused for 36 months.

Where software fits

Steps 2, 3 and 7 are agreements between you, your customers and the banks; no file generator can do them for you. What software can do is keep the mandate data consistent from one collection to the next. SEPA Generator Pro, for example, keeps a local register of customers and mandates and warns about likely sequence mistakes before you export the pain.008 file — see Manage customers and mandates in Pro. It does not sign or register mandates, and it does not submit collections to a bank.

Official sources

Checked on 25 October 2026. The 2025 rulebooks version 1.2 (published 30 September 2026) are in force; version 1.2 changed only the address-format migration date compared with version 1.1.

• European Payments Council, SDD Core rulebook and implementation guidelines — 2025 SDD Core Rulebook (EPC016-06) version 1.2: mandate definition (§4.1), mandate content, 36-month rule, refund rights (Annex V), timelines.
• European Payments Council, SDD B2B rulebook and implementation guidelines — 2025 SDD B2B Rulebook (EPC222-07) version 1.2.
• European Payments Council, Clarification paper on the SDD Core and SDD B2B rulebooks (EPC132-17, version 5.1): amendments and other practical questions.
• European Payments Council, SEPA Direct Debit (SDD) — overview of the two schemes.
• European Payments Council, Creditor Identifier Overview — creditor identifier structure per SEPA country.