IBAN in SEPA Direct Debit Mandates: Setup, Validation & Common Errors

SEPA Direct Debit (SDD) allows creditors to collect recurring or one-off euro payments directly from a debtor's bank account, provided the debtor has signed a mandate authorising the collection. The mandate contains the debtor's IBAN and a set of legal provisions that govern the collection. Getting the IBAN right — and validating it before the first collection — is fundamental to a functioning direct debit setup.

What Is a SEPA Direct Debit Mandate?

A SEPA Direct Debit mandate is a written or digital authorisation signed by the debtor (the person or company being charged) that gives the creditor permission to initiate debit collections from the debtor's bank account. The mandate must contain:

• Creditor identifier (CI): A unique identifier assigned to the creditor by their national payment authority (e.g., a French CI starts with FRfollowed by a two-digit check code).
• Mandate reference: A unique reference chosen by the creditor (max 35 characters) that identifies this specific mandate. Used in every subsequent collection instruction.
• Debtor's full name and address
• Debtor's IBAN — the bank account from which funds will be collected.
• Debtor's bank BIC — required for SEPA Core SDD for cross-border mandates (BIC-only requirement was removed for domestic SEPA SDD in 2016, but many creditor systems still collect it).
• Mandate type: Recurrent (for ongoing subscriptions) or one-off (for single collections that expire after use).
• Date and signature (for paper mandates) or electronic equivalent (for e-mandates).

Why Is IBAN Validation Critical at Mandate Capture?

The mandate IBAN is used in every subsequent collection instruction. An error in the IBAN at the point of capture propagates through every future direct debit until it fails. The consequences vary by error type:

• Structurally invalid IBAN: The collection instruction is rejected by the debtor's bank immediately, with a return code (e.g., AC01 — Incorrect Account Number). You must contact the debtor and capture a corrected mandate.
• Valid IBAN, wrong account: This is the dangerous case. A structurally valid IBAN that belongs to a different person or a closed account will pass automated checks but fail (or, worse, succeed) at the bank level. A collection hitting the wrong account can result in a dispute, a refund request, and potential regulatory scrutiny.
• Valid IBAN, account closed: Returns with code AC04(Closed Account Number). You must re-capture the mandate.
• Valid IBAN, insufficient funds: Returns with AM04. Mandate itself is valid; collection can be retried.

Validate every mandate IBAN at the point of capture using ibanchecker.cash. This catches structural errors (wrong length, failed check digit, invalid country code) before the first collection attempt, eliminating the most avoidable return codes.

What Are the Two SEPA Direct Debit Schemes?

The EPC (European Payments Council) maintains two SDD schemes:

• SEPA Core Direct Debit (SDD Core): The main retail scheme, available for collections from both consumers and businesses. Debtors have an unconditional right to a refund within 8 weeks of the collection date (no reason required), and a refund right for unauthorised collections up to 13 months.
• SEPA B2B Direct Debit (SDD B2B): Designed for business-to-business collections. Debtors waive the unconditional refund right, but must provide their bank with a copy of the signed mandate. Banks verify collections against their mandate records, providing stronger protection for creditors. SDD B2B is only available where both the debtor's and creditor's banks support the scheme.

The mandate format is the same for both schemes; the scheme is determined by the payment type indicator in the collection instruction.

How Far in Advance Must You Notify the Debtor?

Creditors must notify debtors of an upcoming direct debit collection at least 14 calendar days before the collection date, unless a shorter notice period has been agreed in the mandate or underlying contract (minimum 1 day). This "pre-notification" should include:

• The amount to be collected
• The collection date
• The mandate reference
• The creditor identifier

For subscription billing, many creditors include this information in the recurring invoice or billing statement, satisfying the notification requirement without separate communication.

What Are the Most Common SEPA Direct Debit Return Codes?

Understanding return codes speeds up resolution when collections fail:

• AC01 — Incorrect account number (IBAN failed bank-level validation)
• AC04 — Closed account number
• AC06 — Blocked account
• MD01 — No mandate (the debtor's bank has no record of a valid mandate)
• MD02 — Missing mandatory information in mandate (e.g., missing CI or mandate reference)
• MS02 — Refusal by debtor (debtor has instructed their bank to block the collection)
• AM04 — Insufficient funds
• FF01 — Invalid file format (collection instruction does not conform to pain.008 schema)

MD01 and MD02 errors often indicate a process failure rather than a debtor issue — check that the mandate reference and creditor identifier in the collection file exactly match the signed mandate.

How Do You Validate IBANs in Bulk for Direct Debit Portfolios?

Finance teams managing large SDD portfolios — subscription businesses, insurance companies, utility providers — periodically need to audit their mandate database for invalid or misformatted IBANs. This is especially important after data migrations, ERP upgrades, or acquisitions where mandate data is transferred from another system.

Export your mandate IBAN list and run it through the bulk IBAN checker. The checker validates structural correctness (country code, length, check digits) and returns the bank name and BIC for each IBAN. Any IBAN that fails should be flagged for manual review — either contact the debtor for a corrected mandate or mark the mandate as invalid before the next collection cycle.

For developers building mandate capture forms, the ibanchecker.cash API provides real-time IBAN validation via POST /api/v1/validate. Integrate this into your onboarding flow to validate the IBAN as the debtor types it, surfacing errors before form submission.

Last updated: June 2026