ACH return codes are the R-codes a receiving bank attaches when it sends an ACH entry back unpaid, such as R01 for insufficient funds or R02 for a closed account. Nacha publishes the full list in its Operating Rules. For a business collecting by ACH debit, the code says why the payment failed, how long the bank had to send it back, and whether trying again makes sense.
An ACH return code is the three-character reason, from R01 upward, that a receiving bank attaches to an ACH entry it sends back without posting. Nacha defines each code and sets the deadline for using it, so the code also tells the business that sent the payment what kind of problem it has.
The returning bank is the RDFI (receiving depository financial institution), which for a debit is your customer's bank. The return travels back through the network to your bank or processor, which passes the code to you. What follows covers the codes a business collecting payments meets most, grouped by what you should do next.
The return codes you are most likely to see
Titles and meanings are summarized from Nacha's published return reason code tables.
| Code | Nacha title | What it means | What to do |
|---|---|---|---|
| R01 | Insufficient Funds | The available balance doesn't cover the debit | Contact the customer; retry once funds are likely there |
| R02 | Account Closed | A previously active account has been closed | Get new account details and a new authorization; don't retry |
| R03 | No Account/Unable to Locate Account | The number is valid in form but doesn't match an open account or the named person | Confirm the details with the customer |
| R04 | Invalid Account Number Structure | The account number isn't valid in form | Usually a typo; correct it |
| R05 | Unauthorized Debit to Consumer Account Using Corporate SEC Code | A business-type (CCD or CTX) debit hit a personal account without the account holder's authorization | Get a consumer authorization and use the right entry code |
| R07 | Authorization Revoked by Customer | The customer withdrew the permission it gave you | Stop debiting; ask for another way to pay |
| R08 | Payment Stopped | The customer placed a stop payment on this debit | Talk to the customer before anything else |
| R09 | Uncollected Funds | The ledger balance covers it, but the available balance doesn't | Similar to R01; retry later |
| R10 | Customer Advises Originator Is Not Known and/or Is Not Authorized | The customer doesn't recognize you, or says you had no authorization | Check the name customers see; stop until resolved |
| R11 | Customer Advises Entry Not in Accordance with the Terms of the Authorization | Authorization exists, but the debit broke its terms, such as a wrong amount or an early date | Fix the error and confirm with the customer |
| R16 | Account Frozen/Entry Returned per OFAC Instruction | The account is restricted by the bank or by legal action, or OFAC instructed the return | Ask for another payment method |
| R20 | Non-Transaction Account | The account is one where transactions are prohibited or limited | Ask for a checking account |
| R29 | Corporate Customer Advises Not Authorized | A business customer says this debit wasn't authorized | Check your authorization; ask about debit blocks |
The table leaves out codes mostly used between banks, such as R06 (returned at the sending bank's request), and the technical codes for file and formatting errors, such as R17 and R26. If you see one of those, your processor should explain it.
What each group of codes tells you
Money problems: R01 and R09
With these, the customer's account and your authorization are both fine. The money just wasn't there. They are worth a phone call or a reminder, then another attempt, because the customer often still intends to pay. For recurring billing, a failed-payment follow-up routine is the subject of dunning.
Bad account data: R02, R03 and R04
Nacha calls these administrative returns. They mean the details you have are wrong or out of date, and resending the same entry will fail the same way. Fix the data first.
Authorization problems: R05, R07, R10, R11 and R29
Nacha treats these, with R51, as unauthorized returns. They are the ones that put your ability to originate ACH at risk, because Nacha caps how often they can happen. R10 deserves special attention: a long-standing customer who doesn't recognize the name on their statement will report your debit as unknown. Make sure the company name on your entries is the one customers know you by.
Account restrictions: R08, R16 and R20
The account can't take your debit, for reasons on the customer's side. You need a different account or a different payment method.
How long a bank has to return a debit
Nacha sets two windows. For most returns, including R01 through R04, the return must reach your bank by the opening of business on the second banking day after the settlement date. Nacha's guidance for Originators puts it in terms of entry codes: corporate codes carry the standard two-day right of return, and consumer codes carry an extended right of return of 60 days for unauthorized claims. For those extended returns, such as R05, the customer's bank needs a written statement from the customer.
Here is what that means for one debit that settles on Wednesday 2 December 2026:
- Standard return (for example R01 or R02): must be available to your bank by the opening of business on Friday 4 December.
- Consumer unauthorized return (for example R10): the 60th calendar day after settlement is Sunday 31 January 2027, so the return must be available by the opening of business on the next banking day, Monday 1 February 2027.
- Business unauthorized return (R29): falls within the standard two-day window, so by Friday 4 December.
The long tail is why consumer debits carry more risk than business debits, and why the type of account matters when you decide how to accept ACH payments for a given service.
The return rates Nacha watches
Nacha measures each Originator's returns against three levels, using debits over the preceding 60 days or two calendar months:
| Measure | Codes counted | Level |
|---|---|---|
| Unauthorized return rate | R05, R07, R10, R11, R29, R51 | 0.5% |
| Administrative return rate | R02, R03, R04 | 3.0% |
| Overall return rate | All debit returns, excluding RCK entries | 15.0% |
Say a home-security monitoring company bills 1,200 customers by ACH debit each month, so it sent 2,400 debits across September and October. These counts are hypothetical:
- Unauthorized returns: 9. Rate: 9 ÷ 2,400 = 0.375%. The limit allows 12 (2,400 × 0.5%), so three more R10s or R07s would take it to the line, and a 13th would cross it.
- Administrative returns: 41. Rate: 41 ÷ 2,400 = 1.7%, well under 3%.
- All returns, including the R01s: 160. Rate: 160 ÷ 2,400 = 6.7%, under 15%.
The unauthorized limit is the one with the least room, and it is enforced as a threshold. Going over the administrative or overall levels starts an inquiry by Nacha rather than an automatic violation. Fines are assessed to banks, which can pass them on to the business by contract; Nacha's Originator guidance says they can reach $500,000 a month for egregious violations.
Retrying a returned payment
Nacha calls a retry a reinitiation, and it limits it tightly. A returned entry can be reinitiated no more than two times. The retry must keep the same company name, company ID and amount as the original, and carry the description "RETRY PYMT" so the customer's bank knows what it is. Nacha's rules prohibit reinitiation outside the limited circumstances they allow, so ask your processor which return codes its retry feature covers.
In practice, a retry makes sense after R01 or R09 once you have reason to think the money is there. It makes no sense after R02, R03 or R04, where the account details are the problem. Debiting again after R07, R10 or R29 without settling the authorization question with the customer is the pattern the unauthorized return rate exists to catch.
Notifications of change are not returns
Sometimes the payment goes through, but the customer's bank sends a notification of change (NOC) with a C-code, saying something in your entry needs updating, such as a new account number. Nacha's guidance says you must, in most cases, make the change within six banking days or before your next entry, whichever is later. Treat an NOC as a free warning: ignore it and the next payment may come back as a return.
Preventing returns before they happen
- Validate new accounts. For online (WEB) debits, Nacha requires account validation on first use, for example with a prenote or a verification service. It is worth doing for other debits too.
- Match the entry code to the account. A CCD debit to a personal account invites an R05.
- Use a name customers recognize. R10 covers a customer who tells its bank it doesn't know who you are.
- Warn before you debit. A reminder a few days before a recurring debit gives a customer time to move money, which heads off R01s, and puts your name in front of them before it appears on their statement.
- Keep the authorization. Nacha puts the burden of proof on the Originator, and when a customer claims an unauthorized debit, the record is your answer.
Card payments have their own version of all this, the chargeback, which works quite differently. See what a chargeback is for that side, and ACH debit vs ACH credit for why pushed payments rarely come back at all.
Sources
- Nacha: ISO 20022 Guide to Mapping U.S. ACH Return Items and Notifications of Change (PDF, version 2.01, August 2023), Table 1, accessed 15 November 2026
- Nacha: ACH Risk Management Proposals 2023, Proposed Modifications to the Rules (PDF, 2 May 2023), Table of Return Reason Codes, accessed 15 November 2026
- Nacha: RMAG Originator Essentials (PDF, 2024), accessed 15 November 2026
- Nacha: ACH Network Risk and Enforcement Topics, accessed 15 November 2026
- Nacha: How to Calculate Unauthorized Return Rate (PDF), accessed 15 November 2026
- Nacha: Minor Rules Topics (reinitiation limited to two times), accessed 15 November 2026
- Nacha: Supplementing Fraud Detection Standards for WEB Debits, accessed 15 November 2026