List of ISO 20022 "Request for Payment RfP" Return / Reject reason codes
To obtain the most accurate and current information on ISO 20022 "AllCodeSets" reasons for "Request for Payment" in the context of FedNow and Real-time Payments, I recommend checking the official ISO 20022 documentation and any specific guidelines or documentation provided by the Federal Reserve for FedNow or the relevant payment network or authority overseeing Real-time Payments.
When encountering Request For Payment (RFP) return or reject codes during the receiving of funding transmissions, it's important to take specific actions to address the issues and ensure that the message data is "cleaned" before attempting to proceed. Here are common actions associated with handling return and reject codes:
Identify the Reason or Reject Code:
- Review the reason or reject code provided by the bank to understand the specific reason for the rejection. The reject and return codes will typically point to the nature of the issue with the Request For Payment.
Review Payer and Payee Information:
- For codes related to payer or payee information, carefully review the details provided in the RFP. Verify that payer and payee information is accurate, complete, and matches the records on both ends.
Correct Invalid Information:
- If the reject code indicates invalid or incomplete information, take corrective actions to ensure that all required data fields are accurate and properly filled out. This may involve updating payer or payee details.
Communicate with Payer and Payee:
- In cases of invalid payer or payee information, reach out to both parties to resolve any discrepancies. This may include updating contact details, addresses, or account information.
Address Insufficient Funds:
- If the reject or return code is related to insufficient funds, communicate with the payer to address the issue. This may involve requesting additional funds, alternative payment methods, or negotiating payment terms.
Check for Duplicate Transactions:
- If the return or rejection code indicates a duplicate transaction, review recent submissions to ensure that the same request has not been submitted multiple times. Avoid resubmitting duplicate transactions.
Verify Payment Amount:
- For reject codes related to payment amount, verify that the specified amount is within acceptable limits and meets the transaction requirements.
Adhere to Request Format:
- Ensure that the request for payment adheres to the required format and standards specified by the bank. Correct any issues related to the format of the message.
Update Payment Reference:
- If the reject is due to an error with the payment reference or invoice number, update the information to ensure accuracy.
Confirm Payee Account Status:
- If the reject code indicates that the payee's account is closed, confirm the status of the payee's account. If necessary, obtain updated account information.
Correct Bank Account Information:
- For reject codes related to bank account information mismatches, verify and correct the bank account details to ensure accuracy.
Document and Record Actions:
- Keep detailed records of the actions taken to address each reject code. This documentation is crucial for tracking resolutions and ensuring compliance.
Clean Data and Reattempt:
- Once the identified issues are resolved, and the data is cleaned, you can reattempt the transmission of the Request For Payment.
Continuous Monitoring:
- Implement continuous monitoring and validation processes to prevent similar issues in future transactions. Regularly update and review data to ensure accuracy.
Remember to work closely with both the payer and payee, as well as your banking partners, to address any issues promptly and efficiently. Effective communication and proactive resolution of returned and reject codes are essential for successful Request For Payment transactions.
Below are a "range of codes" that make it easier for ERP systems and Persons to understnad the type of document that is being referenced:
| Code | Description |
| AROI | Account Receivable Open Item |
| BOLD | Bill of Lading |
| CINV | Commercial Invoice |
| CMCN | Commercial Contract |
| CNFA | Credit Note Related To Financial Adjustment |
| CREN | Credit Note |
| DEBN | Debit Note |
| DISP | Dispatch Advice |
| DNFA | Debit Note Related To Financial Adjustment |
| HIRI | Hire Invoice |
| MSIN | Metered Service Invoice |
| SBIN | Self-Billed Invoice |
| SOAC | Statement of Account |
| TSUT | Trade Service Utility Transaction |
| VCHR | Voucher |
Please note that these reason codes are provided as examples and may not cover all possible scenarios. The specific reason codes used in a real-time payment system can vary, and financial institutions and payment service providers may define their own sets of reason codes based on their operational and regulatory requirements. It's important to refer to the documentation and rules of the specific payment system or organization to determine the exact reason codes in use.
|
Return Code |
Code Name |
Code Definition |
Usage |
| AB01 | Aborted Clearing Timeout | Clearing process aborted due to timeout. | |
| AB02 | Aborted Clearing Fatal Error | Clearing process aborted due to a fatal error. | |
| AB03 | Aborted Settlement Timeout | Aborted Settlement Timeout | |
| AB04 | Aborted Settlement Fatal Error | Settlement process aborted due to a fatal error | |
| AB05 | Timeout Creditor Agent | Transaction stopped due to timeout at the Creditor Agent | |
| AB06 | Timeout Instructed Agent | Transaction stopped due to timeout at the Instructed Agent | |
| Use QBO Request for Payments | |||
| AB07 | Offline Agent | Agent of message is not online | Generic usage if it cannot be determined who exactly is not online |
| AB08 | Offline Creditor Agent | Creditor Agent is not online | |
| AB09 | Error Creditor Agent | Transaction stopped due to error at the Creditor Agent | |
| AB10 | Error Instructed Agent | Transaction stopped due to error at the Instructed Agent | |
| AC01 | Incorrect Account Number | Account number is invalid or missing | Generic usage if cannot specify between debit or credit account |
| AC02 | Invalid Debtor Account Number | Debtor account number invalid or missing | |
| AC03 | Invalid Creditor Account Number | Creditor account number invalid or missing | |
| AC04 | Closed Account Number | Account number specified has been closed on the bank of account's books. | Generic usage if cannot specify between debit or credit account |
| AC05 | Closed Debtor Account Number | Debtor account number closed | |
| AC06 | Blocked Account | Account specified is blocked, prohibiting posting of transactions against it. | |
| Use RequestForPayment.com | |||
| AC07 | Closed Creditor Account Number | Creditor account number closed | |
| AC08 | Invalid Branch Code | Branch code is invalid or missing | |
| AC09 | Invalid Account Currency | Account currency is invalid or missing | |
| AC10 | Invalid Debtor Account Currency | Debtor account currency is invalid or missing | |
| AC11 | Invalid Creditor Account Currency | Creditor account currency is invalid or missing | |
| AC12 | Invalid Account Type | Account type missing or invalid Generic usage if cannot specify between group and payment information levels |
Generic usage if cannot specify between group and payment information levels |
| AC13 | Invalid Debtor Account Type | Debtor account type missing or invalid | |
| AC14 | Invalid Creditor Account Type | Creditor account type missing or invalid | |
| ACTC | Accepted | The Request for Return of Funds has been accepted | |
| AG01 | Transaction Forbidden | Transaction forbidden on this type of account (formerly NoAgreement) | |
| AG02 | Invalid Bank Operation Code | Bank Operation code specified in the message is not valid for receiver | |
| AG03 | Transaction Not Supported | Transaction type not supported/authorized on this account | |
| AG04 | Invalid Agent Country | Agent country code is missing or invalid Generic usage if cannot specify between group and payment information levels |
Generic usage if cannot specify between group and payment information levels |
| AG05 | Invalid Debtor Agent Country | Debtor agent country code is missing or invalid | |
| AG06 | Invalid Creditor Agent Country | Creditor agent country code is missing or invalid | |
| AG07 | Unsuccesful Direct Debit | Debtor account cannot be debited for a generic reason. Code value may be used in general purposes and as a replacement for AM04 if debtor bank does not reveal its customer's insufficient funds for privacy reasons |
Code value may be used in general purposes and as a replacement for AM04 if debtor bank does not reveal its customer's insufficient funds for privacy reasons |
| AG08 | Invalid Access Rights | Transaction failed due to invalid or missing user or access right | |
| Use QBO Request for Payments | |||
| AG09 | Payment Not Received | Original payment never received | |
| AG10 | Agent Suspended | Agent of message is suspended from the Real Time Payment system | Generic usage if it cannot be determined who exactly is suspended |
| AG11 | Creditor Agent Suspended | Creditor Agent of message is suspended from the Real-Time Payment system | |
| AGNT | Incorrect Agent | Agent in the payment workflow is incorrect | |
| AM01 | Zero Amount | Specified message amount is equal to zero | |
| AM02 | Not Allowed Amount | Specific transaction/message amount is greater than allowed maximum | |
| AM03 | Not Allowed Currency | Specified message amount is an non processable currency outside of existing agreement | |
| AM04 | Insufficient Funds | Amount of funds available to cover specified message amount is insufficient. | |
| AM05 | Duplication | Duplication | |
| AM06 | Too Low Amount | Specified transaction amount is less than agreed minimum. | |
| AM07 | Blocked Amount | Amount of funds available to cover specified message amount is insufficient. | |
| AM09 | Wrong Amount | Amount received is not the amount agreed or expected | |
| AM10 | Invalid Control Sum | Sum of instructed amounts does not equal the control sum. | Generic usage if cannot specify between group and payment information levels |
| AM11 | Invalid Transaction Currency | Transaction currency is invalid or missing | |
| AM12 | Invalid Amount | Amount is invalid or missing | |
| AM13 | Amount Exceeds Clearing System Limit | Transaction amount exceeds limits set by clearing system | |
| Use FedNow Files | |||
| AM14 | Amount Exceeds Agreed Limit | Transaction amount exceeds limits agreed between bank and client | |
| AM15 | Amount Below Clearing System Minimum | Transaction amount below minimum set by clearing system | |
| AM16 | Invalid Group Control Sum | Control Sum at the Group level is invalid | |
| AM17 | Invalid Payment Info Control Sum | Control Sum at the Payment Information level is invalid | |
| AM18 | Invalid Number Of Transactions | Number of transactions is invalid or missing Generic usage if cannot specify between group and payment information levels |
|
| AM19 | Invalid Group Number Of Transactions | Number of transactions at the Group level is invalid or missing | |
| AM20 | Invalid Payment InfoNumber Of Transactions | Number of transactions at the Payment Information level is invalid | |
| AM21 | Limit Exceeded | Transaction amount exceeds limits agreed between bank and client. | |
| AM22 | Zero Amount Not Applied | Unable to apply zero amount to designated account. For example, where the rules of a service allow the use of zero amount payments, however the back-office system is unable to apply the funds to the account. If the rules of a service prohibit the use of zero amount payments, then code AM01 is used to report the error condition | |
| AM23 | Amount Exceeds Settlement Limit | Transaction amount exceeds settlement limit | |
| APAR | Already Paid RTP | Request to pay has already been paid by the Debtor | |
| ARDT | FI | Already Returned Cancellation not accepted as the transaction has already been returned |
|
| BE01 | Inconsisten With End Customer | Identification of end customer is not consistent with associated account number. (formerly CreditorConsistency). | |
| BE04 | Missing Creditor Address | Specification of creditor's address, which is required for payment, is missing/not correct (formerly IncorrectCreditorAddress). | |
| BE05 | Unrecognised Initiating Party | Party who initiated the message is not recognised by the end customer | |
| BE06 | Unknown End Customer | End customer specified is not known at associated Sort/National Bank Code or does no longer exist in the books | |
| BE07 | Missing Debtor Address | Specification of debtor's address, which is required for payment, is missing/not correct. | |
| Use us for Request for Payments | |||
| BE08 | Missing Debtor Name | Debtor name is missing | |
| BE09 | InvalidCountry | Country code is missing or Invalid Generic usage if cannot specifically identify debtor or creditor |
|
| BE10 | Invalid Debtor Country | Debtor country code is missing or Invalid | |
| BE11 | Invalid Creditor Country | Creditor country code is missing or Invalid | |
| BE12 | Invalid Country Of Residence | Country code of residence is missing or Invalid Generic usage if cannot specifically identify debtor or creditor |
|
| BE13 | Invalid Debtor Country Of Residence | Country code of debtor's residence is missing or Invalid | |
| BE14 | Invalid Creditor Country Of Residence | Country code of creditor's residence is missing or Invalid | |
| BE15 | Invalid Identification Code | Identification code missing or invalid Generic usage if cannot specifically identify debtor or creditor |
|
| BE16 | Invalid Debtor Identification Code | Debtor or Ultimate Debtor identification code missing or invalid | |
| BE17 | Invalid Creditor Identification Code | Creditor or Ultimate Creditor identification code missing or invalid | |
| BE18 | Invalid Contact Details | Contact details missing or invalid | |
| BE19 | Invalid Charge Bearer Code | Charge bearer code for transaction type is invalid | |
| BE20 | Invalid Name Length | Name length exceeds local rules for payment type. | |
| BE21 | Missing Name | Name missing or invalid Generic usage if cannot specifically identify debtor or creditor |
|
| BE22 | Missing Creditor Name | Creditor name is missing | |
| CH03 | Requested Execution Date Or Requested Collection Date Too Far In Future | Value in Requested Execution Date or Requested Collection Date is too far in the future | |
| CH04 | Requested Execution Date Or Requested Collection Date Too Far In Past | Value in Requested Execution Date or Requested Collection Date is too far in the past | |
| CH07 | Element Is Not To Be Used At B- and C- Level | Element is not to be used at B- and C-Level | |
| CH09 | Mandate Changes Not Allowed | Mandate changes are not allowed | |
| CH10 | Information On Mandate Changes Missing | Information on mandate changes are missing | |
| CH11 | Creditor Identifier Incorrect | Value in Creditor Identifier is incorrect | |
| CH12 | Creditor Identifier Not Unambiguously At Transaction-Level | Creditor Identifier is ambiguous at Transaction Level | |
| CH13 | Original Debtor Account Is Not To Be Used | Original Debtor Account is not to be used | |
| CH14 | Original Debtor Agent Is Only To Be Used With Sequence Type FRST | Original Debtor Agent is only to be used with Sequence Type=FRST | |
| CH15 | Element Content Includes More Than 140 Characters | Content Remittance Information/Structured includes more than 140 characters | |
| CH16 | Element Content Formally Incorrect | Content is incorrect | |
| CH17 | Element Not Admitted | Element is not allowed | |
| CH19 | Values Will Be Set To Next TARGET day | Values in Interbank Settlement Date or Requested Collection Date will be set to the next TARGET day | |
| CH20 | Decimal Points Not Compatible With Currency | Number of decimal points not compatible with the currency | |
| CH21 | Required Compulsory Element Missing | Mandatory element is missing | |
| CH22 | CORE and B2B within One message | SDD CORE and B2B not permitted within one message | |
| Use QBO Request for Payments | |||
| CN01 | Authorisation Cancelled | Authorisation is cancelled | |
| CNOR | Creditor bank is not registered | Creditor bank is not registered under this BIC in the CSM | |
| CURR | Incorrect Currency | Currency of the payment is incorrect | |
| CUST | Requested By Customer | Cancellation requested by the Debtor | |
| CUTA | Cancel Upon Unable to Apply | Cancellation requested because an investigation request has been received and no remediation is possible | |
| DNOR | Debtor bank is not registered | Debtor bank is not registered under this BIC in the CSM | |
| DS01 | Electronic Signatures Correct | The electronic signature(s) is/are correct | |
| DS02 | Order Cancelled | An authorized user has cancelled the order | |
| DS03 | Order Not Cancelled | The user’s attempt to cancel the order was not successful | |
| DS04 | Order Rejected | The order was rejected by the bank side (for reasons concerning content) | |
| DS05 | Order Forwarded For Post processing | The order was correct and could be forwarded for postprocessing | |
| DS06 | Transfer Order | The order was transferred to VEU | |
| DS07 | Processing OK | All actions concerning the order could be done by the EBICS bank server | |
| DS08 | Decompression Error | The decompression of the file was not successful | |
| DS09 | Decryption Error | The decryption of the file was not successful | |
| DS28 | Return For Technical Reason | Return following technical problems resulting in erroneous transaction | |
| DS0A | Data Sign Requested | Data signature is required. | |
| DS0B | Unknown Data Sign Format | Data signature for the format is not available or invalid. | |
| DS0C | Signer Certificate Revoked | The signer certificate is revoked. | |
| DS0D | Signer Certificate Not Valid | The signer certificate is not valid (revoked or not active). | |
| DS0E | Incorrect Signer Certificate | The signer certificate is not present. | |
| DS0F | Signer Certification Authority Signer Not Valid | The authority of the signer certification sending the certificate is unknown. | |
| DS0G | Not Allowed Payment | Signer is not allowed to sign this operation type. | |
| DS0H | Not Allowed Account | Signer is not allowed to sign for this account. | |
| DS0K | Not Allowed Number Of Transaction | The number of transaction is over the number allowed for this signer. | |
| Use us for RequestforPayments.com | |||
| DS10 | Signer 1 Certificate Revoked | The certificate is revoked for the first signer. | |
| DS11 | Signer 1 Certificate Not Valid | The certificate is not valid (revoked or not active) for the first signer. | |
| DS12 | Incorrect Signer 1 Certificate | The certificate is not present for the first signer. | |
| DS13 | Signer Certification Authority Signer 1 Not Valid | The authority of signer certification sending the certificate is unknown for the first signer. | |
| DS14 | User Does Not Exist | The user is unknown on the server | |
| DS15 | Identical Signature Found | The same signature has already been sent to the bank | |
| DS16 | Public Key Version Incorrect | The public key version is not correct. This code is returned when a customer sends signature files to the financial institution after conversion from an older program version (old ES format) to a new program version (new ES format) without having carried out re-initialisation with regard to a public key change. | |
| DS17 | Different Order Data In Signatures | Order data and signatures don’t match | |
| DS18 | Repeat Order | File cannot be tested, the complete order has to be repeated. This code is returned in the event of a malfunction during the signature check, e.g. not enough storage space. | |
| DS19 | Electronic Signature Rights Insufficient | The user’s rights (concerning his signature) are insufficient to execute the order | |
| DS20 | Signer 2 Certificate Revoked | The certificate is revoked for the second signer. | |
| DS21 | Signer 2 Certificate Not Valid | The certificate is not valid (revoked or not active) for the second signer. | |
| DS22 | Incorrect Signer 2 Certificate | The certificate is not present for the second signer. | |
| DS23 | Signer Certification Authority Signer 2 Not Valid | The authority of signer certification sending the certificate is unknown for the second signer. | |
| DS24 | Waiting Time Expired | Waiting time expired due to incomplete order | |
| DS25 | Order File Deleted | The order file was deleted by the bank server (for multiple reasons) |
|
| DS26 | User Signed Multiple Times | The same user has signed multiple times | |
| DS27 | User Not Yet Activated | The user is not yet activated (technically) | |
| Use QBO Request for Payments | |||
| DT01 | Invalid Date | Invalid date (eg, wrong or missing settlement date) | |
| DT02 | Invalid Creation Date | Invalid creation date and time in Group Header (eg, historic date) | |
| DT03 | Invalid Non Processing Date | Invalid non bank processing date (eg, weekend or local public holiday) | |
| DT04 | Future Date Not Supported | Future date not supported | |
| DT05 | Invalid Cut Off Date | Associated message, payment information block or transaction was received after agreed processing cut-off date, i.e., date in the past. | |
| DT06 | Execution Date Changed | Execution Date has been modified in order for transaction to be processed | |
| DU01 | Duplicate Message ID | Message Identification is not unique. | |
| DU02 | Duplicate Payment Information ID | Payment Information Block is not unique. | |
| DU03 | Duplicate Transaction | Transaction is not unique. | |
| DU04 | Duplicate End To End ID | End To End ID is not unique. | |
| DU05 | Duplicate Instruction ID | Instruction ID is not unique. | |
| Use QBO Request for Payments | |||
| DUPL | Duplicate Payment | Payment is a duplicate of another payment | |
| DS0H | Signer is not allowed to sign for this account | Sender of the message is not linked to the participant | |
| ED01 | Correspondent Bank Not Possible | Correspondent bank not possible. | |
| ED03 | Balance Info Request | Balance of payments complementary info is requested | |
| ED05 | Settlement Failed | Settlement of the transaction has failed. | |
| ED06 | Settlement System Not Available | Interbank settlement system not available | |
| EMVL | EMV Liability Shift | The card payment is fraudulent and was not processed with EMV technology for an EMV card | |
| ERIN | ERI Option Not Supported | The extended remittance information (ERI) option is not supported | |
| FF01 | Invalid File Format | File Format incomplete or invalid | |
| FF02 | Syntax Error | Syntax error reason is provided as narrative information in the additional reason information. | |
| FF03 | Invalid Payment Type Information | Payment Type Information is missing or invalid Generica usage if cannot specify Service Level or Local Instrument code |
|
| FF04 | Invalid Service Level Code | Service Level code is missing or invalid | |
| FF05 | Invalid Local Instrument Code | Local Instrument code is missing or invalid | |
| FF06 | Invalid Category Purpose Code | Category Purpose code is missing or invalid | |
| FF07 | Invalid Purpose | Purpose is missing or invalid | |
| FF08 | Invalid End To End Id | End to End Id missing or invalid | |
| FF09 | Invalid Cheque Number | Cheque number missing or invalid | |
| FF10 | Bank System Processing Error | File or transaction cannot be processed due to technical issues at the bank side | |
| FF11 | Clearing Request Aborted | Clearing request rejected due it being subject to an abort operation | |
| FOCR | Return following a cancellation request | ||
| Use QBO Request for Payments | |||
| FR01 | Fraud | Returned as a result of fraud | |
| FRAD | Fraudulent Origin | Debtor claims payment was unauthorized or fraudulently induced | |
| FRTR | Final Response Mandate Cancelled | Final response / tracking is recalled as mandate is cancelled | |
| ID01 | Corresponding Original File Still Not Sent | Signature file was sent to the bank but the corresponding original file has not been sent yet. | |
| LEGL | Legal Decision | Reported when the cancellation cannot be accepted because of regulatory rules | |
| MD01 | No Mandate | No Mandate | |
| MD02 | Missing Mandatory Information In Mandate | Mandate related information data required by the scheme is missing. | |
| MD03 | Invalid File Format For Other Reason Than Grouping Indicator | File Format is either incomplete or invalid | |
| MD05 | Collection Not Due | Creditor or creditor's agent should not have collected the direct debit | |
| MD06 | Refund Request By End Customer | Return of funds requested by end customer | |
| MD07 | End Customer Deceased | End customer is deceased. | |
| MD08 | No Mandate Service By Agent | Receiving agent does not offer e-Mandate services | |
| MD09 | No Mandate Service On Customer | Account is not open to e-Mandate services | |
| MD10 | No Mandate Service For Specified | Account is not open to e-Mandate services for this particular creditor | |
| MD11 | Unrecognised Agent | Agent to whom the message needs to be forwarded cannot be located | |
| MD12 | Not Unique Mandate Identification | Mandate identification is not unique to the creditor | |
| MD13 | Incorrect Customer Authentication | There is a problem with the customer authentication | |
| MD14 | Incorrect Agent | Agent in the payment workflow is incorrect | |
| MD15 | Incorrect Currenty | Specified currency is incorrect | |
| MD16 | Requested By Customer | Cancellation/amendment is requested by the Debtor (Payer) | |
| MD17 | Requested By Intiating Party | Cancellation/amendment is requested by the Creditor (Payee) | |
| MS02 | Not Specified Reason Customer Generated | Reason has not been specified by end customer | |
| MS03 | Not Specified Reason Agent Generated | Reason has not been specified by agent. | |
| NARR | Narrative | Reason is provided as narrative information in the additional reason information. | |
| NOAS | No Answer From Customer | No response from beneficiary (to the cancellation request) | |
| NOOR | No Original Transaction Received | Original transaction (subject to cancellation) never received | |
| Use us for Request for Payments | |||
| RC01 | Bank Identifier Incorrect | Bank Identifier code specified in the message has an incorrect format (formerly IncorrectFormatForRoutingCode). | |
| RC02 | Invalid Bank Identifier | Bank identifier is invalid or missing Generic usage if cannot specify between debit or credit account |
|
| RC03 | Invalid Debtor Bank Identifier | Debtor bank identifier is invalid or missing | |
| RC04 | Invalid Creditor Bank Identifier | Creditor bank identifier is invalid or missing | |
| RC05 | Invalid BIC Identifier | BIC identifier is invalid or missing Generic usage if cannot specify between debit or credit account |
|
| RC06 | Invalid Debtor BIC Identifier | Debtor BIC identifier is invalid or missing | |
| RC07 | Invalid Creditor BIC Identifier | Creditor BIC identifier is invalid or missing | |
| RC08 | Invalid Clearing System Member Identifier | Clearing System Member identifier is invalid or missing Generic usage if cannot specify between debit or credit account |
|
| RC09 | Invalid Debtor Clearing System Member Identifier | Debtor ClearingSystemMember identifier is invalid or missing | |
| RC10 | Invalid Creditor Clearing System Member Identifier | Creditor ClearingSystemMember identifier is invalid or missing | |
| RC11 | Invalid Intermediary Agent | Intermediary Agent is invalid or missing | |
| RC12 | Missing Creditor Scheme Id | Creditor Scheme Id is invalid or missing | |
| RCON | R-Message Conflict | R-Message Conflict | |
| RF01 | Invalid Payer Information |
|
|
| RF02 | Insufficient Funds |
|
|
| RF03 | Invalid Payment Amount |
|
|
| RF04 | Duplicate Transaction |
|
|
| RF05 | Invalid Request Format |
|
|
| RF06 | Payment Reference Error |
|
|
| RF07 | Payee Account Closed |
|
|
| RF08 | Bank Account Information Mismatch |
|
|
| Use QBO Request for Payments | |||
| RR01 | Missing Debtor Account or Identification | Specification of the debtor’s account or unique identification needed for reasons of regulatory requirements is insufficient or missing | |
| RR02 | Missing Debtor Name or Address | Specification of the debtor’s name and/or address needed for regulatory requirements is insufficient or missing. | |
| RR03 | Missing Creditor Name or Address | Specification of the creditor’s name and/or address needed for regulatory requirements is insufficient or missing. | |
| RR04 | Regulatory Reason | Regulatory Reason | |
| RR05 | Regulatory Information Invalid | Regulatory or Central Bank Reporting information missing, incomplete or invalid. | |
| RR06 | Tax Information Invalid | Tax information missing, incomplete or invalid. | |
| RR07 | Remittance Information Invalid | Remittance information structure does not comply with rules for payment type. | |
| RR08 | Remittance Information Truncated | Remittance information truncated to comply with rules for payment type. | |
| RR09 | Invalid Structured Creditor Reference | Structured creditor reference invalid or missing. | |
| RR10 | Invalid Character Set | Character set supplied not valid for the country and payment type. | |
| RR11 | Invalid Debtor Agent Service ID | Invalid or missing identification of a bank proprietary service. | |
| RR12 | Invalid Party ID | Invalid or missing identification required within a particular country or payment type. | |
| RUTA | Return Upon Unable To Apply | Return following investigation request and no remediation possible | |
| SL01 | Specific Service offered by Debtor Agent | Due to specific service offered by the Debtor Agent | |
| SL02 | Specific Service offered by Creditor Agent | Due to specific service offered by the Creditor Agent | |
| SL11 | Creditor not on Whitelist of Debtor | Whitelisting service offered by the Debtor Agent; Debtor has not included the Creditor on its “Whitelist” (yet). In the Whitelist the Debtor may list all allowed Creditors to debit Debtor bank account | |
| SL12 | Creditor on Blacklist of Debtor | Blacklisting service offered by the Debtor Agent; Debtor included the Creditor on his “Blacklist”. In the Blacklist the Debtor may list all Creditors not allowed to debit Debtor bank account | |
| SL13 | Maximum number of Direct Debit Transactions exceeded | Maximum number of Direct Debit Transactions exceeded | |
| SL14 | Maximum Direct Debit Transaction Amount exceeded | Due to Maximum allowed Direct Debit Transaction amount service offered by the Debtor Agent | |
| SP01 | Payment Stopped | Payment is stopped by account holder | |
| SP02 | Previously Stopped | Previously stopped by means of a stop payment advise | |
| TA01 | Transmisson Aborted | The transmission of the file was not successful – it had to be aborted (for technical reasons) | |
| TD01 | No Data Available | There is no data available (for download) | |
| TD02 | File Non Readable | The file cannot be read (e.g. unknown format) | |
| TD03 | Incorrect File Structure | The file format is incomplete or invalid | |
| TECH | Technical Problem | Cancellation requested following technical problems resulting in an erroneous transaction | |
| Use QBO Request for Payments | |||
| TM01 | Invalid Cut Off Time Formerly: CutOffTime |
Associated message, payment information block or transaction was received after agreed processing cut-off time. | |
| TS01 | Transmission Successful | The (technical) transmission of the file was successful. | |
| TS04 | Transfer To Sign By Hand | The order was transferred to pass by accompanying note signed by hand | |
| UPAY | Undue Payment | Payment has been made through another channel | |
| VR01 | Transaction data integrity validation error |
Transaction data has not been validated by the processor. |
|
| XD19 | Incorrect IBAN |
IBAN format is invalid. Issued if the country code is a valid ISO or SEPA country code but structure of IBAN or check digits is incorrect. |
|
| XD75 | Unauthorised element in the following combination |
There is an unauthorised element in the following combination. |
|
| XT13 | Incorrect file structure |
Transaction contains at least one unsupported field or at least one mandatory field is missing from the transaction. |
|
| XT27 | Incorrect BIC |
Transaction contains at least one element with a BIC that is not SEPA-reachable. |
|
| XT33 | Incorrect XML field |
The content of at least one XML element is not in the format required. The invalid XML field is indicated by the
error code. |
|
| XT43 | Incorrect type of direct debit |
Type of direct debit is incorrect. |
|
| XT53 | Verification of the creditor identifier failed |
Verification of creditor indentifiers in structure/checksum has failed. |
|
| XT73 | Invalid Country Code |
Two characters forming the country code do not constitute a valid ISO or SEPA country code. |
|
| XT74 | Invalid underlying original transaction |
Underlying original transaction is invalid. Further check is required. |
|
| XT75 | Invalid status of underlying original transaction |
Status of underlying original transaction is invalid. No further action is required. |
|
| XT77 | The originally instructed amount was not found or does not match the original transaction amount |
The originally instructed amount was not found or does not match the original transaction amount. |
|
| XT78 | Amount validation failed |
Transaction amount validation has failed. |
|
| XT79 | Debtor Agent is not permitted to receive direct debits |
Debtor agent is not permitted to receive direct debits. |
|
| XT80 | Creditor Agent is not permitted to send direct debits |
Creditor agent is not permitted to send direct debits. |
|
| XT85 | No Settlement Cycle Available |
Settlement cycles are not available. |
|
| XT90 | Invalid use of a Technical BIC |
Technical BIC usage is not valid. |
|
| XT99 | Direct debit rejected for other reasons |
Credit transfer was rejected for other reasons. |
|
| XX01 | Processing Cancelled |
Transaction processing has been cancelled by a customer. |
Request for Payment (RfP) ACH Return Code Reference
|