What Is an ACH Return?
When an ACH transaction cannot be completed, the receiving bank sends it back to the originating bank with a standardized return code — a three-character code beginning with "R" that explains why the transaction failed. Understanding these codes is essential for anyone managing ACH payment operations, from accounts receivable teams to payment developers.
High return rates can signal problems with your data quality, authorization practices, or fraud exposure — and NACHA monitors return rates as a key indicator of originator compliance.
The Most Common ACH Return Codes
| Code | Description | Common Cause |
|---|---|---|
| R01 | Insufficient Funds | Not enough money in the account at settlement time. |
| R02 | Account Closed | The account number was valid but has since been closed. |
| R03 | No Account / Unable to Locate Account | Account number doesn't match any account at the RDFI. Often a data entry error. |
| R04 | Invalid Account Number | Account number fails format validation at the RDFI. |
| R05 | Unauthorized Debit to Consumer Account | A corporate debit (CCD/CTX) was sent to a consumer account without proper authorization. |
| R07 | Authorization Revoked by Customer | The account holder told their bank to stop allowing debits from this originator. |
| R08 | Payment Stopped | A stop payment order was placed on the specific transaction or series. |
| R10 | Customer Advises Not Authorized | The receiver claims they never authorized the debit. A high-risk return for originators. |
| R16 | Account Frozen | The account exists but has been frozen due to legal action or bank action. |
| R20 | Non-Transaction Account | The account type (e.g., savings with transaction limits) cannot receive ACH debits. |
| R29 | Corporate Customer Advises Not Authorized | A business account holder disputes authorization. Similar to R10 for corporate accounts. |
Administrative vs. Unauthorized Returns: Why It Matters
NACHA distinguishes between administrative returns (R02, R03, R04 — account or data issues) and unauthorized returns (R05, R07, R10, R29 — the customer disputes the transaction). Unauthorized return rates are held to a stricter threshold because they indicate potential fraud or authorization problems. Exceeding NACHA's unauthorized return rate threshold can trigger compliance action from your ODFI.
What To Do When You Receive a Return
For R01 (Insufficient Funds)
You may re-present the transaction, but NACHA rules limit the number of re-presentments. Consider reaching out to the customer and establishing a retry schedule. Many payment platforms handle this automatically.
For R02, R03, R04 (Account Issues)
Update your records. Contact the customer to obtain correct banking information before retrying. These returns signal stale or incorrect account data — re-presenting without correcting the information will simply generate another return.
For R07, R08, R10, R29 (Authorization Issues)
Do not re-present without resolving the authorization dispute. Contact the customer to understand their concern, provide proof of authorization if applicable, and update your records. Multiple unauthorized returns from the same customer are a serious compliance flag.
Keeping Your Return Rate Healthy
- Validate account numbers before first use (especially for WEB debits).
- Maintain clear, recognizable company name descriptors on ACH transactions so customers recognize the debit.
- Communicate clearly with customers before debiting — unexpected debits generate unauthorized returns.
- Monitor return rates by type on a regular basis and investigate spikes promptly.
Return codes are not just operational nuisances — they're a feedback signal about your data quality, communication practices, and authorization processes. Treating them as such leads to fewer returns, better customer relationships, and a healthier compliance posture.