ACH return codes list: what each R code means and what to do

ACH return codes are the short codes, R01, R02 and so on, that a bank attaches to an ACH payment it sends back unpaid. Nacha's rules call them return reason codes (Nacha), and each one tells the business that sent the payment what went wrong: no money in the account, no account at all, an account number that doesn't work, or an account holder who says the debit wasn't allowed.

If you collect by ACH debit or eCheck, the code decides your next move. Some returns are a timing problem that a phone call fixes. Some need new bank details. A few mean you should stop debiting that account today. Below you'll find the codes worth knowing, what each means and what to do about it, how long banks have to send returns, and the return rates Nacha watches.

Return codes come from the Nacha Operating Rules, so they mean the same thing whichever bank or processor handles your debits. Clearo offers ACH payment processing; this guide sticks to the codes themselves. For how ACH debits move in the first place, see our ACH payments guide, and for the customer-facing side, our guide to eChecks. We checked every rule cited here in October 2026.

What are ACH return codes?

ACH return codes are the standard reasons a receiving bank gives when it sends an ACH entry back. Say you pull a monthly debit from a customer's account. Their bank (the RDFI, in Nacha's shorthand) can't or won't post it, so it returns the entry through the network with a code attached. Your bank passes the return on to you with the amount, the date and the customer's details, and takes the money back out of your account if the debit had already settled.

Nacha writes the rules that financial institutions follow on the ACH network (Nacha), so the codes mean the same thing at every bank. An R03 from a small credit union says exactly what an R03 from a national bank says. That consistency lets you set one response per code instead of treating every failed payment as a mystery.

A return isn't a decline. A card decline happens in seconds, before the sale is complete, and our guide to credit card decline codes covers those. An ACH return shows up after the payment has gone out, often after the money has landed in your account, which is why it stings more.

ACH return codes list: common R codes and what to do next

This list covers the codes a business collecting by debit should know first. Nacha's full table is longer, so ask your bank or ACH provider for the complete version it uses in its reports.

Where the meanings come from: R01, R09 and R20 from Nacha's micro-entry return chart, R07, R10, R11 and R29 from its rule on differentiating unauthorized return reasons, and R16 from its rule page on a new sanctions return code. R02, R03 and R04 come from a 2009 ACH special edition of the PFC Journal, published by the Treasury's Bureau of the Fiscal Service, and the R08, R09 and R20 titles from the Federal Reserve's FedGlobal ACH origination manual, dated August 3, 2026.

How long does a bank have to return an ACH payment?

Two banking days, for most returns. Under Nacha's rules, two days is the standard return timeframe, and longer windows exist only for specific cases (Nacha). The biggest exception is a debit the customer says they never authorized.

Consumers can return an unauthorized debit for up to 60 days, under what Nacha calls an extended right of return (Nacha), and it applies that 60-day window to both R10 and R11 (Nacha). Business accounts get no extension. Their bank has 2 banking days to send back a debit the company calls unauthorized (Nacha). These deadlines don't change from state to state, because Nacha's rules apply across the United States.

Here's how the dates play out. Say a debit settles on Thursday, October 22, 2026. A return for insufficient funds or a closed account would be due over Friday, October 23, and Monday, October 26, because Saturday and Sunday aren't banking days. If the account belongs to a business and the owner calls the debit unauthorized, the same two days apply. If it belongs to a consumer, an R10 could still show up in the second half of December.

Federal Reserve holidays stretch these windows too, since they aren't banking days either. The Federal Reserve Financial Services holiday schedule lists them; Columbus Day on Monday, October 12, 2026, is one.

Which return codes count toward Nacha's return-rate limits?

Nacha watches three return rates for each business that sends debits: unauthorized returns, administrative returns and all returns combined. Each has its own codes and its own line.

Nacha's how-to on calculating the unauthorized return rate lists the six unauthorized codes and sets the measuring period: a rolling 60 days, or two calendar months. The 0.5% threshold is in its risk and enforcement rules. The administrative codes and the 3.0% and 15.0% levels come from its network quality fact sheet, which says crossing either of those two levels doesn't break the rules by itself but can lead to an inquiry.

Here's how fast the unauthorized rate moves. A pest control company in Tampa debits 450 customers a month for service plans, so 900 debits over two months. In that window:

• 4 come back as R07 or R10: 4 ÷ 900 = 0.44%, just under the 0.5% line.
• 18 come back as R03 or R04 after typos on new sign-ups: 2.00%, under the 3.0% level.
• 36 come back as R01. Counting the others, that's 58 returns, or 6.44%, well under 15.0%.

A fifth unauthorized return makes it 5 ÷ 900 = 0.56%, and the company is over. At 900 debits, 0.5% works out to 4.5 returns, so the margin is a single unhappy customer.

What keeps the number down is dull work: authorizations customers remember agreeing to, a business name that matches what they see on their bank statement, a heads-up before every debit, and cancellations handled the day they arrive. Our page for home services businesses covers the card side of service plans.

What should you do after an ACH return?

Read the code first, then sort it into one of four groups, because each group calls for a different response.

Money problems: R01 and R09

The account was short when the debit arrived. Contact the customer before trying again and agree on a date, ideally after their payday. Keep count if you reinitiate, because Nacha's rules cap reinitiation of a returned entry at two times (Nacha). Firing the same debit at an empty account on back-to-back days burns your retries and can cost a return fee each time.

Account data problems: R02, R03 and R04

Something about the account details is wrong. Ask the customer to confirm the numbers, get a new authorization if the account itself changed, and validate the new number before the next debit. For debits authorized online, Nacha's rules already require that validation the first time you use a number and when it changes (Nacha). The minimum standard is confirming the account is open and able to receive ACH entries (Nacha).

Permission problems: R07, R08, R10, R11 and R29

Stop debiting the account today. Pull the authorization and check it against the return: the amount, the date, the account and the business name the customer would have seen. Then talk to the customer, and don't send the debit again unless they authorize it again.

Handle R10 with care. Nacha has noted that R10 is often the code used when someone falsely claims that a debit they authorized wasn't (Nacha). Your authorization record is your evidence, so make sure you can produce it quickly.

R11 is the exception in this group. The customer did authorize you, but something in the entry was off, such as the amount or the date. Nacha lets you correct the error and send the entry again without a new authorization, as long as you do it within 60 days of the R11's settlement date (Nacha).

Accounts you can't debit: R16 and R20

The account is frozen, or it isn't the kind that takes ACH debits. Ask for another account or another way to pay. A card on file is often the quickest fix, and our recurring billing guide covers setting one up.

How can you cut ACH returns?

Returns fall when better account data goes in, permission is clear up front, and a customer who wants out gets out fast.

1. Validate every new account before the first debit, including ones set up on paper or over the phone.
2. Write the authorization so a customer would recognize it months later: your business name as it shows on their statement, the amount or how it's set, the dates, and how to cancel.
3. Keep proof. For online authorizations, Nacha's WEB guidance says to hold on to the authorization itself plus a record of how you linked it to the customer (Nacha).
4. Give notice when amounts vary. Under Regulation E, a consumer whose debit will change from the last one, or from the amount they authorized, gets written word of the new amount and date 10 days or more in advance, unless they signed up for a range (CFPB). A short reminder before every debit helps even when the law doesn't call for one.
5. Act on stop requests the same day. When a customer asks you to stop, cancel the debit in your system right away. Otherwise it goes out and comes back as an R07, which counts toward your unauthorized rate, or an R08, which still counts toward the overall one.
6. Debit under a name customers know. If your legal name and your brand differ, use the one they'd recognize.
7. Check all three return rates every month, not when your bank calls.
8. Offer a card to customers whose debits keep coming back R01. Clearo's virtual terminal handles recurring card billing and payment links for exactly that.

How do ACH returns compare with card declines and chargebacks?

They hit at different points in a payment's life. A card decline comes before the sale, an ACH return usually comes within days of settlement, and a card chargeback can come months later.

For a sense of how long card disputes can run, Mastercard's chargeback guide lets a cardholder dispute some services as long as 120 calendar days after they ended, within an outer limit of 540 days (Mastercard). Nacha's unauthorized return rate does for ACH roughly what a chargeback ratio does for cards: it's a number that gets watched, and a high one brings questions. Our guide to chargeback reason codes covers the card side's codes.

Next step

If you'd like to talk about running your ACH debits through Clearo, contact us and we'll quote it for your business. For the card half of how customers pay you, send a recent merchant statement our way. The free statement review breaks your card costs down by card type, so you can weigh which customers stay on ACH and which get a card option. We can also set up recurring card billing and payment links for customers whose debits keep coming back.