ACH Reference

ACH Return Codes: Complete Reference Guide

ACH return codes are standardized three-character codes assigned by NACHA that identify why an ACH payment was returned by the receiving bank. This reference covers all major R-codes with descriptions, NACHA threshold impact, and recommended next steps for high-risk ACH originators.

Get ACH processing with real-time return monitoring →

NACHA Return Rate Thresholds

NACHA sets three return rate limits that all ACH originators must stay below. Exceeding them triggers processor intervention and potential account suspension.

Overall

15%

All return codes combined

Administrative

R02, R03, R04 — account issues

Unauthorized

0.5%

R05, R07, R10, R29, R51 — strictest limit

Insufficient Funds & Balance Issues

The most common return category for MCA daily debits and recurring billing. R01 alone typically accounts for 60–80% of all returns in high-volume origination environments.

R01

Insufficient Funds

Available balance is below the debit amount

The available and/or cash reserve balance is not sufficient to cover the dollar value of the debit entry. The account is open and valid — there are simply not enough funds at the time of processing. R01 does not count toward the unauthorized return threshold.

Next steps: Retry after 1–3 business days. For MCA daily debits, GoACH’s intelligent retry engine uses account-level signals to optimize retry timing and reduce repeated R01s. After 2–3 failed attempts, escalate to direct customer contact. Repeated R01s can escalate to R02 — address proactively.

R09

Uncollected Funds

Book balance sufficient but holds reduce available balance

Sufficient book balance exists, but payment holds on the account reduce the available balance below the debit amount. A temporary condition unlike R01.

Next steps: Retry in 1–2 business days once holds are lifted. Advise the customer to contact their bank about any associated return fees.

Account Issues — Administrative Returns Admin threshold: 3%

R02, R03, and R04 count toward NACHA’s 3% administrative return rate threshold. High administrative return rates signal poor account validation. For WEB debits, the 2022 NACHA account validation rule exists specifically to reduce R03 and R04 returns.

R02

Account Closed Admin

A previously active account has been closed

A previously active account has been closed by the customer or the RDFI. R02 counts toward the administrative return rate threshold (3%).

Next steps: Do not retry on this account. Contact the customer to obtain new banking details. For MCA funders, an R02 following repeated R01s may signal the merchant closed the account to avoid debits — treat as a collections escalation.

R03

No Account / Unable to Locate Account Admin

Account number does not correspond to the account holder

The account number structure is valid and passes check digit validation, but does not correspond to the individual identified in the entry. Counts toward the 3% administrative return threshold.

Next steps: Contact the customer and confirm routing number, account number, and name on the account. Request a voided check. Submit a new payment with corrected information. High R03 rates indicate an account validation problem at enrollment.

R04

Invalid Account Number Admin

Account number structure is not valid

The account number structure is not valid — it may fail check digit validation or contain an incorrect number of digits. Counts toward the 3% administrative return threshold.

Next steps: Obtain the correct bank account number, request a voided check, and submit a new payment. Do not retry with the same account number.

R13

RDFI Not Qualified / Invalid ACH Routing Number

Routing number is incorrect or institution not ACH-qualified

The financial institution is not qualified to participate in ACH, or the routing number does not belong to an ACH-participating institution.

Next steps: Verify the routing number against the ABA routing directory. Confirm with the customer and submit with the correct routing number.

R28

Routing Number Check Digit Error

Routing number fails check digit validation

The routing number fails the mathematical check digit validation — catches transposed or mistyped routing numbers.

Next steps: Correct the routing number and reprocess. Confirm with the customer if no error is apparent.

R12

Branch Sold to Another DFI

Account transferred to a new financial institution

The customer’s bank branch has been sold to another financial institution. The RDFI no longer maintains the account.

Next steps: Obtain the new routing and account numbers from the customer and submit a new transaction. Update any recurring payment schedules.

R20

Non-Transaction Account

Account is not set up to allow ACH transfers

The ACH entry is destined for a non-transaction account — typically a savings account or money market account that does not permit ACH debits.

Next steps: Ask for a different account that supports ACH transfers, typically a checking account. Do not retry on the same account.

Unauthorized Returns Unauthorized threshold: 0.5%

The most consequential return category. R05, R07, R10, R29, and R51 all count toward NACHA’s 0.5% unauthorized return rate threshold — the strictest of the three. Each unauthorized return should be treated as a compliance event. Do not retry any of these codes.

R05

Unauthorized Debit to Consumer Account Unauthorized

CCD transaction posted to a consumer account

A CCD (corporate) transaction was posted to a consumer account. The account holder has advised their bank the debit was not authorized. Cannot be re-submitted. Return window: 60 calendar days from settlement date.

Next steps: Immediately suspend any recurring schedules. Verify whether the account is a business or consumer account. If it’s a consumer account, the SEC code must be changed to PPD or WEB. Do not resubmit as CCD.

R07

Authorization Revoked by Customer Unauthorized

Consumer has formally revoked ACH authorization

A consumer who previously authorized ACH payment has revoked authorization. The consumer has notified their bank. Return window: 60 calendar days from settlement date.

Next steps: Immediately suspend all recurring schedules for this account. Do not resubmit — originating after authorization has been revoked is a NACHA violation. Retain original authorization records in case of dispute.

R10

Customer Advises Not Authorized Unauthorized

Account owner signed a Written Statement of Unauthorized Debit

The account owner has told their bank the transaction was unauthorized and signed a Written Statement of Unauthorized Debit (WSUD). The most commonly filed unauthorized return code. Return window: 60 calendar days from settlement. WSUD may be filed up to two years after settlement in some cases.

Next steps: Immediately suspend recurring schedules. Retain your authorization documentation — if you have valid authorization on file, you can dispute the return through your processor. High R10 rates indicate an authorization documentation or customer communication problem.

R29

Corporate Customer Advises Not Authorized Unauthorized

Non-consumer receiver disputes authorization

The RDFI has been notified by a non-consumer receiver (business) that the originator has not been authorized to debit their account. For MCA funders, an R29 means the merchant is formally disputing the debit authorization.

Next steps: Immediately suspend recurring schedules. A bank letter will be required to lift the R29 block. Review your MCA agreement to confirm the ACH debit authorization is properly documented and signed.

R51

Item Related to RCK Entry is Ineligible Unauthorized

Improper re-presented check entry

Used for RCK (Re-presented Check Entry) transactions that are ineligible or improperly originated. Counts toward the 0.5% unauthorized threshold.

Next steps: Review RCK eligibility requirements. Do not resubmit. Contact your processor for guidance.

Payment Stopped & Authorization Disputes

The customer has taken action to stop a specific payment or dispute its terms. These do not count toward the unauthorized threshold but require immediate action.

R08

Payment Stopped

Customer placed a stop payment on this transaction

The receiver has placed a stop payment on this specific transaction with their bank. The authorization may still be valid, but this payment has been stopped.

Next steps: Contact the customer to resolve. The customer must contact their bank to lift the stop payment and provide a bank letter confirming this before resubmission.

R11

Entry Not in Accordance with Terms of Authorization

Authorization exists but payment terms don’t match

An authorization exists but there is an error or defect in the payment that does not conform to the terms — for example, a debit for an amount or date different from what was authorized. Distinct from R10.

Next steps: Review the authorization terms against the transaction details. Contact the customer. They must contact their bank to lift the block and provide confirmation before resubmission.

R06

Return per ODFI’s Request

Your processor requested the return

The ODFI (your processor) has requested that the RDFI return the entry. Processor-initiated — typically used when a duplicate entry is identified or an entry needs to be recalled.

Next steps: Contact your processor (GoACH) for context. The customer may not need to take any action.

Deceased, Frozen & Special Circumstances

Circumstances that permanently or temporarily prevent processing. Most require obtaining alternative payment arrangements.

R14

Representative Payee Deceased or Unable to Continue

Representative payee is deceased or incapacitated; beneficiary is not

The representative payee is either deceased or unable to continue. The beneficiary themselves is not deceased.

Next steps: Contact the appropriate party. A new representative payee may need to be established.

R15

Beneficiary or Account Holder Deceased

The primary account holder has died

The beneficiary or primary account holder is deceased. The account cannot accept further transactions.

Next steps: Immediately cease all transactions on this account. Contact the estate or next of kin.

R16

Account Frozen

Funds unavailable due to RDFI action or legal freeze

The funds in the account are unavailable due to actions taken by the RDFI or legal action (garnishment, court order, fraud investigation).

Next steps: Do not retry. Cannot process until unfrozen. Obtain an alternative payment method. For MCA funders, R16 may indicate legal proceedings involving the merchant.

Quick Reference

All ACH return codes at a glance

Code	Name	Category	Retry?
R01	Insufficient Funds	Balance	Yes
R02	Account Closed	Administrative	No
R03	No Account / Unable to Locate	Administrative	No — fix data first
R04	Invalid Account Number	Administrative	No — fix data first
R05	Unauthorized Debit to Consumer Account	Unauthorized	No
R06	Return per ODFI Request	Processor	Contact processor
R07	Authorization Revoked by Customer	Unauthorized	No
R08	Payment Stopped	Dispute	After resolution
R09	Uncollected Funds	Balance	Yes — after holds lift
R10	Customer Advises Not Authorized	Unauthorized	No
R11	Not in Accordance with Authorization Terms	Dispute	After resolution
R12	Branch Sold to Another DFI	Account	No — get new details
R13	Invalid ACH Routing Number	Account	No — fix routing
R14	Representative Payee Deceased/Unable	Special	Contact customer
R15	Beneficiary or Account Holder Deceased	Special	No
R16	Account Frozen	Special	No
R20	Non-Transaction Account	Account	No — get new account
R28	Routing Number Check Digit Error	Account	No — correct routing
R29	Corporate Customer Advises Not Authorized	Unauthorized	No
R51	Item Related to RCK Entry is Ineligible	Unauthorized	No

Red = unauthorized threshold (0.5%) · Yellow = administrative threshold (3%) · Teal = general return only

FAQ

ACH return code FAQ

What is an ACH return code?

An ACH return code is a standardized three-character code (e.g., R01, R10) assigned by NACHA that identifies why an ACH payment was returned by the receiving bank. When an ACH debit or credit cannot be processed, the RDFI sends back a return entry with the applicable code. Understanding return codes is essential for maintaining NACHA compliance and managing payment operations.

Which ACH return codes count toward the NACHA unauthorized return rate?

Five return codes count toward NACHA’s 0.5% unauthorized return rate threshold: R05, R07, R10, R29, and R51. Exceeding 0.5% of transactions with these codes can trigger NACHA intervention and processor action. Each unauthorized return should be treated as a compliance event, not just a payment failure.

Can I retry a transaction after an ACH return?

It depends on the return code. R01 (Insufficient Funds) and R09 (Uncollected Funds) can be retried. Unauthorized returns (R05, R07, R10, R29) must not be retried — resubmitting after an unauthorized return is a NACHA Operating Rules violation. Administrative returns (R02, R03, R04) should not be retried until the underlying account data issue is corrected. See our SEC codes guide →

What is the return window for ACH returns?

Standard ACH returns must be submitted within 2 banking days of settlement. Unauthorized returns (R05, R07, R10, R29) have an extended return window of 60 calendar days from settlement. This extended window is why maintaining proper authorization documentation is critical — an R10 can arrive 60 days after the original transaction.

How does GoACH monitor ACH return rates?

GoACH monitors return rates in real time across all three NACHA thresholds — overall (15%), administrative (3%), and unauthorized (0.5%). Our AI risk engine tracks return patterns by SEC code, merchant, and batch, and sends anomaly alerts before you approach a threshold. For MCA daily debits, our intelligent retry logic is trained on CCD return code patterns to reduce R01 frequency. Learn more about high-risk ACH processing →

Real-Time Return Monitoring

Need help managing ACH return rates?

GoACH provides real-time return monitoring against all three NACHA thresholds, AI-driven return suppression, and NACHA-compliant ACH processing for high-risk businesses.

Apply for an ACH account →
View SEC codes guide →

About This Reference

This ACH return code reference is published by GoACH, a NACHA-compliant ACH payment processor operated by Unity FI Solutions LLC, headquartered in Charlotte, NC. GoACH specializes in high-risk ACH processing for merchant cash advance, credit repair, debt settlement, and collections — industries where return rate management is operationally critical.