Every ACH transaction that fails comes back with a return code. That code is not just a notification; it is a diagnostic. It tells you exactly what went wrong, whether the problem is fixable, and what action, if any, you are permitted to take next.

Most business owners see return codes as a nuisance and stop there. The ones who understand them use that information to reduce future failures, protect their processing standing, and avoid the compliance consequences that come from handling returns incorrectly.

How ACH Returns Work

When an ACH transaction cannot be processed, the receiving financial institution (the RDFI) sends the transaction back to the originating financial institution (the ODFI) along with a standardized return code. These codes are defined by NACHA, the organization that governs the ACH network in the United States.

Most returns must be transmitted within two banking days of the settlement date. Some codes related to unauthorized transactions allow the receiver up to 60 calendar days to initiate a return. Understanding the timeline matters because it affects how quickly you need to act.

The Most Common ACH Return Codes

Return codes fall into a few broad categories: account and routing issues, fund availability problems, and authorization disputes. Each category requires a different response.

Code	Meaning	Can You Retry?	What to Do
R01	Insufficient Funds	Yes, with limits	Wait 3 to 5 business days. NACHA allows a maximum of 2 retry attempts after the original. Do not retry more than twice.
R02	Account Closed	No	The account no longer exists. Contact the customer and collect updated banking information before submitting again.
R03	No Account / Unable to Locate Account	No	The routing and account number combination does not match any account at the receiving bank. Verify the account details with the customer before resubmitting.
R04	Invalid Account Number	No	The account number does not meet open specifications. Collect a corrected account number from the customer.
R05	Unauthorized Debit to Consumer Account	No	A corporate SEC code was used against a consumer account without proper authorization. Do not retry. Obtain new written authorization using the correct SEC code.
R07	Authorization Revoked by Customer	No	The customer revoked their authorization. Do not retry under any circumstances. A new authorization agreement is required.
R08	Payment Stopped	No	The customer placed a stop payment order on the transaction. Contact the customer to resolve the underlying issue before proceeding.
R09	Uncollected Funds	Yes, with limits	The account balance exists on paper but the funds are not yet available. Treat the same as R01: wait before retrying, apply the two-retry limit.
R10	Customer Advises Not Authorized	No	The customer denies authorizing the transaction. Do not retry. Review your authorization records before taking any further action.
R11	Entry Not in Accordance with Authorization Terms	No	The transaction does not match what the customer authorized, such as a different amount or date. Correct the error and obtain fresh authorization before resubmitting.
R16	Account Frozen	No	The account is under a legal or regulatory hold. Contact the customer; they need to resolve the restriction with their bank.
R20	Non-Transaction Account	No	The account type does not allow ACH debits. Ask the customer to provide a checking account or another eligible account.
R29	Corporate Customer Advises Not Authorized	No	A business customer denies authorizing the debit. Do not retry. Obtain new written authorization from the authorized representative.

The Retry Rule: What NACHA Actually Allows

A common mistake is retrying a failed transaction too many times or too quickly. NACHA is specific: after the original entry, you may submit no more than two additional retry attempts. Those retries must occur within 180 calendar days of the original settlement date.

For insufficient funds returns (R01 and R09), best practice is to wait three to five business days before the first retry, giving the account holder time to replenish their balance. Retrying the same day is almost always ineffective and counts against your allowed attempts.

For any return coded as unauthorized, including R05, R07, R10, R11, and R29, the answer is straightforward: do not retry. Submitting a transaction again after receiving an unauthorized return, without new written authorization from the customer, is a NACHA violation.

Why Return Rates Matter for Your Processing Standing

NACHA monitors return rates for all ACH originators and holds them to specific thresholds. Exceeding these thresholds puts your processing privileges at risk.

• Overall return rate: must stay below 15%
• Administrative return rate (R02, R03, R04): must stay below 3%
• Unauthorized return rate (R05, R07, R10, R11, R29): must stay below 0.5%

The unauthorized return threshold is the most critical. At 0.5%, there is very little margin for error. A small number of disputed transactions can push a business above the limit if volumes are modest. This is why proper authorization practices are not optional; they directly protect your ability to process ACH payments.

Processors and banks are required to monitor originator return rates and report concerns to NACHA. Repeated violations can result in fines, increased scrutiny, or termination of ACH processing privileges.

Practical Steps After Receiving a Return

The action you take after a return depends on the code:

• Account and routing issues (R02, R03, R04, R20): Do not guess. Contact the customer, confirm the correct account details, and update your records before resubmitting.
• Insufficient funds (R01, R09): Wait at least three to five business days, then retry once. If it fails again, reach out to the customer before attempting a second retry.
• Stop payments (R08): Reach out to the customer to understand and resolve the underlying issue. Do not resubmit until the stop payment order is lifted or a new authorization is provided.
• Unauthorized returns (R05, R07, R10, R11, R29): Pull your authorization records immediately. Do not retry. If authorization documentation is in order, follow your processor’s dispute process. If it is not, obtain a new signed authorization.
• Frozen accounts (R16): This is the customer’s problem to resolve with their bank. Notify them and wait.

How ReliaFund Supports ACH Return Management

ReliaFund provides ACH payment processing with reporting tools that give businesses clear visibility into return activity, including the codes, timing, and account-level detail needed to act quickly and correctly.

With U.S.-based support and nearly 25 years of experience in payment processing, ReliaFund helps clients understand their return data and take the right steps to protect their processing standing. If you are seeing a pattern of returns and are not sure what is driving them, contact ReliaFund to review your ACH reporting.