DEV Community

Payout Rail
Payout Rail

Posted on

ACH Return Codes Explained: R01 to R85 and How to Handle Them

ACH Return Codes Explained: R01 to R85 and How to Handle Them

ACH Return Codes Explained: R01 to R85 and How to Handle Them

When you're building a payout system, ACH returns are inevitable. A user's bank account closes. Funds aren't available. The account holder disputes the transfer. Your integration needs to handle these failures gracefully—and that starts with understanding what each return code actually means.

The National Automated Clearing House Association (Nacha) defines 85 standardized return codes (R01 through R85). Each one tells you why a debit or credit failed, and more importantly, what you should do next. Let's walk through the most common ones and how to decode them in your payout flow.

The Big Three: R01, R02, R03

R01: Insufficient Funds

The account exists and is valid, but the balance is too low. This is the most common return code—roughly 30–40% of all ACH returns in production systems.

  • When it fires: During the settlement window (typically 1–2 business days after submission).
  • What it means: The account holder has the account, but not enough money right now.
  • How to handle it: Retry after 2–3 business days, or switch to a different payout method if the user has one on file. Don't retry immediately; the funds won't magically appear.

R02: Account Closed by Institution

The bank shut down the account. This is permanent.

  • When it fires: During settlement.
  • What it means: The account is gone. Do not retry.
  • How to handle it: Flag the account as invalid, notify the user, and ask for a new bank account or alternate payout method.

R03: No Account/Unable to Locate Account

The routing number or account number doesn't exist, or the bank can't find it in their system.

  • When it fires: During settlement or early in the processing window.
  • What it means: The account details are wrong or the account was never opened.
  • How to handle it: Validate the account before the next payout attempt. Use microdeposit verification or real-time account validation (offered by some ACH providers).

Mid-Tier Returns: R04, R10, R29

R04: Reserved

This code is reserved by Nacha and rarely used in practice. If you see it, escalate to your ACH provider.

R10: Customer Advises Not Authorized

The account holder called their bank and said, "I didn't authorize this transfer."

  • When it fires: 60–90 days after settlement (this is the long tail of ACH disputes).
  • What it means: The user is disputing the payout. You may have a legitimate claim, but the burden of proof is now on you.
  • How to handle it: Log the dispute, preserve all transaction records, and prepare to provide proof of authorization (signed agreement, email consent, etc.). Some platforms flag the user as high-risk for future payouts.

R29: Corporate Account Closed

Like R02, but for business accounts.

  • When it fires: During settlement.
  • What it means: The business account is closed. Permanent.
  • How to handle it: Same as R02—ask for a new account.

Rare but Critical: R82, R83, R84

R82: Duplicate Entry

You (or your processor) submitted the same payout twice in the same batch window.

  • When it fires: During settlement.
  • What it means: The bank rejected one copy as a duplicate.
  • How to handle it: Check your idempotency logic. Use a unique transaction ID per payout and ensure your integration doesn't submit the same request twice on retry.

R83: Routing Number Check Digit Error

The routing number format is invalid or the check digit doesn't match.

  • When it fires: During validation, sometimes during settlement.
  • What it means: Bad data. The account details are wrong.
  • How to handle it: Validate routing numbers before submission using the ABA routing number database.

R84: Account Number Structure Error

The account number is malformed (wrong length, invalid characters).

  • When it fires: During validation or settlement.
  • What it means: Data quality issue.
  • How to handle it: Sanitize and validate account numbers on input.

Building Retry Logic Around Return Codes

Here's a simple decision tree for handling returns:

Return Code Retry? Timeline Alternate Action
R01 Yes 2–3 days Switch payout method
R02, R03, R29 No N/A Request new account
R10 No Dispute mode Gather proof of auth
R82, R83, R84 No Immediate Fix data, resubmit

The key insight: not all returns are retryable. R01 (insufficient funds) might resolve itself. R02 (account closed) never will.


Decoding ACH return codes programmatically? The ACH Return Codes API returns the full Nacha R01–R85 set with plain-language descriptions and handling guidance.

Top comments (0)