Skip to content
SEPA MS03

Not specified — agent-generated

Category: Debtor Refusal & Unspecified R-type: Reject / Return

SCT

N/A

SCT Inst

N/A

SDD Core

Applies

SDD B2B

Applies

Retryable

No, until verified

Generated by

Debtor bank, withholding the underlying reason.

ISO 20022 definition

Reason has not been specified by agent.

Typical cause

The single highest-ambiguity SEPA code. Three distinct causes: (1) data-protection substitution — EPC guidance (EPC173-14, stable v4.0–v8.0) requires MS03 in place of AC04, AM04, MD07, RR01, RR02, RR03, or RR04 where national law blocks disclosure, in Austria, Belgium, Germany, Luxembourg, the Netherlands, Slovakia, Slovenia, and Switzerland; (2) bank-side risk control flagging beyond any specific code; (3) a genuine unspecified/catch-all error.

What to do about it

Do not retry without investigation. Treat as you would AC04 on first occurrence — check with the customer whether the account is active and update mandate status if confirmed closed. If the debtor is unreachable, or if prior collections on the same mandate failed with AM04 or AC04, treat repeat MS03 as a likely closed/blocked account and pause collections rather than retry.

Rulebook note

When the debtor bank is in one of the eight countries above, MS03 is most commonly a masked AC04 (closed account) or AM04 (insufficient funds) rather than a genuine unspecified error.

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