What are ACH payment returns?

An ACH payment return occurs when a receiving bank sends a transaction back to the originating bank because it cannot be completed as submitted. Returns are a normal and expected part of ACH processing. They communicate failure at the account level, such as insufficient funds or a closed account, and give the originator the information needed to resolve the issue.

Each return carries a standardized reason code, known as an R-code, that identifies why the payment was returned. NACHA maintains 85 active return codes and prescribes specific rules for how each one must be handled, including the timeframe within which the return must be transmitted.

How ACH returns work

When an ACH payment is initiated, the originating depository financial institution (ODFI) submits the transaction to the ACH network. The receiving depository financial institution (RDFI) processes the entry against the recipient's account. If the RDFI cannot complete the transaction, it sends a return entry back to the ODFI, which then notifies the originator.

The return entry includes:

• The original transaction details
• The R-code identifying the reason for the return
• The settlement date of the original entry

The ODFI passes the return information to the originator, who is then responsible for determining next steps. Depending on the return code, next steps may include correcting account information, contacting the customer, or ceasing future debits entirely.

Return timeframes

NACHA sets specific timeframes within which returns must be transmitted. Most returns must be sent within two banking days of the settlement date of the original entry. Missing the return window means the RDFI loses its right to return the entry and becomes liable for the funds.

A significant exception applies to unauthorized consumer debits. If a consumer claims a debit was unauthorized, they have 60 calendar days from the settlement date to dispute it. This extended window reflects the consumer protection orientation of NACHA rules. For corporate unauthorized returns using the CCD SEC code, the standard two banking day window applies.

Same Day ACH returns follow the same R-code framework as standard ACH returns but are processed within the same-day settlement windows rather than over multiple days.

Most common ACH return codes

A small number of return codes account for the majority of returns in practice. The most frequently encountered include:

• R01: Insufficient funds. The account exists but does not have enough money to cover the debit
• R02: Account closed. The account existed at one point but has since been closed
• R03: No account or unable to locate account. The account number does not correspond to an open account at the RDFI
• R04: Invalid account number structure. The account number format is incorrect
• R07: Authorization revoked by customer. The account holder has revoked the debit authorization
• R10: Customer advises not authorized. The account holder claims the debit was not authorized

For a full breakdown of all 85 codes and how to resolve each one, see the ACH return codes glossary entry.

NACHA return rate thresholds

NACHA monitors return rates for all ACH originators and enforces thresholds that originators must stay within. Exceeding these thresholds is a compliance violation that can result in the ODFI restricting or terminating the originator's ACH privileges.

The three thresholds are:

• Overall return rate: Must remain below 15% of originated debit entries
• Administrative return rate: Returns for R02, R03, and R04 combined must remain below 3%. These codes indicate bad account data, which is largely preventable through account validation
• Unauthorized return rate: Returns for R05, R07, R10, R29, and R51 combined must remain below 0.5%. These codes indicate the originator debited accounts without proper authorization

The unauthorized threshold is the most consequential. A 0.5% limit leaves very little room for error, and exceeding it signals to NACHA and the ODFI that the originator may have authorization or fraud problems that need to be addressed.

Returns vs. reversals vs. NOCs

These three ACH mechanisms are related but distinct, and the terms are often confused.

• A return is initiated by the RDFI when it cannot process a received entry. The money moves back to the originator.
• A reversal is initiated by the originator when it discovers it sent an incorrect entry, such as a wrong amount or wrong account number. The originator sends a correcting entry to undo the original transaction. NACHA rules require reversals to be initiated within five banking days of the original settlement date and require the originator to notify the affected party.
• A Notification of Change (NOC) is sent by the RDFI when account information has changed but the transaction was still processed. Rather than returning the entry, the RDFI sends a zero-dollar notification telling the originator what the correct information should be. The originator must update its records within six banking days of receiving the NOC.

Operational implications of ACH returns

For payment platforms and businesses originating high volumes of ACH transactions, return management is an ongoing operational function rather than an exception-handling task.

Returns affect payment reconciliation directly. A payment that was recorded as sent and settled needs to be reversed in the books when a return is received. The timing difference between the original settlement and the return, which can be up to two banking days, means that funds may have already been recognized or deployed before the return arrives. During the return period, the in-transit funds sit in a clearing account until the return is processed and reconciled.

Monitoring return rates by code is also important for fraud detection. A spike in R07 or R10 returns, indicating revoked or unauthorized authorizations, can signal that an originator's onboarding or authorization processes have been compromised. Acting on these signals quickly, before return rates breach NACHA thresholds, is significantly less costly than remediation after an enforcement action.

Pre-transaction account validation, through methods like ACH prenotes or micro-deposit verification, reduces administrative returns by confirming that account details are valid before live payments are originated. This is the most direct way to keep R02, R03, and R04 return rates well below the 3% administrative threshold.