SEPA direct debit rejected MD01: invalid mandate on first collection

SEPA direct debit rejected MD01: invalid mandate on first collection

TL;DR: the bank rejected the debit because the mandate behind it is invalid: wrong IBAN, revoked mandate, or a mandate that was never properly signed. Get a fresh, correctly signed mandate with the right mandate reference, then resubmit the first collection with the FRST sequence type. Do not resubmit against the same broken mandate.

SEPA direct debit rejected MD01: invalid mandate on first collection

1. Pull the rejection record and confirm the reason code is MD01 (mandate invalid), not MS02/MS03 (insufficient funds). Expected: the return file or processor dashboard names MD01.
2. Inspect the stored mandate: debtor name, IBAN, signature date, and mandate reference. Expected: you find the flaw, usually an IBAN typo or a missing signature.
3. Have the customer sign a new mandate with the correct IBAN and a unique mandate reference. Expected: a signed mandate record with today's date.
4. Verify your creditor identifier matches the one registered for these debits. Expected: the identifier on the mandate matches your submission file.
5. Resubmit the collection with sequence type FRST (first), not RCUR. Expected: the bank accepts the debit for processing.

When this applies:

• First SEPA collection on a new mandate
• Migrated mandates with bad data
• IBAN changes

When it doesn't:

• MS02/MS03 (funds problems)
• Debits the customer actively revoked (that is a dispute, not a data fix)

Compatibility: SEPA Core Direct Debit; Stripe SEPA debits; any SEPA-originating processor; pain.008 submission files.

SEPA debit rejected, mandate invalid

Check the mandate data first; the debit itself is usually fine.

MD01 error on first SEPA collection

First collections get the strictest mandate validation; data flaws show up here.

first SEPA direct debit failed, invalid mandate

Re-sign with correct IBAN and resubmit as FRST.

Why it happens: the debtor's bank validates the mandate data on the first collection. A mistyped IBAN, a mandate signed but never stored, or a FRST collection sent as RCUR all read as invalid mandate to the bank.

Edge cases: mandate references must be unique per debtor; reusing one from an old canceled mandate can trigger MD01. Paper mandates need the physical signature on file; electronic mandates need an audit trail. B2B schemes have stricter rules than Core, so confirm which scheme you are on.

Provenance

Resolved from the public thread: https://vectle.com/posts/pst_dn4Wz9Zdb0zxcyQc8pMNcg

Resolved from the public thread: https://vectle.com/posts/pst_dn4Wz9Zdb0zxcyQc8pMNcg

Thread query: SEPA direct debit rejected MD01: invalid mandate on first collection

TL;DR: