RadarAPIsPricesOrder

Home › SEPA return reason codes

SEPA return reason codes: direct debit and credit transfer

All 25 reason codes a bank can put on a rejected, returned or refunded SEPA direct debit (Core and B2B), and all 43 codes for returned, rejected or recalled SEPA credit transfers: what each code means, why it happens and what to do next. Source: European Payments Council, EPC173-14 version 8.0 (28 November 2024) and EPC135-18 version 6.1 (30 September 2026). Checked 2026-11-17.

Worried about MS03 for unstructured addresses after November 2026? The EPC postponed that date: current status.

Direct debit: AC01 · AC04 · AC06 · AC13 · AG01 · AG02 · AM04 · AM05 · BE05 · CNOR · DNOR · ED05 · FF01 · MD01 · MD02 · MD06 · MD07 · MS02 · MS03 · RC01 · RR01 · RR02 · RR03 · RR04 · SL01

Credit transfer: AC01 · AC03 · AC04 · AC06 · ACNR · ACVA · AG01 · AG02 · AM04 · AM05 · AM09 · ARDT · ARJT · BE04 · CERI · CNOR · CUST · CVAA · DNOR · DUPL · ED05 · ERIN · FF01 · FOCR · FRAD · LEGL · MD07 · MODI · MS02 · MS03 · NERI · NOAS · NOOR · RC01 · RJNR · RJVA · RNPR · RR01 · RR02 · RR03 · RR04 · TECH · TM01

SEPA direct debit (SDD) reason codes

CodeNameMeaningUsed in
AC01Incorrect account numberThe debtor's IBAN is wrong or invalid.Reject, Return
AC04Closed account numberThe account is closed.Reject, Return
AC06Blocked accountThe account is blocked.Reject, Return
AC13Invalid debtor account typeThe debtor account is a consumer account (SDD B2B only).Reject, Return
AG01Transaction forbiddenDirect debit is forbidden on this account for regulatory reasons.Reject, Return
AG02Invalid bank operation codeOperation code, transaction code or sequence type is wrong, or the file format is invalid.Reject, Return
AM04Insufficient fundsNot enough money on the account.Reject, Return
AM05DuplicationDuplicate collection.Reject, Return, Reversal
BE05Unrecognised initiating partyThe creditor identifier is wrong.Reject, Return
CNORCreditor bank is not registeredThe creditor's bank is not registered under this BIC in the clearing system.Reject
DNORDebtor bank is not registeredThe debtor's bank is not registered under this BIC in the clearing system.Reject
ED05Settlement failedSettlement of the collection failed.Reject
FF01Invalid file formatThe file format is invalid.Reject
MD01No mandateNo valid mandate, or the mandate could not be confirmed.Reject, Return, Refund
MD02Missing mandatory mandate informationMandate data is missing or wrong.Reject
MD06Refund request by end customerDisputed authorised transaction (SDD Core only).Refund
MD07End customer deceasedThe debtor has died.Reject, Return
MS02Not specified reason, customer generatedRefused by the debtor.Reject, Return, Reversal, Refusal
MS03Not specified reason, agent generatedReason not given.Reject, Return, Reversal
RC01Bank identifier incorrectThe bank identifier (BIC) is wrong.Reject, Return
RR01Missing debtor account or identificationRegulatory reason.Reject, Return
RR02Missing debtor name or addressRegulatory reason.Reject, Return
RR03Missing creditor name or addressRegulatory reason.Reject, Return
RR04Regulatory reasonRegulatory reason.Reject, Return
SL01Specific service offered by debtor agentDue to a special service of the debtor's bank.Reject, Return

SEPA credit transfer (SCT) reason codes

For bank transfers that were rejected, returned or recalled, and for answers to a recall or an inquiry. Payer = originator, payee = beneficiary.

CodeNameMeaningUsed in
AC01Incorrect account numberThe payee's IBAN is invalid or does not exist.Reject, Return
AC03Invalid creditor account numberThe payment went to the wrong IBAN.Request for recall by the originator (RFRO)
AC04Closed account numberThe payee's account is closed.Return; negative answer to a recall or RFRO
AC06Blocked accountThe payee's account is blocked.Return
ACNRAccepted claim non-receiptPositive answer to a 'claim of non-receipt' inquiry.Positive answer to SCT inquiry
ACVAAccepted value date adjustmentPositive answer to a 'claim for value date correction'.Positive answer to SCT inquiry
AG01Transaction forbiddenCredit transfers are not allowed on this account (for example a savings account).Return
AG02Invalid bank operation codeOperation or transaction code is wrong, or the file format is invalid.Reject, Return
AM04Insufficient fundsNot enough money on the payee's account to give the money back.Negative answer to a recall or RFRO
AM05DuplicationDuplicate payment.Reject, Return
AM09Wrong amountThe payer sent more than intended.Request for recall by the originator (RFRO)
ARDTAlready returnedThe payment was already sent back.Negative answer to a recall, RFRO or claim of non-receipt
ARJTAlready rejectedThe payment was already rejected.Negative answer to a claim of non-receipt
BE04Missing creditor addressThe payee's address is missing.Return
CERICheck ERINot flagged as Extended Remittance Information but contains it.Reject
CNORCreditor bank is not registeredThe payee's bank is not registered under this BIC in the clearing system.Reject, Return
CUSTRequested by customera) Recall asked by the payer without a reason; b) the payee refuses to give the money back.RFRO; negative answer to a recall or RFRO
CVAACorrect value date already appliedNegative answer to a 'claim for value date correction'.Negative answer to SCT inquiry
DNORDebtor bank is not registeredThe payer's bank is not registered under this BIC in the clearing system.Reject
DUPLDuplicate paymentDuplicate sending.Recall
ED05Settlement failedSettlement of the credit transfer failed.Reject
ERINERI option not supportedThe Extended Remittance Information option is not supported.Reject, Return
FF01Invalid file formatThe file format is invalid.Reject
FOCRFollowing cancellation requestPositive answer to a recall.Positive answer to a recall or RFRO
FRADFraudulent originFraudulently started credit transfer.Recall
LEGLLegal decisionLegal reasons.Negative answer to a recall or RFRO
MD07End customer deceasedThe payee has died.Return
MODIModified as per requestConfirmed positive answer to a 'claim for value date correction'.Confirmed positive answer to SCT inquiry
MS02Not specified reason, customer generatedRefused by the payee.Return
MS03Not specified reason, agent generatedReason not given.Reject, Return
NERINo ERIFlagged as Extended Remittance Information but contains none.Reject
NOASNo answer from customerNo response from the payee.Negative answer to a recall or RFRO
NOORNo original transaction receivedThe original transfer was never received.Negative answer to a recall, RFRO or claim of non-receipt
RC01Bank identifier incorrectThe BIC is wrong.Reject, Return
RJNRRejected claim non-receiptNegative answer to a 'claim of non-receipt'.Negative answer to SCT inquiry
RJVARejected value date adjustmentNegative answer to a 'claim for value date correction'.Negative answer to SCT inquiry
RNPROriginal transaction received but not processableReceived but not processable.Negative answer to a claim of non-receipt
RR01Missing debtor account or identificationRegulatory reason.Reject, Return
RR02Missing debtor name or addressRegulatory reason.Reject, Return
RR03Missing creditor name or addressRegulatory reason.Reject, Return
RR04Regulatory reasonRegulatory reason.Reject, Return; negative answer to a claim of non-receipt
TECHTechnical problemTechnical problems caused wrong transfers.Recall
TM01Cut-off timeFile received after the cut-off time.Reject

Every direct debit code explained

AC01: Incorrect account number

Meaning: The debtor's IBAN is wrong or invalid. (Reject, Return)

When banks use it: The IBAN has an invalid format, or the IBAN does not exist at the debtor's bank.

Usual cause: The debtor gave wrong data, the creditor used a wrong IBAN from its customer records, or a technical problem when the collection was made.

What to do: Ask the debtor for the correct IBAN. After a mandate change, check the data the debtor gave you. Check the IBAN for free.

AC04: Closed account number

Meaning: The account is closed. (Reject, Return)

When banks use it: The debtor's account at the debtor's bank is closed. In some SEPA countries data protection law forbids this code and MS03 is used instead.

Usual cause: The debtor closed the account since your last collection on it.

What to do: Ask the debtor for the new account. Check the IBAN for free.

AC06: Blocked account

Meaning: The account is blocked. (Reject, Return)

When banks use it: The account is blocked for any financial transaction.

Usual cause: The debtor's bank blocked the account or the direct debit (for example a court order, suspected misuse, or a request from the debtor).

What to do: Ask the debtor for another account or another way to pay.

AC13: Invalid debtor account type

Meaning: The debtor account is a consumer account (SDD B2B only). (Reject, Return)

When banks use it: A B2B collection was sent to a consumer account, or to an account type that only consumers may hold.

Usual cause: The consumer did not know B2B mandates are for businesses only, the account type does not allow B2B debits, or the debtor gave a wrong account.

What to do: Ask the debtor to agree another way to pay, or sign an SDD Core mandate with them.

AG01: Transaction forbidden

Meaning: Direct debit is forbidden on this account for regulatory reasons. (Reject, Return)

When banks use it: The account type cannot be debited by direct debit (for example a savings account). Not used for B2B-to-consumer cases: that is AC13.

Usual cause: The debtor gave an account that direct debits cannot be booked from.

What to do: Agree another account or another payment method with the debtor.

AG02: Invalid bank operation code

Meaning: Operation code, transaction code or sequence type is wrong, or the file format is invalid. (Reject, Return)

When banks use it: A recurrent collection after a one-off, a one-off after a recurrent, or a wrong scheme code (service level or local instrument) in the message.

Usual cause: A technical error or a process error when the collection or file (sequence type) was made.

What to do: Correct the wrong field (sequence type FRST/RCUR/OOFF, local instrument CORE/B2B) and send again. Check your SEPA XML file for free.

AM04: Insufficient funds

Meaning: Not enough money on the account. (Reject, Return)

When banks use it: There is not enough money on the debtor's account to debit the full amount. In some SEPA countries data protection law forbids this code and MS03 is used instead.

Usual cause: The debtor has too little money on the account, or the creditor sent the pre-notification (date and amount) late or not at all.

What to do: Contact the debtor so that the money is on the account, then collect again.

AM05: Duplication

Meaning: Duplicate collection. (Reject, Return, Reversal)

When banks use it: The clearing house or the debtor's bank thinks an identical collection was sent or processed very recently.

Usual cause: A technical or human error at the creditor or the creditor's bank.

What to do: Check whether the collection really was sent twice before you send it again. Check your SEPA XML file for free.

BE05: Unrecognised initiating party

Meaning: The creditor identifier is wrong. (Reject, Return)

When banks use it: The Creditor Identifier (CI) is not correct, or it changed without the change being reported in the mandate data.

Usual cause: A technical error, or a CI change that was not reported as a mandate amendment.

What to do: Correct the Creditor Identifier in your file. Check your SEPA XML file for free.

CNOR: Creditor bank is not registered

Meaning: The creditor's bank is not registered under this BIC in the clearing system. (Reject)

When banks use it: The creditor's bank is not (or no longer) a direct debit scheme participant under this BIC in the clearing system.

Usual cause: The creditor's bank is not (or no longer) declared as a participant of this clearing system.

What to do: Contact your bank.

DNOR: Debtor bank is not registered

Meaning: The debtor's bank is not registered under this BIC in the clearing system. (Reject)

When banks use it: The debtor's bank is not (or no longer) a direct debit scheme participant under this BIC in the clearing system.

Usual cause: The creditor or its bank did not check that the debtor's bank can be reached.

What to do: Ask your bank to check whether the debtor's bank can be reached, or agree another way to pay with the debtor.

ED05: Settlement failed

Meaning: Settlement of the collection failed. (Reject)

When banks use it: The debtor's bank or the clearing system reports that settlement failed.

Usual cause: The debtor bank's funding for interbank settlement was too low to settle this transaction.

What to do: Depends on the agreement between the debtor's bank and the clearing system; ask your bank.

FF01: Invalid file format

Meaning: The file format is invalid. (Reject)

When banks use it: The XML file is not filled in correctly, has a syntax error, or was not checked against the XSD schema before it was sent.

Usual cause: The creditor, the creditor's bank or the clearing system.

What to do: Repair the XML file and send it again. Check your SEPA XML file for free.

MD01: No mandate

Meaning: No valid mandate, or the mandate could not be confirmed. (Reject, Return, Refund)

When banks use it: No mandate exists; a B2B mandate is not yet confirmed by the debtor; the mandate was cancelled; or (Core only) a refund of an unauthorised transaction, up to 13 months after the debit date.

Usual cause: The debtor's bank cancelled the mandate after 36 months without a collection, the debtor cancelled it or has not confirmed a B2B mandate, or the creditor used no or a wrong Unique Mandate Reference (UMR).

What to do: Check the collection data (mandate reference, dates). For a refund, contact the debtor. Check your SEPA XML file for free.

MD02: Missing mandatory mandate information

Meaning: Mandate data is missing or wrong. (Reject)

When banks use it: Mandate data in the collection differs from the mandate (an amendment was not reported), differs from the version already received for this UMR, or after a mandate amendment the original IBAN and the new IBAN are the same.

Usual cause: The mandate change was not done the way the rulebook says, or the changed data is wrong.

What to do: Repair the mandate amendment data and send again. Check your SEPA XML file for free.

MD06: Refund request by end customer

Meaning: Disputed authorised transaction (SDD Core only). (Refund)

When banks use it: The debtor asked for the unconditional refund of a Core collection, up to 8 weeks after the debit date.

Usual cause: The amount differs from the pre-notification, or the debtor used the unconditional refund right under the Payment Services Directive (PSD).

What to do: Contact the debtor.

MD07: End customer deceased

Meaning: The debtor has died. (Reject, Return)

When banks use it: The debtor is deceased. In some SEPA countries data protection law forbids this code and MS03 is used instead.

What to do: Close the agreement with the deceased debtor.

MS02: Not specified reason, customer generated

Meaning: Refused by the debtor. (Reject, Return, Reversal, Refusal)

When banks use it: The debtor refused the collection when it was presented.

Usual cause: After the pre-notification the debtor decided to refuse the collection.

What to do: Contact the debtor.

MS03: Not specified reason, agent generated

Meaning: Reason not given. (Reject, Return, Reversal)

When banks use it: Only to be used when national law (for example data protection) does not allow AC04, AM04, MD07, RR01, RR02, RR03 or RR04. Banks are asked to use a more precise code when they can.

Usual cause: One of the reasons above that the bank may not name in that country (closed account, no funds, deceased, missing regulatory data).

What to do: Contact the debtor.

RC01: Bank identifier incorrect

Meaning: The bank identifier (BIC) is wrong. (Reject, Return)

When banks use it: The BIC of the scheme participant is not correct.

Usual cause: For a collection from a non-EEA SEPA country the creditor gave an incomplete BIC (8 characters instead of 11), or the BIC in the interbank message does not exist in the BIC directory.

What to do: Ask the debtor for the correct BIC (non-EEA collections), or ask your bank to use the correct, complete BIC of the debtor's bank. Check the IBAN for free.

RR01: Missing debtor account or identification

Meaning: Regulatory reason. (Reject, Return)

When banks use it: Details about the debtor's account or identification are missing. In some SEPA countries MS03 is used instead.

Usual cause: The debtor's IBAN or identification needed for regulatory reasons is missing or not enough.

What to do: Repair the collection so the debtor's account data is complete, or contact your bank. Check your SEPA XML file for free.

RR02: Missing debtor name or address

Meaning: Regulatory reason. (Reject, Return)

When banks use it: The debtor's name is missing; the debtor's address is missing on a non-EEA collection; or the address format is invalid or no longer allowed (for example an unstructured address sent after the November 2026 phase-out). In some SEPA countries MS03 is used instead.

Usual cause: The debtor's name and/or address needed for regulatory reasons is missing or not enough.

What to do: Repair the collection with the debtor's name and a structured address, or contact your bank. Check your SEPA XML file for free.

RR03: Missing creditor name or address

Meaning: Regulatory reason. (Reject, Return)

When banks use it: The creditor's name is missing, or the creditor's address format is invalid or no longer allowed (for example an unstructured address sent after the November 2026 phase-out). In some SEPA countries MS03 is used instead.

Usual cause: The creditor's name needed for regulatory reasons is missing or not enough.

What to do: Repair the collection with your name (and a structured address if you send one), or contact your bank. Check your SEPA XML file for free.

RR04: Regulatory reason

Meaning: Regulatory reason. (Reject, Return)

When banks use it: Only for regulatory reasons other than RR01, RR02 or RR03. In some SEPA countries MS03 is used instead.

What to do: Contact your bank.

SL01: Specific service offered by debtor agent

Meaning: Due to a special service of the debtor's bank. (Reject, Return)

When banks use it: Consumer rights the debtor switched on at their bank: the creditor is blocked, an amount limit, or a frequency limit; or another service of the debtor's bank.

What to do: Contact the debtor.

Every credit transfer code explained

AC01 (credit transfer): Incorrect account number

Meaning: The payee's IBAN is invalid or does not exist. (Reject, Return)

When banks use it: Reject: the IBAN has an invalid format or does not exist at the payee's bank. Return: the IBAN does not exist at the payee's bank.

Usual cause: The payee gave a wrong IBAN, the payer used a wrong IBAN from its own records, or a technical problem when the payment was made.

What to do: Ask the payee for the correct IBAN and pay again. Check the IBAN for free.

AC03 (credit transfer): Invalid creditor account number

Meaning: The payment went to the wrong IBAN. (Request for recall by the originator (RFRO))

When banks use it: The payer sent a transfer to a wrong IBAN and asks to get the money back.

Usual cause: The payer picked or typed a wrong IBAN for the payee.

What to do: Check IBANs before you send (for example with an IBAN checker) so it does not happen again. Check the IBAN for free.

AC04 (credit transfer): Closed account number

Meaning: The payee's account is closed. (Return; negative answer to a recall or RFRO)

When banks use it: The payee's account at the payee's bank is closed. In some SEPA countries data protection law forbids this code and MS03 is used instead.

Usual cause: The payee closed the account since your last transfer to it.

What to do: Ask the payee for the new account. Check the IBAN for free.

AC06 (credit transfer): Blocked account

Meaning: The payee's account is blocked. (Return)

When banks use it: The account is blocked for any financial transaction.

Usual cause: The payee's bank blocked the account (court order, suspected misuse, or a request from the payee).

What to do: Ask the payee for another account or another way to pay.

ACNR (credit transfer): Accepted claim non-receipt

Meaning: Positive answer to a 'claim of non-receipt' inquiry. (Positive answer to SCT inquiry)

When banks use it: The payee's bank confirms it credited the payment to the payee's IBAN and gives the date it was credited.

What to do: Your bank tells you the payment was processed as you instructed.

ACVA (credit transfer): Accepted value date adjustment

Meaning: Positive answer to a 'claim for value date correction'. (Positive answer to SCT inquiry)

When banks use it: The payee's bank agrees to correct the value date and asks the payer's bank for interest compensation first.

Usual cause: The wrong value date was not caused by the payee's bank.

What to do: The payer's bank pays the interest compensation first.

AG01 (credit transfer): Transaction forbidden

Meaning: Credit transfers are not allowed on this account (for example a savings account). (Return)

When banks use it: The transfer cannot be booked on this type of account.

Usual cause: The payee gave an account that transfers cannot be booked to.

What to do: Agree another account or payment method with the payee.

AG02 (credit transfer): Invalid bank operation code

Meaning: Operation or transaction code is wrong, or the file format is invalid. (Reject, Return)

When banks use it: The scheme code (service level or local instrument) in the message is wrong. Pure XML file problems use FF01 instead.

Usual cause: A technical error or a processing error in the transfer or the file of transfers.

What to do: Correct the wrong field and send again. Check your SEPA XML file for free.

AM04 (credit transfer): Insufficient funds

Meaning: Not enough money on the payee's account to give the money back. (Negative answer to a recall or RFRO)

When banks use it: The payee's account does not hold the full amount of the recall or RFRO. In some SEPA countries CUST is used instead.

Usual cause: Too little money on the payee's account.

What to do: Contact the payee directly to get the money back outside the recall procedure.

AM05 (credit transfer): Duplication

Meaning: Duplicate payment. (Reject, Return)

When banks use it: The clearing system or the payee's bank thinks an identical transfer was sent or processed very recently.

Usual cause: A technical or human error at the payer or the payer's bank.

What to do: Check whether the transfer really was sent twice. Check your SEPA XML file for free.

AM09 (credit transfer): Wrong amount

Meaning: The payer sent more than intended. (Request for recall by the originator (RFRO))

When banks use it: The payer sent a transfer for a higher amount than intended and asks for the money back.

Usual cause: A technical or human error at the payer.

What to do: Fix how payment amounts are entered so it does not happen again.

ARDT (credit transfer): Already returned

Meaning: The payment was already sent back. (Negative answer to a recall, RFRO or claim of non-receipt)

When banks use it: Recall/RFRO: the payee already sent the money back (by SCT, SCT Inst or another way). Claim of non-receipt: the payee's bank could not process the original transfer and returned it.

What to do: No action; for a return, follow the return reason code.

ARJT (credit transfer): Already rejected

Meaning: The payment was already rejected. (Negative answer to a claim of non-receipt)

When banks use it: The payee's bank could not process the original transfer.

Usual cause: See the reject reason code of the original transfer.

What to do: Follow the advice for that reject code.

BE04 (credit transfer): Missing creditor address

Meaning: The payee's address is missing. (Return)

When banks use it: The payee's address was not given but is needed for further processing.

Usual cause: Missing or invalid payee address.

What to do: Send the transfer again with the payee's address (structured: at least town and country). Check your SEPA XML file for free.

CERI (credit transfer): Check ERI

Meaning: Not flagged as Extended Remittance Information but contains it. (Reject)

When banks use it: The transfer is not tagged as an ERI instruction but carries ERI data.

Usual cause: An error in the payer's or the payer's bank's system when the payment message was made.

What to do: The payer's bank checks its process and may come back to the payer.

CNOR (credit transfer): Creditor bank is not registered

Meaning: The payee's bank is not registered under this BIC in the clearing system. (Reject, Return)

When banks use it: The payee's bank is not (or no longer) a SCT participant under this BIC in the clearing system.

Usual cause: The payee's bank is not (or no longer) declared as a participant of this clearing system.

What to do: Ask the payee how they can receive transfers through another bank.

CUST (credit transfer): Requested by customer

Meaning: a) Recall asked by the payer without a reason; b) the payee refuses to give the money back. (RFRO; negative answer to a recall or RFRO)

When banks use it: a) The payer wants back the money of an earlier settled transfer. b) The payee will not honour the recall or RFRO.

Usual cause: a) No specific reason given. b) The payee says it is entitled to the money.

What to do: a) No action. b) Contact the payee directly to get the money back outside the recall procedure.

CVAA (credit transfer): Correct value date already applied

Meaning: Negative answer to a 'claim for value date correction'. (Negative answer to SCT inquiry)

When banks use it: The payee's bank refuses the value date correction.

Usual cause: The payee's bank says it already applied the correct value date.

What to do: The payer's bank explains that the transfer was done as instructed.

DNOR (credit transfer): Debtor bank is not registered

Meaning: The payer's bank is not registered under this BIC in the clearing system. (Reject)

When banks use it: The payer's bank is not (or no longer) a SCT participant under this BIC in the clearing system.

Usual cause: The payer's bank sent the transfer by mistake to its former clearing system.

What to do: The payer's bank routes it to its current clearing system; otherwise agree another way to pay.

DUPL (credit transfer): Duplicate payment

Meaning: Duplicate sending. (Recall)

When banks use it: The payer or the payer's bank found a duplicate transfer and tries to get that money back.

Usual cause: A technical or human error at the payer or the payer's bank.

What to do: Set up checks that stop duplicate payments. Check your SEPA XML file for free.

ED05 (credit transfer): Settlement failed

Meaning: Settlement of the credit transfer failed. (Reject)

When banks use it: The payer's bank or the clearing system reports a settlement failure.

Usual cause: The payer bank's funding for interbank settlement was too low for this transfer.

What to do: Depends on the agreement between the payer's bank and the clearing system; ask your bank.

ERIN (credit transfer): ERI option not supported

Meaning: The Extended Remittance Information option is not supported. (Reject, Return)

When banks use it: Reject: the payer's bank and/or the payee's bank do not support ERI. Return: the payee's bank does not support ERI.

Usual cause: One of the banks does not offer the ERI option.

What to do: The payer decides how to go on (for example pay without ERI).

FF01 (credit transfer): Invalid file format

Meaning: The file format is invalid. (Reject)

When banks use it: The XML file is not filled in correctly, has a syntax error, or was not checked against the XSD schema before it was sent.

Usual cause: The payer, the payer's bank or the clearing system.

What to do: Repair the XML file and send it again. Check your SEPA XML file for free.

FOCR (credit transfer): Following cancellation request

Meaning: Positive answer to a recall. (Positive answer to a recall or RFRO)

When banks use it: The payee's bank or the payee agrees to pay the money back to the payer or the payer's bank.

What to do: No action.

FRAD (credit transfer): Fraudulent origin

Meaning: Fraudulently started credit transfer. (Recall)

When banks use it: The payer or the payer's bank found a fraudulent transfer and tries to get the money back.

Usual cause: The payer was a victim of fraud, or fraudsters manipulated the payer bank's systems.

What to do: Set up measures that stop fraudulent transfers.

LEGL (credit transfer): Legal decision

Meaning: Legal reasons. (Negative answer to a recall or RFRO)

When banks use it: The payee's bank is not allowed to pay the money back.

Usual cause: The money cannot be paid back for legal reasons.

What to do: Contact the payee directly to get the money back outside the recall procedure.

MD07 (credit transfer): End customer deceased

Meaning: The payee has died. (Return)

When banks use it: The payee is deceased. In some SEPA countries data protection law forbids this code and MS03 is used instead.

What to do: No action.

MODI (credit transfer): Modified as per request

Meaning: Confirmed positive answer to a 'claim for value date correction'. (Confirmed positive answer to SCT inquiry)

When banks use it: The payee's bank confirms it corrected the value date on the payee's IBAN.

Usual cause: The payee's bank got the interest compensation, asks none, or asks for it later (code VADA).

What to do: The payer's bank pays the interest compensation if VADA was given.

MS02 (credit transfer): Not specified reason, customer generated

Meaning: Refused by the payee. (Return)

When banks use it: The payee refused the transfer when it was presented to the payee's bank.

Usual cause: The payee told its bank not to accept money from this account, this payer, or this payment scheme.

What to do: Ask the payee how you should pay what you owe.

MS03 (credit transfer): Not specified reason, agent generated

Meaning: Reason not given. (Reject, Return)

When banks use it: Only when national law (for example data protection) does not allow AC04, RR01, RR02, RR03 or RR04. Banks are asked to use a more precise code.

Usual cause: One of the reasons above that the bank may not name in that country.

What to do: Ask the payee how you should pay what you owe.

NERI (credit transfer): No ERI

Meaning: Flagged as Extended Remittance Information but contains none. (Reject)

When banks use it: The transfer is tagged as an ERI instruction but carries no ERI data.

Usual cause: An error in the payer's or the payer's bank's system when the payment message or file was made.

What to do: Send the transfer (file) again with the ERI data. Check your SEPA XML file for free.

NOAS (credit transfer): No answer from customer

Meaning: No response from the payee. (Negative answer to a recall or RFRO)

When banks use it: The payer or the payer's bank tries to get money back from an earlier transfer.

Usual cause: The payee's bank cannot reach the payee, or the payee does not answer.

What to do: Contact the payee directly to get the money back outside the recall procedure.

NOOR (credit transfer): No original transaction received

Meaning: The original transfer was never received. (Negative answer to a recall, RFRO or claim of non-receipt)

When banks use it: The payee's bank or the payee says it never received the original transfer.

Usual cause: The recall or inquiry went to the wrong bank or payee, or the payee's bank never got the transfer.

What to do: The payer's bank sends the recall or inquiry to the correct bank or payee.

RC01 (credit transfer): Bank identifier incorrect

Meaning: The BIC is wrong. (Reject, Return)

When banks use it: The BIC of the scheme participant is not correct.

Usual cause: For a transfer to a non-EEA SEPA country the payer gave an incomplete BIC (8 characters instead of 11), or the BIC in the interbank message does not exist in the BIC directory.

What to do: Ask the payee for the correct, complete BIC (non-EEA transfers), or ask your bank to fix it. Check the IBAN for free.

RJNR (credit transfer): Rejected claim non-receipt

Meaning: Negative answer to a 'claim of non-receipt'. (Negative answer to SCT inquiry)

When banks use it: The payee's bank gives a precise reason: NOOR, RNPR, ARJT, ARDT or RR04.

Usual cause: Never received (NOOR), received but not processable (RNPR), already rejected (ARJT), already returned (ARDT), regulatory reason (RR04).

What to do: Follow the advice for the code given.

RJVA (credit transfer): Rejected value date adjustment

Meaning: Negative answer to a 'claim for value date correction'. (Negative answer to SCT inquiry)

When banks use it: The payee's bank refuses to correct the value date.

Usual cause: The debit date is more than 13 months before the inquiry, or before 17 November 2019 (when the inquiry procedure started).

What to do: No further action.

RNPR (credit transfer): Original transaction received but not processable

Meaning: Received but not processable. (Negative answer to a claim of non-receipt)

When banks use it: The payee's bank cannot process the transfer at this time, for a reason other than ARJT, ARDT or RR04.

What to do: The two banks contact each other to solve it.

RR01 (credit transfer): Missing debtor account or identification

Meaning: Regulatory reason. (Reject, Return)

When banks use it: The payer's account details are missing. In some SEPA countries MS03 is used instead.

Usual cause: The payer's account or identification needed for regulatory reasons is missing or not enough.

What to do: The payer's bank completes the payer's account data and sends again. Check your SEPA XML file for free.

RR02 (credit transfer): Missing debtor name or address

Meaning: Regulatory reason. (Reject, Return)

When banks use it: The payer's name is missing; the payer's address is missing on a non-EEA transfer; or the payer's address format is invalid or no longer allowed. In some SEPA countries MS03 is used instead.

Usual cause: The payer's name and/or address needed for regulatory reasons is missing or not enough.

What to do: Send the transfer again with the payer's name and a structured address. Check your SEPA XML file for free.

RR03 (credit transfer): Missing creditor name or address

Meaning: Regulatory reason. (Reject, Return)

When banks use it: The payee's name is missing, or the payee's address format is invalid or no longer allowed. In some SEPA countries MS03 is used instead.

Usual cause: The payee's name needed for regulatory reasons is missing or not enough.

What to do: Send the transfer again with the payee's name (and a structured address if you send one). Check your SEPA XML file for free.

RR04 (credit transfer): Regulatory reason

Meaning: Regulatory reason. (Reject, Return; negative answer to a claim of non-receipt)

When banks use it: Only for regulatory reasons other than RR01, RR02 or RR03. In some SEPA countries MS03 is used instead (not for a claim of non-receipt).

Usual cause: A possible hit in anti-money-laundering, embargo or counter-terrorist-financing checks.

What to do: Contact your bank.

TECH (credit transfer): Technical problem

Meaning: Technical problems caused wrong transfers. (Recall)

When banks use it: The payer or the payer's bank found a technical problem that sent wrong transfers and tries to get the money back.

Usual cause: A technical issue in the payer's systems or the payer bank's systems when the transfers or files were made.

What to do: Set up measures that stop such technical problems.

TM01 (credit transfer): Cut-off time

Meaning: File received after the cut-off time. (Reject)

When banks use it: The clearing system did not receive the transfer (file) before its cut-off time.

Usual cause: A connection, processing or validation issue between the payer's bank and the clearing system.

What to do: The payer's bank sends the transfers again before the next cut-off time.

Check a SEPA XML file before you send itMake a SEPA payment fileFree IBAN checker

Questions

What is a SEPA return reason code?

A 4-character ISO 20022 code that the debtor's bank, the clearing system or the creditor's bank puts on a direct debit that could not be paid normally (a reject, return, refund, refusal or reversal). It tells the creditor why, for example AM04 = not enough money, AC04 = account closed, MD06 = the customer asked for a refund.

What does MS03 mean?

MS03 means 'reason not specified' by the bank. The EPC says it should only be used when national law, such as data protection, does not allow the real code (AC04 closed account, AM04 no funds, MD07 deceased, or RR01-RR04 regulatory). Contact the debtor to find out more.

What is the difference between a reject, a return and a refund?

A reject stops the collection before it is settled (by your bank, the clearing system or the debtor's bank). A return comes from the debtor's bank after settlement. A refund is asked for by the debtor after the money was taken: under SDD Core up to 8 weeks for any reason (MD06), and up to 13 months for an unauthorised debit without a valid mandate (MD01).

Why do I suddenly get RR02 or RR03?

RR02 (debtor) and RR03 (creditor) mean a regulatory name or address field is missing or its format is not allowed. The EPC guidance names one case: an unstructured address sent after the November 2026 phase-out. Send structured address fields (at least town and country) in your pain.008 file.

Which reason codes mean I made a mistake in my file?

AG02 (wrong sequence type or scheme code), AM05 (sent twice), BE05 (wrong Creditor Identifier), FF01 (invalid XML), MD01/MD02 (mandate reference or mandate data), RC01 (wrong BIC) and RR01-RR03 (missing account, name or address). You can check a SEPA XML file for most of these before you send it.

My bank transfer (credit transfer) came back: which code is it?

Returned or rejected SEPA credit transfers use their own list, for example AC01 (wrong IBAN), AC04 (account closed), AG01 (account cannot receive transfers), MS02 (the payee refused it) or RR04 (regulatory check). Recall answers use codes such as CUST, LEGL, NOAS or FOCR. See the SEPA credit transfer table on this page.

Where does this list come from?

From the European Payments Council's EPC173-14 version 8.0 'Guidance on Reason Codes for SDD R-transactions', published 28 November 2024, and EPC135-18 version 6.1 'Guidance on Reason Codes for SCT R-transactions', published 30 September 2026. The wording here is our plain-English summary; the EPC documents and the rulebooks are the binding text.

Sources: European Payments Council, EPC173-14 version 8.0, Guidance on Reason Codes for SDD R-transactions, published 28 November 2024; EPC135-18 version 6.1, Guidance on Reason Codes for SCT R-transactions, published 30 September 2026. Our wording is a plain-English summary; the EPC documents and the rulebooks are binding. Last checked against the source: 2026-11-17. See also IBAN format by country.