What are ACH return codes?

ACH return codes are standardized identifiers issued under the NACHA Operating Rules that specify why an ACH payment was returned to the originating bank. Each code begins with "R" followed by two digits, for example R01 for insufficient funds or R02 for a closed account. There are currently 85 active return codes, numbered R01 through R85.

When an ACH entry cannot be completed, the Receiving Depository Financial Institution (RDFI) transmits a return entry to its ACH operator with the relevant code. The Originating Depository Financial Institution (ODFI) then passes the return back to the business or platform that initiated the payment. The ACH Network processed 35.2 billion payments valued at $93 trillion (USD) in 2025, making return code handling a core operational requirement for any fintech or PSP running USD payment flows.

What do the most common ACH return codes mean?

Most ACH return volume is concentrated in a small number of codes. The ones below account for the majority of returns a fintech processing ACH will encounter.

• R01 – Insufficient funds: The receiver's account lacks the funds to cover the debit. The most frequent return code across the network. May be retried after allowing time for account funding.
• R02 – Account closed: The account existed but has been closed by the account holder or the institution. Retrying without updating the account data will generate another return.
• R03 –  No account / unable to locate account: The account number does not match any account at the receiving institution. Indicates stale or incorrect account data.
• R04 –  Invalid account number structure: The account number format is invalid. Typically caught before settlement and requires correction before resubmission.
• R07 –  Authorization revoked: The consumer has revoked the authorization for the debit. The RDFI has up to 60 calendar days from settlement to return the entry.
• R10 – Customer advises unauthorized: The receiver states they did not authorize the transaction. Also carries a 60-day return window, creating a post-settlement clawback exposure for originators.
• R11 – Entry not in accordance with terms: Used when a payment was received for the wrong amount or on the wrong date. Updated by NACHA in 2021 to reflect this more specific purpose.
• R16 – Account frozen: The account has been frozen due to legal action or RDFI account action. As of a recent NACHA rule update, R16 is now distinct from sanctions-related returns, which use the new R90 code.
• R29 –  Corporate customer advises not authorized: The non-consumer equivalent of R10, applicable to business accounts disputing authorization.

How Nacha categorizes return codes

Nacha groups return codes into three categories for monitoring and enforcement purposes. Each category carries its own return rate threshold, measured against total debit entry volume.

The three categories are administrative returns, unauthorized returns, and overall returns. Understanding which category a return falls into matters because breaching a threshold triggers escalating consequences under Nacha’s risk and enforcement framework, up to and including suspension of ACH origination rights.

Administrative returns

Administrative returns cover entries returned due to account data errors: R02 (Account Closed), R03 (No Account), and R04 (Invalid Account Number Structure). The threshold for this category is 3%. High administrative return rates typically signal that account data collection or verification processes need improvement. Pre-payment account validation, which confirms an account exists and is open before initiating an entry, directly reduces R02 and R03 exposure.

Unauthorized returns

Unauthorized returns cover entries returned because the receiver disputes authorization. The codes in this category are R05, R07, R10, R11, R29, and R51, and the threshold is 0.5%. The 60-day return window on consumer unauthorized codes means a payment that appeared to settle successfully can be clawed back months later. Platforms disbursing funds to consumer accounts need to account for this exposure window in their risk models.

Overall return rate

The overall return rate applies to all debit entries returned for any reason, excluding RCK entries. Exceeding a 15% overall return rate triggers Nacha monitoring and can result in fines or removal from the ACH network.

ACH return codes vs. notices of change

A related but distinct category is the Notice of Change (NOC). An NOC is not a return: the RDFI settles the payment and sends a correction code alongside it, notifying the originator that account information has changed. Common NOC codes include C01 (incorrect account number) and C02 (incorrect routing number). Under Nacha rules, originators receiving an NOC must update the account data within six banking days, or before initiating the next entry to that account, whichever is later.

Why ACH return codes matter for fintechs

For fintechs and PSPs running ACH pay-ins or payouts, return code management has direct implications for reconciliation, compliance, and counterparty risk. Key operational considerations include:

• Retry logic: R01 may warrant a retry. R02 and R03 require account re-verification first – retrying without correcting the data inflates administrative return rates toward the 3% threshold.
• Return monitoring: Nacha thresholds apply at the originator level. A platform acting as a third-party sender is responsible for the return rates of the businesses it serves, not just its own payments.
• 60-day exposure window: Consumer unauthorized return codes carry a 60-day clawback window from settlement date. Risk models for consumer-facing ACH debits need to account for this.
• Faster returns: A 2025 NACHA bulletin encouraged RDFIs to use same-day processing windows for returns, noting the Same Day Entry fee does not apply to return entries. Faster returns mean originators receive actionable information sooner.

For a broader overview of how ACH fits into USD payment infrastructure, see our guide to understanding ACH payments, and our explainer on electronic funds transfers for context on how ACH sits within the wider US payments landscape. For fintechs managing return data across multiple rails, see our guide to payment reconciliation.