Skip to content
SEPA MD01

No mandate

Category: Mandate R-type: Reject / Return

SCT

N/A

SCT Inst

N/A

SDD Core

Applies

SDD B2B

Applies

Retryable

No — re-mandate required

Generated by

Debtor bank.

ISO 20022 definition

No Mandate.

Typical cause

No valid mandate on file, the mandate was cancelled, the SequenceType (FRST/RCUR/FNAL) does not match, or — for SDD B2B — the mandate was never pre-registered at the debtor bank before the first collection.

What to do about it

Verify mandate status against the debtor bank; re-obtain the mandate if cancelled. For B2B, confirm the mandate was pre-registered before retrying. Reconcile MD01 returns to the specific mandate reference and sequence type: a pattern at FRST usually means the B2B pre-registration step was skipped; a pattern at RCUR usually means the customer cancelled at their bank.

Rulebook note

The highest-signal mandate failure code — the debtor bank explicitly checked and could not match a valid registered mandate. Particularly definitive for SDD B2B, where mandates are pre-registered at the debtor bank.

Confidence: high. Sourced from PaymentBrief's SEPA R-transaction reference article, cross-verified against ISO 20022 external code sets and EPC guidance documents. Reason-code applicability and timing windows vary by rulebook version and bank handling — verify against your bank or PSP before acting.

Full reference

SEPA Return and Reject Codes: The R-Transaction Reference

Related codes