The ACH Return Rate Threshold That Can Flag an Account Before Visa Does · Midcore Operations
Midcore Operations
Managed Payments Operations

The ACH Return Rate Threshold That Can Flag an Account Before Visa Does

Nacha sets a hard 0.5 percent unauthorized return rate threshold on ACH debits, measured every 60 days, completely independent of a card network ratio.

Published
15 November 2026
Reading time
10 min read
Author
Managed Payments Operations practice
Topic
Managed Payments Operations
Key takeaways
  • Nacha's ODFI Return Rate Reporting Rule sets a hard unauthorized return rate threshold of 0.5 percent on ACH debits, calculated over a rolling 60 day or two calendar month window. Exceeding it is a direct rule violation, not just a warning sign, and it runs entirely independent of any card network ratio.
  • Nacha separately defines two Return Rate Levels, 3.0 percent for administrative or account data errors and 15.0 percent for all debit returns combined, that trigger a preliminary inquiry rather than an automatic violation. Treating a Level the same as the Threshold, or the reverse, misreads how Nacha's own enforcement process actually works.
  • The originating bank, called the ODFI, is the party Nacha's rule makes responsible for continuously monitoring its originators' and third party senders' return rates, the same liability structure that puts an acquirer on the hook for a merchant's card activity under Visa's rules.
  • A merchant account processing both cards and ACH debits can be clean on its Visa VAMP ratio and still be sitting on an unauthorized ACH return rate well past 0.5 percent, because the two numbers measure entirely different transaction types against entirely different rulebooks.

The ACH return rate threshold that can flag a merchant account before Visa ever does is set by Nacha, not by any card network, and it runs on its own completely separate rulebook. Nacha’s ODFI Return Rate Reporting Rule sets a hard 0.5 percent threshold on unauthorized ACH debit returns, recalculated every 60 days, and crossing it is treated as a rule violation in its own right. A merchant account that looks clean on every card network ratio can still be sitting well past that line, because nothing about a card-based monitoring program ever looks at ACH activity at all.

Why this threshold exists, and why it is separate from anything Visa does

Nacha governs the ACH Network, the rail that moves direct debits and direct deposits between bank accounts rather than through card rails at all. Nacha’s own guidance on calculating the unauthorized return rate states plainly that the ODFI Return Rate Reporting Rule exists to improve ACH Network quality by reducing the incidence of exceptions, returned entries, and the associated financial and reputational costs. Originating Depository Financial Institutions, the banks that originate ACH debits on behalf of a merchant or a platform, are made responsible for continuously monitoring the return rates of their originators and third party senders.

That sentence describes a liability structure that should sound familiar to anyone who has read how Visa assigns responsibility for a merchant’s card activity. The ODFI, not the merchant, is the party Nacha holds accountable for keeping return rates under control. The merchant has no direct relationship with Nacha any more than a card-accepting merchant has a direct relationship with Visa. The bank originating the ACH debits carries that exposure, which is exactly why an ODFI, or a payments platform originating ACH debits through one, needs its own monitoring discipline for this specific number rather than assuming a card-focused risk program already covers it.

The actual calculation, worked through

Nacha’s calculation guide spells out exactly how the 0.5 percent threshold gets measured, and the specificity matters because it is easy to calculate this wrong. The unauthorized return rate is the number of debits returned for a specific set of return reason codes divided by the number of debits originated, measured over the preceding 60 days or two calendar months. The return reason codes that count as unauthorized are R05, R07, R10, R11, R29, and R51, each representing a variation on the same underlying claim: the customer says the debit was never authorized, or that an authorization that once existed was revoked.

Nacha’s own worked example in that guide uses a two-month window to make the arithmetic concrete: 300 returned debits in the first month plus 200 in the second, against 60,000 originated debits in the first month plus 40,000 in the second, for a total of 500 returns against 100,000 originated debits. That produces exactly a 0.5 percent rate, sitting right at the line. The calculation is not a rolling daily average or a simple current-month snapshot. It is a specific two-month lookback, recalculated continuously, which means a return spike from several weeks ago can still be actively pulling an account’s current rate toward the threshold even if the most recent days have looked clean.

The two numbers that are not actually thresholds, even though they sound like them

Nacha’s framework includes two more figures that get described in industry commentary as thresholds, and that imprecision causes real confusion about how exposed an account actually is. Nacha’s own ACH Network Risk and Enforcement Topics page is explicit that these are Return Rate Levels, not thresholds, and that the distinction is not cosmetic.

The first Level covers administrative and account data errors specifically, return reason codes R02, R03, and R04, set at 3.0 percent. The second Level covers all debit returns combined, for any reason, excluding RCK entries, set at 15.0 percent. Nacha states directly that crossing either Level does not automatically count as a rules violation. Instead, it is “considered a starting point for a review of the Originator’s or Third-Party Sender’s origination activity to determine if a reduction is warranted.” The inquiry process that follows does not automatically trigger enforcement. Nacha even contextualizes the 15.0 percent figure against history, noting it sits roughly ten and a half times higher than the overall industry return rate average Nacha measured in 2013, and the 3.0 percent administrative figure sits more than nine times higher than that same era’s industry average for account data error returns.

The 0.5 percent unauthorized return rate is built differently on purpose. Nacha’s materials draw the contrast directly: a Threshold is a hard rule, and exceeding it is itself a violation that can lead to enforcement through the originating bank, with no separate inquiry step required first. A monitoring program that treats the 15.0 percent overall Level as the real danger line, because it is the biggest number on the page, is watching the wrong metric. An account can sit safely under 15.0 percent overall returns for any reason while still blowing through the 0.5 percent unauthorized threshold on its own, because the unauthorized category is a small slice of total returns measured against a line set roughly thirty times stricter.

Why a card-clean account can still have an ACH problem

A merchant or a platform running both card and ACH payment rails typically has two completely separate monitoring questions to answer, and a program built only around card network ratios answers just one of them. A card-not-present merchant’s Visa VAMP ratio tracks fraud and disputes against settled card transactions, calculated and enforced entirely inside Visa’s own rulebook. Nothing about an ACH debit, a different transaction type moving through a different network under a different set of rules, shows up in that calculation at all.

This means the two numbers can diverge sharply without either one catching the other. A subscription business processing recurring ACH debits for a membership fee can have a spotless card-side risk profile, no meaningful card fraud, low chargebacks, while its ACH unauthorized return rate climbs past 0.5 percent because its authorization language, timing, or renewal notice practices are generating customer disputes that get coded as unauthorized returns rather than card chargebacks. A monitoring program that reports “clean” based on the card metrics alone has not actually confirmed the account is healthy. It has confirmed one specific number is healthy, while leaving a separate, independently enforced number completely unwatched.

A concrete example: the recurring-billing platform that only watched one number

Picture a subscription fitness platform that added ACH as a lower-cost alternative to card payments for its annual memberships, routing those debits through its processor’s ODFI relationship. The platform’s risk team, built around card payments from the company’s early years, tracks chargeback and fraud ratios closely and reports a clean dashboard every month. Nobody on that team is specifically watching the ACH unauthorized return rate, because nobody built that metric into the original risk dashboard when ACH was added as an afterthought feature.

Eight months in, a wave of members who forgot they had agreed to annual auto-renewal start disputing the renewal charge with their banks as unauthorized, generating R10 returns at a rate that climbs past 0.5 percent over a two-month window. The platform’s ODFI gets notified first, because the rule makes the ODFI responsible for catching this, not the platform. By the time the platform’s own team hears about it, the account is already past the threshold and the bank is asking hard questions about the renewal notice language, the same conversation a card-side team would recognize instantly from a chargeback inquiry, just arriving through a completely different channel the team never built a watch for.

What an actual monitoring program needs to track separately

A merchant account management process built only around card network metrics is missing half the picture for any portfolio that touches ACH at all. The fix is not complicated, but it does require treating the ACH return rate as its own tracked number rather than assuming a healthy card ratio implies a healthy ACH rate by association. That means calculating the unauthorized return rate on the specific 60 day rolling window Nacha actually uses, watching the R05, R07, R10, R11, R29, and R51 return codes specifically rather than all returns generically, and treating a climb toward 0.5 percent with the same urgency a card program gives an approaching VAMP threshold, because the enforcement mechanism on the other side is just as real.

It also means understanding that the 3.0 percent and 15.0 percent Levels are not false alarms to ignore, even though Nacha itself says they are not automatic violations. A rising Level is the signal that arrives before the harder 0.5 percent threshold does, in the same way a portfolio manager watches an approaching VAMP ratio before an account actually crosses into Excessive Merchant status. Reading a Level correctly, as an early inquiry trigger rather than either a non-event or an automatic violation, is exactly the distinction a program built from commentary rather than Nacha’s own rule language tends to get wrong.

Building a monitoring program that actually tracks ACH return rates with this level of precision, alongside the card network ratios most teams already watch, is exactly the discipline behind Midcore’s merchant management practice. Where the underlying driver is unauthorized claims specifically, whether they arrive as ACH returns or card disputes, fraud and chargeback prevention work is where the authorization language and notice practices that actually cause them get fixed. And once a return or a dispute has already been filed, dispute management is where that individual case gets resolved before it adds to the next 60 day calculation.

Frequently Asked Questions

What is Nacha’s unauthorized return rate threshold, specifically?

It is 0.5 percent, set by Nacha’s ODFI Return Rate Reporting Rule. It is calculated as the number of debits returned for specific unauthorized return reason codes, R05, R07, R10, R11, R29, and R51, divided by the number of debits originated, measured over the preceding 60 days or two calendar months. Nacha calls this a threshold specifically because exceeding it is treated as a direct rule violation, not just a flag for review.

What is the difference between a Nacha Return Rate Level and a Return Rate Threshold?

A Threshold, like the 0.5 percent unauthorized return rate, is a hard line. Crossing it is itself a rule violation that can lead to enforcement action through the originating bank. A Level, like the 3.0 percent administrative return rate or the 15.0 percent overall return rate, triggers a preliminary inquiry process instead. Nacha is explicit that crossing a Level does not automatically count as a rules violation. It is a starting point for a review of why the return rate is high, not an automatic penalty.

Can a merchant pass every card network risk check and still have an ACH problem?

Yes, because the two systems measure entirely different things. A card network ratio like Visa’s VAMP ratio tracks card-not-present fraud and disputes against settled card transactions. Nacha’s return rate thresholds and levels track ACH debit returns against ACH debits originated, under a completely separate rulebook enforced by a completely separate network. A merchant running clean on one can be running hot on the other, and a monitoring process that only watches card ratios will never see it.

Sources: Nacha, How to Calculate Unauthorized Return Rate and Nacha, ACH Network Risk and Enforcement Topics.

Managed Payments Operations practiceMidcore Operations · 15 November 2026
All insights
Free consultation

Get your free Assess

Tell us what is happening. We reply within one business day with a US-based practice lead, not a salesperson.

  1. 01Within 1 business dayA US-based practice lead replies and books a 30 minute call.
  2. 02On the callWe map the problem, the volume, the partners, and the constraints.
  3. 03After the callYou get a written read of one to three pages, yours to keep.
  • Handled under NDA
  • Written, not a slide deck
  • No obligation to continue

No obligation. We will tell you if you do not need us.

Before you go

Take the written read with you

Every engagement opens with an Assess: a written read of what is happening, what it costs, and what to do about it. It is quoted on its own and you can stop after it.

+1 (786) 619-0152