ACH Return Codes: Complete List & What They Mean
Complete list of ACH return codes with explanations and recommended actions. Learn what R01, R02, R03, R04, and every other Nacha return reason code means and how to reduce returns.
What Are ACH Return Codes?
When a bank (the Receiving Depository Financial Institution, or RDFI) cannot process an ACH entry or the receiver disputes it, the RDFI sends the entry back through the ACH network as a return. Each return includes a reason code — a standardized identifier that explains exactly why the entry was rejected.
ACH return codes follow a simple format: the letter R followed by a two-digit number (R01 through R85). These codes are defined by Nacha (the National Automated Clearing House Association) and are used uniformly across all banks and ACH operators in the United States.
Understanding return codes is essential for anyone originating ACH payments. The code tells you what went wrong, whether the issue is correctable, and what action to take next.
How ACH Returns Work
The ACH return process follows a specific timeline and flow:
Entry is originated
The originator creates an ACH entry and submits it through their ODFI (Originating Depository Financial Institution).
Entry is delivered to the RDFI
The ACH operator (Federal Reserve or EPN) routes the entry to the receiver's bank.
RDFI processes or rejects
The RDFI validates the entry against the receiver's account. If there is a problem (wrong account number, insufficient funds, closed account), the RDFI initiates a return.
Return is sent back
The RDFI sends the return entry (with the reason code) back through the ACH network to the ODFI, which notifies the originator.
Key timing: For most return codes, the RDFI has 2 banking days from the settlement date to initiate a return. For unauthorized consumer entries (R05, R07, R10), the consumer has up to 60 calendar days to claim the transaction was unauthorized, giving the RDFI an extended return window.
Most Common ACH Return Codes
Below is a comprehensive reference of the most frequently encountered ACH return codes. Each entry includes the return reason, a detailed description, and the recommended action to take.
| Code | Reason | Description | Action to Take |
|---|---|---|---|
| R01 | Insufficient Funds | The available balance in the receiver's account is not sufficient to cover the dollar amount of the debit entry. | Contact the receiver to arrange an alternative payment method or retry after confirming funds are available. |
| R02 | Account Closed | The receiver's account has been closed at the RDFI. No further entries should be sent to this account. | Contact the receiver to obtain new account information. Remove the closed account from your records. |
| R03 | No Account / Unable to Locate | The account number provided does not correspond to any existing account at the RDFI. | Verify the account number with the receiver. The routing number may be valid but the account number is incorrect. |
| R04 | Invalid Account Number | The account number structure is not valid. It may contain an incorrect number of digits or invalid characters. | Collect the correct account number from the receiver. Validate format before re-originating. |
| R05 | Unauthorized Debit to Consumer Account | The consumer has notified the RDFI that the debit entry was not authorized. This must be returned within 2 banking days. | Review your authorization records. Contact the consumer to resolve the dispute. Ensure you have a valid signed authorization on file. |
| R06 | Returned per ODFI's Request | The ODFI has requested the RDFI to return the entry. This is typically initiated by the originator. | No corrective action needed — this return was requested by the originator or ODFI. |
| R07 | Authorization Revoked by Customer | The consumer has revoked a previously granted authorization for recurring debits. The RDFI must honor the revocation. | Cease all future debits to this account. Contact the customer to settle any outstanding balance via alternative means. |
| R08 | Payment Stopped | The receiver has placed a stop payment order on this specific ACH debit entry. | Contact the receiver to understand why payment was stopped and arrange an alternative payment method. |
| R09 | Uncollected Funds | The account has sufficient ledger balance but insufficient available (collected) balance to cover the entry. | Retry the entry after allowing time for the receiver's deposited funds to clear. |
| R10 | Customer Advises Unauthorized, Improper, Ineligible, or Part of an Incomplete Transaction | The consumer claims the entry is unauthorized or improper. This code can be used within the extended 60-day return window. | Review authorization records thoroughly. This is a serious claim — respond promptly and provide authorization documentation to your ODFI if requested. |
| R11 | Check Truncation Entry Return | The RDFI is returning a check truncation (TRX) entry because it cannot process the truncated item. | Review the check truncation entry for errors and re-originate if appropriate. |
| R12 | Branch Sold to Another DFI | The branch where the receiver's account was held has been sold to a different financial institution. | Obtain updated routing number information from the receiver or the acquiring institution. |
| R13 | RDFI Not Qualified to Participate | The RDFI is not a participant in the ACH network or is not qualified to process the specific entry type. | Verify the routing number. The financial institution may have lost its ACH participation status. |
| R14 | Representative Payee Deceased or Unable to Continue | The representative payee (the person authorized to receive payments on behalf of the beneficiary) is deceased or unable to continue in that capacity. | Contact the beneficiary or their new representative to update payment information. |
| R15 | Beneficiary or Account Holder Deceased | The actual beneficiary or account holder is deceased. The account may be in probate. | Cease all entries to this account. Contact the estate or legal representative if payment is still owed. |
| R16 | Account Frozen / Entry Returned per OFAC Instruction | The account has been frozen by legal action, regulatory order, or OFAC screening. No debits or credits can be processed. | Do not retry. Contact the receiver through other channels to understand the situation. Consult compliance if OFAC-related. |
| R17 | File Record Edit Criteria | The entry contains fields that do not pass the RDFI's edit criteria or are inconsistent with the entry type. | Review the entry detail record for formatting errors, invalid transaction codes, or mismatched data. Correct and re-originate. |
| R20 | Non-Transaction Account | The entry is directed to a non-transaction account (e.g., a savings account that does not permit ACH debits under Reg D). | Obtain a transaction-eligible account number from the receiver (typically a checking account). |
| R21 | Invalid Company Identification | The Company Identification field in the batch header does not match the RDFI's records or the receiver's expectations. | Verify your Company Identification (EIN/Tax ID) is correct in the batch header. Contact your ODFI if needed. |
| R22 | Invalid Individual ID Number | The Individual Identification Number in the entry detail record is not valid or does not match the RDFI's records. | Verify and correct the Individual ID Number field in the entry detail record. |
| R23 | Credit Entry Refused by Receiver | The receiver has instructed the RDFI to refuse credit entries. This is specific to credits, not debits. | Contact the receiver to understand why the credit was refused and arrange an alternative payment method. |
| R24 | Duplicate Entry | The RDFI has identified this entry as a duplicate of a previously processed entry (same amount, date, and trace number). | Review your origination records to confirm whether the entry was indeed sent twice. If not a duplicate, contact your ODFI. |
| R29 | Corporate Customer Advises Not Authorized | The corporate receiver (CCD/CTX) claims the entry was not authorized. This is the corporate equivalent of R10. | Review your corporate authorization agreement. Contact the business receiver to resolve the dispute. Provide authorization documentation to your ODFI. |
| R31 | Permissible Return Entry (CCD and CTX Only) | The RDFI is returning a CCD or CTX entry with the receiver's permission. This is a voluntary return by the corporate receiver. | Contact the corporate receiver to understand why the payment was returned and arrange re-payment if needed. |
| R51 | Item Related to RCK Entry is Ineligible | The check being re-presented via RCK is ineligible — it may exceed the dollar limit, be a third-party check, or have already been re-presented twice. | Review RCK eligibility rules. The item may have exceeded the $2,500 limit or the two-attempt maximum. Pursue collection through other means. |
Administrative vs Consumer Return Codes
ACH return codes fall into two broad categories, and the distinction matters because they carry different risk profiles and response requirements.
Administrative Returns
Administrative returns are caused by data errors or account status issues — not by a dispute from the receiver. Common examples include R01 (Insufficient Funds), R02 (Account Closed), R03 (No Account), R04 (Invalid Account Number), and R16 (Account Frozen).
These returns must be initiated by the RDFI within 2 banking days of settlement. They are generally correctable: you can fix the account number, wait for funds to become available, or obtain updated account information from the receiver. Nacha monitors administrative return rates, and originators exceeding a 3% overall return rate or 0.5% unauthorized return rate may face enforcement action.
Consumer Unauthorized Returns
Consumer unauthorized returns (R05, R07, R10) carry significantly more risk. They indicate the receiver is disputing the transaction — claiming it was never authorized or that authorization was revoked. These returns have an extended window of up to 60 calendar days from settlement.
Unauthorized returns are taken very seriously by Nacha and the ODFI. High rates of unauthorized returns can result in fines, increased reserves, or termination of your ACH origination privileges. Always maintain proper authorization documentation and respond promptly when these returns occur.
How to Reduce ACH Returns
Every ACH return costs time, money, and administrative effort. Here are proven strategies to minimize your return rate:
1. Validate Account and Routing Numbers
R03 and R04 returns are entirely preventable. Use routing number validation to confirm the ABA number exists and is ACH-eligible. Consider sending a prenote (a zero-dollar test entry) before the first live transaction to verify the account is valid and open. Micro-deposit verification is another option — send two small credits and ask the receiver to confirm the amounts.
2. Obtain Proper Authorization
R05, R07, R10, and R29 returns stem from authorization problems. Ensure you have a signed (physical or electronic) authorization that clearly states the terms, amount, frequency, and the right to revoke. For WEB entries, use commercially reasonable authentication. Store all authorizations securely — you will need them if a return is disputed.
3. Use the Correct SEC Code
Using the wrong SEC code can trigger R17 (File Record Edit Criteria) returns and compliance issues. Match the SEC code to how the transaction was authorized: PPD for signed consumer authorizations, WEB for internet, TEL for telephone, CCD/CTX for business payments.
4. Monitor and Act on Returns Promptly
Track your return rates by code. If you see a pattern — for instance, a spike in R01 returns from a particular customer segment — address the root cause. Update account information promptly after R02 and R03 returns. Do not retry entries that returned as R07 (Authorization Revoked) or R10 (Customer Advises Unauthorized).
5. Keep Records Current
Account numbers and routing numbers change when customers switch banks, and accounts can close without notice. Implement a process to periodically verify banking details, especially for recurring payments. When you receive an R02 (Account Closed) or R12 (Branch Sold), proactively reach out for updated information.
ACH Return Timeframes
The window for returning an ACH entry depends on the type of return and the SEC code used. Here is a summary of the key timeframes:
| Return Type | Timeframe | Applicable Codes | Notes |
|---|---|---|---|
| Standard Administrative | 2 banking days from settlement | R01–R04, R06, R08, R09, R11–R17, R20–R24 | Covers most data-error and account-status returns |
| Consumer Unauthorized | 60 calendar days from settlement | R05, R07, R10 | Extended window for consumer disputes; high-risk for originators |
| Corporate Unauthorized (CCD/CTX) | 2 banking days from settlement | R29 | No extended window for corporate entries |
| Corporate Permissible Return | 2 banking days from settlement | R31 | Voluntary return by corporate receiver |
| IAT Returns | 2 banking days from settlement | Various (IAT-specific) | International entries may have additional OFAC-related return reasons |
Frequently Asked Questions
- What is the most common ACH return code?
- R01 (Insufficient Funds) is by far the most common ACH return code. It occurs when the receiver's account does not have enough available balance to cover the debit entry. This is similar to a bounced check.
- How long does an ACH return take?
- Most ACH returns must be initiated within 2 banking days of settlement. However, unauthorized consumer returns (R05, R07, R10, R29) have an extended window of up to 60 calendar days from the settlement date.
- Can an ACH credit be returned?
- Yes. While less common than debit returns, ACH credits can be returned for reasons like account closed (R02), invalid account number (R04), or credit refused by receiver (R23). The RDFI has 2 banking days to return most credit entries.
- What is the difference between R05 and R10?
- Both relate to unauthorized transactions, but they differ in timing and context. R05 (Unauthorized Debit) is used within the standard 2-day return window when the consumer claims the debit was not authorized. R10 (Customer Advises Unauthorized) is used within the extended 60-day window and typically involves the consumer contacting their bank after the initial return period.
- How can I reduce ACH returns?
- The most effective strategies include: validating routing and account numbers before originating (prenote or micro-deposit verification), obtaining proper written or electronic authorization, using the correct SEC code, maintaining up-to-date customer records, and monitoring return rates to identify patterns.
Reduce ACH returns with accurate NACHA files
BatchPay QB validates routing numbers, formats entries to spec, and generates compliant NACHA files directly from your QuickBooks data. Fewer formatting errors means fewer returns.
Start Free Trial