What are ACH return rates and thresholds?

When an ACH entry cannot be posted, the RDFI sends it back as a return, carrying a reason code that explains why. Nacha monitors returns closely because high return rates are a reliable signal of fraud, weak authorization practices, or bad account data. For debit Originators, staying under Nacha’s return-rate thresholds is one of the most concrete, measurable compliance obligations there is — and one an auditor can check against hard numbers.

The three thresholds to know

Nacha enforces three distinct return-rate limits on debit Originators. Each is calculated over a rolling basis and each is measured against a different set of return reason codes.

• Unauthorized Entry Return Rate — must stay below 0.5%. It is calculated from returns for unauthorized or improper debits, using reason codes R05, R07, R10, R11, R29, and R51.
• Administrative Return Rate — a threshold of 3%, calculated from administrative returns for account errors: R02 (account closed), R03 (no account/unable to locate), and R04 (invalid account number).
• Overall Return Rate — a threshold of 15%, calculated across all debit return reason codes (with limited exclusions such as RCK entries).

(Threshold definitions and included reason codes can be refined between Rules editions — confirm the current figures and code lists in your edition.) The 0.5% unauthorized threshold is the most sensitive of the three, because unauthorized returns most directly indicate an authorization or fraud problem.

How the rates are calculated

Each rate is a simple ratio: the number of returns in the relevant category divided by the number of debit entries originated, measured over a defined period (commonly a rolling 60-day window for monitoring purposes). Because the denominator is your own volume, a low-volume Originator can cross a threshold on a small number of returns, while a high-volume Originator has more room to absorb them. This is exactly why trend monitoring matters more than any single month.

What happens if you exceed a threshold

Exceeding a threshold can trigger a Nacha inquiry through your ODFI, a requirement to research the cause, and a mandatory reduction plan to bring the rate back into line. Persistent or egregious breaches can lead to fines under the National System of Fines. In practice, your ODFI will usually act first, because it warrants your entries and carries the network liability — it may cap your volume, demand a corrective plan, or in serious cases terminate origination. An auditor will expect to see that you monitor all three rates and that you have a documented response when any of them climbs.

A worked example

Suppose an Originator sends 10,000 debits over a monitoring window and receives 60 unauthorized returns (R10 and R11). That is a 0.6% unauthorized return rate — over the 0.5% limit. Even though 60 out of 10,000 sounds small, it breaches the most sensitive threshold, and the Originator should expect its ODFI to require research into why those debits were returned as unauthorized, together with a plan to reduce the rate. Catching the upward trend a month earlier, while the rate was still 0.4%, would have avoided the breach entirely.