Note For additional information on return reason codes, and for up-to-date reason codes and descriptions, refer to your institution's ACH Rules book and NACHA's website at http://www.nacha.org/.

Return reason categories are found on the system by performing a query (using the AHRETRSN entity in the BANKCTL library).

Return
Reason
Code

Return Reason Code Description

R13

RDFI Not Qualified to Participate Invalid ACH Routing Number

R18

Improper Effective Entry Date

• 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.
• The effective entry date for a debit entry is more than one banking day after the processing date.

R19

Amount Field Error

• Amount field is non-numeric.
• Amount field is not zero in a prenotification, DNE, ENR, Notification of Change, Refused Notification of Change, or zero dollar entry.
• Amount field is zero in an entry other than a prenotification, DNE, ENR, Notification of Change, Refused Notification of Change, Return, Dishonored Return, Contested Dishonored Return, or zero dollar entry.
• Amount field is greater than $25,000 for ARC and POP entries.

R25

Addenda Error

• Addenda Record Indicator value is not 0 or 1.
• Addenda Record Indicator value is 0 but Addenda Record follows.
• Addenda Record Indicator value is 1 but no Addenda Record follows.
• Addenda Record Indicator on a CTX or TRX entry is 0 and Number of Items Paid or Number of Addenda Records is not zero. Addenda Record Indicator is 1 and Number of Items Paid or Number of Addenda Records is 0.
• The Addenda Record Indicator for notifications of change, refused notifications of change, returns, dishonored returns, contested dishonored returns, DNE, ENR, MTE, POS, SHR, TRX, and zero dollar entries other than prenotifications is not equal to "1".
• Addenda Type Code is not valid if not equal to "02" for MTE, POS, or SHR entries; "05" for ACK, ATX, CCD, CIE, CTX, DNE, ENR, PPD, TRX, or WEB entries; "98" on Automated Notification of Change or Automated Refused Notification of Change; or "99" or "05" (TRX only) on Automated Return, Automated Dishonored Return, or Automated Contested Dishonored Return Entries.
• Total number of Addenda Records exceeds the maximum number allowable (9,999) per Entry Detail Record (CTX, ENR, or TRX).
• The number of Addenda Records exceeds one (1) for CCD, CIE, DNE, MTE, POS, PPD, SHR, WEB, notifications of change, refused notifications of change, returns, dishonored returns, and contested dishonored returns.
• Addenda Sequence Number is not valid.
• The actual number of addenda records is not equal to the Number of Addenda Records in the Corporate Entry Detail Record (CTX) or the Entry Detail Record (ENR, TRX).R26 Mandatory Field Error
• Individual Name contains all spaces or all zeros (MTE Entry).
• Individual Identification Number contains all spaces or all zeros (MTE entries or CIE entries).
• Check Serial Number contains all spaces or all zeros (ARC entries, POP entries, RCK entries, or XCK entries).
• Terminal City contains all spaces or all zeros (POP entries only).
• Terminal State contains all spaces or all zeros (POP entries only).
• Card Transaction Type Code is not a valid code as specified in Appendix Two [ACH Record Format Specifications) (POS and SHR entries only].
• Number of Addenda Records in a Corporate Entry Detail Record is not numeric.
• The Return Reason Code field for return entries, the Dishonored Return Reason Code field for dishonored returns, or the Contested Dishonored Return Reason Code field for contested dishonored returns does not contain a valid code as specified in Appendix Five (Return Entries).
• The Change Code field for notification of change entries or the Refused COR Code field for refused notification of change entries does not contain a valid code as specified in Appendix Six (Notification of Change).
• On a Notification of Change or Refused Notification of Change, the Corrected Data field is blank, or on a Refused Notification of Change, the Change Code is not a currently assigned value (see Appendix Six, Notification of Change) or the COR Trace Sequence Number field is not numeric. A Refused Notification of Change is denoted by a valid Refused COR Code in the Refused COR Code field. See Appendix Six for a list of valid codes.
• In a dishonored return or contested dishonored return, the Return Trace Number is not numeric, the Return Settlement Date is not a valid Julian date in the range 001-366, or the Return Reason Code is not a currently assigned value for Returns.
• In a dishonored return bearing Return Reason Code R69 (Field Error), the Addenda Information Field contains all spaces or all zeros.
• In a contested dishonored return, the Dishonored Return Trace Number is not numeric, the Dishonored Return Settlement Date is not a valid Julian date

R26

Mandatory Field Error

• Individual name contains all spaces or all zeros (MTE entry).
• Individual identification number contains all spaces or all zeros (MET entries or CIE entries).
• Check serial number contains all spaces or all zeros (ARC entries, POP entries, RCK entries, or XCK entries).
• Terminal city contains all spaces or all zeros (POP entries only).
• Terminal state contains all spaces or all zeros (POP entries only).
• Card transaction type code is not a valid code.
• Number of addenda records in a corporate entry detail record is not numeric.
• The return reason code field for return entries, the dishonored return reason code field for dishonored returns, or the contested dishonored return reason code field for contested dishonored returns does not contain a valid code.
• The change code field for notification of change entries or the refused COR code field for refused notification of change entries does not contain a valid code.
• On a notification of change or refused notification of change, the corrected data field is blank, or on a refused notification of change, the change code is not a currently assigned value or the COR trace sequence number field is not numeric.
• In a dishonored return or contested dishonored return, the return trace number is not numeric, the return settlement date is not a valid Julian date in the range 001-366, or the return reason code is not a currently assigned value for returns.
• In a contested dishonored return, the dishonored return trace number is not numeric, the dishonored return settlement date is not a valid Julian date in the range 001-366, or the dishonored return reason code is not a currently assigned value for dishonored returns.
• In a contested dishonored return with contested dishonored return reason code R73 (timely original return), the original settlement date is not a valid Julian date in the range 001- 366, or the date original entry returned is not a valid date in the range 001-366, or the Dishonored Return Reason Code is not a currently assigned value for dishonored returns.
• In a contested dishonored return with Contested Dishonored Return Reason Code R73 (timely original return), the Original Settlement Date is not a valid Julian date in the range 001-366, or the Date Original Entry Returned is not a valid date.

R27

Trace Number Error

• Original Entry Trace Number is not present in the Addenda Record on an automated return. Original Entry Trace Number is not present in the Addenda Record on an automated return or Notification of Change entry.
• Trace Number of an Addenda Record is not the same as the Trace Number of the preceding Entry Detail Record.

R28

Routing Number Check Digit Error

The Check Digit for a Routing Number is not valid.

R30

RDFI Not Participant in Check Truncation Program

R32

RDFI Non-Settlement

The RDFI is not able to settle the entry.

R34

Limited Participation DFI

The RDFI's participation has been limited by a federal or state supervisor.

R35

Return of Improper Debit Entry

• ACH debit entries (with the exception of reversals) are not permitted for use with the CIE Standard Entry Class Code.
• ACH debit entries (with the exception of reversals) are not permitted to loan accounts.

R36

Return of Improper Credit Entry

• ACH credit entries (with the exception of reversals) are not permitted for use with the ARC Standard Entry Class Code.
• ACH credit entries (with the exception of reversals) are not permitted for use with the POP Standard Entry Class Code.
• RCK entries must be limited to debits to demand accounts, with the exception of reversals to correct erroneous entries.
• ACH credit entries (with the exception of reversals) are not permitted for use with the WEB Standard Entry Class Code.
• ACH credit entries (with the exception of reversals) are not permitted for use with the TEL Standard Entry Class Code.
• ACH credit entries (with the exception of reversals) are not permitted for use with the following Standard Entry Class Codes: ARC, POP, RCK, TEL, WEB, and XCK.

Return
Reason
Code

Return Reason Code Description

R71

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 (positions 04-12, including Check Digit, of the Entry Detail Record).

R72

Untimely Dishonored Return

The dishonored return entry has not been sent within the designated timeframe.

R73

Timely Original Return

The RDFI is certifying that the original return entry was sent within the timeframe designated in these rules.

R75

Original Return Not a Duplicate

The original return entry was not a duplicate of an entry previously returned by the RDFI. This code may be used by the RDFI to contest an entry dishonored by the ODFI using Return Reason Code R67 (Duplicate Return).

This code may be used by the RDFI to contest the ODFI's dishonor of an entry as a duplicate return [R67 (duplicate return)] when the return was not a duplicate.

R76

No Errors Found

The original return entry did not contain the errors indicated by the ODFI in the Dishonored Return Entry bearing Return Reason Code R69 (Field Errors).

This code is used by an RDFI to contest the ODFI's dishonor of a return entry for multiple errors [using return reason code R69 (multiple field errors)] when no errors were present.

R77

R77

Non-Acceptance of R62 Dishonored Return

This return reason can only be used to contest a dishonored return with a R62 return reason.

Return
Reason
Code

Return Reason Code Description

R61

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 (positions 04-12, including Check Digit, of the Entry Detail Record).

R62

Return of Erroneous or Reversing Debit

R67

Duplicate Return

The ODFI has received more than one return for the same entry.

R68

Untimely Return

The return entry has not been sent within the timeframe established by these rules.

R69

R69 Multiple Errors [Field Error(s)]

Two or more of the following fields - Original Entry Trace Number, Amount, Individual Identification Number/Identification Number, Company Identification, and/or Tran code -- are incorrect. [One or more of the following fields – DFI Account Number, Original Entry Trace Number, Amount, Individual Identification Number/Identification Number, Company Identification, and/or Tran code - are incorrect. The ODFI must insert the appropriate code(s) from the list below, separated by an asterisk (*), within the Addenda Information Field of the Addenda Record Format for Automated Dishonored Returns to indicate the field(s) in which the errors occur:

• 01 Return Contains Incorrect 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 Tran code
• 06 Return Contains Incorrect Company Identification Number
  for example, 01*03*06

  You select check boxes associated with the errors after the user enters R69.

  HORIZON-XE does not support R74 (corrected return) to correct and return a dishonored return with a reason code of R69.

R70

Permissible Return Entry Not Accepted Permissible Return Entry Not Accepted/Return Not Requested by ODFI

The ODFI has received a CCD or CTX return entry identified by the RDFI as being returned with the permission of the ODFI, but the ODFI has not agreed to accept the entry. This code may be used only to dishonor a return containing an R31 return reason code. 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. This code may be used only to dishonor return entries containing return reason codes R06 and R31.

Return
Reason
Code

Return Reason Code Description

R40

Return of ENR Entry by Federal Government Agency (ENR only)

The Federal Government Agency determines at its sole discretion to return an ENR entry. This return reason code may be used only to return ENR entries.

R41

Invalid Transaction Code (ENR only)

Either the Tran code included in Field 3 of the Addenda Record does not conform to the ACH Record Format Specifications or it is not appropriate with regard to an automated enrollment entry.

R42

Routing Number/Check Digit Error (ENR only)

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.

R43

Invalid DFI Account Number (ENR only)

The consumer's or company's account number included in Field 3 of the Addenda Record must include at least one alphabetic character.

R44

Invalid Individual ID Number/Identification Number (ENR only)

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.

R45

Invalid Individual Name/Company Name (ENR only)

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 alphanumeric character.

R46

Invalid Representative Payee Indicator (ENR only)

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.

R47

Duplicate Enrollment (ENR only)

The entry is a duplicate of an automated enrollment entry previously initiated by a participant in the ENR automated enrollment program.

Return
Reason
Code

Return Reason Code Description

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 Receiving Depository Financial Institution (RDFI).

R03

No Account/Unable to Locate Account

The 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 open account. (Note: This Return Reason Code may not be used to return ARC entries or 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 may contain an incorrect number of digits.

R05

Reserved (Unauthorized Debit to Consumer Account Using Corporate SEC Code).

A CCD, CTX, or CBR debit entry was transmitted to a Consumer Account of the Receiver and was not authorized by the Receiver. 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 8.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 a 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. 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 original entry.

R06

Returned per ODFI's Request

The Originating Depository Financial Institution (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 Six (Return, Adjustment, Correction, and Acknowledgment of Entries and Entry Information) of these 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

The Receiver of a debit transaction has the right to stop payment on any specific ACH debit. A stop payment request is handled in accordance with the provisions of Article Eight (Recall, Stop Payment, Recredit, and Adjustment) of these Rules. The RDFI verifies 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.

R09

Uncollected Funds

Sufficient book or ledger balance exists to satisfy the dollar value of the transaction, but the dollar value of transactions in the process of collection (i.e., 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 8.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. With the exception of ARC and POP entries, 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.7.1 (Notice Obligation), (2) the source document used for the debit entry is improper pursuant to subsection 3.7.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 8.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.8.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 8.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 is used only if no other return reason code is applicable. The RDFI uses 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.).

The Addenda Information field is required when using this return reason code.

R12

Account Sold to Another DFI

A financial institution may continue to receive entries destined for an account that has been sold to another financial institution. Because the RDFI no longer maintains the account and is unable to post the entry, it returns 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

• The beneficiary is the person entitled to the benefits and is deceased. The beneficiary may or may not be the account holder; or
• 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 are unavailable due to specific action taken by the RDFI or by legal action. Access to the account is restricted due to specific action taken by the RDFI or by legal action.

R17

Questionable transaction

Beginning on June 21, 2019, a new NACHA rule will allow financial institutions to use return reason code R17 to indicate that they believe a transaction was initiated under questionable circumstances.

R20

Non-Transaction Account

The ACH entry destined for a non-transaction account, as defined in Regulation D, would include either an account against which transactions are prohibited or limited or a pass-through where the 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 is normally used on CIE transactions.

R22

Invalid Individual ID Number

In CIE and MTE entries, the Individual ID Number is used by the Receiver to identify the account. The Receiver has indicated to the RDFI that the number with 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:

• a minimum amount required by the Receiver has not been remitted
• the exact amount required has not been remitted
• the account is subject to litigation and the Receiver does not accept the transaction
• acceptance of the transaction results in an overpayment
• the Originator is not known by the Receiver
• the Receiver has not authorized this credit entry to this account.

R24

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. This code is used with extreme care. The RDFI should be aware that if a file is duplicated, the Originator may have already generated a reversal transaction to handle the situation.

R29

Corporate Customer Advises Not Authorized

The RDFI has been notified by the Receiver (non-consumer) that a specific transaction has not been authorized by the Receiver.

R31

Permissible Return Entry (CCD and CTX only)

The RDFI has been notified by the ODFI that the ODFI agrees to accept a CCD or CTX return entry in accordance with Article Eight, section 8.3 (ODFI Agrees to Accept CCD or CTX Return).

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 days after its Settlement Date.

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.

R38

Stop Payment on Source Document

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.

R39

Improper Source Document

The RDFI determines that the source document used for an ARC or POP entry to its Receiver's account is improper pursuant to subsections 3.7.2 (Source Documents) and 3.8.1 (Source Documents). An entry returned using this Return Reason Code 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.

This code is used by an RDFI when the source document used for the debit entry is improper.

R50

State Law Affecting RCK Acceptance

• 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

• 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.
  
  An RCK entry that is returned using this Return Reason Code must be transmitted by the RDFI to its ACH Operator no later than midnight of the second banking day following the banking day of receipt of the presentment notice.

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 does not contain a pre-printed serial number; (4) the item is in an amount of $2,500 or more; (5) 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; (6) 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); (7) the item is drawn on a non-Consumer Account; or (8) 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.6.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. The Receiver may request immediate credit from the RDFI for an RCK 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 pertaining to that debit entry. The Receiver must also provide the RDFI with a written statement under penalty of perjury, pursuant to subsection 8.6.5.3 (Receiver's Written Statement Under Penalty of Perjury for RCK Entries), that (i) notice stating the terms of the re- presented check entry policy was not provided by the Originator, (ii) the item to which the RCK entry relates is not eligible pursuant to subsection 2.8.2 (Eligible Item), (iii) all signatures on the item to which the RCK entry relates are not authorized or authentic, or the item to which the RCK entry relates has been altered, or (iv) 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 8.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
• invalid Transaction Type Code

  This return reason code is only used by the gateway operator when the SEC code of the transaction is IAT.

  The following message displays if this return reason code is used with a record that does not have an SEC code of IAT:
  Return Code not valid for SEC: xxx. (where xxx is the SEC 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.

This return reason code is only used by the gateway operator when the SEC code of the transaction is IAT.

The following message displays if this return reason code is used with a record that does not have an SEC code of IAT:
Return Code not valid for SEC: xxx. (where xxx is the SEC code)

R82

Invalid Foreign Receiving DFI Identification

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

This return reason code is only used by the gateway operator when the SEC code of the transaction is IAT.

The following message displays if this return reason code is used with a record that does not have an SEC code of IAT:
Return Code not valid for SEC: xxx. (where xxx is the SEC code)

R83

Foreign Receiving DFI Unable to Settle

The cross-border entry is being returned due to settlement problems in the foreign payment system.

This return reason code is only used by the gateway operator when the SEC code of the transaction is IAT.

The following message displays if this return reason code is used with a record that does not have an SEC code of IAT:
Return Code not valid for SEC: xxx. (where xxx is the SEC code)

R84

Entry Not Processed by OGO

The cross-border entry has not been processed and is being returned at the OGO's discretion because the processing of such entry may expose the OGO to excessive risk.

This return reason code is only used by the gateway operator when the SEC code of the transaction is IAT.

The following message displays if this return reason code is used with a record that does not have an SEC code of IAT:
Return Code not valid for SEC: xxx. (where xxx is the SEC code)