ACH Return Reason Code Lookup
Look up any Nacha return reason code, R01 to R85 — Nacha's own definition, which Standard Entry Class codes it applies to, its ISO 20022 camt.053 mapping, and what to do next. Where Nacha publishes the return time frame or the reinitiation position, the card states it and cites the page. Where it does not, the card says so rather than guessing. 71 codes.
The Nacha Operating Rules are the governing text. Nacha sells them, and they were not used here. Definitions are taken from Nacha's own public ISO 20022 mapping guide and from the Nacha rule pages listed on each card, corroborated against the US Treasury Green Book and the Federal Reserve's FedGlobal manual. Ten public documents were reviewed; where they are silent, the card says so, and says it of those documents rather than of everything Nacha has published.
No codes match your search. , or try the ACH return-code table in the direct-debit reference →
Funds
Insufficient funds
Available and/or cash reserve balance is not sufficient to cover the dollar value of the debit Entry.
Account & routing
Account Closed
A previously active account has been closed by action of the customer or the RDFI.
Account & routing
No Account / Unable to Locate Account
Account number structure is valid and it passes the check digit validation, but the account number does not correspond to the individual identified in the Entry, or the account number designated is not an existing account i.e., not an open account.
Account & routing
Invalid Account Number Structure
Account number structure is not valid.
Authorization & consumer dispute
Unauthorized Debit to Consumer Account Using Corporate SEC Code
CCD or CTX debit Entry was transmitted to a Consumer Account of the Receiver and was not authorized by the Receiver.
RDFI, regulatory & deceased
Returned per ODFI's Request
ODFI has requested that the RDFI return an Erroneous Entry, or a credit Entry originated without the authorization of the Originator.
Authorization & consumer dispute
Authorization Revoked by Customer
RDFI's customer (the Receiver) revoked the authorization previously provided to the Originator for this debit Entry.
Authorization & consumer dispute
Payment Stopped
The Receiver has placed a stop payment order on this debit Entry e.g., recurring debit.
Funds
Uncollected Funds
A sufficient book or ledger balance exists to satisfy the dollar value of the transaction (i.e., uncollected checks), but the available balance is below the dollar value of the debit entry.
Authorization & consumer dispute
Customer Advises Originator is Not Known to Receiver and/or Originator is Not Authorized by Receiver to Debit Receiver’s Account
RDFI has been notified by the Receiver that the Receiver does not know the identity of the Originator; has no relationship with the Originator; or has not authorized the Originator to debit his account.
Authorization & consumer dispute
Customer Advises Entry Not in Accordance with the Terms of the Authorization
The RDFI has been notified by the Receiver that the Originator and the Receiver have a relationship and an authorization to debit exists, but there is an error or defect in the payment such that the entry does not conform to the terms of authorization (for example, the entry is for an amount different than authorized; the entry was initiated for settlement earlier than authorized; the entry is part of an Incomplete Transaction; the debit entry was improperly reinitiated; the Reversing Entry was improperly initiated by the Originator or ODFI; the Receiver did not affirmatively initiate a Subsequent Entry in accordance with the terms of the Standing Authorization.
Account & routing
Account Sold to Another DFI
A financial institution received an Entry to an account that was sold to another financial institution.
Account & routing
Invalid ACH Routing Number
Entry contains a Receiving DFI Identification or Gateway Identification that is not a valid ACH routing number.
RDFI, regulatory & deceased
Representative Payee Deceased or Unable to Continue in That Capacity
Representative payee is either deceased or unable to continue in that capacity. The beneficiary is not deceased.
RDFI, regulatory & deceased
Beneficiary or Account Holder (Other Than a Representative Payee) Deceased
(1) The beneficiary is deceased, or (2) The account holder is deceased.
RDFI, regulatory & deceased
Account Frozen / Entry Returned Per OFAC Instruction
(1) Access to the account is restricted due to specific action taken by the RDFI or by legal action; or (2) OFAC has instructed the RDFI or Gateway to return the Entry.
RDFI, regulatory & deceased
File Record Edit Criteria / Entry with Invalid Account Number Initiated Under Questionable Circumstances / Return of Improperly Initiated Reversal
(1) Field(s) cannot be processed by RDFI; (2) the Entry contains an invalid DFI Account Number (account closed / no account / unable to located account / invalid account number) and is believed by the RDFI to have been initiated under questionable circumstances; or (3) either the RDFI or the Receiver has identified a reversing Entry as one that was improperly initiated by the Originator or ODFI. If the Entry cannot be processed by the RDFI, the field(s) causing the error must be identified In the Addenda Information field of the Return. If the RDFI uses R17 to return an entry that contains an invalid DFI Account Number and believes that it was initiated under questionable circumstances, the RDFI must insert “QUESTIONABLE” within the first 12 positions of the Addenda Information field.
Format & data
Improper Effective Entry Date
(1) The effective Entry date for a credit Entry is more than two Banking Days after the Banking Day of processing as established by the Originating ACH Operator; or (2) The Effective Entry Date for a debit Entry is more than one Banking Day after the processing date.
Format & data
Amount Field Error
(1) Amount field is non-numeric. (2) Amount field is not zero in a Prenotification, DNE, ENR, Notification of Change, refused Notification of Change, or zero dollar CCD, CTX, or IAT Entry. (3) Amount field is zero in Entry other than a Prenotification, DNE, ENR, Notification of Change, Return, Dishonored Return, contested Dishonored Return, or zero dollar CCD, CTX, or IAT Entry. (4) Amount field is greater than $25,000 for ARC, BOC, POP Entries.
Account & routing
Non-Transaction Account
ACH Entry to a non-Transaction Account i.e., an account against which transactions are prohibited or limited.
Format & data
Invalid Company Identification
The Identification Number used in the Company Identification Field is not valid.
Format & data
Invalid Individual ID Number
The Receiver has indicated to the RDFI that the number with which the Originator was identified is not correct.
RDFI, regulatory & deceased
Credit Entry Refused by Receiver
Any credit Entry that is refused by the Receiver may be returned by the RDFI.
Format & data
Duplicate Entry
The RDFI has received what appears to be a duplicate Entry i.e., the trace number, date, dollar amount and/or other data matches another transaction.
Format & data
Addenda Error
Addenda record value indicator is incorrect. Addenda Type Code is invalid, out of sequence, or missing. Number of Addenda Records exceeds allowable maximum. Addenda Sequence Number is invalid.
Format & data
Mandatory Field Error
Erroneous data or missing data in a mandatory field.
Format & data
Trace Number Error
(1) Original Entry Trace Number is not present in the Addenda Record on a Return or Notification of Change Entry; or (2) Trace Number of an Addenda Record is not the same as the Trace Number of the preceding Entry Detail Record.
Format & data
Routing Number Check Digit Error
The Check digit for a routing number is not valid.
Authorization & consumer dispute
Corporate Customer Advises Not Authorized
The RDFI has been notified by the Receiver (non-consumer) that a specific Entry has not been authorized by the Receiver.
RDFI, regulatory & deceased
RDFI Not Participant in Check Truncation Program
RDFI does not participate in a Check truncation program.
RDFI, regulatory & deceased
Permissible Return Entry (CCD and CTX) only
RDFI may return a CCD or CTX Entry that the ODFI agrees to accept.
RDFI, regulatory & deceased
RDFI Non-Settlement
RDFI is not able to settle the Entry.
RDFI, regulatory & deceased
Return of XCK Entry
This Return Reason Code may only be used to return XCK Entries and is at he [sic] RDFI's sole discretion.
RDFI, regulatory & deceased
Limited Participation DFI
RDFI's participation has been limited by a federal or state advisor e.g., bank closure.
Format & data
Return of Improper Debit Entry
Debit Entries (with the exception of Reversing Entries) are not permitted for CIE Entries or to loan accounts.
Format & data
Return of Improper Credit Entry
ACH Entries (with the exception of Reversing Entries) are not permitted for use with ARC, BOC, POP, RCK, TEL, WEB, and XCK.
Check conversion & RCK
Source Document Presented for Payment
The source document to which an ARC, BOC, or POP Entry relates has been presented for payment.
Check conversion & RCK
Stop Payment on Source Document
RDFI determines a stop payment order has been placed on the source document to which the ARC or BOC Entry relates.
Check conversion & RCK
Improper Source Document / Source Document Presented for Payment
RDFI determines that: (1) the source document used for an ARC, BOC, or POP Entry to its Receiver's account is improper, or (2) an ARC, BOC, or POP Entry and the source document to which the Entry relates have been presented for payment and posted to the Receiver's account.
Federal enrolment (ENR)
Return ENR Entry by Federal Government Agency
This Return Reason Code may only be used to return ENR Entries and is at the Federal Government Agency's sole discretion.
Federal enrolment (ENR)
Invalid Transaction Code
Either the Transaction Code included in Field 3 of the Addenda Record does not conform to the ACH Record Format Specifications contained in Appendix Three (ACH Record Format Specifications) or it is not appropriate with respect to an Automated Enrollment Entry.
Federal enrolment (ENR)
Routing Number / Check Digit Error
The Routing Number and the Check Digit included in Field 3 of the Addenda Record is either not a valid number or it does not conform to the Modulus 10 formula.
Federal enrolment (ENR)
Invalid DFI Account Number
The Receiver's account number included in Field 3 of the Addenda must include at least one alphameric character.
Federal enrolment (ENR)
Invalid Individual ID Number / Identification Number
The Individual ID Number / Identification Number provided in Field 3 of the Addenda Record does not match a corresponding ID number in the Federal Government Agency's records.
Federal enrolment (ENR)
Invalid Individual Name / Company Name
The name of the consumer or company provided in Field 3 of the Addenda Record either does not match a corresponding name in the Federal Government Agency's records or fails to include at least one alphameric character.
Federal enrolment (ENR)
Invalid Representative Payee Indicator
The Representative Payee Indicator Code included in Field 3 of the Addenda Record has been omitted or it is not consistent with the Federal Government Agency's records.
Federal enrolment (ENR)
Duplicate Enrollment
The Entry is duplicate of an Automated Enrollment Entry previously initiated by a DFI.
Check conversion & RCK
State Law Affecting RCK Acceptance
(1) The RDFI is located in a state that has not adopted Revised Article 4 of the Uniform Commercial Code (1990 Official Text) and has not revised its customer agreements to allow for Electronic presentment; or (2) The RDFI is located within a state that requires all canceled Checks to a specific type of account to be returned to the Receiver within the periodic statement.
Check conversion & RCK
Item related to RCK Entry is Ineligible or RCK Entry is Improper
A RCK Entry considered to be ineligible or improper.
Check conversion & RCK
Stop Payment on Item Related to RCK Entry
A stop payment order has been placed on the item to which the RCK Entry relates.
Check conversion & RCK
Item and RCK Entry Presented for Payment
In addition to an RCK Entry, the item to which the RCK Entry relates has also been presented for payment.
Dishonored return (ODFI)
Misrouted Return
The financial institution preparing the Return Entry (the RDFI of the original Entry) has placed the incorrect Routing Number in the Receiving DFI Identification field.
Dishonored return (ODFI)
Return of Erroneous or Reversing Debit
The Originator's / ODFI's use of the reversal process has resulted in, or failed to correct, an unintended credit to the Receiver.
Dishonored return (ODFI)
Duplicate Return
The ODFI has received more than one Return for the same Entry.
Dishonored return (ODFI)
Untimely Return
The Return Entry has not been sent within the time frame established by these Rules.
Dishonored return (ODFI)
Field Error(s)
One or more of the field requirements are incorrect.
Dishonored return (ODFI)
Permissible Return Entry Not Accepted / Return Not Requested by ODFI
The ODFI has received a Return Entry identified by the RDFI as being returned with the permission of, or at the request of, the ODFI, but the ODFI has not agreed to accept the Entry or has not requested the return of the Entry.
Contested dishonored return (RDFI)
Misrouted Dishonored Return
The financial institution preparing the dishonored Return Entry (the ODFI of the original Entry) has placed the incorrect Routing Number in the Receiving DFI Identification field.
Contested dishonored return (RDFI)
Untimely Dishonored Return
The dishonored Return Entry has not been sent within the designated time frame.
Contested dishonored return (RDFI)
Timely Original Return
The RDFI is certifying that the original Return Entry was sent within the timeframe designated in these Rules.
Contested dishonored return (RDFI)
Corrected Return
The RDFI is correcting a previous Return Entry that was dishonored using Return Reason Code R69 (Field Error(s)) because it contained incomplete or incorrect information.
Contested dishonored return (RDFI)
Return Not a Duplicate
The Return Entry was not a duplicate of an Entry previously returned by the RDFI.
Contested dishonored return (RDFI)
No Errors Found
The original Return Entry did not contain the errors indicated by the ODFI in the dishonored Return Entry.
Contested dishonored return (RDFI)
Non-Acceptance of R62 Dishonored Return
The RDFI returned both the Erroneous Entry and the related Reversing Entry, or the funds relating to the R62 dishonored Return are not recoverable from the Receiver.
International (IAT)
IAT Entry Coding Error
The IAT Entry is being returned due to one or more of the following conditions: ▪ Invalid DFI / Bank Branch Country Code ▪ Invalid DFI / Bank Identification Number Qualifier ▪ Invalid Foreign Exchange Indicator ▪ Invalid ISO Originating Currency Code ▪ Invalid ISO Destination Currency Code ▪ Invalid ISO Destination Country Code ▪ Invalid Transaction Type Code
International (IAT)
Non-Participant in IAT Program
The IAT Entry is being returned because the Gateway does not have an agreement with either the ODFI or the Gateway's customer to transmit Outbound IAT Entries.
International (IAT)
Invalid Foreign Receiving DFI Identification
The reference used to identify the Foreign Receiving DFI of an Outbound IAT Entry is invalid.
International (IAT)
Foreign Receiving DFI Unable to Settle
The IAT Entry is being returned due to settlement problems in the foreign payment system.
International (IAT)
Entry Not Processed by Gateway
For Outbound IAT Entries, the Entry has not been processed and is being returned at the Gateway's discretion because the processing of such Entry may expose the Gateway to excessive risk.
International (IAT)
Incorrectly Coded Outbound International Payment
The RDFI/Gateway has identified the Entry as an Outbound internal [sic] payment and is returning the Entry because it bears an SEC Code that lacks information required by the Gateway for OFAC Compliance. [For Gateway use only.]
Sanctions (not yet in force)
Entry Returned Due to RDFI's Sanctions Compliance Obligations
The RDFI/Gateway has determined that the Entry must be returned to comply with its sanctions compliance obligations.
What each card states, and what it deliberately does not
Stated, with the source named on the card: Nacha's definition and the Standard Entry Class scope, from Nacha's public ISO 20022 return-mapping guide; the camt.053 reason code the guide maps it to; the return time frame and the reinitiation position where a public Nacha rule page states them — the 60-day window Nacha states for R11 and the Written Statement of Unauthorized Debit it requires for R10 and R11, R11's correct-and-resubmit route, the two-day frame Nacha's own pages refer to; and whether the code counts toward Nacha's unauthorized return rate.
Not stated, because none of the ten public documents reviewed here states it: the numeric reinitiation limit for funds-related returns — the Nacha rule pages reviewed confirm reinitiation is restricted under the Rules and must carry RETRY PYMT, but neither the count nor the window appears in them. The card says that rather than repeating a figure from a bank's summary. This is a statement about the documents reviewed, not a claim that Nacha has published the figure nowhere. Operator actions on each card are PaymentBrief guidance and are labelled as such.
Definitions from the Nacha ISO 20022 Guide to Mapping U.S. ACH Return Items and Notifications of Change, August 2023, Version 2.01; rule positions from Nacha's published rule pages; titles corroborated against the US Treasury Green Book (Chapter 4, Returns) and the Federal Reserve FedGlobal ACH Payments Origination Manual (3 August 2026). Confirm the current Nacha Operating Rules with your ODFI before acting on a specific case.