List of ISO 20022 "Request for Payment RfP" Return / Reject reason codes for 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:

1. 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.

2. 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.

3. 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.

4. 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.

5. 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.

6. 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.

7. Verify Payment Amount:

• For reject codes related to payment amount, verify that the specified amount is within acceptable limits and meets the transaction requirements.

8. 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.

9. Update Payment Reference:

• If the reject is due to an error with the payment reference or invoice number, update the information to ensure accuracy.

10. 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.

11. Correct Bank Account Information:

• For reject codes related to bank account information mismatches, verify and correct the bank account details to ensure accuracy.

12. 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.

13. 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.

14. 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.