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.
- 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
| Code | Name | Retry? | Action |
|---|---|---|---|
| R01 | Insufficient Funds | Limited | Confirm funds and provider instructions before retrying |
| R02 | Account Closed | No | Request new account |
| R03 | No Account Found | No | Verify account info |
| R10 | Customer Unauthorized | No | Stop immediately, investigate |
| R20 | Non-Transaction Account | No | Request 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.
| Code | Description | Retry? | Typical Cause | Action |
|---|---|---|---|---|
| R01 | Insufficient Funds | Yes* | Balance too low | Retry in 3-5 days (payday timing) |
| R02 | Account Closed | No | Account no longer exists | Request new account from customer |
| R03 | No Account/Unable to Locate | No | Wrong account number | Verify and correct account info |
| R04 | Invalid Account Number | No | Malformed account number | Correct account number format |
| R05 | Unauthorized Debit (consumer) | No | Customer disputes authorization | Stop debits, investigate |
| R06 | Returned per ODFI's Request | Maybe | Bank-initiated return | Contact your bank for details |
| R07 | Authorization Revoked | No | Customer canceled permission | Stop debits, obtain new auth |
| R08 | Payment Stopped | No | Customer issued stop payment | Contact customer directly |
| R09 | Uncollected Funds | Yes* | Check deposited, not yet cleared | Retry in 5-7 days |
| R10 | Customer Advises Not Authorized | No | Disputes authorization | Stop immediately, investigate |
| R11 | Debit doesn't match authorization terms | Conditional | Wrong amount, early debit or another authorization error | Correct the error under the R11 rules below |
| R12 | Branch Sold to Another DFI | No | Bank merger/sale | Update routing number |
| R13 | Invalid ACH Routing Number | No | Routing number doesn't exist | Correct routing number |
| R14 | Representative Payee Deceased | No | Account representative died | Update account |
| R15 | Beneficiary/Account Holder Deceased | No | Account holder died | Account must be closed |
| R16 | Account Frozen | No | Legal hold on account | Customer must resolve with bank |
| R17 | File Record Edit Criteria | No | ACH file formatting error | Fix 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.
| Code | Description | Timing | What Happened |
|---|---|---|---|
| R05 | Unauthorized Debit Entry | About 60 days after settlement (consumer) | Consumer account debited using a corporate code |
| R07 | Authorization Revoked | About 60 days after settlement (consumer) | Customer canceled recurring authorization |
| R10 | Customer Advises Not Authorized | About 60 days after settlement (consumer) | Customer disputes authorization |
| R11 | Debit doesn't match authorization terms | About 60 days after settlement (consumer) | Authorization exists, but the debit is wrong |
| R51 | Improper re-presented check debit (RCK) | Check the bank's code-specific deadline | Problem with an RCK debit |
Corporate ACH Authorization Disputes
| Code | Description | Timing | What Happened |
|---|---|---|---|
| R29 | Corporate Customer Advises Not Authorized | 2 banking days after settlement (business) | Business customer disputes |
Handling Unauthorized Returns
- 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.
- Review your authorization records:
- Do you have signed ACH authorization?
- Did customer consent via web/phone?
- Is the authorization date before the transaction?
- Investigate the customer:
- First transaction or established?
- Other returns in history?
- Fraud pattern indicators?
- Document everything - you'll want the authorization, the timestamps, the whole trail
- Respond to the ODFI if they ask for records
- Update your fraud rules if you see a pattern
Unauthorized Return Prevention
| Prevention | Implementation |
|---|---|
| Prenotes | Send $0 verification before first debit |
| Micro-deposits | Verify account ownership with small deposits |
| Bank verification APIs | Instant account validation (Plaid, MX, etc.) |
| Clear authorization language | Explicit consent, saved and timestamped |
| Email confirmation | Send receipt immediately after authorization |
Extended Returns (R20-R39)
| Code | Description | Retry? | Notes |
|---|---|---|---|
| R20 | Non-Transaction Account | No | Savings account with transaction limits |
| R21 | Invalid Company Identification | No | Fix your company ID in file |
| R22 | Invalid Individual ID Number | No | Fix customer ID in record |
| R23 | Credit Entry Refused by Receiver | No | Customer refused incoming payment |
| R24 | Duplicate Entry | No | Already processed this transaction |
| R25 | Addenda Error | No | Fix addenda record format |
| R26 | Mandatory Field Error | No | Required field missing/invalid |
| R27 | Trace Number Error | No | Fix trace number |
| R28 | Routing Number Check Digit Error | No | Last digit of routing number wrong |
| R29 | Corporate Customer Advises Not Authorized | No | Corporate unauthorized; see the ordinary business debit deadline |
| R30 | RDFI Not Participant in Check Truncation | No | Bank doesn't support this |
| R31 | Permissible Return Entry | Maybe | CCD/CTX specific return |
| R32 | RDFI Non-Settlement | No | Bank settlement issue |
| R33 | Return of XCK Entry | No | Check conversion return |
| R34 | Limited Participation DFI | No | Bank has restrictions |
| R35 | Return of Improper Debit Entry | No | Wrong SEC code for debit |
| R36 | Return of Improper Credit Entry | No | Wrong SEC code for credit |
Return Timeframes
Standard ACH
| Return Category | Timing Reference |
|---|---|
| Routine returns, for example R01 to R04 | 2 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 returns | Check 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 Code | Retry Recommended? | Optimal Wait Time |
|---|---|---|
| R01 (NSF) | Yes (limited times) | 3-5 business days, align with payday |
| R09 (Uncollected) | Yes | 5-7 business days |
| R02-R04 | No | Correct info first |
| R05, R07, R10 | Never | Don't retry |
| R16 (Frozen) | Maybe | After customer confirms resolved |
NACHA Retry Rules
| Rule | Requirement |
|---|---|
| Max retries for NSF | 2 retries per debit (3 total attempts) |
| Same amount | Retry must be for original amount |
| Timing | Eligible reinitiations must be within 180 days of the original settlement; confirm provider timing before retrying |
| Consumer notification | Required if retry fee charged |
Smart Retry Timing
| Strategy | When to Use |
|---|---|
| Payday alignment | Retry on 1st, 15th of month |
| End of week | Friday afternoon (deposits cleared) |
| Customer confirmation | Ask customer to confirm funds available |
| Staggered retry | Day 3, then Day 7 if still failing |
Retry Decision Tree
Fraud Indicators
High-Risk Return Patterns
| Pattern | Risk Level | What It Suggests |
|---|---|---|
| Multiple R10s from same account | Critical | Authorization fraud or dispute abuse |
| R02/R03 after prior success | High | Account takeover or closed in panic |
| R05 after legitimate pattern | Medium | Friendly fraud or buyer's remorse |
| Velocity of R01s | Medium | Financial stress or testing accounts |
| New account + immediate return | High | Fraudulent 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
| Indicator | Action |
|---|---|
| First R10 ever | Investigate, may be one-off |
| Second R10 same customer | Keep debits stopped and review authorization, prior returns and possible account misuse |
| R10 + other fraud signals | Block immediately, investigate |
| Pattern across customers | Check 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 Product | Return 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 Category | Published line | What it means |
|---|---|---|
| Unauthorized debit returns (R05/R07/R10/R11/R29/R51) | 0.5% threshold | Bank monitoring and possible enforcement |
| Administrative debit returns (R02/R03/R04) | 3% inquiry level | Allows preliminary inquiry |
| Overall debit returns, using your bank's permitted RCK treatment | 15% inquiry level | Allows 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
| Consideration | Guidance |
|---|---|
| R01 (NSF) fees | Often passed to customer; check state law |
| R10 (Unauthorized) fees | Never pass to customer; you're at fault |
| Disclosed in terms | Fee passing must be disclosed upfront |
| State law limits | Some states cap NSF fee pass-through |
| Customer relationship | First-time courtesy waiver builds goodwill |
Fee Mitigation Strategies
| Strategy | Impact |
|---|---|
| Pre-validation | Reduce R01-R04 with account verification |
| Clear authorization | Reduce R10/R29 with strong consent |
| Smart retry timing | Retry R01 at strategic times (paydays) |
| Customer notification | Contact before retry to confirm funds |
| Account update prompts | Proactive 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
| Limit | Amount |
|---|---|
| Per-transaction limit | $1,000,000 |
| Return window | Depends 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
| Method | What It Checks | R Codes Prevented |
|---|---|---|
| Prenote | Account exists, accepts debits | R02, R03, R04, R13 |
| Micro-deposits | Account active, customer has access | R02, R03, ownership |
| Bank verification API | Account status, ownership | R02, R03, R20 |
| Balance check | Available balance | R01 (not guaranteed) |
Validation Trade-offs
| Method | Cost | Speed | Coverage |
|---|---|---|---|
| Prenote | Free | 3-4 days | Limited |
| Micro-deposits | ~$0.05 | 2-3 days | Good |
| Instant verification | $0.10-0.50 | Instant | Best |
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 Code | Use Case | Timing Reference |
|---|---|---|
| PPD | Personal (recurring) | Usually consumer: about 60 days for unauthorized (R10, R11) |
| WEB | Web-initiated | Usually consumer: about 60 days for unauthorized (R10, R11) |
| TEL | Telephone-initiated | Usually consumer: about 60 days for unauthorized (R10, R11) |
| CCD | Corporate | Business: 2 banking days for unauthorized (R29) |
| CTX | Corporate trade exchange | Business: 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
| Metric | What to compare | Action |
|---|---|---|
| Overall return rate | Your debit mix, bank limit and the inquiry level above | Investigate changes by code |
| Unauthorized return rate | All six codes, using the scoped calculation above | Alert early enough to meet your bank's remediation deadline |
| R01 rate | Comparable debit cohorts and retry attempts | Check payment timing, verification and collection costs |
| R10 rate | Authorization records and recent account patterns | Investigate 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 Volume | Focus |
|---|---|
| Under $50k/mo | Use basic validation. Watch unauthorized rate. |
| $50k-$250k/mo | Implement instant verification. Track metrics monthly. |
| $250k-$1M/mo | Optimize retry logic. Automate monitoring. |
| Over $1M/mo | Advanced fraud rules. Dedicated ACH operations review. |
Next Steps
New to ACH returns?
- Learn ACH operations - Bank payment management fundamentals
- Understand bank transfers - ACH fundamentals and risk
Reducing return rates?
- Implement identity verification - Account validation methods
- Set up velocity rules - Pattern detection for fraud prevention
Investigating unauthorized returns?
- Review Regulation E - Consumer protection requirements
- Understand first-party fraud - Authorization fraud patterns
- Check AML basics - Compliance requirements
Related Pages
- Bank Transfers - ACH fundamentals and fraud
- FX and Settlement - Cross-border considerations
- Fraud Detection - Fraud monitoring
- Operations - Payment operations
- Real-Time Payments - RTP/FedNow alternatives
- Payments Metrics - Success rate tracking
- Identity Verification - Account validation
- Velocity Rules - Pattern detection
- First-Party Fraud - Authorization fraud patterns
- Decline Codes - Card decline comparison
- AML Basics - Compliance requirements
- Processor Management - Bank relationships