ACH Reference
ACH Return Codes: Complete List (R01–R85) & Meanings
An ACH return code is a standardized three-character code assigned by NACHA that the receiving bank (RDFI) sends back to the originating bank (ODFI) to explain why an ACH entry could not be posted. This reference lists every return code from R01 through R85 with its meaning, NACHA threshold impact, and the correct next step for originators.
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.
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
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.
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 / OFAC Instruction
Funds unavailable due to RDFI action, legal freeze, or OFAC
The funds in the account are unavailable due to actions taken by the RDFI or legal action (garnishment, court order, fraud investigation). R16 is also returned when access to the account is restricted following OFAC instruction.
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. If OFAC-related, escalate to compliance immediately.
Format, Data & Entry Errors
These returns indicate a problem with how the entry itself was constructed rather than with the receiver’s account. They are almost always fixable at the origination layer — a persistent pattern here points to a file-formatting or data-hygiene defect worth correcting at the source.
R17
File Record Edit Criteria / Questionable Circumstances
Entry contains invalid data the RDFI cannot process
The entry contains a field the RDFI is unable to process, or the RDFI has identified an entry with an invalid account number that appears to have been initiated under questionable circumstances. The RDFI describes the reason in the addenda record.
Next steps: Read the addenda record for the specific defect. Correct the field and reoriginate. If the return cites questionable circumstances, treat it as a potential fraud signal and review the merchant before reoriginating.
R21
Invalid Company Identification
Company ID number in the entry is not valid
The identification number used in the Company Identification Field is not valid. Applies to CIE and corporate entries.
Next steps: Correct the Company Identification field in your origination profile and reoriginate. A systemic R21 pattern means your originator profile is misconfigured.
R23
Credit Entry Refused by Receiver
Receiver actively refused a credit you sent
The receiver refused the credit entry — commonly because the amount is incorrect, the entry is a duplicate, or the receiver has no relationship with the originator. Relevant to MCA funders sending funding disbursements.
Next steps: Contact the receiver to confirm the correct amount and account before reoriginating. Do not simply resend the identical entry.
R24
Duplicate Entry
RDFI received an apparent duplicate of a prior entry
The RDFI has received what appears to be a duplicate entry — same amount, trace number, and other identifying detail as a previously received entry.
Next steps: Confirm whether a genuine duplicate was transmitted before doing anything else. If the second debit was legitimate and distinct, contact your processor rather than reoriginating blindly — a duplicate debit that posts is a fast route to an R10.
R26
Mandatory Field Error
A required field is missing or improperly formatted
A mandatory field in the entry is missing or contains improperly formatted or incorrect data. Grouped with R25 (Addenda Error) and R27 (Trace Number Error) as file-construction defects.
Next steps: Correct the field and reoriginate. Repeated R25/R26/R27 returns indicate a defect in your file generation — fix it at the source rather than per-entry.
Improper Entry & Permissible Returns
Returns the RDFI uses to reverse entries that should never have been originated in the form they took. R35 and R36 in particular indicate an SEC code or transaction-type error on your side.
R31
Permissible Return Entry (CCD and CTX only)
RDFI returned a corporate entry with ODFI agreement
The RDFI has requested, and the ODFI has agreed to accept, a return of a CCD or CTX entry beyond the normal return deadline. Only available for corporate SEC codes.
Next steps: This return was agreed to by your processor. Confirm the circumstances with GoACH and pursue the funds directly with the merchant.
R35
Return of Improper Debit Entry
A debit was sent where debits are not permitted
A debit entry was transmitted in an application where debit entries are not permitted — for example, a debit sent under an SEC code that supports credits only.
Next steps: Review the SEC code applied to the entry against the transaction type. See the SEC codes guide to confirm the correct code before reoriginating.
R36
Return of Improper Credit Entry
A credit was sent where credits are not permitted
A credit entry was transmitted in an application that permits debits only — the mirror image of R35.
Next steps: Correct the SEC code or transaction type and reoriginate. Persistent R35/R36 returns mean your SEC code mapping is wrong at the product level.
Quick Reference
All ACH return codes (R01–R85) at a glance
The complete NACHA return code list. Codes R01–R33 are the ones most originators encounter day to day. R34–R47 apply to limited-participation, ENR (automated enrollment), and government applications. R50–R53 apply to re-presented check (RCK) entries. R61–R85 are dishonored and contested returns exchanged between financial institutions rather than originated by you.
| Code | Name | Category | Retry? |
|---|---|---|---|
| Everyday origination returns (R01–R33) | |||
| R01 | Insufficient Funds | Balance | Yes |
| R02 | Account Closed | Administrative | No |
| R03 | No Account / Unable to Locate Account | Administrative | No — fix data first |
| R04 | Invalid Account Number Structure | Administrative | No — fix data first |
| R05 | Unauthorized Debit to Consumer Account Using Corporate SEC Code | Unauthorized | No |
| R06 | Returned per ODFI’s 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 Originator Not Known / Not Authorized | Unauthorized | No |
| R11 | Entry Not in Accordance with Terms of Authorization | 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 or Unable to Continue | Special | Contact customer |
| R15 | Beneficiary or Account Holder Deceased | Special | No |
| R16 | Account Frozen / Entry Returned per OFAC Instruction | Special | No |
| R17 | File Record Edit Criteria / Questionable Circumstances | Format | After correction |
| R18 | Improper Effective Entry Date | Format | After correction |
| R19 | Amount Field Error | Format | After correction |
| R20 | Non-Transaction Account | Account | No — get new account |
| R21 | Invalid Company Identification | Format | After correction |
| R22 | Invalid Individual ID Number | Format | After correction |
| R23 | Credit Entry Refused by Receiver | Dispute | Contact receiver |
| R24 | Duplicate Entry | Format | No — verify first |
| R25 | Addenda Error | Format | After correction |
| R26 | Mandatory Field Error | Format | After correction |
| R27 | Trace Number Error | Format | After correction |
| R28 | Routing Number Check Digit Error | Account | No — correct routing |
| R29 | Corporate Customer Advises Not Authorized | Unauthorized | No |
| R30 | RDFI Not Participant in Check Truncation Program | Program | No |
| R31 | Permissible Return Entry (CCD and CTX only) | Permissible | No |
| R32 | RDFI Non-Settlement | Program | Contact processor |
| R33 | Return of XCK Entry | Program | No |
| Limited participation, improper entries & ENR automated enrollment (R34–R47) | |||
| R34 | Limited Participation DFI | Program | No |
| R35 | Return of Improper Debit Entry | Improper | No — fix SEC code |
| R36 | Return of Improper Credit Entry | Improper | No — fix SEC code |
| R37 | Source Document Presented for Payment | Check conversion | No |
| R38 | Stop Payment on Source Document | Check conversion | No |
| R39 | Improper Source Document | Check conversion | No |
| R40 | Return of ENR Entry by Federal Government Agency | ENR | No |
| R41 | Invalid Transaction Code (ENR only) | ENR | After correction |
| R42 | Routing Number / Check Digit Error (ENR only) | ENR | After correction |
| R43 | Invalid DFI Account Number (ENR only) | ENR | After correction |
| R44 | Invalid Individual ID Number (ENR only) | ENR | After correction |
| R45 | Invalid Individual Name / Company Name (ENR only) | ENR | After correction |
| R46 | Invalid Representative Payee Indicator (ENR only) | ENR | After correction |
| R47 | Duplicate Enrollment (ENR only) | ENR | No |
| Re-presented check entries — RCK (R50–R53) | |||
| R50 | State Law Affecting RCK Acceptance | RCK | No |
| R51 | Item Related to RCK Entry is Ineligible or RCK Entry is Improper | Unauthorized | No |
| R52 | Stop Payment on Item Related to RCK Entry | RCK | No |
| R53 | Item and RCK Entry Presented for Payment | RCK | No |
| Dishonored and contested returns — bank to bank (R61–R85) | |||
| R61 | Misrouted Return | Dishonored | N/A |
| R62 | Return of Erroneous or Reversing Debit | Dishonored | N/A |
| R67 | Duplicate Return | Dishonored | N/A |
| R68 | Untimely Return | Dishonored | N/A |
| R69 | Field Error(s) | Dishonored | N/A |
| R70 | Permissible Return Entry Not Accepted / Return Not Requested by ODFI | Dishonored | N/A |
| R71 | Misrouted Dishonored Return | Contested | N/A |
| R72 | Untimely Dishonored Return | Contested | N/A |
| R73 | Timely Original Return | Contested | N/A |
| R74 | Corrected Return | Contested | N/A |
| R75 | Return Not a Duplicate | Contested | N/A |
| R76 | No Errors Found | Contested | N/A |
| R77 | Non-Acceptance of R62 Dishonored Return | Contested | N/A |
| R80 | IAT Entry Coding Error | IAT | After correction |
| R81 | Non-Participant in IAT Program | IAT | No |
| R82 | Invalid Foreign Receiving DFI Identification | IAT | After correction |
| R83 | Foreign Receiving DFI Unable to Settle | IAT | No |
| R84 | Entry Not Processed by Gateway | IAT | No |
| R85 | Incorrectly Coded Outbound International Payment | IAT | After correction |
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.
How many ACH return codes are there?
NACHA defines roughly 80 return codes running from R01 to R85, though the numbering is not continuous. Most originators encounter only about a dozen in practice: R01, R02, R03, R04, R05, R07, R08, R09, R10, R11, R16, R20 and R29 cover the overwhelming majority of real-world returns. Codes above R60 are dishonored and contested returns exchanged between financial institutions rather than returns you originate.
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.
What is the difference between R10 and R11?
R10 means the receiver states there was never valid authorization — the originator is not known to them or never had permission to debit. R11 means authorization does exist, but this particular entry did not match its terms, such as a wrong amount or an incorrect debit date. R10 counts toward the 0.5% unauthorized threshold; R11 does not. R11 is also correctable — resolve the discrepancy with the customer and you may reoriginate, which is never true of R10.
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. NACHA limits reinitiation of a returned debit to two attempts following the original entry. 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.
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.
Return code definitions follow the NACHA Operating Rules & Guidelines. Return rate thresholds cited are the NACHA-published limits in effect as of 2026. Last reviewed August 2026.
Related: ACH SEC Codes Guide · High-Risk ACH Processing · ACH Payment Processor · High-Risk ACH FAQ