ACH Return Codes

When processing an ACH payment, you may come across an ACH return code and there are hundreds of reasons why a return code can occur. 

If working with an ACH payment client, like Sila, it’s important to understand what these ACH return codes mean. 

To help you get a better and understanding, and to prepare you to properly process ACH transfers, we’ve provided this article covering the following topics:

  • ACH Return Codes
  • How to process ACH return codes
  • And How to resolve ACH return codes

 

ACH Transfers

Whether or not you are familiar with the term “ACH transfer,” it is likely that you interact with them on a regular basis. If you are looking to send a bank-to-bank transfer of electronic cash funds, you are sending an ACH transfer. 

ACH transfers include this form of payment but are named after the Automated Clearing Hosue (ACH) as operated by the National Automated Clearing House Association (Nacha).  Nacha is the national ACH organizer for the United States and in 2019, it facilitated the transfer of $55.8 trillion. 

ACH transfers are used whenever money is being directly deposited or credited from or to a bank account. ACH debits will allow an originator to debit money (withdraw) from another bank account and deposit that money into the originator’s bank account. A similar process occurs for an ACH credit, but instead the money is deposited into (credited) into an account.

All ACH transfers exist within the U.S. and operate under USD and FDIC regulation. Therefore, the ACH network, or the Clearing House and the Federal Reserve, oversee all transactions and verify that each transaction is completed under Nacha rules and in accordance with compliance regulations.

 

ACH Return Codes

When sending any ACH transfer, there is the possibility that the money is returned. A return can happen for a variety of reasons. To simplify this process, returns will be given codes.

ACH return codes are specific, three-character codes that are denoted to mean a given event has occurred. These are specific to ACH transactions, but return codes do exist for other types of financial transactions as well. 

You can think of these return codes as a form of status for the return. Within each code are little bits of information that tell you what is lacking or causing a problem and caused the ACH debit or ACH credit to be returned to the sender. 

A return code usually suggests that there is a problem when sending the ACH transaction. Each return code expects a unique resolution. Therefore, there is no one ‘one size fits all’ approach to resolving ACH returns.

 

Common ACH Return Codes

There are hundreds of return codes that exist as provided by Nacha at this moment. These ACH return codes have been standardized, and all financial institutions operating using the ACH network will know and operate based on these codes.

Here are the most common return codes, listed in numerical order:

 

ACH Return Code R01 – Insufficient funds

The current cash reserve balance is not sufficient to cover the value of the debit entry. Deposit the appropriate amount of funds to resolve this return code. The transaction can be attempted two more times within 180 days of the original authorization date.

 

ACH Return Code R02 – Account Closed

The account in question was previously active but has been closed due to the actions of the receiving depository financial institution (RDFI) or the consumer. Contact the consumer to obtain different bank account information. You could also potentially withhold providing the goods or services that were agreed upon until payment has been settled. 

 

ACH Return Code R03 – No Account/Unable to Locate Account

The account number structure (format) is valid and it passes a digital validation check. However, the account number does not correspond with the individual identified in the return entry. Or, the account number is not designated as an open account. To resolve this, you’ll need to contact the consumer to confirm the account number, routing number, transit name, and the name on the bank account. If the new information provided does not match what was initially entered, make the changes and submit a new request. 

 

ACH Return Code R04 – Invalid Account Number

The account number structure is not valid and the entry may either contain an incorrect number of digits or fail the check digital validation. To resolve this, contact the customer to obtain the correct bank account number. Then, submit another request with the corrected account number. 

 

ACH Return Code R05 – Unauthorized Debit to Consumer Account Using Corporate SEC Code

An ACH debit was sent to a consumer account and the receiving account did not authorize the debit entry. To resolve this, contact the consumer and let them know that the debit was unauthorized in order to figure out why the transaction did not process. 

 

ACH Return Code R06 – Returned per ODFI’s Request

The ACH entry was returned by the originating depository financial institution (ODFI) and let the RDFI know. A return of this sort could be because the ACH entry was an erroneous entry or the credit entry originator did not have the authorization of the originator. To resolve this, the RDFI should agree to return the entry and indemnify the RDFI in accordance with the guidelines. 

 

ACH Return Code R07 – Authorization Revoked by Customer

The receiver who originally authorized the entry has revoked or withdrawn authorization for a given transaction. To resolve this, begin by suspending any recurring payments that exist with this bank account. Then, contact the consumer to resolve the issue around authorization. This might involve asking if the consumer wishes to continue a recurring payment, or it may involve seeking collections support. A different bank account can also be suggested if the bank account was changed or is faulty. If the same bank account is used, then the consumer will most likely need to call their bank to remove the block that is restricting transactions. 

 

ACH Return Code R08 – Payment Stopped

The receiving has issued a “stop payment request” on a debit entry. This can be placed on more than one debit entry. To resolve this, contact the customer to work out the issues associated with the payment stop. The transaction can be re-entered once proper authorization has been obtained. 

 

ACH Return Code R09 – Uncollected Funds

A sufficient 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. To resolve this, try the transaction again as a new transaction. You can do this up to 30 days after the original authorization date. 

 

ACH Return Code R10 – Customer Advises Unauthorized, Improper, Ineligible, or Part of an Incomplete Transaction

The Receiver notified the RDFI that the entry was either improper, negligible, unauthorized or part of an incomplete transaction. The receiver may request immediate credit from the RDFI after this return code is issued and if it is a return code for an unauthorized debit. A request of this sort must occur within 60 days of the RDFI sending or making available to the receiver the pertinent information. Authorization needs to be provided again for the amount to be debited. 

To resolve this, suspend any recurring payments that are linked to this bank account. Then, contact the consumer to resolve the issue of the return. This might involve asking if the consumer wishes to continue a recurring payment, or it may involve seeking collections support. A different bank account can also be suggested if the bank account was changed or is faulty. If the same bank account is used, then the consumer will most likely need to call their bank to remove the block that is restriction transactions. 

 

ACH Return Code R11 – Check Truncation Entry Return

Used when a returning a check truncation entry, which involves the digitization of a physical paper cheque into an electronic form. Used only when no other return code is available.

To resolve this, suspend any recurring payments that are linked to this bank account. Then, contact the consumer to resolve the issue of the return. This might involve asking if the consumer wishes to continue a recurring payment, or it may involve seeking collections support. A different bank account can also be suggested if the bank account was changed or is faulty. If the same bank account is used, then the consumer will most likely need to call their bank to remove the block that is restriction transactions. 

 

ACH Return Code R12 – Branch Sold to Another DFI

The financial institution that is set to receive an entry sold to another financial institution. To resolve this, obtain a new routing number and the appropriate account information. Then, set up a new transaction using the new account information. If this transaction was part of a recurring payment, update the schedule accordingly. 

 

ACH Return Code R13 – Invalid ACH Routing Number

The entry contains a receiving correlation ID that is an invalid ACH routing number. To resolve this, check that the routing number is entered correctly and contact the consumer if necessary. Then, submit a new payment using the correct routing number.

 

ACH Return Code R14 – Representative Payee Deceased or Unable to Continue in that Capacity

A payee is either deceased or is no longer able to continue in original capacity (ie. legally incapacitated adults or minors), and the beneficiary is not deceased. To resolve this, contact the person legally entitled to the payee’s assets.

 

ACH Return Code R15 – Beneficiary or Account Holder Deceased

The beneficiary is deceased, and they may or may not be the account holder. Or, the account holder (who may be acting in a non-representative capacity as the payee) is the owner and is deceased. To resolve this, contact the person legally entitled to the assets.

 

ACH Return Code R16 – Account Frozen/Entry Returned per OFAC Instruction

Action taken by the RDFI or by legal action has restricted access to the account. The RDFI was instructed to return the entry. To resolve this, obtain a different form of payment as transactions will not be processed until the bank account is no longer frozen.

 

ACH Return Code R17 – File Record Edit Criteria

The fields of the record cannot be processed by the RDFI. 

 

ACH Return Code R18 – Improper Effective Entry Date

The effective entry date for a credit entry is longer than the suggested timeline, two banking days after the banking day of processing as established by the originating ACH operator. Or, the effective date is after the window of processing. To resolve this, submit a new transaction.

 

ACH Return Code R19 – Amount Field Error

The amount field is either non-numeric, zero, or it exceeds $25,000. 

 

ACH Return Code R20 – Non-Transaction Account

The ACH entry is destined for an account that cannot process transactions, which is typically an account where transactions are prohibited or limited. To resolve this, contact the consumer to charge a different account. 

 

ACH Return Code R21 – Invalid Company Identification

The company identification information is invalid.

 

ACH Return Code R22 – Invalid Individual ID number

The receiver has indicated to the RDFI that the number with which the originator was identified is not correct. To resolve this, indicate to the consumer the need to enter the appropriate identifier in the appropriate slots.

 

ACH Return Code R23 – Credit Entry Refused by Receiver

Any credit entry refused by the receiver may be returned by the RDFI. For example, the receiver may have returned an entry because the minimum or exact amount is not remitted. To resolve this, contact the consumer to work out the issue or have the consumer contact their bank. Confirm that the credit will be accepted before submitting it again. 

 

ACH Return Code R24 – Duplicate Entry

The RDFI received what looks like a duplicate entry. Confirm that the trace number, date, dollar amount, and or other data does not match another transaction. 

 

Uncommon ACH Return Codes

These are the remaining, albeit less common, ACH return codes that you might experience, listed in numerical order. 

ACH Return Code R25 – Addenda Error

ACH Return Code R26 – Mandatory Field Error

ACH Return Code R27 – Trace Number Error

ACH Return Code R28 – Routing Number Check Digit Error

ACH Return Code R29 – Corporate Customer Advises Not Authorized

ACH Return Code R30 – RDFI Not Participant in Check Truncation Program

ACH Return Code R31 – Permissible Return Entry (CCD and CTX only)

ACH Return Code R32 – RDFI Non-Settlement

ACH Return Code R33 – Return of XCK Entry

ACH Return Code R34 – Limited Participation DFI

ACH Return Code R35 – Return of Improper Debit Entry

ACH Return Code R36 – Return of improper Credit Entry

ACH Return Code R37 – Source Document Presented for Payment

ACH Return Code R38 – Stop Payment on Source Document

ACH Return Code R39 – Improper Source Document/Source Document Presented for Payment

ACH Return Code R40 – Return of ENR entry by Federal Government Agency

ACH Return Code R41 – Invalid Transaction Code

ACH Return Code R42 – Routing Number/Check Digit Error

ACH Return Code R43 – Invalid DFI Account Number

ACH Return Code R44 – Invalid Individual ID Number/Identification Number

ACH Return Code R45 – Invalid Individual Name/Company Name

ACH Return Code R46 – Invalid Representative Payee Indicator

ACH Return Code R47 – Duplicate Enrollment

ACH Return Code R50 – State Law Affecting RCK Acceptance

ACH Return Code R51 – Item Related to RCK Entry is Ineligible or RCK Entry is Improper

ACH Return Code R52 – Stop Payment on Item Related to RCK Entry

ACH Return Code R53 – Item and RCK Entry Presented for Payment

ACH Return Code R61 – Misrouted Return

ACH Return Code R62 – Return of Erroneous or Reversing Debt

ACH Return Code R67 – Duplicate Return

ACH Return Code R68 – Untimely Return

ACH Return Code R69 – Field Error(s)

ACH Return Code R70 – Permissible Return Entry Not Accepted/Return Not Requested by ODFI

ACH Return Code R71 – Misrouted Dishonored Return

ACH Return Code R72 – Untimely Dishonored Return

ACH Return Code R73 – Timely Original Return

ACH Return Code R74 – Corrected Return

ACH Return Code R75 – Return Not a Duplicate

ACH Return Code R76 – No Errors Found

ACH Return Code R77 – Non-Acceptance of R62 Dishonored Return

The following are international ACH return codes:

ACH Return Code R80 – IAT Entry Coding Errors

ACH Return Code R81 – Non-Participant in IAT Program

ACH Return Code R82 – Invalid Foreign Receiving DFI Identification

ACH Return Code R83 – Foreign Receiving DFI Unable to Settle

ACH Return Code R84 – Entry Not Processed by Gateway

ACH Return Code R85 – Incorrectly Coded Outbound International Payment

 

PART 4.2 Table of Return Reason Codes
CODETITLEDESCRIPTIONINITIATED BYRETURN TYPEACCOUNT TYPETIME FRAMEWRITTEN STATEMENT REQUIREDCROSS REFERENCENOTES
R01Insufficient FundsThe available and/or cash reserve balance is not sufficient to cover the dollar value of the debit Entry.RDFIReturnConsumer or Non-Consumer* 2 Banking DaysNoArticle Three, Section 3.8
– RDFI’s Right to Transmit Return Entries.
R02Account ClosedA previously active account has been closed by action of the customer or the RDFI.RDFIReturnConsumer or Non-Consumer* 2 Banking DaysNoArticle Three, Section 3.8
– RDFI’s Right to Transmit Return Entries.
R03No Account/ Unable to Locate AccountThe 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.
RDFIReturnConsumer or Non-Consumer* 2 Banking DaysNoArticle Three, Section 3.8
– RDFI’s Right to Transmit Return Entries.
This Return Reason Code may not be used to return ARC, BOC, or POP Entries solely because they do not contain the
Receiver’s name in the Individual Name/Receiving Company Name Field.
R04Invalid Account Number StructureThe account number structure is not valid.RDFIReturnConsumer or Non-Consumer* 2 Banking DaysNoArticle Three, Section 3.8
– RDFI’s Right to Transmit Return Entries.
The Entry may fail the Check digit validation or may contain an incorrect number of digits.
R05Unauthorized Debit to Consumer Account Using Corporate SEC CodeCCD or CTX debit Entry was transmitted to a Consumer Account of the Receiver and was not authorized by the Receiver.RDFIExtended ReturnConsumer** 60 Calendar DaysYesArticle Three, Section 3.13
– RDFI Right to Transmit Extended Return Entries.
Article Three, Subsection
3.12.1 – Unauthorized Debit Entry.
The Entry may fail the Check digit validation or may contain an incorrect number of digits.
R06Returned per ODFI’s RequestThe ODFI has requested that the RDFI return an Erroneous Entry.RDFIReturnConsumer or Non-ConsumerNot defined, determined by ODFI and RDFI.NoArticle Two, Subsection 2.12.2
– ODFI Request for Return.
If the RDFI agrees to return the Entry, the ODFI must indemnify the RDFI according to Article Two, Subsection 2.12.3.
*Each Return Entry must be received by the RDFI’s ACH Operator by its deposit deadline for the Return Entry to be made available to the ODFI no later than the opening of business on the second Banking Day following the Settlement Date of the original Entry.
**Each Return Entry must be received by the RDFI’s ACH Operator by its deposit deadline for the Return Entry to be made available to the ODFI no later than the opening of business on the Banking Day following the sixtieth calendar day following the Settlement Date of the original Entry.
CODETITLEDESCRIPTIONINITIATED BYRETURN TYPEACCOUNT TYPETIME FRAMEWRITTEN STATEMENT REQUIREDCROSS REFERENCENOTES
R07Authorization Revoked by CustomerThe RDFI’s customer (the Receiver) revoked the authorization previously provided to the Originator for this debit Entry.RDFIExtended ReturnConsumer** 60 Calendar DaysYesArticle Three, Section 3.13
– RDFI Right to Transmit Extended Return Entries.
Article Three, Subsection
3.12.1 – Unauthorized Debit Entry
This Return Reason Code may not be used for ARC, BOC, POP, or RCK Entries..
R08Payment StoppedThe Receiver has placed a stop payment order on this debit Entry.RDFIReturnConsumer or Non-Consumer* 2 Banking DaysNoArticle Three, Section 3.7
– RDFI Obligation to Stop Payment.
A stop payment order may be placed on one or more debit Entries.
R09Uncollected FundsA sufficient ledger balance exists to satisfy the dollar value of the transaction, but the available balance is
below the dollar value of the debit Entry.
RDFIReturnConsumer or Non-Consumer* 2 Banking DaysNoArticle Three, Section 3.8
– RDFI’s Right to Transmit Return Entries.
R10Customer Advises Not Authorized, Improper, or Ineligible Customer Advises Not Authorized, Improper, Ineligible, or part of an Incomplete TransactionThe RDFI has been notified by the Receiver that the Entry is unauthorized, improper, ineligible, or part of an Incomplete Transaction.RDFIExtended ReturnConsumer; for ARC, BOC, IAT,
or POP, Entries may also be a Non-Consumer.
See note for additional exceptions.
** 60 Calendar DaysYesArticle Three, Subsection
3.12.1 – Unauthorized Debit Entry.
Article Three, Subsection
3.12.2 – Improper ARC, BOC, POP, and RCK Debit Entries.
Article Three, Subsection 3.12.3- Incomplete Transaction.
Article Three, Subsection 3.1.3
– RDFI May Rely on Standard Entry Class Codes.
Article Three, Subsection
3.4.1.2 Rule Exception for CCD and CTX Entries to Consumer Accounts.
Article Three, Section 3.13
– RDFI Right to Transmit Extended Return Entries.Article Eight, Section 8.53 – Incomplete Transaction
May be used for any Entry except CCD or CTX Entries
For CCD or CTX Entries to Consumer Accounts, see R05.
For CCD or CTX to Non- Consumer Accounts, see R29.
May also be used to return an unauthorized debit Entry to a non-consumer account if the debit Entry contains a consumer SEC Code.
CODETITLEDESCRIPTIONINITIATED BYRETURN TYPEACCOUNT TYPETIME FRAMEWRITTEN STATEMENT REQUIREDCROSS REFERENCENOTES
R11Check Truncation Entry ReturnUsed when returning a Check truncation Entry.RDFIReturnConsumer or Non-Consumer* 2 Banking DaysNoArticle Three, Section 3.8
– RDFI’s Right to Transmit Return Entries.
This Return Reason Code should be used only if no other code is applicable. The RDFI must use the Addenda Information field in the Return addenda record to specify the
reason for return (i.e. “exceeds dollar amount,” “stale date,” etc.).
R12Account Sold to Another DFIA financial institution received an Entry to an account that was sold to another financial institution.RDFIReturnConsumer or Non-Consumer* 2 Banking DaysNoArticle Three, Section 3.8
– RDFI’s Right to Transmit Return Entries.
R13Invalid ACH Routing NumberEntry contains a Receiving DFI Identification or Gateway Identification that is not a valid ACH routing number.ACH OperatorReject/ ReturnConsumer or Non-ConsumerNext file delivery time following processingNoAppendix Two, Part 2.5 (Automatic Entry Detail Rejection Criteria).For ACH Operator use only.
R14Representative Payee Deceased
or Unable to Continue in That Capacity
The representative payee is either deceased or unable to continue in that capacity. The beneficiary is not deceased.RDFIReturnConsumer or Non-Consumer* 2 Banking DaysNoArticle Three, Section 3.8
– RDFI’s Right to Transmit Return Entries.
The representative payee is a person or institution authorized to accept Entries on behalf of one or more other persons, such as legally incapacitated adults or minor children.
R15Beneficiary or Account Holder (Other Than a Representative Payee) Deceased(1) The beneficiary is deceased, or
(2) The account holder is deceased.
RDFIReturnConsumer* 2 Banking DaysNoArticle Three, Section 3.8
– RDFI’s Right to Transmit Return Entries.
(1) The beneficiary is the person entitled to the benefits and
may or may not be the account holder; or
(2) The account holder is the owner of the account and is not a representative payee.
R16Account 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 EntryRDFI or GatewayReturnConsumer or Non-Consumer* 2 Banking DaysNoArticle Three, Section 3.8
– RDFI’s Right to Transmit Return Entries.
R17File Record Edit Criteria File Record Edit Criteria/Entry with Invalid Account Number Initiated Under Questionable CircumatancesFiled(s) cannot be processed by RDFI (1) Field(s) cannot be processed by RDFI; or (2) the Entry contains an invalid DFI Account Number (account closed/no account/unable to locate account/invalid account number) and is believed by the RDFI to have been initiated under questionable circumstancesRDFIReturnConsumer or Non-Consumer* 2 Banking DaysNoArticle Three, Section 3.8
– RDFI’s Right to Transmit Return Entries. Appendix Three, Part 3.2 -Glossary of ACH Record Format Specifications
Some fields that are not edited by the ACH Operator are edited by the RDFI. If the Entry cannot be processed by the RDFI, the field(s) causing the processing error must be identified in the Addenda information field of the Return. (1) Some fields that are not edited by the ACH Operator are edited by the RDFI. (2) An RDFImay use ReturnReason Code R17 to return an Entry that contains an invalid DFI Account Number and is believed by the RDFI to have been initiated under questionable circumstances. The RDFI must insert “QUESTIONABLE” within the first twelve positions of the Addenda Information field. The RDFI may include additional explanatory information within the remaining positions of this field.
R18Improper Effectove Entry Date(1) The Effective Entry Date for a credit Entry is more than two Banking Days after the Banking Day of Date for 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.ACH OperatorReject/ ReturnConsumer or Non-ConsumerNext file delivery time following processingNoAppendix Two, Part 2.5 (Automatic Entry Detail Rejection Criteria).For ACH Operator use only.
CODETITLEDESCRIPTIONINITIATED BYRETURN TYPEACCOUNT TYPETIME FRAMEWRITTEN STATEMENT REQUIREDCROSS REFERENCENOTES
R19Amount Field ErrorAmount field is non-numeric.
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.
Amount field is zero in an Entry other than a
Prenotification, DNE, ENR, Notification of Change, Return, dishonored Return, contested dishonored Return, or zero dollar CCD, CTX, or IAT Entry.
Amount field is greater than
$25,000 for ARC, BOC, POP Entries.
ACH OperatorReject/ ReturnConsumer or Non-ConsumerNext file delivery time following processingNoSee Appendix Two, Part
2.5 (Automatic Entry Detail Rejection Criteria) for a full explanation of this Return Reason Code.
For ACH Operator use only.
R20Non- Transaction AccountACH Entry to a non- Transaction Account.RDFIReject/ ReturnConsumer or Non-Consumer* 2 Banking DaysNoArticle Three, Section 3.8
– RDFI’s Right to Transmit Return Entries.
A non-Transaction Account. as defined in Regulation D, would include an account against which transactions are prohibited or limited.
R21Invalid Company IdentificationThe identification number used in the Company Identification Field is not valid.RDFIReturnNon-Consumer* 2 Banking DaysNoArticle Three, Section 3.8
– RDFI’s Right to Transmit Return Entries.
This Return Reason Code is generally used on CIE transactions.
R22Invalid Individual ID NumberThe Receiver has indicated to the RDFI that the number with which the Originator was identified is not correct.RDFIReturnConsumer or Non-Consumer* 2 Banking DaysNoArticle Three, Section 3.8
– RDFI’s Right to Transmit Return Entries.
In CIE and MTE Entries, the Individual ID Number is used by the Receiver to identify the account.
CODETITLEDESCRIPTIONINITIATED BYRETURN TYPEACCOUNT TYPETIME FRAMEWRITTEN STATEMENT REQUIREDCROSS REFERENCENOTES
R23Credit Entry Refused by ReceiverAny credit Entry that is refused by the Receiver may be returned by the RDFI.RDFIReturnConsumer or Non-ConsumerRDFI must transmit the Return Entry to the ACH Operator by the ACH Operator’s deposit deadline for the Return Entry to be made available
to the ODFI no later than the opening
of business on the second Banking Day following the RDFI’s receipt of notification of refusal of the Entry from its Receiver.
NoArticle Three, Subsection
3.8.3.2 – Timing Requirements for Credit Entries Refused by Receiver.
Examples:
(1) a minimum amount required by the Receiver has not been remitted;
(2) the exact amount required has not been remitted;
(3) the account is subject to litigation and the Receiver will not accept the transaction;
(4) acceptance of the transaction results in an overpayment;
(5) the Originator is not known by the Receiver; or
(6) the Receiver has not authorized this credit Entry to this account.
R24Duplicate EntryThe 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.RDFIReturnConsumer or Non-Consumer* 2 Banking DaysNoArticle Three, Section 3.8
– RDFI’s Right to Transmit Return Entries.
The RDFI should use this code with extreme care and should be aware that if a file has been duplicated, the Originator may have already generated a reversal transaction to handle the situation.
R25Addenda ErrorAddenda Record Indicator value is incorrect.
Addenda Type Code is invalid, out of sequence, or missing,
Number of Addenda Records exceeds allowable maximum,
Addenda Sequence Number is invalid.
ACH OperatorReturn/RejectConsumer or Non-ConsumerNext file delivery time following processingNoAppendix Two, Part 2.5 (Automatic Entry Detail Rejection Criteria).For ACH Operator use only.
R26Mandatory Field ErrorErroneous data or missing data in a mandatory field.ACH OperatorReturn/RejectConsumer or Non-ConsumerNext file delivery time following processingNoAppendix Two, Part 2.5 (Automatic Entry Detail Rejection Criteria).For ACH Operator use only.
CODETITLEDESCRIPTIONINITIATED BYRETURN TYPEACCOUNT TYPETIME FRAMEWRITTEN STATEMENT REQUIREDCROSS REFERENCENOTES
R27Trace Number ErrorOriginal Entry Trace Number is not present in the Addenda Record on a Return or Notification of Change
Entry; or
Trace Number of an Addenda Record is not the same
as the Trace Number of the preceding Entry Detail Record.
ACH OperatorReturn/RejectConsumer or Non-ConsumerNext file delivery time following processingNoAppendix Two, Part 2.5 (Automatic Entry Detail Rejection Criteria).For ACH Operator use only.
R28Routing Number Check Digit ErrorThe Check digit for a routing number is not valid.ACH OperatorReturn/RejectConsumer or Non-ConsumerNext file delivery time following processingNoAppendix Two, Part 2.5 (Automatic Entry Detail Rejection Criteria).For ACH Operator use only.
R29Corporate Customer Advises Not AuthorizedThe RDFI has been notified by the Receiver (non-consumer) that a specific Entry has not been authorized by the Receiver.RDFIReturnNon-Consumer* 2 Banking DaysNoArticle Three, Section 3.8
– RDFI’s Right to Transmit Return Entries.
Article Three, Subsection
3.12.1 – Unauthorized Debit Entry
Beyond the return time frame the ODFI may agree to accept a late Return Entry; if so use R31.
R30RDFI Not
Participant in Check Truncation Program
The RDFI does not participate in a Check truncation program.ACH OperatorReturn/RejectConsumer or Non-ConsumerNext file delivery time following processingNoAppendix Two, Part 2.5 (Automatic Entry Detail Rejection Criteria).
Aricle Four, Subsection 4.2.6
– Return and Rejection of TRC Entries or TRX Entries.
For ACH Operator use only.
R31Permissible Return Entry (CCD and CTX only)The RDFI may return a CCD or CTX Entry that the ODFI agrees to accept.RDFIReturnNon-ConsumerNot defined, determined by the ODFI and RDFI.NoArticle Three, Subsection
3.8.3.5 – Late Return Entries for CCD or CTX Entries with ODFI Agreement.
CCD and CTX Entries only.
R32RDFI Non-
Settlement
The RDFI is not able to settle the Entry.ACH OperatorReturn/RejectConsumer or Non-ConsumerNext file delivery time following processingNoAppendix Two, Part 2.5 (Automatic Entry Detail Rejection Criteria).For ACH Operator use only.
R33Return of XCK EntryThis Return Reason Code may only be used to return XCK Entries and is at the RDFI’s sole discretion.RDFIExtended ReturnConsumer or Non-Consumer** 60 Calendar DaysNoArticle Three, Subsection
3.8.3.4 – Timing Requirements for Return of XCK Entries.
CODETITLEDESCRIPTIONINITIATED BYRETURN TYPEACCOUNT TYPETIME FRAMEWRITTEN STATEMENT REQUIREDCROSS REFERENCENOTES
R34Limited Participation DFIThe RDFI’s participation has been limited by a federal or state supervisor.ACH OperatorReturn/RejectConsumer or Non-ConsumerNext file delivery time following processingNoAppendix Two, Part 2.5 (Automatic Entry Detail Rejection Criteria).For ACH Operator use only.
R35Return of Improper Debit EntryDebit Entries (with the exception of Reversing Entries) are not permitted for CIE Entries or to loan accounts.ACH OperatorReturn/RejectConsumer or Non-ConsumerNext file delivery time following processingNoAppendix Two, Part 2.5 (Automatic Entry Detail Rejection Criteria)For ACH Operator use only.
R36Return of Improper Credit EntryACH credit Entries (with the exception of Reversing
Entries) are not permitted for use with ARC, BOC, POP, RCK, TEL, WEB, and XCK.
ACH OperatorReturn/RejectConsumer or Non-ConsumerNext file delivery time following processingNoAppendix Two, Part 2.5 (Automatic Entry Detail Rejection Criteria).For ACH Operator use only.
R37Source Document Presented for PaymentThe source document to which an ARC, BOC, or POP Entry relates has been presented for payment.RDFIExtended ReturnConsumer or Non-Consumer** 60 Calendar DaysYesArticle Three, Subsection
3.12.2 – Improper ARC, BOC, POP, and RCK Debit Entries.
Article Three, Section 3.13
– RDFI Right to Transmit Extended Return Entries
For use with ARC, BOC, and POP Entries only.
R38Stop Payment on Source DocumentThe RDFI determines a stop payment order has been placed on the source document to which the ARC or BOC Entry relates.RDFIExtended ReturnConsumer or Non-Consumer** 60 Calendar DaysNoArticle Three, Subsection
3.11.2.2 – RDFI Obligation to Recredit for ARC, BOC, and RCK Entries Regarding Stop Payments Orders.
Article Three, Section 3.13
– RDFI Right to Transmit Extended Return Entries.
For use with ARC and BOC Entries only.
R39Improper Source Document/ Source Document Presented for PaymentThe 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 both been presented for payment and posted to the Receiver’s account.
RDFIReturnConsumer or Non-Consumer* 2 Banking DaysNoArticleThree, Subsection
3.12.2 – Improper ARC, BOC, POP, and RCK Debit Entries.
Article Eight, Section 8.32 – Eligible Source Document.
For use with ARC, BOC, and POP Entries only and when the RDFI (rather than the Receiver) determines the Entry is improper.
CODETITLEDESCRIPTIONINITIATED BYRETURN TYPEACCOUNT TYPETIME FRAMEWRITTEN STATEMENT REQUIREDCROSS REFERENCENOTES
RETURN REASON CODES TO BE USED BY FEDERAL GOVERNMENT AGENCIES RETURNING ENR ENTRIES
R40Return of ENR Entry by Federal Government AgencyThis Return Reason Code may only be used to return ENR Entries and is at
the Federal Government Agency’s sole discretion.
Federal Government AgencyReturn – ENR OnlyN/AN/ANoThe Green Book For Federal Government Agency use only.
R41Invalid Transaction CodeEither 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 regard to an Automated Enrollment Entry.
Federal Government AgencyReturn – ENR OnlyN/AN/ANoThe Green Book
Appendix Three – ACH Record Format Specifications, Part
3.2 – Glossary of ACH Record Format Data Elements – Payment Related Information
For Federal Government Agency use only.
Example: Transaction Code “28,” Prenotification of Demand Deposit Debit Authorization, for an ENR sent to SSA pertaining to a direct deposit enrollment.
R42Routing Number/Check Digit ErrorThe 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 Government AgencyReturn – ENR OnlyN/AN/ANoThe Green BookFor Federal Government Agency use only.
R43Invalid DFI Account NumberThe Receiver’s account number included in Field 3 of the Addenda Record must include at least one alphameric character.Federal Government AgencyReturn – ENR OnlyN/AN/ANoThe Green Book For Federal Government Agency use only.
R44Invalid 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 Government AgencyReturn – ENR OnlyN/AN/ANoThe Green BookFor Federal Government Agency use only.
R45Invalid Individual Name/Company NameThe 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 Government AgencyReturn – ENR OnlyN/AN/ANoThe Green Book For Federal Government Agency use only.
R46Invalid Representative Payee IndicatorThe 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 Government AgencyReturn – ENR OnlyN/AN/ANoThe Green BookExamples: The Representative Payee Indicator Code is “zero,” and Social Security’s records indicate that payments should be sent to a representative payee on behalf of an
entitled beneficiary; or The Representative Payee Indicator Code is “one,” and Social Security’s records indicate that there is no representative payee and the beneficiary may receive payments directly.
For Federal Government Agency use only.
R47Duplicate EnrollmentThe Entry is a duplicate of an Automated Enrollment Entry previously initiated by a DFI.Federal Government AgencyReturn – ENR OnlyN/AN/ANoThe Green BookFor Federal Government Agency use only.
CODETITLEDESCRIPTIONINITIATED BYRETURN TYPEACCOUNT TYPETIME FRAMEWRITTEN STATEMENT REQUIREDCROSS REFERENCENOTES
CODES TO BE USED FOR RETURN OF RCK ENTRIES
R50State Law Affecting RCK AcceptanceThe 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
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.
RDFIReturnConsumer* 2 Banking DaysNoUniform Commercial Code Article 4
http://www.law.cornell.edu/ ucc/4/
For use with RCK Entries only.
R51Item Related to RCK Entry is Ineligible or RCK Entry is Improper.An RCK Entry considered to be ineligible or improper.RDFIExtended ReturnConsumer** 60 Calendar DaysYesArticle Three, Subsection
3.12.2 – Improper ARC, BOC, POP, and RCK Debit Entries.
Article Two, Subsection
2.5.13.3 – RCK Eligible Items.
Article Two, Subsection
2.5.13.4 – RCK Ineligible Items.
For use with RCK Entries only.
R52Stop Payment on Item Related to RCK EntryA stop payment order has been placed on the item to which the RCK Entry relates.RDFIExtended ReturnConsumer** 60 Calendar DaysNoArticle Three, Subsection
3.11.2.2 – RDFI Obligation to Recredit for ARC, BOC, and RCK Entries Regarding Stop Payment Orders.
For use with RCK Entries only.
R53Item and RCK Entry Presented for PaymentIn addition to an RCK Entry, the item to which the RCK Entry relates has also been presented for payment.RDFIExtended ReturnConsumer** 60 Calendar DaysYesArticle Three, Subsection
3.12.2 – Improper ARC, BOC, POP, and RCK Debit Entries.
For use with RCK Entries only.
CODETITLEDESCRIPTIONINITIATED BYRETURN TYPEACCOUNT TYPETIME FRAMEWRITTEN STATEMENT REQUIREDCROSS REFERENCENOTES
CODES TO BE USED BY THE ODFI FOR DISHONORED RETURN ENTRIES
R61Misrouted ReturnThe financial institution preparing the Return Entry (the RDFI of the original Entry) has placed the incorrect Routing Number in the Receiving DFI Identification field.ODFIDishonored Return May be used for all Entries except IATConsumer or Non-ConsumerThe ODFI must transmit a dishonored Return Entry to its ACH Operator within five Banking Days after the Settlement Date of the Return Entry.NoArticle Two, Subsection
2.12.5.1 – Dishonor of Return by ODFI.
May be used for all Entries except IAT.
R62Return of Erroneous or Reversing DebitThe Originator’s/ODFI’s use of the reversal process has resulted in, or failed to correct, an unintended credit to the Receiver.ODFIDishonored Return May be used for all Entries except IATConsumer or Non-ConsumerThe ODFI must transmit a dishonored Return Entry to its ACH Operator within five Banking Days after the Settlement Date of the Return Entry.NoArticle Two, Subsection
2.12.5.1 – Dishonor of Return by ODFI. Article two, Subsection 2.12.5.2 – Specific Warranties for Dishonored Return Relating to Reversals
May be used for all Entries except IAT.Usage is limited to the following two Reversal scenarios: (1) A debit Erroneous Entry and a subsequent credit Reversing Entry are both Transmitted to the Receiver’s account. The debit Erroneous Entry is posted and made available to the Receiver. (2) A credit Erroneous Entry and a subsequent debit Reversing Entry are both Transmitted to the Receiver’s account. The credit Erroneous Entry is posted and made available to the receiver, but the debit Reversing Entry is returned.
R67Duplicate ReturnThe ODFI has received more than one Return for the same Entry.ODFIDishonored Return May be used for all Entries except IATConsumer or Non-ConsumerThe ODFI must transmit a dishonored Return Entry to its ACH Operator within five Banking Days after the Settlement Date of the Return Entry.NoArticle Two, Subsection
2.12.5.1 – Dishonor of Return by ODFI.
May be used for all Entries except IAT.
R68Untimely ReturnThe Return Entry has not been sent within the timeframe established by these Rules.ODFIDishonored Return May be used for all Entries except IATConsumer or Non-ConsumerThe ODFI must transmit a dishonored Return Entry to its ACH Operator within five Banking Days after the Settlement Date of the Return Entry.NoArticle Two, Subsection
2.12.5.1 – Dishonor of Return by ODFI.
May be used for all Entries except IAT.
R69Field Error(s)One or more of the field requirements are incorrect.ODFIDishonored Return May be used for all Entries except IATConsumer or Non-ConsumerThe ODFI must transmit a dishonored Return Entry to its ACH Operator within five Banking Days after the Settlement Date of the Return Entry.NoArticle Two, Subsection
2.12.5.1 – Dishonor of Return by ODFI.
The ODFI must insert the appropriate code(s) from below, separated by an asterisk (*), within the Addenda Information Field of the Addenda Record Format for dishonored Returns to indicate the field(s) in which the errors occur. 01– Return Contains Inncorrect DFI Account Number 02– Return Contains Incorrect Original Entry Trace Number 03– Return Contains Incorrect Dollar Amount 04– Return Contains Incorrect Individual Identification Number/Identification Number 05– Return Contains Incorrect Transaction Code 06– Return Contains Incorrect Company Identification Number 07–Return Contains an Invalid Effective Entry Date For Example: 01*03*06 May be used for all Entries except IAT
R70Permissible Return Entry Not Accepted/ Return Not Requested by ODFIThe 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.ODFIDishonored Return May be used for all Entries except IATConsumer or Non-ConsumerThe ODFI must transmit a dishonored Return Entry to its ACH Operator within five Banking Days after the Settlement Date of the Return Entry.NoArticle Two, Subsection
2.12.5.1 – Dishonor of Return by ODFI.
This code may be used only to dishonor Return Entries containing Return Reason Codes R06 and R31.
May be used for all Entries except IAT.
CODETITLEDESCRIPTIONINITIATED BYRETURN TYPEACCOUNT TYPETIME FRAMEWRITTEN STATEMENT REQUIREDCROSS REFERENCENOTES
CODES TO BE USED BY THE RDFI FOR CONTESTED DISHONORED RETURN ENTRIES
R71Misrouted Dishonored ReturnThe 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.
RDFIContested Dishonored Return May be used for all Entries except IATConsumer or Non-ConsumerThe contested dishonored Return Entry must be transmitted to the ACH Operator within two Banking Days after the Settlement Date of the dishonored Return Entry.NoArticle Three, Subsection
3.8.5.2 – RDFI May Contest Dishonored Returns.
May be used for all Entries except IAT.
R72Untimely Dishonored ReturnThe dishonored Return Entry has not been sent within the designated timeframe.RDFIContested Dishonored Return May be used for all Entries except IATConsumer or Non-ConsumerThe contested dishonored Return Entry must be transmitted to the ACH Operator within two Banking Days after the Settlement Date of the dishonored Return Entry.NoArticle Two, Subsection
2.12.5.1 – Dishonor of Return by ODFI.
Article Three, Subsection
3.8.5.2 – RDFI May Contest Dishonored Returns.
May be used for all Entries except IAT.
R73Timely Original ReturnThe RDFI is certifying that the original Return Entry was sent within the timeframe designated in these Rules.RDFIContested Dishonored Return May be used for all Entries except IATConsumer or Non-ConsumerThe contested dishonored Return Entry must be transmitted to the ACH Operator within two Banking Days after the Settlement Date of the dishonored Return Entry.NoArticle Three, Subsection
3.8.5.2 – RDFI May Contest Dishonored Returns.
May be used for all Entries except IAT.
CODETITLEDESCRIPTIONINITIATED BYReturn TypeACCOUNT TYPETIME FRAMEWRITTEN STATEMENT REQUIREDCROSS REFERENCENOTES
R74Corrected ReturnThe RDFI is correcting a previous Return Entry that was dishonored using Return Reason Code R69 (Field Errors) because it contained incomplete or incorrect information.RDFIContested Dishonored Return May be used for all Entries except IATConsumer or Non-ConsumerThe corrected Return Entry must be transmitted to the ACH Operator within two Banking Days after the Settlement Date
of the dishonored Return Entry.
NoArticle Three, Subsection
3.8.5.1 – RDFI May Correct Dishonored Returns.
Data must be obtained from the following fields in the original Company Batch Header Record, Entry Detail Record or Addenda Record:
• DFI Account Number
• Trace Number
• Amount
• Individual Identification Number/
Identification Number
• Transaction Code
• Company Identification
• Effective Entry Date
May be used for all Entries except IAT.
R75Return Not a DuplicateThe Return Entry was not a duplicate of an Entry previously returned by the RDFI.RDFIContested Dishonored Return May be used for all Entries except IATConsumer or Non-ConsumerThe contested dishonored Return Entry must be transmitted to the ACH Operator within two Banking Days after the Settlement Date of the dishonored Return Entry.NoArticle Three, Subsection
3.8.5.2 – RDFI May Contest Dishonored Returns.
This code may be used by the RDFI to contest a dishonored Return Entry from an ODFI that used Return Reason Code R67 (Duplicate Return).
May be used for all Entries except IAT.
R76No Errors FoundThe original Return Entry did not contain the errors indicated by the ODFI in the dishonored Return Entry.RDFIContested Dishonored Return May be used for all Entries except IATConsumer or Non-ConsumerThe contested dishonored Return Entry must be transmitted to the ACH Operator within two Banking Days after the Settlement Date of the dishonored Return Entry.NoArticle Three, Subsection
3.8.5.2 – RDFI May Contest Dishonored Returns.
This code may be used by the RDFI to contest a dishonored Return Entry from an ODFI that used Return Reason Code R69 (Field Errors).
May be used for all Entries except IAT.
R77Non-Acceptance of R62 Dishonored ReturnThe 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.RDFIContested Dishonored Return May be used for all Entries except IATConsumer or Non-ConsumerThe contested dishonored Return Entry must be transmitted to the ACH Operator within two Banking Days after the Settlement Date of the dishonored Return Entry.NoArticle Three, Subsection
3.8.5.2 – RDFI May Contest Dishonored Returns.
May be used for all Entries except IAT. For use by the RDFI in response to the receipt of Dishonored Return Code R62 – Return of Erroneous or Reversing Debit. For use only when the RDFI has returned both the Erroneous Entry and the subsequent reversing Entry, or the RDFI is unable to recover the funds relating to the R62 dishonored Return from the Receiver.
CODETITLEDESCRIPTIONINITIATED BYRETURN TYPEACCOUNT TYPETIME FRAMEWRITTEN STATEMENT REQUIREDCROSS REFERENCENOTES
CODES TO BE USED BY GATEWAYS FOR THE RETURN OF INTERNATIONAL PAYMENTS
R80IAT Entry Coding ErrorThe 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.
GatewayReturnConsumer or Non-Consumer* 2 Banking DaysNoArticle Three, Section 3.8
– RDFI’s Right to Transmit Return Entries.
Article Five, Section 5.3 – Gateway Assumes Obligations of Other Participants.
For Gateway use with Outbound IAT Entries only
R81Non-Participant in IAT ProgramThe IAT Entry is being returned because the Gateway does not have an agreement with either the ODFI or the Gateway’s customer to transmit IAT Entries.GatewayReturnConsumer or Non-Consumer* 2 Banking DaysNoArticle Five, Subsection
5.1.1 – Gateway Must Enter Agreement with ODFI or Gateway’s customer.
For Gateway use with Outbound IAT Entries only
R82Invalid Foreign Receiving DFI IdentificationThe reference used to identify the Foreign Receiving DFI
of an Outbound IAT Entry is invalid.
GatewayReturnConsumer or Non-Consumer* 2 Banking DaysNoAppendix Three, Subpart 3.2.2 -Glossary of Data Elements: Receiving DFI IdentificationFor Gateway use with Outbound IAT Entries only
R83Foreign Receiving DFI Unable to SettleThe IAT Entry is being returned due to settlement problems in the foreign payment system.GatewayReturnConsumer or Non-Consumer* 2 Banking DaysNoFor Gateway use with Outbound IAT entries only.
R84Entry Not Processed by GatewayFor Outbound IAT Entries, the Entry has not been processed and is being returned at the Gateway’s discretion because either (1) the processing of such Entry may expose the Gateway to excessive risk,
or (2) the foreign payment system does not support the functions needed to process the transaction.
GatewayReturnConsumer or Non-Consumer* 2 Banking DaysNoFor Gateway use with Outbound IAT entries only.
R85Incorrectly Coded Outbound International PaymentThe RDFI/Gateway has identified the Entry as an Outbound international payment and is returning the Entry because it bears an SEC Code that lacks information required by the Gateway for OFAC compliance.GatewayReturnConsumer or Non-Consumer* 2 Banking DaysNoFor Gateway use with Entries bearing SEC Code other than IAT.
*Each Return Entry must be received by the RDFI’s ACH Operator by its deposit deadline for the Return Entry to be made available to the ODFI no later than the opening of business on the second Banking Day following the Settlement Date of the original Entry.
**Each Return Entry must be received by the RDFI’s ACH Operator by its deposit deadline for the Return Entry to be made available to the ODFI no later than the opening of business on the Banking Day following the sixtieth calendar day following the Settlement Date of the original Entry.