Skip to main content

ACH Return Codes

This page covers ACH return codes, the R numbers like R01 or R10 that come back when a bank debit fails. Looking for a declined card or a card chargeback?

Check what the payment ran on. ACH pulls from a routing and account number, and every return code here starts with R. On a card, 05 or 51 means it was declined at the sale, and 10.4 or 4853 means a dispute is taking money back.

TL;DR
  • ACH return codes tell you why a bank transfer failed and whether you're allowed to retry
  • R01 insufficient funds may be eligible for two retries after the original debit. Confirm funds and provider instructions before another attempt
  • R02 account closed, R03 no account found and R10 customer unauthorized are terminal. Stop and fix the underlying data
  • R10 is the ACH equivalent of a fraud chargeback. Investigate it, don't just re-run the debit
  • Nacha sets a 0.5% unauthorized-return threshold. Its 3% administrative and 15% overall levels allow inquiry; they aren't automatic rules violations. Check your bank's stricter limits

A bank pushed your debit back and handed you a code. It tells you why, and whether you're allowed to try again. Get that second part wrong and NACHA starts counting. Most returns are boring account problems you can fix. A few mean stop, and those are the ones that cost you ACH.

Quick Reference: Most Common Returns​

CodeNameRetry?Action
R01Insufficient FundsLimitedConfirm funds and provider instructions before retrying
R02Account ClosedNoRequest new account
R03No Account FoundNoVerify account info
R10Customer UnauthorizedNoStop immediately, investigate
R20Non-Transaction AccountNoRequest different account

Return Codes R01-R17​

Read the reason before deciding what to do next. This range includes account problems, stopped payments and authorization issues.

CodeDescriptionRetry?Typical CauseAction
R01Insufficient FundsYes*Balance too lowRetry in 3-5 days (payday timing)
R02Account ClosedNoAccount no longer existsRequest new account from customer
R03No Account/Unable to LocateNoWrong account numberVerify and correct account info
R04Invalid Account NumberNoMalformed account numberCorrect account number format
R05Unauthorized Debit (consumer)NoCustomer disputes authorizationStop debits, investigate
R06Returned per ODFI's RequestMaybeBank-initiated returnContact your bank for details
R07Authorization RevokedNoCustomer canceled permissionStop debits, obtain new auth
R08Payment StoppedNoCustomer issued stop paymentContact customer directly
R09Uncollected FundsYes*Check deposited, not yet clearedRetry in 5-7 days
R10Customer Advises Not AuthorizedNoDisputes authorizationStop immediately, investigate
R11Debit doesn't match authorization termsConditionalWrong amount, early debit or another authorization errorCorrect the error under the R11 rules below
R12Branch Sold to Another DFINoBank merger/saleUpdate routing number
R13Invalid ACH Routing NumberNoRouting number doesn't existCorrect routing number
R14Representative Payee DeceasedNoAccount representative diedUpdate account
R15Beneficiary/Account Holder DeceasedNoAccount holder diedAccount must be closed
R16Account FrozenNoLegal hold on accountCustomer must resolve with bank
R17File Record Edit CriteriaNoACH file formatting errorFix technical submission

*The waits shown here are suggested test settings. Confirm funds and provider instructions; 3-5 business days isn't a universal minimum.


Unauthorized Returns (R05, R07, R10, R11, R29, R51)​

Count all six codes in the unauthorized return rate. R11 means an authorization exists, but the debit doesn't follow its terms. It doesn't cover complaints about the goods or services.

Consumer ACH Authorization Disputes​

Use the bank return deadlines and later-claim qualifications. The clock starts at settlement.

CodeDescriptionTimingWhat Happened
R05Unauthorized Debit EntryAbout 60 days after settlement (consumer)Consumer account debited using a corporate code
R07Authorization RevokedAbout 60 days after settlement (consumer)Customer canceled recurring authorization
R10Customer Advises Not AuthorizedAbout 60 days after settlement (consumer)Customer disputes authorization
R11Debit doesn't match authorization termsAbout 60 days after settlement (consumer)Authorization exists, but the debit is wrong
R51Improper re-presented check debit (RCK)Check the bank's code-specific deadlineProblem with an RCK debit

Corporate ACH Authorization Disputes​

CodeDescriptionTimingWhat Happened
R29Corporate Customer Advises Not Authorized2 banking days after settlement (business)Business customer disputes

Handling Unauthorized Returns​

  1. Stop the returned debit. Don't send it again unchanged. For R11, a corrected new entry can use the existing authorization if its terms still cover the payment. Send it within 60 days after the R11 return settles.
  2. Review your authorization records:
    • Do you have signed ACH authorization?
    • Did customer consent via web/phone?
    • Is the authorization date before the transaction?
  3. Investigate the customer:
    • First transaction or established?
    • Other returns in history?
    • Fraud pattern indicators?
  4. Document everything - you'll want the authorization, the timestamps, the whole trail
  5. Respond to the ODFI if they ask for records
  6. Update your fraud rules if you see a pattern

Unauthorized Return Prevention​

PreventionImplementation
PrenotesSend $0 verification before first debit
Micro-depositsVerify account ownership with small deposits
Bank verification APIsInstant account validation (Plaid, MX, etc.)
Clear authorization languageExplicit consent, saved and timestamped
Email confirmationSend receipt immediately after authorization

Extended Returns (R20-R39)​

CodeDescriptionRetry?Notes
R20Non-Transaction AccountNoSavings account with transaction limits
R21Invalid Company IdentificationNoFix your company ID in file
R22Invalid Individual ID NumberNoFix customer ID in record
R23Credit Entry Refused by ReceiverNoCustomer refused incoming payment
R24Duplicate EntryNoAlready processed this transaction
R25Addenda ErrorNoFix addenda record format
R26Mandatory Field ErrorNoRequired field missing/invalid
R27Trace Number ErrorNoFix trace number
R28Routing Number Check Digit ErrorNoLast digit of routing number wrong
R29Corporate Customer Advises Not AuthorizedNoCorporate unauthorized; see the ordinary business debit deadline
R30RDFI Not Participant in Check TruncationNoBank doesn't support this
R31Permissible Return EntryMaybeCCD/CTX specific return
R32RDFI Non-SettlementNoBank settlement issue
R33Return of XCK EntryNoCheck conversion return
R34Limited Participation DFINoBank has restrictions
R35Return of Improper Debit EntryNoWrong SEC code for debit
R36Return of Improper Credit EntryNoWrong SEC code for credit

Return Timeframes​

Standard ACH​

Return CategoryTiming Reference
Routine returns, for example R01 to R042 banking days after settlement
Unauthorized Consumer (R05, R07, R10, R11)About 60 days after settlement (consumer rule)
Unauthorized Corporate (R29)2 banking days after settlement (business rule)
Other returnsCheck the code; the R20-R39 range isn't one deadline

Measured from settlement. These deadlines aren't absolute finality: late returns and separate warranty claims can follow.

Same-Day ACH Returns​

Same-day processing can send a return back sooner. It doesn't replace the return deadline for the code and account type. Use the debit return rules.


Retry Strategies​

When to Retry​

Return CodeRetry Recommended?Optimal Wait Time
R01 (NSF)Yes (limited times)3-5 business days, align with payday
R09 (Uncollected)Yes5-7 business days
R02-R04NoCorrect info first
R05, R07, R10NeverDon't retry
R16 (Frozen)MaybeAfter customer confirms resolved

NACHA Retry Rules​

RuleRequirement
Max retries for NSF2 retries per debit (3 total attempts)
Same amountRetry must be for original amount
TimingEligible reinitiations must be within 180 days of the original settlement; confirm provider timing before retrying
Consumer notificationRequired if retry fee charged

Smart Retry Timing​

StrategyWhen to Use
Payday alignmentRetry on 1st, 15th of month
End of weekFriday afternoon (deposits cleared)
Customer confirmationAsk customer to confirm funds available
Staggered retryDay 3, then Day 7 if still failing

Retry Decision Tree​


Fraud Indicators​

High-Risk Return Patterns​

PatternRisk LevelWhat It Suggests
Multiple R10s from same accountCriticalAuthorization fraud or dispute abuse
R02/R03 after prior successHighAccount takeover or closed in panic
R05 after legitimate patternMediumFriendly fraud or buyer's remorse
Velocity of R01sMediumFinancial stress or testing accounts
New account + immediate returnHighFraudulent account linkage

Red Flags​

  • First transaction returns R10 (never authorized)
  • Same bank info used across multiple accounts
  • Returns after long dormancy
  • Pattern of small tests then large returns
  • Customer provides incorrect info multiple times

Fraud Response​

IndicatorAction
First R10 everInvestigate, may be one-off
Second R10 same customerKeep debits stopped and review authorization, prior returns and possible account misuse
R10 + other fraud signalsBlock immediately, investigate
Pattern across customersCheck for common vector

ACH Return Fee Liability​

Return fees depend on your bank, processor and product. Don't assume one fee or one payer for every code.

Published Provider Examples​

Provider and ProductReturn Fee
Braintree ACH Direct Debit$5 when returned by the bank network; $5 when disputed as unauthorized
Helcim ACH$5 for a payment rejected or returned by the bank network

Ask your bank about any other contractual charges. These examples aren't a universal fee schedule.

NACHA Return Rate Thresholds​

Return CategoryPublished lineWhat it means
Unauthorized debit returns (R05/R07/R10/R11/R29/R51)0.5% thresholdBank monitoring and possible enforcement
Administrative debit returns (R02/R03/R04)3% inquiry levelAllows preliminary inquiry
Overall debit returns, using your bank's permitted RCK treatment15% inquiry levelAllows preliminary inquiry

NETWORK Nacha's public explanation distinguishes inquiry from an automatic violation. Its calculation sheets cover unauthorized returns and administrative/overall returns over the preceding 60 days or two calendar months. RCK entries and returns may be excluded from both sides of the overall calculation. Confirm the permitted denominator with your bank; a weekly code review doesn't replace that calculation. Checked 22 October 2026.

Act before a breach. Your bank can impose stricter limits. Get those and its required response in writing.

Passing Fees to Customers​

ConsiderationGuidance
R01 (NSF) feesOften passed to customer; check state law
R10 (Unauthorized) feesNever pass to customer; you're at fault
Disclosed in termsFee passing must be disclosed upfront
State law limitsSome states cap NSF fee pass-through
Customer relationshipFirst-time courtesy waiver builds goodwill

Fee Mitigation Strategies​

StrategyImpact
Pre-validationReduce R01-R04 with account verification
Clear authorizationReduce R10/R29 with strong consent
Smart retry timingRetry R01 at strategic times (paydays)
Customer notificationContact before retry to confirm funds
Account update promptsProactive requests when issues appear

Same-Day ACH Considerations​

Same-Day ACH mostly reuses the same return codes. What's different is the speed and the per-transaction ceiling.

Same-Day ACH Return Codes​

Use the return code for the actual reason. R31 concerns a CCD or CTX return the originating bank agrees to accept; it isn't a same-day participation code.

Same-Day ACH Limits​

LimitAmount
Per-transaction limit$1,000,000
Return windowDepends on the return code and account type; same-day processing doesn't replace it

When Same-Day ACH Returns Faster​

Same-day ACH can return the same business day for:

  • Insufficient funds
  • Account issues
  • Format errors

Operational impact: You can know the same day instead of waiting 2+ days. That's days back to chase the customer.


Account Validation Best Practices​

The cheapest return is the one you never get. Validate the account before you debit it.

Pre-Transaction Validation​

MethodWhat It ChecksR Codes Prevented
PrenoteAccount exists, accepts debitsR02, R03, R04, R13
Micro-depositsAccount active, customer has accessR02, R03, ownership
Bank verification APIAccount status, ownershipR02, R03, R20
Balance checkAvailable balanceR01 (not guaranteed)

Validation Trade-offs​

MethodCostSpeedCoverage
PrenoteFree3-4 daysLimited
Micro-deposits~$0.052-3 daysGood
Instant verification$0.10-0.50InstantBest

SEC Codes and Returns​

Check both the SEC (Standard Entry Class) code and the receiving account type. R10 and R11 can also apply to consumer codes used on non-consumer accounts. Use the bank debit return deadlines.

SEC CodeUse CaseTiming Reference
PPDPersonal (recurring)Usually consumer: about 60 days for unauthorized (R10, R11)
WEBWeb-initiatedUsually consumer: about 60 days for unauthorized (R10, R11)
TELTelephone-initiatedUsually consumer: about 60 days for unauthorized (R10, R11)
CCDCorporateBusiness: 2 banking days for unauthorized (R29)
CTXCorporate trade exchangeBusiness: 2 banking days for unauthorized (R29)

Using wrong SEC code: Can result in R35 (Improper Debit) or R36 (Improper Credit).


Reporting and Monitoring​

Key Metrics to Track​

MetricWhat to compareAction
Overall return rateYour debit mix, bank limit and the inquiry level aboveInvestigate changes by code
Unauthorized return rateAll six codes, using the scoped calculation aboveAlert early enough to meet your bank's remediation deadline
R01 rateComparable debit cohorts and retry attemptsCheck payment timing, verification and collection costs
R10 rateAuthorization records and recent account patternsInvestigate each return; track the combined unauthorized rate too

Monthly ACH Health Report​

Track monthly:

  • Total return count and rate
  • Return breakdown by code
  • Unauthorized return rate
  • Top returning accounts
  • Return trend (improving/worsening)

Scale Callout​

Your ACH volume decides what's worth building here.

ACH VolumeFocus
Under $50k/moUse basic validation. Watch unauthorized rate.
$50k-$250k/moImplement instant verification. Track metrics monthly.
$250k-$1M/moOptimize retry logic. Automate monitoring.
Over $1M/moAdvanced fraud rules. Dedicated ACH operations review.

Next Steps​

New to ACH returns?

  1. Learn ACH operations - Bank payment management fundamentals
  2. Understand bank transfers - ACH fundamentals and risk

Reducing return rates?

  1. Implement identity verification - Account validation methods
  2. Set up velocity rules - Pattern detection for fraud prevention

Investigating unauthorized returns?

  1. Review Regulation E - Consumer protection requirements
  2. Understand first-party fraud - Authorization fraud patterns
  3. Check AML basics - Compliance requirements

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