Skip to main content

What is ACH Return Code R29, and How Can You Resolve Issues Related to It?

ACH (Automated Clearing House) Return Code R29, also known as "Corporate Customer Advises Not Authorized," is a common error that arises during bank transaction processes.

This error indicates that the payer's bank has rejected the payment request because the account owner specifically instructed the bank to block this type of transaction. Below, we discuss the causes, resolution steps, and how to provide documentation when dealing with ACH Return Code R29.
​

Causes of ACH Return Code R29

R29 occurs due to the following reason:

  • The payer (account owner) notified their bank not to allow a specific transaction or similar transactions. This directive typically means that the transaction is not authorized from the payer's perspective.
    ​

  • The payer's business bank account has an ACH debit filter or debit block turned on, which rejects debits from any originator the account owner has not pre-approved. This is the most common cause, and it is not a dispute about the payment itself.

Resolving ACH Return Code R29 Issues

To address and resolve issues caused by R29, follow these steps:

  1. Communicate with the Payer: Reach out to the account owner to verify if and why they advised their bank not to authorize the transaction. Resolving discrepancies here can help clarify whether this was intentional or an error.
    ​

  2. Have the payer authorize the debit with their bank. If their account has a debit filter, they need to add the originator to their list of approved debits. Give them:
    - Company ID (originator ID): 0000022514
    - Company Name: your own business name, exactly as it appears on the payment. This is your statement descriptor if you have set one, otherwise your business name in Nickel.

    Important: The debit does not go out under the name "Nickel". Your customers see your business name, and your vendors see the vendor name on bill payments. If the payer whitelists "Nickel", the retry will be returned again. Give them the Company ID above together with the business name that appears on their statement.

  3. Retrying the Transaction: If the payer confirms the transaction is authorized, request that they contact their bank to lift the block. Then, retry the transaction once the bank removes the restriction.

Providing Evidence of a Failed ACH Transaction

If you need to prove that an ACH payment failed due to an R29 return code, you can utilize documentation from your Nickel support message. Look for the error message indicating that the payment failed due to the ACH R29 return code. This documented message reflects the ACH return reason, which can be shared directly with the payer as evidence.

Additional Tips for Handling ACH Payment Issues

  • Maintain Clear Communication: Always inform the payer in case of failed transactions to avoid confusion.
    ​

  • Document All Failures: Keep a record of return codes and failure reasons for reference and resolution.
    ​

  • Resolve them promptly. Repeated ACH returns on the account that funds your payments, including R29, can temporarily affect your eligibility for expedited vendor payouts. Clearing the block with your bank keeps that from becoming an issue.
    ​

  • Understand ACH Processes: Become familiar with ACH codes and their meanings to address issues more swiftly.

By identifying the root cause of the R29 return code and using the appropriate documentation as evidence, you can effectively manage these situations and resolve payment discrepancies efficiently.
​

Need help?

If you have questions, please chat with our team via the Help Center when you login to the platform.

Did this answer your question?