Skip to main content

ACH Operations

TL;DR
  • ACH Direct Debit takes time to confirm. Wait for the provider's success status. A later return can still take the payment back
  • R01 (insufficient funds) you can retry. R10 you can't. R10 means unauthorized, and that's a fraud signal. Stop debiting that account
  • Nacha publishes a 0.5% unauthorized-return threshold. Its 3% administrative and 15% overall levels trigger inquiry, not an automatic rules violation. Use the scoped table below
  • Verify the account before you debit it. That's the highest-ROI fraud control on ACH. Plaid and MX pay for themselves fast

ACH settles before anyone knows whether it'll stick. There's no real-time authorization. A card gives you an answer on the spot. ACH just goes. Then a return lands days later. Maybe the account was empty. Maybe the customer told their bank they never agreed to it. You're always working on a delay. This page covers the return codes that matter, then verification tools, retry logic, and Nacha's thresholds.

If You're Under $1M/Year on ACH

Start with account verification on new customers. Paid risk scoring is optional; the fraud-monitoring duty below still applies.

Nacha Requirements in Effect in 2026​

Checked 21 October 2026.

  • Fraud monitoring: since 22 June 2026, all non-consumer ACH originators, Third-Party Senders and Third-Party Service Providers must have fraud checks suited to their role. Cover unauthorized payments and payments authorized under false pretenses, such as someone posing as a vendor or account owner. Review the process at least annually and update it as risks change. Small volume isn't an exemption.
  • Entry descriptions: since 20 March 2026, use PAYROLL for wages and similar compensation paid by ACH credit to consumer accounts. Use PURCHASE for consumer ACH debits for online tangible-goods purchases, including recurring purchases first authorized online. The latter doesn't cover services.

Ask your bank or processor to confirm your setup. See Nacha's monitoring guidance and entry-description guidance.

The Big Four Return Codes​

These are the returns you'll see 90%+ of the time:

CodeNameWhat It Really MeansYour Exposure
R01Insufficient FundsAccount is empty or overdrawnRetry in a few days, might work
R02Account ClosedAccount no longer existsDon't retry, get new payment method
R03No Account/Unable to LocateAccount number is wrongData entry error, verify with customer
R10Customer Advises UnauthorizedCustomer told their bank they didn't authorize thisThis is the ACH version of a chargeback

R10 is the scary one. It means the customer went to their bank and said "I didn't authorize this." Even if they did authorize it, you now have a dispute on your hands and potential issues with your ACH provider.

Less Common But Important​

CodeNameWhen You'll See It
R05Unauthorized Consumer DebitConsumer account debited using a corporate SEC code (CCD/CTX instead of PPD/WEB)
R07Authorization RevokedCustomer cancelled their authorization
R08Payment StoppedCustomer put a stop payment on this specific transaction
R09Uncollected FundsFunds exist but aren't available yet
R29Corporate Customer Advises Not AuthorizedR10 equivalent for business accounts

See ACH Return Codes for the complete list.

Nacha Thresholds​

MeasureNacha's published lineYour earlier alert
Unauthorized debit returns, R05/R07/R10/R11/R29/R510.5% thresholdAgree a lower trigger with your bank
Administrative debit returns, R02/R03/R043% inquiry levelSet from your recent rate and time needed to fix account data
Overall debit returns, using your bank's permitted RCK treatment15% inquiry levelAgree a trigger suited to your debit mix

NETWORK Nacha's unauthorized calculation uses a preceding 60-day or two-calendar-month window and two permitted denominator methods. Its administrative and overall calculation permits overall RCK entries and returns to be excluded from both numerator and denominator over that window. Confirm your bank's calculation and stricter account limits.

Above the administrative or overall level, Nacha describes a preliminary inquiry, not an automatic rules violation. An inquiry can lead to required remediation. Checked 22 October 2026.

Investigate R10s when they arrive. Check the authorization, account and recent activity. A raw count of three or five doesn't predict your bank's response; the debit denominator and account terms matter.

Verification Stack​

From cheapest to most expensive:

1. Micro-deposits (Cheapest, Slowest)​

Send two small deposits (usually $0.01-$0.99), customer confirms the amounts.

Good for: Low-risk recurring payments where you can wait 2-3 days Bad for: Anything time-sensitive, high-value first transactions Cost: Ask your provider for its verification fee

2. Instant Account Verification​

Connect to customer's bank via Plaid, Stripe Financial Connections, Finicity, or MX. Verify account ownership instantly.

Good for: Most ecommerce and subscription businesses Bad for: Customers who won't connect their bank (some demographics resist this) Cost: $0.50-2.00 per verification

3. Balance Check​

Same connection as above, but also check current balance.

Where this breaks: Balance checks are a snapshot, not a promise. The customer can drain the account between your check and the debit. Useful for flagging obviously-empty accounts, not for guaranteeing payment.

4. Risk Scoring (Plaid Signal, etc.)​

ML-based scoring using account history, balance patterns, identity signals.

Good for: High-value transactions, lending, insurance premiums Bad for: Low-value transactions where the cost doesn't justify the risk reduction Cost: $1-5+ per transaction

Volume-Tiered Recommendations​

Under $100K/year ACH:

$100K-$1M/year:

  • Instant account verification for all new customers
  • Choose a balance-check amount using return costs and check fees; the $500 test below is an example
  • Track your R01 rate weekly

$1M-$10M/year:

  • Plaid (Auth + Balance) or equivalent
  • Consider Plaid Signal for high-value transactions
  • Automated retry logic for R01s
  • R10 investigation workflow

Over $10M/year:

  • Full verification stack
  • Risk scoring on all transactions
  • Dedicated ACH operations monitoring
  • Direct Nacha membership consideration
Experiment to Run: Balance Check ROI

Hypothesis: Balance checks will reduce R01 returns enough to justify the cost.

Test: For 30 days, run balance checks only on first debits over $500. Compare R01 rates vs. segment with no checks.

Metrics: R01 rate, balance check cost, net savings

Decision rule: If (R01 reduction × average recovery cost) > balance check cost, keep it

Read the result: the $500 split above is an example test setting. Change it using your debit amounts, return costs and check fees; the result may differ by customer group.

Verification Tool Comparison​

ToolCoverageStrengthBest For
Plaid (Auth, Identity, Balance, Signal)BroadestMost features, best knownDefault choice for most
Stripe Financial ConnectionsGoodTight Stripe integrationAlready on Stripe
Finicity (Mastercard)GoodEnterprise featuresLarge volume, need alternatives
MXStrong in credit unionsCU coverageCustomers at credit unions

Honest take: Plaid has the most coverage and is the default for a reason. The others are worth evaluating if you're large enough to negotiate pricing or have specific coverage gaps.

Retry Logic for R01s​

When you get an R01 (insufficient funds), don't immediately give up:

Timing matters: the waits below are example collection settings, not Nacha-mandated delays. Use the customer's confirmed funds timing and your provider's retry instructions.

  • Retry 3-5 business days later
  • If monthly payment, try around typical payday (1st, 15th)
  • For R01, no more than two retries after the original debit, per Nacha's reinitiation guidance; confirm eligibility and timing with your provider

Don't retry:

  • R02 (closed account) - Account is gone
  • R03 (can't locate) - Wrong account number
  • R10 (unauthorized) - They've disputed, stop trying

Handling R10s​

An R10 is a claim of unauthorized transaction. Treat it seriously:

  1. Stop all debits to that customer immediately
  2. Pull the authorization records - Do you have signed ACH authorization?
  3. Check for fraud signals - New customer? Changed bank details recently?
  4. Respond to your processor within 24 hours if they ask

At Stripe and Square, an ordinary timely ACH return has no card-style appeal. Contact the customer about the unpaid invoice, and send authorization records if your provider requests them for an inquiry or a separate bank warranty claim.

Where This Breaks​

Balance checks don't prevent R01s: A customer can have $5,000 when you check and $0 when you debit. Balance is directional, not deterministic.

Weekend timing: ACH doesn't process on weekends or bank holidays. A debit initiated Friday might not settle until Tuesday, giving three days for the balance to change.

Business vs Consumer accounts: Different rules, different protections. Business accounts have fewer protections, which cuts both ways.

Same-day ACH limitations: Same-day ACH has dollar limits and cutoff times. Not all transactions qualify.

Next Steps​

Setting up ACH operations?

  1. Know the big four returns - R01, R02, R03, R10
  2. Choose verification stack - Micro-deposits to risk scoring
  3. Follow volume recommendations - Right-sized approach

Handling ACH returns?

  1. Implement retry logic - When to retry R01s
  2. Handle R10s properly - Unauthorized claims
  3. Stay under Nacha thresholds - Target metrics

Choosing verification tools?

  1. Compare verification options - Cost vs coverage
  2. Evaluate tools - Plaid, Stripe, Finicity
  3. Consider balance checks - Test ROI before committing

Something wrong on this page? Email matt at paymentsandrisk.com and say what needs fixing.