RDFIs must return entries that are not posted to Receivers' accounts. Entries must be returned for valid reasons, as follows:

R01 Insufficient Funds
The available and/or cash reserve balance is not sufficient to cover the dollar value of the debit entry.

R02 Account Closed
A previously active account has been closed by action of the customer or the RDFI.

R03 No Account/Unable to Locate Account
The account number structure is valid and 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 open account. This Return Reason Code may not be used to return POP entries that do not contain an Individual Name.

R04 Invalid Account Number
The account number structure is not valid, the entry may fail the check digit validation, or it may contain an incorrect number of digits.

R05 Reserved

R06 Returned per ODFI Request.
The ODFI has requested that the RDFI return the ACH entry. If the RDFI agrees to return the entry, the ODFI must indemnify the RDFI according to Article Five of the NACHA Operating Rules.

R07 Authorization Revoked by Customer (adjustment entries)
The RDFI's customer (the Receiver) has revoked the authorization previously provided to the Originator for this particular transaction. The Receiver may request immediate credit from the RDFI for an unauthorized debit. The request must be made in writing within fifteen (15) days after the RDFI sends or makes available to the Receiver information pertaining to that debit entry. The Receiver must also provide the RDFI with a written statement under penalty of perjury that the authorization for the debit entry has been revoked by the Receiver. The RDFI must return the rescinded transaction to its ACH Operator by its deposit deadline for the adjustment 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. This code and related Operating Rule provisions apply to Consumer entries only. (Note: This Return Reason Code may not be used for POP entries, Single- Entry WEB entries, or TEL entries.)

R08 Payment Stopped or Stop Payment on Source Document
The Receiver of a recurring debit transaction has the right to stop payment on any specific ACH debit. A stop payment request should be handled in accordance with the provisions of Article Seven (Recall, Stop Payment, Recredit, and Adjustment) of these Rules. The RDFI should verify the Receiver's intent when a request for stop payment is made to ensure this is not intended to be a revocation of authorization (R07). A stop payment order shall remain in effect until the earliest of the following occurs: a lapse of six months from the date of the stop payment order, payment of the debit entry has been stopped, or the Receiver withdraws the stop payment order.

OR

The RDFI determines that a stop payment order has been placed on the source document to which the ARC entry relates. An RDFI using this Return Reason Code must transmit the return entry by its 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 banking day following the sixtieth calendar day following the Settlement Date of the ARC entry to which the source document relates.

R09 Uncollected Funds
Sufficient book or ledger balance exists to satisfy the dollar value of the transaction, but the dollar value of transactions in process of collection (e.g., uncollected checks) brings the available and/or cash reserve balance below the dollar value of the debit entry.

R10 Customer Advises Not Authorized, Notice Not Provided, Improper Source Document, or Amount of Entry Not Accurately Obtained from Source Document (adjustment entries)
For entries to Consumer Accounts that are not ARC entries, POP entries, or RCK entries, the RDFI has been notified by its customer, the Receiver, that the Originator of a given transaction has not been authorized to debit his account. The Receiver may request immediate credit from the RDFI for an unauthorized debit. The request must be made in writing within fifteen (15) days after the RDFI sends or makes available to the Receiver information pertaining to that debit entry. The Receiver must also provide the RDFI with a written statement under penalty of perjury, pursuant to subsection 7.6.5 (Receiver's Written Statement Under Penalty of Perjury), that the debit entry was not authorized by the Receiver. For purposes of this code and related Operating Rules provisions, a debit entry was not authorized by the Receiver if (1) the authorization requirements of Article Two, subsection 2.1.2 (Receiver Authorization and Agreement) have not been met; (2) the debit entry was initiated in an amount greater than that authorized by the Receiver; or (3) the debit entry was initiated for settlement earlier than authorized by the Receiver. An unauthorized debit entry does not include a debit entry initiated with fraudulent intent by the Receiver or any person acting in concert with the Receiver. The RDFI must return the rescinded transaction to its ACH Operator by its deposit deadline for the adjustment 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. This code and related Operating Rule provisions apply to Consumer entries only.

OR

For ARC entries, the RDFI has been notified by its customer, the Receiver, that (1) the required notice was not provided by the Originator in accordance with Article Three, subsection 3.6.1 (Notice Obligation), (2) the source document used for the debit entry is improper pursuant to subsection 3.6.2 (Source Documents), or (3) the amount of the ARC entry was not accurately obtained from the source document. The Receiver may request immediate credit from the RDFI for an ARC entry for the reasons described above. The request must be made in writing within fifteen (15) days after the RDFI sends or makes available to the Receiver information relating to that debit entry. The Receiver must also provide the RDFI with a written statement under penalty of perjury, pursuant to subsection 7.6.5.1 (Receiver's Written Statement Under Penalty of Perjury for ARC Entries), that (1) the required notice was not provided, (2) the source document used for the debit entry is improper, or (3) the amount of the ARC entry was not accurately obtained from the source document. An RDFI using this Return Reason Code must transmit the return entry by its 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 banking day following the sixtieth calendar day following the Settlement Date of the ARC entry.

OR

* For POP entries, the RDFI has been notified by its customer, the Receiver, that (1) the Originator of a given transaction has not been authorized to debit his account, or (2) the source document for the debit entry is improper pursuant to subsection 3.7.1 (Source Documents). The Receiver may request immediate credit from the RDFI for a POP entry for the reasons described above. The request must be made in writing within fifteen (15) days after the RDFI sends or makes available to the Receiver information relating to that debit entry. The Receiver must also provide the RDFI with a written statement under penalty of perjury, pursuant to subsection 7.6.5.2 (Receiver's Written Statement Under Penalty of Perjury for POP Entries), that (1) the entry was not authorized, or (2) the source document for the entry is improper. An RDFI using this Return Reason Code must transmit the return entry by its 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 banking day following the sixtieth calendar day following the Settlement Date of the entry.

R11 Check Truncation Entry Return (Specify) To be used when returning a check truncation entry
This reason for return should be used only if no other return reason code is applicable. The RDFI should use the appropriate field in the addenda record to specify the reason for return (i.e., "exceeds dollar limit," "no match on ARP," "stale date," etc.).

R12 Branch Sold to Another DFI
A financial institution may continue to receive entries destined for an account at a branch that has been sold to another financial institution. Because the RDFI no longer maintains the account and is unable to post the entry, it should return the entry to the ODFI.

R14 Representative Payee Deceased or Unable to Continue in that Capacity
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. The representative payee is either deceased or unable to continue in that capacity. The beneficiary is not deceased.

R15 Beneficiary or Account Holder (Other Than a Representative Payee) Deceased
 (1) The beneficiary is the person entitled to the benefits and is deceased. The beneficiary may or may not be the account holder; or (2) The account holder (acting in a non-representative payee capacity) is an owner of the account and is deceased.

R16 Account Frozen
The funds in the account have been made unavailable due to specific action taken by the RDFI or by legal action.

R17 File Record Edit Criteria (Specify)
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 record information field of the return.

R20 Non-transaction Account
The ACH entry destined for a non-transaction account would include (1) an account against which transactions are prohibited or limited (e.g., Regulation D); or, (2) a pass-through where entry is for a credit union or thrift organization, and Regulation E descriptive requirements cannot be met.

R21 Invalid Company Identification
The identification number used in the Company Identification Field is not valid. This Return Reason Code will normally be used on CIE transactions.

R22 Invalid Individual ID Number
The Individual ID Number of CIE or MTE type entries is used by the Receiver to identify the account. The Receiver has indicated to the RDFI that the number by which the Originator was identified is not correct.

R23 Credit Entry Refused by Receiver
The Receiver may return a credit entry because one of the following conditions exists: (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.

R24 Duplicate Entry
The Receiving DFI has received what appears to be a duplicate entry; i.e., the trace number, date, dollar amount and/or other data matches another transaction. This code should be used with extreme care. The Receiving DFI should be aware that if a file has been duplicated, the Originator may have already generated a reversing file to remedy the situation.

R29 Corporate Customer Advises Not Authorized
The RDFI has been notified by the Receiver (non-consumer) that the Originator of a given transaction has not been authorized to debit the Receiver's account.

R31 Permissible Return Entry (CCD and CTX only)
The RDFI has been notified by the ODFI that the ODFI agrees to accept a corporate return entry (CCD and CTX) in accordance with section 7.3 (ODFI Agreement to Accept CCD or CTX Return) of the NACHA Operating Rules.

R33 Return of XCK Entry
The RDFI determines at its sole discretion to return an XCK entry. This return reason code may only be used to return XCK entries. An XCK entry may be returned up to sixty (60) days after its Settlement Date.

(Note: Effective March 15, 2002, the following new Return Reason Code (R37 Source Document Presented for Payment) will become effective to address situations in which both an ARC entry or POP entry and the Receiver's source document (i.e., the check) have been presented for payment:)

R37 Source Document Presented for Payment
The source document to which an ARC entry or a POP entry relates has been presented for payment. The Receiver may request immediate credit from the RDFI for an ARC entry or a POP entry for the reason described above. The request must be made in writing within fifteen (15) days after the RDFI sends or makes available to the Receiver information relating to that debit entry. The Receiver must also provide the RDFI with a written statement under penalty of perjury that the source document was presented for payment. An RDFI using this return reason code must transmit the return entry by its 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 banking day following the sixtieth calendar day following the Settlement Date of the ARC entry or the POP entry.

The following return reason codes may be used by participating Federal Government Agencies to return Automated Enrollment entries.

R40 Return of ENR Entry by Federal Government Agency (ENR only)
The Federal Government Agency that received the Automated Enrollment entry has chosen not to accept ENR entries. DFIs/Receivers should contact the Agency outside the ACH system regarding the enrollment information.

The following return reason codes relate to the contents of the addenda records associated with the ENR entry.

R41 Invalid Transaction Code
The Transaction Code included in Field 3 of the Addenda Record is something other than "22" (Automated Deposit for Demand Account Credit Records), "27" (Automated Payment for Demand Debit Account), "32" (Automated Deposit for Savings Account Credit Records), or "37" (Automated Payment for Savings Account Debit Records). The transaction code contained within the Payment Related Information Field of the addenda record is used to indicate the type of ACH entry that will be originated either by the DFI's account holder or the Federal Agency.

Note: For direct deposit credit enrollments for Federal Government benefit payments, the Transaction Code contained within the Payment Related Information Field of the addenda record must contain either a "22" (Automated Deposit for Demand Credit Account Records) or a "32" (Automated Deposit for Savings Account Credit Records). Use of any other transaction code within this field will cause the enrollment entry to be returned by the Federal Government Agency.

R42 Routing Number/Check Digit Error
The routing number of the Receiver's financial institution contained within the Payment Related Information field of the addenda record is incorrect. The routing number and check digit for the Receiver's financial institution are necessary for the Federal Government Agency to transmit future ACH payments to the Receiver's account. An invalid routing number and/or check digit will cause the enrollment entry to be returned by the Federal Government Agency.

R43 Invalid DFI Account Number
The enrollee's account number at the DFI (contained within the Payment Related Information Field of the addenda record) is either missing, exceeds 17 positions, or contains invalid characters. The enrollee's account number is necessary for the Federal Government Agency to transmit future ACH transactions to the enrollee. An invalid account number will cause the enrollment entry to be returned by the Federal Government Agency.

R44 Invalid Individual ID Number/Identification Number
The enrollee's identification number contained within the Payment Related Information field of the addenda record is either invalid (e.g., contains more or fewer than 9 digits or is otherwise an invalid number), or it does not match a corresponding identification number in the Federal Agency's records. The enrollee's valid identification number is necessary for the Federal Government Agency to process the enrollment information. An invalid identification number or one not matching the Federal Agency's records will cause the enrollment entry to be returned by the Agency.

R45 Invalid Individual Name/Company Name
The name of the enrollee provided in the Payment Related Information field of the addenda record either does not match a corresponding name in the Federal Agency's records, or it fails to include at least one alphameric character. The enrollee's name is necessary for the Federal Agency to process the enrollment information. An enrollee's name not matching the Federal Government Agency's records or not containing alphameric characters will cause the enrollment entry to be returned by the Agency.

R46 Invalid Representative Payee Indicator
The Representative Payee Indicator Code included in the Payment Related Information field of the addenda record has been omitted or is not consistent with the Federal Agency's records. The Representative Payee Indicator code must be either a "zero" to denote that the payment will be sent to the Receiver, or a "one" to denote that the payment will be sent to a representative payee on behalf of an entitled beneficiary. (Example: 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.)

Note: For direct deposit credit enrollments for Federal Government benefit payments, the Representative Payee Indicator field must contain a "0" (zero) or a "1" (one). Any other code in this field will cause the enrollment entry to be returned by the Federal Government Agency.

R47 Duplicate Enrollment. The Federal Agency has received duplicate Automated Enrollment entries from the same DFI.

The following Return Reason Codes may be used only for Re-presented Check Entries.

R50 State Law Affecting RCK Acceptance

R51 Item is Ineligible, Notice Not Provided, Signature Not Genuine, Item Altered, or Amount of Entry Not Accurately Obtained from Item (adjustment entries)

An RCK entry may be considered to be ineligible if (1) the item to which the RCK entry relates is not an item within the meaning of Revised Article 4 of the Uniform Commercial Code (1990 Official Text); (2) the item is not a negotiable demand draft drawn on or payable through or at a Participating DFI, other than a Federal Reserve Bank or Federal Home Loan Bank; (3) the item is in an amount of $2,500 or more; (4) the item does not indicate on the face of the document that it was returned due to "Not Sufficient Funds," "NSF," "Uncollected Funds," or comparable language; (5) the item is dated more than 180 days from the date the entry is being transmitted to the RDFI (i.e., the item to which the RCK entry relates is stale dated); (6) the item is drawn on a non-Consumer Account; or (7) the item has been previously presented more than two times in its physical form, or more than one time in its physical form and more than one time as an RCK entry.

OR

The Originator did not provide notice as provided for within Article Three, subsection 3.5.2 (Notice Obligation).

OR

All signatures on the item to which the RCK entry relates are not authentic or authorized, or the item to which the RCK entry relates has been altered.

OR

The amount of the RCK entry was not accurately obtained from the item.

An RDFI using this Return Reason Code must transmit the return entry by its 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 banking day following the sixtieth calendar day following the Settlement Date of the RCK entry to which the item relates.

R52 Stop Payment on Item (adjustment entries)
The RDFI determines that a stop payment order has been placed on the item to which the RCK entry relates. An RDFI using this Return Reason Code must transmit the return entry by its 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 banking day following the sixtieth calendar day following the settlement date of the RCK entry to which the item relates.

R53 Item and ACH Entry Presented for Payment (adjustment entries)
 In addition to an RCK entry, the item to which the RCK entry relates has also been presented for payment. The Receiver may request immediate credit from the RDFI for an RCK entry for the reason described above. The request must be made in writing within fifteen (15) days after the RDFI sends or makes available to the Receiver information relating to that debit entry. The Receiver must also provide the RDFI with a written statement under penalty of perjury, pursuant to subsection 7.6.5.3 (Receiver's Written Statement Under Penalty of Perjury for RCK Entries), that both the RCK entry and the item to which it relates were presented for payment. An RDFI using this return reason code must transmit the return entry by its 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 banking day following the sixtieth calendar day following the Settlement Date of the RCK entry.

R80 Cross-Border Payment Coding Error
The cross- border entry is being returned due to one or more of the following conditions: invalid Foreign Exchange Indicator; invalid ISO Originating Currency Code; invalid ISO Destination Currency Code; invalid ISO Destination Country Code; or invalid Transaction Type Code.

R81 Non-Participant in Cross-Border Program
The cross-border entry is being returned because the Originating Gateway Operator does not have an agreement with the ODFI to process cross-border entries.

R82 Invalid Foreign Receiving DFI Identification
The reference used to identify the Foreign Receiving DFI of an outbound cross-border entry is invalid.

R83 Foreign Receiving DFI Unable to Settle
The cross- border entry is being returned due to settlement problems in the foreign payment system.

*Source NACHA Operating Rules and Guidelines 2002