What is ACH Return Code R01? Insufficient Funds Explained

Roughly three out of every four ACH returns in the United States come back for the same unglamorous reason: the money wasn't there. Plaid's own product documentation puts insufficient-funds returns at more than 75% of all returns, and the three characters stamped on nearly all of them are R01. It arrives quietly, in a batch file, two banking days after you already recorded the payment as collected. By then you may have shipped the product, unlocked the software, or sent the technician.

The most common failure on a network that moved $93 trillion last year

Nacha reported 35.2 billion ACH Network payments in 2025, worth $93 trillion, plus another 6.9 billion "on-us" payments that never touch an ACH Operator because the sending and receiving bank are the same institution. Add those together and total 2025 ACH volume was 42.1 billion payments. The network averaged 141 million transactions a day, and in November 2025 it set a daily record of 151 million. December 2025 produced the highest monthly volume ever recorded at 3.22 billion payments. Same Day ACH grew 16.7% to 1.4 billion payments carrying $3.9 trillion. Against numbers that size, even a return rate that looks tolerable in a dashboard translates into a very large pile of failed debits.

ACH debit is cheap, which is precisely why R01 hurts. The Federal Reserve charges originating banks $0.0035 per forward ACH item under the FedACH fee schedule effective January 1, 2026. Stripe charges merchants 0.8% capped at $5, so a $2,400 invoice costs five dollars to collect instead of the roughly $70 a card would take. That arithmetic is the entire argument for bank debit. It also collapses fast when returns show up, because Stripe charges $4 for a failed ACH Direct Debit and Chase charges $5 per return. A gym billing $19 memberships against a 9% failure rate is not saving money on ACH. It's donating it.

Here's the part worth sitting with: R01 is not a fraud signal. It's a liquidity and timing signal, and the customer is usually paying too. Bankrate's 2025 Checking Account and ATM Fee Study found the average overdraft fee slipped 1% to $26.77 and the average NSF fee fell for a fourth straight year to a record low of $16.82, though 61% of accounts still charge one. American consumers paid about $12.1 billion in combined overdraft and NSF fees in 2024. When your debit bounces, there's a decent chance the person on the other end just lost twenty-seven dollars because of it, and that shapes how you should write the follow-up email.

What R01 actually says, word for word

Nacha defines R01 as Insufficient Funds, meaning the available and/or cash reserve balance is not sufficient to cover the dollar value of the debit entry. That's the whole definition. It applies to every Standard Entry Class code, consumer and non-consumer accounts alike, PPD and CCD and WEB and TEL. Nothing about the code is restricted to a particular transaction type, which is part of why it dominates the return mix.

Notice what the receiving bank does not tell you. There's no shortfall amount, no partial payment, no indication of whether the account was ten dollars short or four thousand. The RDFI has no obligation to disclose any of that, and it won't. You get a code and a dollar figure that matches your original entry, reversed. Everything else you infer.

R01 versus R09: no money against not-yet money

R09 is Uncollected Funds, and the two codes get conflated constantly by people who should know better. R09 means the balance exists on paper but is made up of items that haven't cleared yet, most often a deposited check still sitting under a hold. The customer looks at their app and sees $3,000. The bank looks at the same account and sees $3,000 in ledger balance with $2,850 of it uncollected.

R01 means something different and simpler. The available balance genuinely could not cover the entry. No hold is going to release and fix it. Someone has to deposit money.

Why R09 tends to clear itself and R01 usually doesn't

Treat R09 as a scheduling problem and R01 as a collections problem. An R09 retried four business days later has a high success rate, because the hold has almost certainly expired by then and nothing about the customer's underlying finances has changed. Retrying an R01 on the same schedule without any new information is closer to a coin flip weighted against you, which is why timing the second attempt to a deposit event matters far more than timing it to a fixed interval.

The two-banking-day window that decides your cash position

The RDFI must transmit an R01 return so that it's available to the ODFI by the opening of business on the second banking day following the settlement date. Practically, that means a debit originated Monday and settling Tuesday can produce a return that lands in your file Wednesday or Thursday morning. Most R01 returns arrive on the earlier end of that window rather than the later one, because insufficient-funds decisions are made by automated posting logic overnight, not by a human reviewing anything.

Settlement date, banking days, and the Thursday origination trap

Banking days, not calendar days. That distinction eats more finance teams than any other detail in ACH exception handling. Originate on a Thursday, settle Friday, and your return window runs through Tuesday morning. Drop a federal holiday into the middle and it stretches further. Nacha itself had to publish guidance in 2026 explaining that because June 19 fell on a federal holiday, the practical compliance date for its Phase 2 risk management rules was Monday, June 22. If the rulemaking body has to write that memo, your accounting close probably needs the same reminder.

The consequence for cash forecasting is direct. A business that originates its monthly billing run on the 28th and closes books on the 31st is closing books before it knows what got returned. Anyone reconciling a subscription business against gross originated volume rather than net settled volume is reporting revenue that hasn't happened yet.

Same Day ACH speeds up the debit, not the return

Same Day ACH runs three processing windows each banking day, with submission deadlines at 10:30 a.m., 2:45 p.m., and 4:45 p.m. Eastern, and most banks impose internal cutoffs thirty to sixty minutes earlier. The Same Day Entry Fee sits at 5.2 cents, and Nacha's eight-year review completed in March 2026 left it unchanged for another two years. The per-payment cap has been $1 million since March 2022 and rises to $10 million on September 17, 2027, which will finally align it with RTP and FedNow.

What Same Day ACH does not do is shorten the return clock. You'll know about the debit faster. You'll learn it failed on roughly the same schedule. Companies that pay the same-day premium expecting faster failure information are buying something the rule doesn't sell.

Attribute	Detail
Code	R01
Official meaning	Insufficient Funds: available and/or cash reserve balance not sufficient to cover the debit entry
Applies to	All SEC codes, consumer and non-consumer accounts
Return timeframe	2 banking days following settlement date
Retry permitted	Yes, up to 2 reinitiations (3 total presentments)
Retry deadline	Within 180 days of the original entry's settlement date
Required label on retry	Company Entry Description of RETRY PYMT
Counts toward unauthorized rate (0.5%)	No
Counts toward administrative rate (3%)	No
Counts toward overall rate (15%)	Yes
New authorization needed	No, the original authorization remains valid

What is happening inside the account when R01 fires

Understanding the mechanics changes how you fix the problem, so it's worth walking through what the receiving bank is doing at two in the morning when it decides your entry doesn't post.

Available balance is not the number your customer sees

Banks maintain at least two balances. Ledger balance is everything posted. Available balance subtracts pending card authorizations, holds on recent deposits, and any amount the bank has decided to sequester. A customer who filled a gas tank on Sunday might have a $125 authorization sitting against a $38 purchase for three days. Rental car companies and hotels routinely hold several hundred dollars beyond the actual charge.

So the customer genuinely believes the money is there. They're looking at a number their bank shows them, and the number their bank uses to make posting decisions is a different one. When you tell them the payment failed for insufficient funds, a meaningful share of them will argue with you, and they will not be lying.

Overdraft opt-in status after Congress killed the $5 cap

Whether an ACH debit posts into overdraft or bounces back at you depends on the customer's arrangement with their bank, and that arrangement got more variable, not less, over the past two years. The CFPB finalized a rule in December 2024 that would have given institutions holding $10 billion or more in assets three compliance paths, including a $5 per-overdraft cap, with an effective date of October 1, 2025. Congress overturned it under the Congressional Review Act through S.J.Res. 18, which the President signed on May 9, 2025 as P.L. 119-10. The rule never took effect.

Market pricing had already moved on its own. Capital One, Ally, and Citibank charge nothing for overdraft. Bank of America dropped to $10. Wells Fargo still sits at $35. Alliant Credit Union stopped charging overdraft and NSF fees in August 2021 and instead extends Courtesy Pay to members in good standing, which it defines as an account open at least six months with $600 or more in qualifying deposits in the prior 30 days. That kind of discretionary coverage is exactly what determines whether your entry posts or returns, and you have no visibility into it.

One detail trips up nearly everyone. Regulation E opt-in requirements apply to one-time debit card and ATM transactions. They do not cover ACH debits or checks. A customer who deliberately opted out of overdraft coverage to stop card purchases from triggering fees can still have your recurring ACH debit paid into a negative balance and get charged for it. That asymmetry generates a specific and predictable kind of angry phone call.

The payroll calendar moves your return rate more than your dunning copy

The ACH Network delivered 8.74 billion Direct Deposits in 2025. Those deposits do not arrive randomly. Biweekly payrolls cluster on Fridays. Social Security retirement benefits pay on the second, third, or fourth Wednesday depending on birth date, with certain older beneficiaries and SSI recipients paid on the 1st and 3rd. Semi-monthly employers pay on the 15th and the last business day.

Now overlay the standard billing calendar. Rent, mortgages, insurance premiums, and most subscription renewals all hit on the 1st. So the highest-density debit day of the month lands in the trough between two paychecks for a large slice of the working population. Moving a subscription billing date from the 1st to the 16th costs nothing and frequently cuts R01 volume by a third or better, which is a better return on effort than any rewrite of your failed-payment email.

What a single R01 actually costs you

Merchants tend to book the processor's return fee and stop counting. The real number is several times larger once you include the work. Consider a $412 recurring debit from a services business, returned R01, retried once successfully eleven days later.

Cost component	Amount	Notes
Processor failure fee	$4.00	Stripe ACH Direct Debit failure fee; Chase charges $5 per return
Original processing fee reversed	$0.00 net	The 0.8% is reversed, but the failure fee replaces it
Exception handling labor	$5.60	12 minutes at a fully loaded $28 per hour
Customer outreach	$2.80	Email plus one follow-up call attempt
Retry processing fee	$3.30	0.8% of $412 on the successful second attempt
Cost of 11 days of delayed cash	$1.11	At an 9% annualized cost of working capital
Reconciliation and journal adjustment	$2.33	5 minutes of bookkeeper time
Total on a recovered payment	$19.14	4.6% of the invoice value
If the second attempt also fails	add $9.00 to $14.00	Second failure fee plus escalation labor

Four point six percent. On a payment method chosen specifically because it costs 0.8%. Run that across a book of business with a 6% R01 rate and the blended cost of ACH collection stops looking like the bargain the pricing page advertised.

Return rate thresholds: where R01 counts and where it doesn't

Nacha's ACH Network Risk and Enforcement rules set three monitored levels, each calculated over a rolling 60-day window of debit entries. R01 lands in exactly one of them, and understanding which one prevents a lot of unnecessary panic.

Category	Threshold	Codes included	Does R01 count?
Unauthorized returns	0.5%	R05, R07, R10, R11, R29, R51	No
Administrative returns	3.0%	R02, R03, R04	No
Overall returns	15.0%	Every return reason code	Yes

The 15% overall level is the one R01 can break

The unauthorized threshold dropped from 1.0% to 0.5% under the Risk and Enforcement rule, and Nacha noted at the time that even 0.5% sat more than sixteen times above the network's average unauthorized return rate of 0.03%. That gap tells you something. Unauthorized returns are rare enough that exceeding the limit signals a real problem with how you obtained authorizations.

The 15% overall level works differently. Nacha's own rule language acknowledges that some returns, specifically including funding-related ones, may be unavoidable. Nobody expects a zero R01 rate from a business collecting rent in a market with thin household reserves. But the level exists because a book running 18% insufficient-funds returns is telling the network something about its underwriting, its customer selection, or its billing practices, and none of the answers are flattering.

What your ODFI does when the number moves

Your bank sees your return rate before Nacha does, and it will act on its own risk appetite long before any formal threshold is breached. Plenty of ODFIs set internal limits well under the published numbers. Sila, for instance, publishes customer-facing limits of 2.5% administrative and 0.4% unauthorized against Nacha's 3% and 0.5%. Expect your sponsor bank to do something similar and to not advertise the exact figure.

If a formal inquiry does begin, the process runs on written requests for information, a requirement to reduce the rate within 60 days of that request, and an obligation to hold it below the threshold for a further 180 days. The realistic worst case is not a fine. It's your ODFI deciding your account isn't worth the file review and giving you 30 days to find another sponsor, which for a business built on recurring bank debit is close to an extinction event.

Reinitiation: two retries, 180 days, and the words RETRY PYMT

Nacha permits an originator to reinitiate an entry returned R01 or R09 up to two times, for a total of three presentments including the original. All reinitiations must occur within 180 days of the settlement date of the original entry. You do not need a new authorization, because the original one never lapsed.

The formatting requirements are specific and frequently ignored. The reinitiated entry must carry the same Company Name, Company Identification, and dollar amount as the original. The Company Entry Description field must contain RETRY PYMT. Best practice, and in many bank agreements a requirement, is to send retries in a separate batch from fresh originations so your processor and your ODFI can identify them cleanly.

That field matters more now than it did two years ago. As of March 20, 2026, Nacha requires standardized Company Entry Descriptions in other contexts too: PAYROLL for PPD credits representing wages and salaries, and PURCHASE for e-commerce consumer debits. Company Entry Description used to be a field nobody looked at. It's now a field that gets policed, and a retry sent without the RETRY PYMT label is a rules violation that leaves a trail.

What Nacha does not count as a reinitiated entry

A handful of narrow situations fall outside the reinitiation limits entirely, and knowing them keeps you from artificially capping your own collection efforts. A genuinely new payment that the receiver separately authorizes after being told the first one failed is a new entry, not a retry. An entry originated to collect a returned-item fee, where your agreement permits one, is a separate collection. Entries corrected after an administrative return, where you fixed a bad account number, sit in different territory than an R01 retry because the underlying problem was data, not money.

Where people get into trouble is dressing up a fourth attempt as a "new authorization" collected by clicking a checkbox in an email. If the customer didn't affirmatively agree to a new payment on new terms, you've originated an entry that exceeds the limit, and the paper trail will say so.

Three days, five days, or the 15th? Picking the retry date

Retrying the next morning is the single most common mistake in ACH collections. It burns one of your two permitted attempts against an account that has had roughly eighteen hours to change, generates another failure fee, and adds a second return to your rolling 60-day denominator. The account balance did not fix itself overnight.

Three to five business days is the standard advice and it's reasonable as a default. Payday-anchored timing is better where you have the data. If your customer's deposits land every other Friday, retry on the following Monday and you're catching the account at its monthly high point rather than its trough. Some billing platforms now support this natively by reading deposit cadence from a linked account.

Billing type	First retry timing	Second retry	Reasoning
Consumer subscription under $50	Day 4	Often not worth it	A $4 failure fee against a $19 charge kills the margin fast
Consumer subscription $50 to $300	Day 5, or next payday	Day 14 to 16	Catches both semi-monthly and biweekly pay cycles
B2B invoice	Day 2 after a phone call	Day 7	Business R01s are often a sweep or a timing error, not distress
Loan or lease payment	Day 5	Day 12, coordinated with servicing	Late-fee timing and delinquency reporting interact here
Rent	Day 3	Only after tenant contact	Lease notice provisions usually govern before ACH rules do
Returned R09	Day 4	Rarely needed	Deposit holds typically release within that window

Three decisions that turn on R01 math

Abstract guidance about "optimizing your payment mix" doesn't help anybody. Here are three situations where the arithmetic actually decides the answer.

A four-van HVAC company weighing a retry against a card fallback

A heating and cooling outfit outside Boise runs 340 maintenance-plan customers at $412 billed annually on the third of the month, plus service invoices averaging $780. Their R01 rate on the plan billing is 6.2%. The owner wants to know whether to keep retrying or push everyone to cards.

Card cost on $412 at 2.9% plus $0.30 is $12.25, guaranteed, every single time. ACH costs $3.30 when it works. With a 6.2% failure rate and a fully loaded exception cost of $19.14 per return, the expected ACH cost per attempt is $3.30 plus 0.062 times $19.14, or about $4.49. ACH still wins by nearly eight dollars per customer per year, which across 340 customers is roughly $2,640.

Change one input and the answer flips. If the same business billed monthly at $38 instead of annually at $412, card cost drops to $1.40 while ACH cost becomes $0.30 plus 0.062 times $13.50 in exception handling, or $1.14. Now the gap is twenty-six cents a month and the operational headache of running a dunning process is almost certainly not worth it. The lesson isn't "ACH is cheaper." It's that ACH is cheaper above a ticket size that depends on your own return rate, and most businesses have never calculated where that line sits for them.

A dental membership plan billing 640 patients on the first

A two-location practice in Philadelphia sells an in-house membership plan at $34 a month covering cleanings and a discount on restorative work. All 640 members bill on the first. The office manager reports a 9.1% failure rate, meaning roughly 58 returns a month, and she's been retrying every one of them twice.

The math on that policy is unkind. Fifty-eight first retries at $4 is $232. Of those, maybe 55% succeed, leaving 26 second retries at another $104. Add exception labor at twelve minutes each across 84 attempts and you've spent about 17 staff hours a month, or roughly $470 in wages, to recover a portion of $1,972 in billings. Total collection cost lands near $806 against gross plan revenue of $21,760, so about 3.7% of the entire program.

The fix isn't a better retry sequence. It's moving the billing date. Split the roster: patients who tell you they're paid biweekly get billed on the first business day after the 15th, everyone else stays on the 1st. Practices that do this typically see insufficient-funds returns fall into the 4% to 5% range, which cuts the monthly exception load roughly in half and frees the office manager for work that generates revenue rather than recovers it. Second retries then get reserved for balances above some threshold, since a $34 charge that has already cost $4 to fail is not worth another four dollars on a coin flip.

A household deciding between a due-date change and a cash buffer

Consider a couple in Tulsa with a $1,180 auto loan auto-debited on the 5th and a paycheck that clears on the 6th. Three times in the past year the debit came back R01. Each time cost them a $17 NSF fee from their credit union, a $29 late fee from the lender, and a bruised payment history entry that may or may not have been reported.

Two options are on the table. They could call the lender and request a due-date change to the 10th, which most auto lenders will do once per loan term at no cost, though it usually requires the account to be current and may add a few days of accrued interest to the payoff. Or they could hold a $1,200 buffer in checking permanently, which costs them the yield they'd earn on that money elsewhere, currently somewhere around $48 a year in a high-yield savings account.

The due-date change is free and structural. The buffer costs $48 a year and depends on discipline they've already demonstrated they don't reliably have. Against $138 in annual fees, both beat the status quo, but only one of them keeps working when a car repair eats the buffer in March. Fixing the timing beats fixing the balance, and that's true for businesses on the other side of the transaction too.

Technical support triage: the first hour after the return file lands

Most support teams handle R01 badly for a structural reason: the return arrives in a system the support team doesn't monitor, gets summarized by a system that renames it, and reaches the customer as a message that doesn't match what their bank told them.

Where the code lives in your processor's API and dashboard

The raw return reason code sits in the addenda record of the return entry, and depending on your stack you may or may not see it. Plaid's Transfer dashboard groups returns into categories and buckets R01 under "Other," which is not intuitive if you're hunting for the most common code on the network. Stripe surfaces failures on the PaymentIntent with a failure code and, in the rare case where the return arrives after a payment already succeeded, creates a dispute instead. Modern Treasury exposes the return reason code directly on the return object with the associated transaction ID.

Whatever you're using, make sure the literal code reaches your support tooling. A ticket that says "payment failed" produces a generic apology. A ticket that says R01 on a $412 debit that settled Tuesday tells the agent exactly what happened, exactly when the customer's bank likely charged them a fee, and exactly what the retry options are.

The customer message that actually gets paid

Do not use the word "declined." Cards decline; ACH debits get returned by a bank, and customers who hear "declined" go looking for a card problem that doesn't exist. Say the bank returned the payment, name the date it was attempted, name the amount, and say what happens next and when.

Then give them a way to fix it in one action. A payment link that works on a phone recovers a meaningfully higher share than an instruction to log in and update a payment method. And offer the date change, because a customer whose debit failed on the 1st and who gets paid on the 15th will tell you so if you ask, and that one exchange prevents the next eleven failures.

Cutting R01 before the debit ever leaves the building

Everything above is remediation. The higher-leverage work happens before origination.

Balance checks and return-risk scoring

Plaid positions its Balance product explicitly as the affordable answer to insufficient-funds returns, on the reasoning that those account for over 75% of all returns. A real-time balance call before origination is a blunt instrument, but blunt works here: if the available balance is $61 and you're about to debit $412, don't.

Signal Transaction Scores go further, generating a return-risk score from more than 80 attributes including connection history, past ACH events on the account, and identity changes, then letting you write rules against the output. One parameter deserves specific attention: the API accepts your actual funds-availability hold time, because how long you wait before releasing funds materially changes your realized loss even when it doesn't change the return itself. Holding funds does not prevent R01. It prevents R01 from costing you the principal.

Prenotes, micro-deposits, and account validation

Account validation has been mandatory for WEB debits since the rule took effect on March 19, 2021, and the common methods are micro-deposits, prenotification entries, and instant verification through an aggregator. None of these tell you anything about the balance. They tell you the account exists and is open, which prevents R02, R03, and R04, the codes that count against your 3% administrative threshold.

Worth being clear about, because vendors blur it constantly in their marketing: account validation solves administrative returns. Balance and risk scoring solve insufficient-funds returns. Buying the first and expecting the second is a recurring and expensive misunderstanding.

Billing date design

The cheapest intervention available is asking customers when they'd like to be billed and then honoring the answer. It costs a form field. It converts a guess about their cash flow into information. And it moves your debits off the congested first of the month, where they compete against rent, mortgage, insurance, and every other subscription the household holds.

For businesses billing other businesses, ask about the AP run schedule instead. A company that cuts payables every second Wednesday will fail a debit on the intervening Monday and clear the identical debit two days later, and no amount of dunning sophistication substitutes for knowing that.

What the 2026 Nacha rules change, and what they leave alone

March 20, 2026 marked Phase 1 of Nacha's risk management amendments, applying to all ODFIs regardless of size and to non-consumer originators, third-party service providers, and third-party senders whose 2023 ACH origination volume reached 6 million entries or more, along with RDFIs receiving 10 million or more. Phase 2 landed on June 19, 2026, practically Monday June 22, and removed the volume threshold entirely. Every non-consumer participant on the network now needs documented, risk-based, auditable processes for identifying entries initiated due to fraud, reviewed annually.

The package grew out of Nacha's "Risk Management Framework for the Era of Credit-Push Fraud," published three and a half years before Phase 1 took effect, which argued that the dominant threat had shifted from unauthorized debits pulling money out of accounts to scams that convince people to send money themselves. The rules add an explicit definition of false pretenses covering business email compromise, vendor impersonation, and payroll diversion.

None of this targets R01. Insufficient funds is not fraud, and Nacha has never treated it as such. What changed is the surrounding environment: your sponsor bank now runs documented monitoring on your origination behavior, your Company Entry Descriptions are standardized and inspected, and your file quality is visible in a way it wasn't in 2023. An originator with a 14% overall return rate and sloppy RETRY PYMT labeling is now a documented exception in someone's annual review rather than a number nobody pulled.

The European equivalent: AM04, MS03, and the countries that won't tell you

SEPA Direct Debit has its own insufficient-funds code, AM04, defined under the ISO 20022 external return reason list and governed by the European Payments Council's guidance document EPC173-14, currently at version 8.0 and applicable to the 2025 SDD rulebooks that entered force on 5 October 2025.

Then there's the wrinkle that catches every US company expanding into Europe. In several countries, national data protection legislation prohibits the debtor's bank from disclosing that the reason was insufficient funds. Those banks return MS03 instead, which translates roughly to "the reason is not being disclosed." The EPC guidance identifies Austria, Belgium, Germany, Luxembourg, the Netherlands, Slovakia, Slovenia, and Switzerland as applying the restriction. Practically, a Dutch bank will often send AM04 while a Belgian bank sends MS03 for the identical circumstance, and your analytics will show a phantom country-level difference in failure reasons that doesn't exist.

The other structural difference matters more for risk modelling. Under SDD Core, the debtor has an unconditional right to a refund for eight weeks after the debit date, no reason required, and thirteen months for genuinely unauthorized collections. The B2B scheme is different, with payments treated as final a few business days after the debit date and no refund right for authorized transactions. Nothing in US ACH resembles the eight-week no-questions-asked window. Consumer disputes here run through Regulation E and the unauthorized return codes, on a different clock and with a different burden.

Feature	US ACH (R01)	SEPA Direct Debit (AM04)
Insufficient funds code	R01	AM04, or MS03 where disclosure is restricted
Return window	2 banking days after settlement	Up to 5 banking days after due date for returns
Retry limit	2 reinitiations within 180 days	No fixed scheme-level cap; creditor bank rules apply
Consumer no-fault refund right	None equivalent	8 weeks under SDD Core
Unauthorized claim window	60 days for consumer accounts under Reg E	13 months under SDD Core
Mandate model	Authorization held by originator	Mandate with unique reference, held by creditor
Advance notice to payer	Required for varying amounts	Pre-notification required, typically 14 days unless agreed shorter

When to stop debiting a customer entirely

At some point the right answer is not a better retry. Two consecutive R01s on the same account inside 60 days is a reasonable line. Three is generous. Past that you are paying failure fees to learn something the account already told you twice.

Credit-push alternatives have matured enough to be a real option now. The RTP network carries a $10 million per-transaction limit and reaches institutions holding close to 90% of US demand deposit accounts, while FedNow raised its own limit to $10 million in late 2025 and had passed 1,600 enrolled institutions by early 2026. Request for Payment on FedNow costs the requestor a cent per message plus $0.045 per credit transfer, which for a high-volume biller is close to free. The structural advantage is that credit-push payments cannot be returned for insufficient funds, because the payer's bank simply won't send money the payer doesn't have. You get a non-payment instead of a return, which sounds identical and is not: no failure fee, no addition to your 60-day denominator, no reversal to reconcile.

Card fallback remains the pragmatic answer for consumer billing under a few hundred dollars. Just carry Ronen's warning from Plaid's own risk guidance into the decision: a customer you don't trust on one payment method is not automatically trustworthy on another. Routing a chronic R01 account to a card can convert an insufficient-funds return into a chargeback, which costs more and counts against a different set of thresholds.

Return codes you will see sitting next to R01

Code	Meaning	Retry?	Counts toward
R01	Insufficient funds	Yes, up to 2	Overall 15%
R02	Account closed	No, stop origination	Administrative 3%
R03	No account or unable to locate	Only with corrected data	Administrative 3%
R04	Invalid account number	Only with corrected data	Administrative 3%
R05	Unauthorized debit to consumer account using corporate SEC code	No	Unauthorized 0.5%
R07	Authorization revoked by customer	No	Unauthorized 0.5%
R08	Payment stopped	Only with new authorization	Overall 15%
R09	Uncollected funds	Yes, up to 2	Overall 15%
R10	Customer advises originator is not known or entry not authorized	No	Unauthorized 0.5%
R16	Account frozen or funds subject to legal action	No	Overall 15%
R20	Non-transaction account	No, collect a different account	Overall 15%
R29	Corporate customer advises entry not authorized	No	Unauthorized 0.5%

Frequently asked questions about ACH return code R01

Does R01 mean my customer's account is closed?

No. A closed account returns R02 and an account the bank cannot locate returns R03. R01 means the account is open and functioning, and the available balance simply couldn't cover the entry on the day it posted.

How many times can I retry an ACH payment returned as R01?

Twice, for three total presentments including the original, and all attempts must fall within 180 days of the original entry's settlement date. Each retry needs the same company name, company ID, and dollar amount, with RETRY PYMT in the Company Entry Description field.

Can I charge my customer a fee for an R01 return?

Often yes, provided your authorization or service agreement clearly discloses the fee before the fact and the amount complies with applicable state law, some of which caps returned-item charges. The disclosure has to exist in the original agreement, not in the email you send after the payment fails.

Will an R01 return hurt my ability to process ACH?

Only through the 15% overall return rate level, and indirectly through whatever internal limit your sponsor bank enforces, which is usually tighter. R01 is excluded from both the 0.5% unauthorized and 3% administrative thresholds.

How long before I know a debit failed?

Typically two banking days after settlement, sometimes sooner. Build your cash forecasting around net settled volume rather than originated volume, and never close a month on billings that haven't cleared the return window.

A few thoughts after years of reading return files

What keeps striking me about R01 is how much energy gets spent on the wrong end of it. Companies will rewrite dunning emails six times, A/B test subject lines, and buy retry-optimization software, all to squeeze another two points out of recovery, while never once asking a customer what day of the month they'd actually prefer to be billed. The billing calendar is the lever. Almost everything else is downstream of it.

I've also come to think the industry underrates how much of this is simply a mismatch between two calendars that were never designed to talk to each other. Payroll runs on employer convenience. Billing runs on accounting convenience. Neither was built around the reality that a household's balance is a sawtooth, high on Friday afternoon and thin by Wednesday. R01 is what happens where those two schedules cross badly, and the fix is usually a conversation rather than a product. That's an unsatisfying answer for anyone selling payments infrastructure, which may be why you rarely hear it.

Legal Disclaimer

This article is provided for general informational and educational purposes only and does not constitute financial, legal, tax, accounting, or regulatory advice, nor does it create any advisory or fiduciary relationship. Nacha Operating Rules, Federal Reserve fee schedules, processor pricing, bank fee structures, state fee-cap statutes, and European Payments Council rulebooks change over time, and specific figures cited here reflect publicly available information as of publication and may since have been amended. Readers should consult the current Nacha Operating Rules, their own Originating Depository Financial Institution, a qualified attorney, and a licensed accounting or compliance professional before making decisions about ACH origination practices, return handling, retry policies, or customer fee assessment, and should independently verify all thresholds, deadlines, and pricing with primary sources before relying on them.