MS03 reason code: direct debit returned without a reason
Last updated: 28 October 2026
MS03 means “reason not specified”: the payer's bank did not pay or returned the SEPA direct debit and does not say why. In some countries banks are not allowed to pass on certain reasons for data protection reasons and report MS03 instead, for example for insufficient funds.
- Code
- MS03
- Meaning in the rulebook
- Reason not specified
- ISO name
- Not Specified Reason Agent Generated: raised by the bank, without a reason
- Type of R-transaction
- Reject before the debit, return after the debit, or reversal
- Schemes
- SEPA Core and SEPA B2B
- Collect again?
- Only after talking to the payer
What MS03 means
Every returned direct debit carries a code from a fixed list. MS03 means that the payer's bank refused the direct debit and gives no reason. If the payer refused it, the code is MS02 instead.
The European Payments Council, which sets the SEPA direct debit rules, allows MS03 for one situation only: when national law, such as data protection law, does not allow the precise code. This concerns AC04 (account closed), AM04 (insufficient funds), MD07 (payer deceased) and RR01 to RR04 (regulatory reasons).
Germany is an example: a German savings bank states that it reports AM04 (insufficient funds), MD07 (account holder deceased) and RR04 as MS03 for data protection reasons. Banks there describe MS03 as “no reason given, returned by the bank (other reasons)”.
What the payer and the creditor see
As the payer
If the direct debit was rejected before the debit, it does not appear on your statement. If it was returned afterwards, you see the debit and the credit of the return.
Your bank informs you that it did not pay the direct debit and, as far as it may, why. Ask your bank if the notice does not explain it.
As the creditor
Your bank debits the amount back, usually with a fee for the return, and shows return reason MS03 in the transaction details. In electronic statements (camt.053, camt.054) the code is in the return reason field.
You do not learn the actual reason. Only the payer can find out from their bank.
| Date | Transaction | Amount EUR |
|---|---|---|
| 3 Nov | SEPA direct debit collection, 214 itemsMembership fees 11/2026 | +8,560.00 |
| 6 Nov | SEPA direct debit returnMandate M-0412, membership fee 11/2026Return reason MS03 Reason not specified | −40.00 |
| 6 Nov | Return fee | −3.00 |
Typical causes
- Insufficient funds (AM04) that the bank may not report as such.
- Death of the account holder (MD07), reported as MS03 for the same reason.
- A closed account (AC04) in countries where that code may not be used.
- Regulatory reasons (RR01 to RR04), such as missing details about the payer.
What you can do as the payer
- Check your balance on the due date and whether your bank sent you a notice about the unpaid direct debit.
- Ask your bank for the reason; it can tell you as its customer.
- Contact the creditor and agree how you will pay: by credit transfer or with a new direct debit on a date when your account is funded.
- Ask the creditor which costs, if any, they want to charge for the return, and on what basis.
What you can do as the creditor
- Contact the payer. Their bank tells them the reason, not you.
- Bear in mind that insufficient funds, a closed account or a death may be behind MS03, and ask with care.
- Collect again only once the reason is clear. Announce the new collection with amount and due date (pre-notification), at least 14 calendar days in advance unless agreed otherwise.
- The collection must reach the payer's bank no later than one bank business day before the due date; your bank tells you its cut-off time.
- If the direct debit comes back with MS03 again, agree on another way to pay, such as payment by invoice.
Deadlines
A return with MS03 arrives shortly after the due date: under SEPA Core no later than five bank business days afterwards, under SEPA B2B no later than three. Separately, under SEPA Core the payer can ask for a refund of a paid direct debit for eight weeks; the code is then MD06.
Related reason codes
- AM04: insufficient funds – a reason that MS03 may hide in some countries.
- MS02: refused by the payer – the refusal comes from the customer, not the bank.
- AC04: account closed – also reported as MS03 in some countries.
- MD07: payer deceased – reported as MS03 in Germany for data protection reasons.
Frequently asked questions
Does MS03 always mean insufficient funds?
No. In some countries banks report insufficient funds as MS03, but also the death of the account holder, a closed account or regulatory reasons. Only the payer's bank knows the actual reason and tells its customer.
What is the difference between MS03 and MS02?
With MS03 the payer's bank refused the direct debit; with MS02 the payer did. Neither code gives a reason.
Can the creditor collect again straight away after MS03?
They can submit a new collection if a valid mandate exists, announced in advance with amount and due date (at least 14 calendar days unless agreed otherwise). It only makes sense once it is clear why the first one came back.
Which costs arise with a return?
The creditor's bank usually charges the creditor a fee, and the payer's bank may charge the payer for the notice if its terms say so. Whether the creditor may pass costs on to the payer depends on the contract and the law of the country concerned.
Sources
- European Payments Council: Guidance on Reason Codes for SDD R-transactions, EPC173-14 version 8.0 – meaning, use cases and root causes of each code
- European Payments Council: 2025 SDD Core Rulebook, version 1.1 – rules of the SEPA Core scheme, deadlines, pre-notification
- European Payments Council: 2025 SDD B2B Rulebook, version 1.1 – rules of the SEPA B2B scheme
- Sparkasse KölnBonn: SEPA-Rückgabe-Codes bei Lastschriften – in German; AM04, MD07 and RR04 reported as MS03 for data protection reasons, MD02 as MD01