Swift rejection codes
This page lists Swift rejection codes, which indicate why a payment or message could not be processed. Each code specifies the type of issue and the reason for the rejection
Swift Rejection Codes and Reasons
| Code | Type | Reason |
|---|---|---|
| C01 | Account Number | Format of the account number specified is not correct. |
| AC02 | Account Number | Format of the account number specified is non-numeric. |
| AC03 | Account Number | Format of the account number specified is not valid for local sort/national clearing code. |
| AC04 | Account Number | Account number specified has been closed on the receiver's books. |
| AC05 | Account Number | Account number specified is not a valid account at the Account with Institution. |
| AC06 | Account Number | Account specified is blocked, prohibiting posting of transactions against it. |
| AM01 | Amount | Specified transaction/message amount is equal to zero. |
| AM02 | Amount | Specified transaction/message amount is greater than allowed maximum. |
| AM03 | Amount | Specified transaction/message amount is in a non-processable currency outside of existing agreement. |
| AM04 | Amount | Amount of funds available to cover specified transaction/message amount is insufficient. |
| AM05 | Amount | This transaction/message appears to have been duplicated. |
| AM06 | Amount | Specified transaction amount is less than agreed minimum. |
| AM07 | Amount | Amount specified in transaction/message has been blocked by regulatory authorities. |
| AM08 | Amount | Specified charge amount is not as agreed between sender and receiver. |
| BE01 | Beneficiary | Specification of beneficiary is not consistent with associated account number. |
| BE02 | Beneficiary | Beneficiary specified is not known at associated sort/national clearing code. |
| BE03 | Beneficiary | Beneficiary specified no longer exists in the books. |
| BE04 | Beneficiary | Specification of beneficiary address – which is required for payment – is missing/not correct. |
| BE05 | Beneficiary | Party who initiated the transaction/message is not recognised by the beneficiary. |
| AG01 | Agreement | No agreement is on file at the receiver for affecting associated transaction/message. |
| AG02 | Agreement | Bank Operation code specified in the transaction/message is not valid for receiver. |
| DT01 | Date | Invalid date (for example, wrong settlement date). |
| MS01 | General | Reason has not been specified due to sensitivities. |
| PY01 | Party | Unknown Account-With Institution. |
| RF01 | Reference | Transaction reference is not unique within the message. |
| RC01 | Routing Code | Routing code specified in the transaction/message has an incorrect format. |
| RC02 | Routing Code | Routing code specified in the transaction/message is not numeric. |
| RC03 | Routing Code | Routing code specified in the transaction/message is not valid for local clearing. |
| RC04 | Routing Code | Routing code specified in the transaction/message refers to a closed branch. |
| RR01 | Regulatory Requirement | Specification of the ordering customer's account or unique identification – needed for reasons of regulatory requirements – is insufficient or missing. |
| RR02 | Regulatory Requirement | Specification of the ordering customer's name and/or address – needed for regulatory requirements – is insufficient or missing. |
| RR03 | Regulatory Requirement | Specification of the beneficiary customer's name and/or address – needed for regulatory requirements – is insufficient or missing. |
| TM01 | Receipt Time | Associated transaction/message was received after agreed processing cut-off time. |
| X1!c2!n | Bilateral | Refers to a reject/return code whose specification and meaning has been bilaterally agreed to by Sending and Receiving parties. |
Updated about 2 hours ago