ACH Return Codes (R01–R85) Explained: Meanings, Fixes, and Prevention Checklist

Use this guide to identify whether the return is funds, account status, authorization, or formatting-related and take the safest corrective step.

More banking guides Banking hub Banking code directory

TL;DR

✓ Treat ACH returns as categories: funds, account status, authorization, or format/routing issues.
✓ Confirm debit vs credit and who initiated it; next steps differ.
✓ Fix the underlying issue before retrying to avoid repeat returns and risk controls.
✓ Keep an audit trail: authorization, timestamps, and return details.

Quick Navigation

Symptoms Root Causes Step-by-step fixes What NOT to do If it persists Code directory Related guides & hubs FAQ References

Symptoms / When you see this

✓ ACH payment returns with R01/R03/R10-like codes.
✓ Payroll/vendor payments are returned.
✓ Repeat returns occur for the same customer/vendor.

Root causes (grouped)

✓ Funds-related (insufficient/uncollected funds).
✓ Account status (closed/frozen/no account).
✓ Authorization/mandate issues (customer disputes debit).
✓ Format/routing issues (invalid account/routing details).
✓ Timing issues (stop payment, return windows).

Step-by-step fixes (safe, prioritized)

✓ Confirm debit vs credit and the initiating party.
✓ Use the return category to choose the fix path (authorization vs details vs funds).
✓ If authorization-related, validate mandate and descriptor before retrying.
✓ If format-related, re-verify routing/account number and account type.
✓ If funds-related, coordinate a new payment date or method instead of repeated retries.

What NOT to do

✓ Do not repeatedly retry on authorization-related returns.
✓ Do not ignore high return rates; they can trigger risk controls.
✓ Do not store bank details insecurely.

If it persists (escalation checklist)

✓ Collect: return code, transaction details, authorization record, bank trace details.
✓ Confirm bank restrictions on the account.
✓ Use processor/bank support for repeated anomalies.

Code directory within this guide

✓ Return meanings can vary by processor mapping. Always use the return code and bank-provided context together.

Code	Meaning	Next step
R01	Insufficient funds — This code indicates the receiving account did not have enough available balance to cover the ACH debit entry at the time it was presented.	Follow the checklist on the code page
R02	Account closed — This code indicates the RDFI returned the entry because the receiving account is closed.	Follow the checklist on the code page
R03	No account/unable to locate — This code indicates the RDFI could not locate an account matching the information provided.	Follow the checklist on the code page
R04	Invalid account number — This code indicates the account number provided is invalid or fails the RDFI’s account validation requirements.	Follow the checklist on the code page
R05	Unauthorized debit — This code indicates the receiver has disputed the debit as unauthorized under applicable ACH authorization rules.	Follow the checklist on the code page
R06	Returned per ODFI request — This code indicates the entry was returned at the request of the originating depository financial institution.	Follow the checklist on the code page
R08	Stop payment — This code indicates the RDFI returned the entry because a stop payment order applies to the transaction.	Follow the checklist on the code page
R09	Uncollected funds — This code indicates there were funds in the account, but they were not collected/available for the ACH debit at the time of presentment.	Follow the checklist on the code page
R10	Customer advises unauthorized — This code indicates the receiver advised their bank that the debit entry was unauthorized, prompting the RDFI to return it.	Follow the checklist on the code page
R11	Check truncation entry returned — This code indicates the RDFI returned an ACH entry identified as a check truncation-related item that could not be processed as presented.	Follow the checklist on the code page
R12	Branch sold to another bank — This code indicates the receiving branch or institution relationship changed, and the entry could not be processed under the prior routing/branch structure.	Follow the checklist on the code page
R14	Invalid individual ID — This code indicates the individual identification information in the ACH entry was deemed invalid by the receiving institution’s processing rules.	Follow the checklist on the code page
R15	Beneficiary deceased — This code indicates the receiving institution returned the entry because records show the receiver/beneficiary is deceased.	Follow the checklist on the code page
R16	Account frozen — This code indicates the receiving account is frozen or restricted and cannot accept the entry as presented.	Follow the checklist on the code page

Tip: If your exact code isn’t listed, use the closest hub link above and browse related prefixes or message patterns.

FAQ

Is an ACH return the same as a card decline?

No. ACH returns happen after submission; card declines happen at authorization.

Can I retry immediately?

It depends on the return reason and your authorization rules. Repeated retries can create disputes.

What’s the most common cause?

Commonly funds-related or invalid details, but it varies by customer base and payment flow.

How do I reduce returns?

Validate bank details, keep clean authorization records, and use clear descriptors.

What if the customer says their account is fine?

Some returns are restrictions-related rather than funds. The return category helps narrow this.

Do return windows matter?

Yes. Some return types are time-sensitive; track dates and respond quickly.

Can banks block debits?

Yes, via restrictions or stop payments. The return category often indicates this.

When should I switch payment method?

If returns repeat, using another method can reduce repeated failures and customer friction.

References / Notes

✓ Bank/processor ACH return mappings
✓ Authorization/mandate records
✓ Banking compliance guidance