SEPA Direct Debit Mandate: Schemes, Refunds, and Cancellation

A SEPA direct debit mandate is the written authorization you give a business to pull euro payments directly from your bank account under the Single Euro Payments Area rules. The mandate names the creditor, identifies your account by IBAN, carries a unique reference, and records your signature. Without a valid one on file, your bank will refuse the collection.

The rules behind it come from Regulation (EU) No 260/2012, which sets the data every collection must carry and, in effect, what the mandate form has to capture.¹ The scheme is run by the European Payments Council, and the mandate is the piece that connects you, as the payer, to a system that otherwise moves money automatically.

What a Valid Mandate Must Include

A mandate that is missing required information will produce a rejected collection, usually under reason code MD02. The fields the mandate has to carry are:

Your IBAN. Since February 2016, the IBAN alone is enough for both domestic and cross-border collections. You no longer need to supply a BIC.²
Your full name as registered with the bank.
The Creditor Identifier, a unique code every SEPA creditor must hold.
The Unique Mandate Reference (UMR), an alphanumeric code of up to 35 characters that the creditor assigns to this specific authorization.
Whether the mandate is for a one-off payment or a recurring series.
The creditor’s name.
Date of signing and your signature.

An incorrect IBAN produces an automatic rejection under reason code AC01, and creditors generally pay a fee for each failed collection, which is why most will ask you to check the number twice before submitting.³

Core Scheme and B2B Scheme

SEPA operates two direct debit schemes, and which one you sign under changes your rights significantly. The Core scheme is the default and covers both consumers and businesses. The Business-to-Business (B2B) scheme is open only to businesses; a private individual cannot sign a B2B mandate.⁴

The biggest difference is the refund right. Under the Core scheme, you can claim a no-questions-asked refund within eight weeks of any collection. Under B2B, that right does not exist for authorized collections. Once an authorized B2B debit settles, the money is gone unless the creditor chooses to reverse it.⁴

In exchange for giving up the refund right, B2B offers the creditor more payment certainty. The debtor’s bank verifies each incoming B2B collection against the mandate information on file, which blocks unauthorized debits before they settle. The debtor and the bank have to agree in advance on how that verification works.

How You Sign and Where the Mandate Lives

You authorize a mandate by signing it, on paper or electronically. The creditor supplies the form, usually at checkout, during onboarding, or through a service portal. You fill in your IBAN, name, and address, then sign.

Paper mandates are still common with utility companies and insurers. Electronic mandates (e-mandates) connect to your bank’s authentication system so you can approve digitally without printing. Under the B2B scheme, e-mandates can accommodate multiple signatories where a business requires more than one authorized person to approve payments.⁴

Once signed, the creditor becomes the custodian of the mandate. They must keep the original as proof of your authorization for the life of the mandate and for at least 14 months after the last collection under it.⁴ The creditor then passes the mandate data to its bank, which registers it in the SEPA clearing system so collections can begin.

Pre-Notification Before Each Collection

Before a creditor pulls funds from your account, they must tell you the exact amount and the collection date. The standard pre-notification period is 14 calendar days before the collection, though you and the creditor can agree on a shorter window, and many subscription services shorten it to a few days in their terms of service.⁵

On the processing side, the creditor’s bank must present the collection to the clearing system at least one business day before the scheduled payment date, and no earlier than 14 calendar days before the due date.⁶

Your Refund Rights

Under the Core scheme, you have an unconditional right to a refund for eight weeks after any collection debits your account. Your bank must process the refund without asking why. The right is absolute during that window.⁷

If the collection was completely unauthorized, meaning no valid mandate existed, the window extends to 13 months from the debit date. That covers a fabricated mandate, a mandate that had already been cancelled, or an amount with no basis in the authorization you gave.⁵

B2B works differently. Because the debtor’s bank checks each collection against the mandate before it settles, authorized B2B collections do not carry the eight-week refund right. That is the tradeoff the business is accepting when it signs a B2B mandate rather than a Core one.⁴

Changing, Expiring, or Cancelling a Mandate

If your bank account changes, update your IBAN with the creditor. Most offer an online dashboard or form for this. A mandate with an outdated IBAN produces a rejection under code AC01, and a closed account produces AC04.³

A recurring mandate does not last forever on its own. If 36 months pass without any collection attempt under the mandate, it expires automatically. The creditor must then cancel it and cannot start collecting again, even if you never revoked the authorization yourself. Any collection attempt, including rejected or refunded ones, resets the clock. Tracking the 36 months is the creditor’s responsibility; banks are not required to enforce it.⁸

You can cancel a mandate at any time by notifying the creditor in writing. That ends their right to collect going forward. Telling your own bank to block collections under that mandate reference is a sensible extra step, in case the creditor has already submitted something to the clearing system.

When a Collection Fails

SEPA uses standardized reason codes, called R-transactions, to explain why a collection was refused, rejected, returned, or refunded. The ones that come up most often are:³

AC01, incorrect IBAN.
AC04, closed account.
AC06, blocked account.
AM04, insufficient funds.
MD01, no valid mandate on file (Core scheme).
MD02, missing or incorrect mandate data.
MD06, authorized collection disputed by the payer (Core scheme).
MS02, debtor instructed the bank to refuse the collection.
AG01, direct debits forbidden on the account under local rules.

Data protection laws in some SEPA countries prevent banks from using certain specific codes, such as those that would reveal an account is closed or that the account holder has died. In those cases, the bank substitutes the generic code MS03, “reason not specified.”³

Where the Mandate Works

SEPA covers more than 40 countries and territories: all 27 EU member states, the three additional EEA countries (Iceland, Liechtenstein, Norway), and eleven non-EEA participants including the United Kingdom, Switzerland, Andorra, Monaco, San Marino, Vatican City, Albania, Moldova, Montenegro, North Macedonia, and Serbia. Several overseas territories of EU states, such as French Guiana, Guadeloupe, Gibraltar, and the Channel Islands, are also in scope.⁹

One boundary matters even if your bank account is held in a different SEPA currency: the collection itself must be denominated in euros. A Swedish creditor collecting from a Finnish debtor runs the collection in euros even if either account is in krona.⁵ A payment in another currency, or from an account outside the SEPA area, falls outside what a SEPA mandate can authorize.

1
Legislation.gov.uk. Regulation (EU) No 260/2012 – Establishing Technical and Business Requirements for Credit Transfers and Direct Debits in Euro – Section: ANNEX
2
European Parliament and Council. Regulation (EU) No 260/2012 – Official Journal
3
European Payments Council. Guidance on Reason Codes for SDD R-transactions
4
European Payments Council. Shortcut to SEPA Direct Debit (SDD)
5
European Payments Council. SEPA Direct Debit
6
European Payments Council. SEPA Direct Debit Core Scheme Rulebook 2025 Version 1.1
7
Legislation.gov.uk. Directive (EU) 2015/2366 (PSD2) – Payment Services Directive
8
European Payments Council. SEPA Direct Debit Core Scheme Rulebook 2025 Version 1.0
9
European Payments Council. EPC List of SEPA Scheme Countries v8.0