ACH Return Codes: What R01, R10, and R29 Mean for Your Business
ACH return codes decoded for recurring billers: what each return means, which ones count toward Nacha limits, and what to do before you retry.

Photo: Pixabay
On this page 6 sections
- How ACH Returns Differ From Card Declines and Chargebacks
- The Most Common ACH Return Codes and What Triggers Them
- Return Deadlines: Why an R10 Can Arrive Weeks After Settlement
- Nacha Return Rate Thresholds and ACH Return Rate Limits
- When You Can Re-Present a Returned Payment
- Reducing Returns With Account Validation and Better Authorizations
Key takeaways
- R01 is a collections problem you can usually retry. R10 and R29 are compliance problems that count against you and need a new authorization before you debit again.
- A consumer can claim an unauthorized debit weeks after it settles, so don't treat a consumer ACH payment as final on settlement day.
- R29 returns from business customers often come from bank debit filters. Send your customer's AP team your exact Company ID and Company Name before the first debit.
- Track unauthorized returns separately from the rest, because that limit leaves the least room. Get the current Nacha and bank limits in writing.
ACH return codes are the short "R" codes a customer's bank attaches when it sends back an ACH debit you initiated, and each one tells you why the payment failed. R01 means the account didn't have enough money. A consumer who tells their bank they never authorized the debit produces an R10, and a business customer making the same claim produces an R29. You can usually retry an R01, because it's a collections problem. R10 and R29 are compliance problems: they count against you with your bank, and too many of them can cost you the ability to pull payments by ACH.
For a gym drafting monthly dues, a school running tuition plans or a wholesaler debiting net-30 invoices, the code on a return decides your next move. Some codes mean you should try again on a better day. Others mean you have to stop and get something new from the customer first.
How ACH Returns Differ From Card Declines and Chargebacks
A card payment gets approved or declined by the issuing bank in seconds, before you hand over anything. ACH works on a delay. You, or your processor, send a debit request in a batch through your bank, which the ACH system calls the ODFI (originating depository financial institution). The customer's bank, the RDFI, receives the request and decides afterward whether to honor it. Money can land in your account before you learn the debit failed, and then the return pulls it back out.
The contrast with chargebacks matters even more. When a cardholder disputes a charge, the card networks run a dispute process in which you can submit evidence and argue your case. An unauthorized ACH return gives you no comparable evidence-and-response step inside the ACH network. Once the customer's bank sends the debit back as unauthorized, your recourse sits outside the system. You go to the customer with the signed authorization and ask them to pay again with fresh consent. That is why the authorization you capture up front carries so much weight, and our guide to ACH authorization requirements, forms and proof covers what that record should contain.
The rules come from more than one place. Nacha, the organization that governs the ACH network, writes the return codes and the deadlines for sending returns, and it also sets return rate thresholds for originators. Separately, federal consumer protection law gives consumers rights when an electronic debit they didn't authorize hits their account. The fee you pay per returned item is your bank's or processor's pricing, not a Nacha rule. Treat everything legal in this article as general information and confirm the specifics for your business with a qualified professional.
The Most Common ACH Return Codes and What Triggers Them
Nacha defines dozens of Nacha return codes. A small group accounts for most of what recurring and online billers actually see:
| Code | What it means | Typical trigger | What to do |
|---|---|---|---|
| R01 | Insufficient funds | Debit hit before payday | Retry within Nacha's limits |
| R02 | Account closed | Customer switched banks | Get new account details |
| R03 | No account / unable to locate | Typo or fake number | Re-collect and validate |
| R04 | Invalid account number | Wrong format or digits | Re-collect and validate |
| R07 | Authorization revoked | Customer told bank to stop you | Stop; get new authorization |
| R08 | Payment stopped | Stop-payment on one debit | Contact customer before retrying |
| R09 | Uncollected funds | Deposit not yet available | Retry like an R01 |
| R10 | Consumer says not authorized | Unrecognized name, disputed cancellation | Stop; resolve directly |
| R11 | Debit didn't match the authorization | Wrong amount or date | Fix the error before resending |
| R16 | Account frozen | Legal or bank action | Collect another way |
| R20 | Non-transaction account | Savings account with limits | Ask for a checking account |
| R29 | Business says not authorized | Debit block or filter at their bank | Get your Company ID approved |
Official code descriptions get revised from time to time, so build your processes from the current list your bank or processor provides.
R01 Insufficient Funds Is Usually a Timing Problem
R01 insufficient funds returns tend to cluster around billing dates that don't line up with paydays. A martial arts studio that drafts every family's tuition on the first of the month collides with parents who get paid mid-month. Education and training providers with tuition payment plans can see R01s climb in the weeks before a term starts, when household budgets are tightest. These customers generally intend to pay, so the fix lives in your billing schedule and your retry timing.
R10 Unauthorized Often Means "I Don't Recognize This"
An R10 unauthorized return rarely means a stranger stole account numbers. In subscription and membership businesses, a frequent cause is a statement descriptor the customer doesn't recognize. Family plans add another: a spouse sees a debit for a membership someone else in the household signed up for. Then there are members who believe they canceled. A gym that only accepts cancellations in person or by certified letter sets up exactly this fight, because the frustrated member goes to their bank instead, and the bank returns the debit as unauthorized.
R29 Is the B2B Version, Often Caused by Debit Filters
Wholesalers and B2B service firms get R29s even from customers whose accounts payable teams agreed to the debit. Many business bank accounts carry ACH debit blocks or filters that reject debits from any company ID not on an approved list. The customer's bank returns the debit as unauthorized, and it counts against you even though nobody disputed the invoice. Before the first draft, send the customer's AP contact your exact Company ID and Company Name and ask them to add both to their filter.
Return Deadlines: Why an R10 Can Arrive Weeks After Settlement
Most returns, including R01s and account-data returns, have to come back within a short window measured in banking days after settlement. If that window passes without a return, those debits are generally safe.
Consumer unauthorized claims run on a much longer clock. When a consumer signs a written statement with their bank saying a debit wasn't authorized, the bank can return it as an R10 or a related unauthorized code within an extended window measured in weeks, not days. Business customers' unauthorized claims are handled differently and generally fall under the shorter timeline. Ask your ODFI for the exact current windows for each code you see.
That extended window should change how you treat consumer ACH money. A training company that grants full course access on a large first payment, or a membership business that ships an annual starter kit, is exposed until the consumer window closes. Consider holding back high-value deliverables, or taking the first payment by card. For the settlement side of the timeline, see our explainer on how long an ACH transfer takes.
Nacha Return Rate Thresholds and ACH Return Rate Limits
Nacha measures originators against separate ACH return rate limits, one for each category of return:
| Category | What counts | Example codes |
|---|---|---|
| Unauthorized | Debits the customer or their bank says weren't authorized | R10, R29 and related unauthorized codes |
| Administrative | Bad or dead account data | R02 through R04 |
| Overall | Every debit return, for any reason | Everything above, plus R01 |
Your bank can tell you exactly which codes fall in each category. Each rate is your returns in that category divided by the debit entries you originated over the same measurement period. Nacha sets the unauthorized threshold much lower than the overall one, so a handful of disputes can matter more than a pile of insufficient-funds returns.
Crossing a threshold draws scrutiny. Your bank may have to review your activity and ask you for a plan to bring the rate down, and an originator whose rates stay high can face enforcement under Nacha's rules. In practice, the pressure lands on you, and the most serious outcome is losing ACH origination. Your bank or processor agreement may also set internal limits tighter than Nacha's. Ask for the current numbers that apply to your account, and get them in writing.
Worked example (illustrative numbers only). Assume a fitness studio originates 1,200 membership debits over one quarter. During that quarter it receives five R10 returns, 14 administrative returns and 70 returns in total, most of them R01s.
| Category | Returns | Debits | Rate per 1,000 debits |
|---|---|---|---|
| Unauthorized | 5 | 1,200 | about 4.2 |
| Administrative | 14 | 1,200 | about 11.7 |
| Overall | 70 | 1,200 | about 58.3 |
Five disputed debits look trivial next to 70 total returns. But because the unauthorized limit has the least room, those five may be the figure that brings this studio closest to a bank review. Compare each rate with its own current threshold, never with each other. Card disputes work on the same logic, and our guide to calculating your chargeback ratio walks through the card version.
When You Can Re-Present a Returned Payment
Nacha's rules allow a debit returned for insufficient or uncollected funds (R01 or R09) to be re-presented, within limits. The limits govern how many times you can retry and how soon, and the rules specify how a retry has to be labeled. Get the current limits and labeling requirements from your ODFI before you build retry logic, because your processor's system has to match them.
Timing decides whether a retry works. Resubmitting the next morning usually fails the same way. Aim the retry at a likely payday instead: mid-month for a family paid twice a month, or the end of the week for hourly earners. Our article on smart retries and dunning for failed subscription payments covers scheduling and the customer messages that go with it.
Other returns can't be retried as they are:
- Bad account data (R02 through R04): Resending fails the same way. Collect new details and validate them first.
- Refusals by the customer or their bank (R07, R08, R10, R29): You need a new authorization before you debit that account again.
- Mismatches with the authorization (R11): Correct the amount or date, then ask your ODFI how to resend.
- Frozen accounts (R16): Collect some other way.
Never split a returned amount into smaller debits or relabel an entry to get around a return. Banks treat that as evading the return, and it will end your ACH access faster than the original returns would. If you want to charge a returned-payment fee, check your authorization terms and your state's law with a qualified professional before you do.
Reducing Returns With Account Validation and Better Authorizations
Administrative returns are the easiest to prevent, because they come from account numbers that were never good. Validating an account before the first debit is standard practice for online billers, and your ODFI may require it for debits authorized online, so ask. Instant verification through the customer's bank login confirms the account is open and belongs to the person paying. Micro-deposits take longer but work for customers who won't log in. Our guide to instant bank account verification before debiting compares the options.
Unauthorized returns need different fixes:
- Use a statement descriptor that matches the name on your storefront or door, not your legal entity name.
- Send a reminder before any debit that varies in amount and before every annual renewal.
- Make cancellation as easy as sign-up, and confirm each cancellation in writing.
- For B2B accounts, confirm debit-filter approval before the first draft.
The third fix is where most membership businesses lose ground. Our piece on subscription cancellation flows that save customers legally shows how to keep the save attempt without sending members to their bank. Gyms and studios face all four problems at once. Our guide to gym membership payment processing applies these fixes to both card and ACH dues, and MannyPay's payment options for gyms and fitness studios cover the card side of member billing.
Start with your own numbers this week. Pull the last quarter of returns and sort them by code. Calculate the unauthorized rate first, since that limit has the least room, then work out the other two. Ask your bank for the thresholds that apply to your account, in writing. If unauthorized returns keep coming from the same kind of customer and you're weighing a move to cards for them, compare online card payment options or request a free quote, and a MannyPay specialist will respond within one business day.
This article is for general educational purposes and is not legal, tax or financial advice. Card network rules and state laws change; confirm current requirements for your business.


