EU bank statements, SEPA & VAT data
Collection
Open data + in-browser tools for MT940/CAMT.053, EU VAT rates, 2027 holidays. More: radarbg.com • 6 items • Updated
scheme stringclasses 2
values | code stringlengths 4 4 | name stringlengths 6 49 | short_meaning stringlengths 14 91 | used_for stringlengths 6 57 | official_description stringlengths 49 263 | typical_cause stringlengths 33 204 ⌀ | what_to_do stringlengths 10 129 | source stringclasses 2
values | checked stringdate 2026-11-17 00:00:00 2026-11-17 00:00:00 |
|---|---|---|---|---|---|---|---|---|---|
SEPA Direct Debit (SDD) | AC01 | Incorrect account number | The debtor's IBAN is wrong or invalid. | Reject, Return | The IBAN has an invalid format, or the IBAN does not exist at the debtor's bank. | The debtor gave wrong data, the creditor used a wrong IBAN from its customer records, or a technical problem when the collection was made. | Ask the debtor for the correct IBAN. After a mandate change, check the data the debtor gave you. | EPC173-14 version 8.0 (28 November 2024) | 2026-11-17 |
SEPA Direct Debit (SDD) | AC04 | Closed account number | The account is closed. | Reject, Return | 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. | The debtor closed the account since your last collection on it. | Ask the debtor for the new account. | EPC173-14 version 8.0 (28 November 2024) | 2026-11-17 |
SEPA Direct Debit (SDD) | AC06 | Blocked account | The account is blocked. | Reject, Return | The account is blocked for any financial transaction. | The debtor's bank blocked the account or the direct debit (for example a court order, suspected misuse, or a request from the debtor). | Ask the debtor for another account or another way to pay. | EPC173-14 version 8.0 (28 November 2024) | 2026-11-17 |
SEPA Direct Debit (SDD) | AC13 | Invalid debtor account type | The debtor account is a consumer account (SDD B2B only). | Reject, Return | A B2B collection was sent to a consumer account, or to an account type that only consumers may hold. | 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. | Ask the debtor to agree another way to pay, or sign an SDD Core mandate with them. | EPC173-14 version 8.0 (28 November 2024) | 2026-11-17 |
SEPA Direct Debit (SDD) | AG01 | Transaction forbidden | Direct debit is forbidden on this account for regulatory reasons. | Reject, Return | The account type cannot be debited by direct debit (for example a savings account). Not used for B2B-to-consumer cases: that is AC13. | The debtor gave an account that direct debits cannot be booked from. | Agree another account or another payment method with the debtor. | EPC173-14 version 8.0 (28 November 2024) | 2026-11-17 |
SEPA Direct Debit (SDD) | AG02 | Invalid bank operation code | Operation code, transaction code or sequence type is wrong, or the file format is invalid. | Reject, Return | 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. | A technical error or a process error when the collection or file (sequence type) was made. | Correct the wrong field (sequence type FRST/RCUR/OOFF, local instrument CORE/B2B) and send again. | EPC173-14 version 8.0 (28 November 2024) | 2026-11-17 |
SEPA Direct Debit (SDD) | AM04 | Insufficient funds | Not enough money on the account. | Reject, Return | 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. | The debtor has too little money on the account, or the creditor sent the pre-notification (date and amount) late or not at all. | Contact the debtor so that the money is on the account, then collect again. | EPC173-14 version 8.0 (28 November 2024) | 2026-11-17 |
SEPA Direct Debit (SDD) | AM05 | Duplication | Duplicate collection. | Reject, Return, Reversal | The clearing house or the debtor's bank thinks an identical collection was sent or processed very recently. | A technical or human error at the creditor or the creditor's bank. | Check whether the collection really was sent twice before you send it again. | EPC173-14 version 8.0 (28 November 2024) | 2026-11-17 |
SEPA Direct Debit (SDD) | BE05 | Unrecognised initiating party | The creditor identifier is wrong. | Reject, Return | The Creditor Identifier (CI) is not correct, or it changed without the change being reported in the mandate data. | A technical error, or a CI change that was not reported as a mandate amendment. | Correct the Creditor Identifier in your file. | EPC173-14 version 8.0 (28 November 2024) | 2026-11-17 |
SEPA Direct Debit (SDD) | CNOR | Creditor bank is not registered | The creditor's bank is not registered under this BIC in the clearing system. | Reject | The creditor's bank is not (or no longer) a direct debit scheme participant under this BIC in the clearing system. | The creditor's bank is not (or no longer) declared as a participant of this clearing system. | Contact your bank. | EPC173-14 version 8.0 (28 November 2024) | 2026-11-17 |
SEPA Direct Debit (SDD) | DNOR | Debtor bank is not registered | The debtor's bank is not registered under this BIC in the clearing system. | Reject | The debtor's bank is not (or no longer) a direct debit scheme participant under this BIC in the clearing system. | The creditor or its bank did not check that the debtor's bank can be reached. | Ask your bank to check whether the debtor's bank can be reached, or agree another way to pay with the debtor. | EPC173-14 version 8.0 (28 November 2024) | 2026-11-17 |
SEPA Direct Debit (SDD) | ED05 | Settlement failed | Settlement of the collection failed. | Reject | The debtor's bank or the clearing system reports that settlement failed. | The debtor bank's funding for interbank settlement was too low to settle this transaction. | Depends on the agreement between the debtor's bank and the clearing system; ask your bank. | EPC173-14 version 8.0 (28 November 2024) | 2026-11-17 |
SEPA Direct Debit (SDD) | FF01 | Invalid file format | The file format is invalid. | Reject | The XML file is not filled in correctly, has a syntax error, or was not checked against the XSD schema before it was sent. | The creditor, the creditor's bank or the clearing system. | Repair the XML file and send it again. | EPC173-14 version 8.0 (28 November 2024) | 2026-11-17 |
SEPA Direct Debit (SDD) | MD01 | No mandate | No valid mandate, or the mandate could not be confirmed. | Reject, Return, Refund | 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. | 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). | Check the collection data (mandate reference, dates). For a refund, contact the debtor. | EPC173-14 version 8.0 (28 November 2024) | 2026-11-17 |
SEPA Direct Debit (SDD) | MD02 | Missing mandatory mandate information | Mandate data is missing or wrong. | Reject | 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. | The mandate change was not done the way the rulebook says, or the changed data is wrong. | Repair the mandate amendment data and send again. | EPC173-14 version 8.0 (28 November 2024) | 2026-11-17 |
SEPA Direct Debit (SDD) | MD06 | Refund request by end customer | Disputed authorised transaction (SDD Core only). | Refund | The debtor asked for the unconditional refund of a Core collection, up to 8 weeks after the debit date. | The amount differs from the pre-notification, or the debtor used the unconditional refund right under the Payment Services Directive (PSD). | Contact the debtor. | EPC173-14 version 8.0 (28 November 2024) | 2026-11-17 |
SEPA Direct Debit (SDD) | MD07 | End customer deceased | The debtor has died. | Reject, Return | The debtor is deceased. In some SEPA countries data protection law forbids this code and MS03 is used instead. | null | Close the agreement with the deceased debtor. | EPC173-14 version 8.0 (28 November 2024) | 2026-11-17 |
SEPA Direct Debit (SDD) | MS02 | Not specified reason, customer generated | Refused by the debtor. | Reject, Return, Reversal, Refusal | The debtor refused the collection when it was presented. | After the pre-notification the debtor decided to refuse the collection. | Contact the debtor. | EPC173-14 version 8.0 (28 November 2024) | 2026-11-17 |
SEPA Direct Debit (SDD) | MS03 | Not specified reason, agent generated | Reason not given. | Reject, Return, Reversal | 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. | One of the reasons above that the bank may not name in that country (closed account, no funds, deceased, missing regulatory data). | Contact the debtor. | EPC173-14 version 8.0 (28 November 2024) | 2026-11-17 |
SEPA Direct Debit (SDD) | RC01 | Bank identifier incorrect | The bank identifier (BIC) is wrong. | Reject, Return | The BIC of the scheme participant is not correct. | 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. | 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. | EPC173-14 version 8.0 (28 November 2024) | 2026-11-17 |
SEPA Direct Debit (SDD) | RR01 | Missing debtor account or identification | Regulatory reason. | Reject, Return | Details about the debtor's account or identification are missing. In some SEPA countries MS03 is used instead. | The debtor's IBAN or identification needed for regulatory reasons is missing or not enough. | Repair the collection so the debtor's account data is complete, or contact your bank. | EPC173-14 version 8.0 (28 November 2024) | 2026-11-17 |
SEPA Direct Debit (SDD) | RR02 | Missing debtor name or address | Regulatory reason. | Reject, Return | 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. | The debtor's name and/or address needed for regulatory reasons is missing or not enough. | Repair the collection with the debtor's name and a structured address, or contact your bank. | EPC173-14 version 8.0 (28 November 2024) | 2026-11-17 |
SEPA Direct Debit (SDD) | RR03 | Missing creditor name or address | Regulatory reason. | Reject, Return | 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. | The creditor's name needed for regulatory reasons is missing or not enough. | Repair the collection with your name (and a structured address if you send one), or contact your bank. | EPC173-14 version 8.0 (28 November 2024) | 2026-11-17 |
SEPA Direct Debit (SDD) | RR04 | Regulatory reason | Regulatory reason. | Reject, Return | Only for regulatory reasons other than RR01, RR02 or RR03. In some SEPA countries MS03 is used instead. | null | Contact your bank. | EPC173-14 version 8.0 (28 November 2024) | 2026-11-17 |
SEPA Direct Debit (SDD) | SL01 | Specific service offered by debtor agent | Due to a special service of the debtor's bank. | Reject, Return | 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. | null | Contact the debtor. | EPC173-14 version 8.0 (28 November 2024) | 2026-11-17 |
SEPA Credit Transfer (SCT) | AC01 | Incorrect account number | The payee's IBAN is invalid or does not exist. | Reject, Return | 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. | 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. | Ask the payee for the correct IBAN and pay again. | EPC135-18 version 6.1 (30 September 2026) | 2026-11-17 |
SEPA Credit Transfer (SCT) | AC03 | Invalid creditor account number | The payment went to the wrong IBAN. | Request for recall by the originator (RFRO) | The payer sent a transfer to a wrong IBAN and asks to get the money back. | The payer picked or typed a wrong IBAN for the payee. | Check IBANs before you send (for example with an IBAN checker) so it does not happen again. | EPC135-18 version 6.1 (30 September 2026) | 2026-11-17 |
SEPA Credit Transfer (SCT) | AC04 | Closed account number | The payee's account is closed. | Return; negative answer to a recall or RFRO | 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. | The payee closed the account since your last transfer to it. | Ask the payee for the new account. | EPC135-18 version 6.1 (30 September 2026) | 2026-11-17 |
SEPA Credit Transfer (SCT) | AC06 | Blocked account | The payee's account is blocked. | Return | The account is blocked for any financial transaction. | The payee's bank blocked the account (court order, suspected misuse, or a request from the payee). | Ask the payee for another account or another way to pay. | EPC135-18 version 6.1 (30 September 2026) | 2026-11-17 |
SEPA Credit Transfer (SCT) | ACNR | Accepted claim non-receipt | Positive answer to a 'claim of non-receipt' inquiry. | Positive answer to SCT inquiry | The payee's bank confirms it credited the payment to the payee's IBAN and gives the date it was credited. | null | Your bank tells you the payment was processed as you instructed. | EPC135-18 version 6.1 (30 September 2026) | 2026-11-17 |
SEPA Credit Transfer (SCT) | ACVA | Accepted value date adjustment | Positive answer to a 'claim for value date correction'. | Positive answer to SCT inquiry | The payee's bank agrees to correct the value date and asks the payer's bank for interest compensation first. | The wrong value date was not caused by the payee's bank. | The payer's bank pays the interest compensation first. | EPC135-18 version 6.1 (30 September 2026) | 2026-11-17 |
SEPA Credit Transfer (SCT) | AG01 | Transaction forbidden | Credit transfers are not allowed on this account (for example a savings account). | Return | The transfer cannot be booked on this type of account. | The payee gave an account that transfers cannot be booked to. | Agree another account or payment method with the payee. | EPC135-18 version 6.1 (30 September 2026) | 2026-11-17 |
SEPA Credit Transfer (SCT) | AG02 | Invalid bank operation code | Operation or transaction code is wrong, or the file format is invalid. | Reject, Return | The scheme code (service level or local instrument) in the message is wrong. Pure XML file problems use FF01 instead. | A technical error or a processing error in the transfer or the file of transfers. | Correct the wrong field and send again. | EPC135-18 version 6.1 (30 September 2026) | 2026-11-17 |
SEPA Credit Transfer (SCT) | AM04 | Insufficient funds | Not enough money on the payee's account to give the money back. | Negative answer to a recall or RFRO | The payee's account does not hold the full amount of the recall or RFRO. In some SEPA countries CUST is used instead. | Too little money on the payee's account. | Contact the payee directly to get the money back outside the recall procedure. | EPC135-18 version 6.1 (30 September 2026) | 2026-11-17 |
SEPA Credit Transfer (SCT) | AM05 | Duplication | Duplicate payment. | Reject, Return | The clearing system or the payee's bank thinks an identical transfer was sent or processed very recently. | A technical or human error at the payer or the payer's bank. | Check whether the transfer really was sent twice. | EPC135-18 version 6.1 (30 September 2026) | 2026-11-17 |
SEPA Credit Transfer (SCT) | AM09 | Wrong amount | The payer sent more than intended. | Request for recall by the originator (RFRO) | The payer sent a transfer for a higher amount than intended and asks for the money back. | A technical or human error at the payer. | Fix how payment amounts are entered so it does not happen again. | EPC135-18 version 6.1 (30 September 2026) | 2026-11-17 |
SEPA Credit Transfer (SCT) | ARDT | Already returned | The payment was already sent back. | Negative answer to a recall, RFRO or claim of non-receipt | 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. | null | No action; for a return, follow the return reason code. | EPC135-18 version 6.1 (30 September 2026) | 2026-11-17 |
SEPA Credit Transfer (SCT) | ARJT | Already rejected | The payment was already rejected. | Negative answer to a claim of non-receipt | The payee's bank could not process the original transfer. | See the reject reason code of the original transfer. | Follow the advice for that reject code. | EPC135-18 version 6.1 (30 September 2026) | 2026-11-17 |
SEPA Credit Transfer (SCT) | BE04 | Missing creditor address | The payee's address is missing. | Return | The payee's address was not given but is needed for further processing. | Missing or invalid payee address. | Send the transfer again with the payee's address (structured: at least town and country). | EPC135-18 version 6.1 (30 September 2026) | 2026-11-17 |
SEPA Credit Transfer (SCT) | CERI | Check ERI | Not flagged as Extended Remittance Information but contains it. | Reject | The transfer is not tagged as an ERI instruction but carries ERI data. | An error in the payer's or the payer's bank's system when the payment message was made. | The payer's bank checks its process and may come back to the payer. | EPC135-18 version 6.1 (30 September 2026) | 2026-11-17 |
SEPA Credit Transfer (SCT) | CNOR | Creditor bank is not registered | The payee's bank is not registered under this BIC in the clearing system. | Reject, Return | The payee's bank is not (or no longer) a SCT participant under this BIC in the clearing system. | The payee's bank is not (or no longer) declared as a participant of this clearing system. | Ask the payee how they can receive transfers through another bank. | EPC135-18 version 6.1 (30 September 2026) | 2026-11-17 |
SEPA Credit Transfer (SCT) | CUST | Requested by customer | 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 | a) The payer wants back the money of an earlier settled transfer. b) The payee will not honour the recall or RFRO. | a) No specific reason given. b) The payee says it is entitled to the money. | a) No action. b) Contact the payee directly to get the money back outside the recall procedure. | EPC135-18 version 6.1 (30 September 2026) | 2026-11-17 |
SEPA Credit Transfer (SCT) | CVAA | Correct value date already applied | Negative answer to a 'claim for value date correction'. | Negative answer to SCT inquiry | The payee's bank refuses the value date correction. | The payee's bank says it already applied the correct value date. | The payer's bank explains that the transfer was done as instructed. | EPC135-18 version 6.1 (30 September 2026) | 2026-11-17 |
SEPA Credit Transfer (SCT) | DNOR | Debtor bank is not registered | The payer's bank is not registered under this BIC in the clearing system. | Reject | The payer's bank is not (or no longer) a SCT participant under this BIC in the clearing system. | The payer's bank sent the transfer by mistake to its former clearing system. | The payer's bank routes it to its current clearing system; otherwise agree another way to pay. | EPC135-18 version 6.1 (30 September 2026) | 2026-11-17 |
SEPA Credit Transfer (SCT) | DUPL | Duplicate payment | Duplicate sending. | Recall | The payer or the payer's bank found a duplicate transfer and tries to get that money back. | A technical or human error at the payer or the payer's bank. | Set up checks that stop duplicate payments. | EPC135-18 version 6.1 (30 September 2026) | 2026-11-17 |
SEPA Credit Transfer (SCT) | ED05 | Settlement failed | Settlement of the credit transfer failed. | Reject | The payer's bank or the clearing system reports a settlement failure. | The payer bank's funding for interbank settlement was too low for this transfer. | Depends on the agreement between the payer's bank and the clearing system; ask your bank. | EPC135-18 version 6.1 (30 September 2026) | 2026-11-17 |
SEPA Credit Transfer (SCT) | ERIN | ERI option not supported | The Extended Remittance Information option is not supported. | Reject, Return | Reject: the payer's bank and/or the payee's bank do not support ERI. Return: the payee's bank does not support ERI. | One of the banks does not offer the ERI option. | The payer decides how to go on (for example pay without ERI). | EPC135-18 version 6.1 (30 September 2026) | 2026-11-17 |
SEPA Credit Transfer (SCT) | FF01 | Invalid file format | The file format is invalid. | Reject | The XML file is not filled in correctly, has a syntax error, or was not checked against the XSD schema before it was sent. | The payer, the payer's bank or the clearing system. | Repair the XML file and send it again. | EPC135-18 version 6.1 (30 September 2026) | 2026-11-17 |
SEPA Credit Transfer (SCT) | FOCR | Following cancellation request | Positive answer to a recall. | Positive answer to a recall or RFRO | The payee's bank or the payee agrees to pay the money back to the payer or the payer's bank. | null | No action. | EPC135-18 version 6.1 (30 September 2026) | 2026-11-17 |
SEPA Credit Transfer (SCT) | FRAD | Fraudulent origin | Fraudulently started credit transfer. | Recall | The payer or the payer's bank found a fraudulent transfer and tries to get the money back. | The payer was a victim of fraud, or fraudsters manipulated the payer bank's systems. | Set up measures that stop fraudulent transfers. | EPC135-18 version 6.1 (30 September 2026) | 2026-11-17 |
SEPA Credit Transfer (SCT) | LEGL | Legal decision | Legal reasons. | Negative answer to a recall or RFRO | The payee's bank is not allowed to pay the money back. | The money cannot be paid back for legal reasons. | Contact the payee directly to get the money back outside the recall procedure. | EPC135-18 version 6.1 (30 September 2026) | 2026-11-17 |
SEPA Credit Transfer (SCT) | MD07 | End customer deceased | The payee has died. | Return | The payee is deceased. In some SEPA countries data protection law forbids this code and MS03 is used instead. | null | No action. | EPC135-18 version 6.1 (30 September 2026) | 2026-11-17 |
SEPA Credit Transfer (SCT) | MODI | Modified as per request | Confirmed positive answer to a 'claim for value date correction'. | Confirmed positive answer to SCT inquiry | The payee's bank confirms it corrected the value date on the payee's IBAN. | The payee's bank got the interest compensation, asks none, or asks for it later (code VADA). | The payer's bank pays the interest compensation if VADA was given. | EPC135-18 version 6.1 (30 September 2026) | 2026-11-17 |
SEPA Credit Transfer (SCT) | MS02 | Not specified reason, customer generated | Refused by the payee. | Return | The payee refused the transfer when it was presented to the payee's bank. | The payee told its bank not to accept money from this account, this payer, or this payment scheme. | Ask the payee how you should pay what you owe. | EPC135-18 version 6.1 (30 September 2026) | 2026-11-17 |
SEPA Credit Transfer (SCT) | MS03 | Not specified reason, agent generated | Reason not given. | Reject, Return | 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. | One of the reasons above that the bank may not name in that country. | Ask the payee how you should pay what you owe. | EPC135-18 version 6.1 (30 September 2026) | 2026-11-17 |
SEPA Credit Transfer (SCT) | NERI | No ERI | Flagged as Extended Remittance Information but contains none. | Reject | The transfer is tagged as an ERI instruction but carries no ERI data. | An error in the payer's or the payer's bank's system when the payment message or file was made. | Send the transfer (file) again with the ERI data. | EPC135-18 version 6.1 (30 September 2026) | 2026-11-17 |
SEPA Credit Transfer (SCT) | NOAS | No answer from customer | No response from the payee. | Negative answer to a recall or RFRO | The payer or the payer's bank tries to get money back from an earlier transfer. | The payee's bank cannot reach the payee, or the payee does not answer. | Contact the payee directly to get the money back outside the recall procedure. | EPC135-18 version 6.1 (30 September 2026) | 2026-11-17 |
SEPA Credit Transfer (SCT) | NOOR | No original transaction received | The original transfer was never received. | Negative answer to a recall, RFRO or claim of non-receipt | The payee's bank or the payee says it never received the original transfer. | The recall or inquiry went to the wrong bank or payee, or the payee's bank never got the transfer. | The payer's bank sends the recall or inquiry to the correct bank or payee. | EPC135-18 version 6.1 (30 September 2026) | 2026-11-17 |
SEPA Credit Transfer (SCT) | RC01 | Bank identifier incorrect | The BIC is wrong. | Reject, Return | The BIC of the scheme participant is not correct. | 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. | Ask the payee for the correct, complete BIC (non-EEA transfers), or ask your bank to fix it. | EPC135-18 version 6.1 (30 September 2026) | 2026-11-17 |
SEPA Credit Transfer (SCT) | RJNR | Rejected claim non-receipt | Negative answer to a 'claim of non-receipt'. | Negative answer to SCT inquiry | The payee's bank gives a precise reason: NOOR, RNPR, ARJT, ARDT or RR04. | Never received (NOOR), received but not processable (RNPR), already rejected (ARJT), already returned (ARDT), regulatory reason (RR04). | Follow the advice for the code given. | EPC135-18 version 6.1 (30 September 2026) | 2026-11-17 |
SEPA Credit Transfer (SCT) | RJVA | Rejected value date adjustment | Negative answer to a 'claim for value date correction'. | Negative answer to SCT inquiry | The payee's bank refuses to correct the value date. | The debit date is more than 13 months before the inquiry, or before 17 November 2019 (when the inquiry procedure started). | No further action. | EPC135-18 version 6.1 (30 September 2026) | 2026-11-17 |
SEPA Credit Transfer (SCT) | RNPR | Original transaction received but not processable | Received but not processable. | Negative answer to a claim of non-receipt | The payee's bank cannot process the transfer at this time, for a reason other than ARJT, ARDT or RR04. | null | The two banks contact each other to solve it. | EPC135-18 version 6.1 (30 September 2026) | 2026-11-17 |
SEPA Credit Transfer (SCT) | RR01 | Missing debtor account or identification | Regulatory reason. | Reject, Return | The payer's account details are missing. In some SEPA countries MS03 is used instead. | The payer's account or identification needed for regulatory reasons is missing or not enough. | The payer's bank completes the payer's account data and sends again. | EPC135-18 version 6.1 (30 September 2026) | 2026-11-17 |
SEPA Credit Transfer (SCT) | RR02 | Missing debtor name or address | Regulatory reason. | Reject, Return | 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. | The payer's name and/or address needed for regulatory reasons is missing or not enough. | Send the transfer again with the payer's name and a structured address. | EPC135-18 version 6.1 (30 September 2026) | 2026-11-17 |
SEPA Credit Transfer (SCT) | RR03 | Missing creditor name or address | Regulatory reason. | Reject, Return | 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. | The payee's name needed for regulatory reasons is missing or not enough. | Send the transfer again with the payee's name (and a structured address if you send one). | EPC135-18 version 6.1 (30 September 2026) | 2026-11-17 |
SEPA Credit Transfer (SCT) | RR04 | Regulatory reason | Regulatory reason. | Reject, Return; negative answer to a claim of non-receipt | 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). | A possible hit in anti-money-laundering, embargo or counter-terrorist-financing checks. | Contact your bank. | EPC135-18 version 6.1 (30 September 2026) | 2026-11-17 |
SEPA Credit Transfer (SCT) | TECH | Technical problem | Technical problems caused wrong transfers. | Recall | The payer or the payer's bank found a technical problem that sent wrong transfers and tries to get the money back. | A technical issue in the payer's systems or the payer bank's systems when the transfers or files were made. | Set up measures that stop such technical problems. | EPC135-18 version 6.1 (30 September 2026) | 2026-11-17 |
SEPA Credit Transfer (SCT) | TM01 | Cut-off time | File received after the cut-off time. | Reject | The clearing system did not receive the transfer (file) before its cut-off time. | A connection, processing or validation issue between the payer's bank and the clearing system. | The payer's bank sends the transfers again before the next cut-off time. | EPC135-18 version 6.1 (30 September 2026) | 2026-11-17 |
Every ISO 20022 reason code a bank uses when a SEPA Direct Debit or SEPA Credit Transfer is rejected, returned, refused or recalled (AC01, AC04, AC06, AM04, MD01, MS02, MS03, SL01 ...), in one CSV: 25 SDD codes + 43 SCT codes. For each code: the official meaning, where it is used (reject / return / refund / recall), the typical cause, and what to do next.
scheme, code, name, short_meaning, used_for, official_description, typical_cause, what_to_do, source, checked.import pandas as pd
df = pd.read_csv("hf://datasets/Radarbg/sepa-return-reason-codes/sepa_return_reason_codes.csv")
print(df[df.code == "AM04"])
Check or upgrade a SEPA XML payment file (pain.001 / pain.008) for free: https://radarbg.com/instant/sepa-check?ref=hf