U.S. ACH decline codes

Was this article helpful?
0 out of 0 found this helpful
Follow
Below, you'll find explanations of decline codes you may have encountered, and also potential solutions and resolutions to the issue at hand.
 
Declines are made by the customer's bank, not your software. If your client does not believe their account should have declined, please advise them to call their bank directly for more information.

If you receive a decline that is not listed on this page please contact Merchant Support.

Return Code

Description Definition
C01 Account Number Corrected The Account Number structure is not valid. For example, the Originator uses the on-us field of a check or shared draft to obtain the account number, but additional or fewer characters are needed to post the ACH entry. The account number could also be incorrect due to the transportation of characters, etc. The Correct Account Number appears in the first (left justified) 17 positions of the Corrected Data Field. For outbound cross-border entries, the correct Foreign Receiver's Account Number will appear in the first (left justified) 25 positions of the Correct Data Field.
C02 Routing Number Corrected Due to merger or consolidation, a once-valid Routing Number must be changed. The Correct Routing Number (including Check Digit) appears in the first nine positions of the Corrected Data Field. For outbound cross-border entries, this field will refer to the Originating Gateway Operator's routing number.
C03 Routing and Account Nbr Corrected Due to merger or consolidation, a once-valid Routing Number and Account Number must be changed. This code could also be used when the Originator obtains both the Routing Number and the Account Number from the MICR encoding on a check or share draft, and both are invalid for ACH entries (payable through information.) The Correct Routing Number (including Check Digit) appears in the first nine positions the Corrected Data Field. The Correct Account Number appears in the 13th through 29th positions of the same field with a space in the 10th, 11th, and 12th positions. This code should not be used for outbound cross-border entries due to field length limitations.
C04 Individual Name Corrected The Individual Name filed on the entry needs to be changed. The Correct Account Name appears in the Corrected Data Field.
C05 Transaction Code Corrected The entry is being directed to the wrong type of account. For example, a savings account transaction code is needed, but a demand account transaction code is being used, or vice versa. The correct Transaction Code appears in the first two positions of the Correct Data Field.
C06 Account Nbr and Incorrect Transaction Code Corrected A once-valid Account Number and Transaction Code must both be charged; for example, an entry posting to a savings account should actually be going to a demand account or vice versa, and the account number is also incorrect. The correct Account Number appears in the first (left justified) 17 positions of the Corrected Data Field; the correct Transaction Code appears in the 21st and 22nd positions of the same field with spaces in the 18th, 19th, and 20th positions. For outbound cross-border entries, the correct Foreign Receiver's Account Number will appear in the first (left justified) 25 positions of the Correct Data Field. The correct Transaction Code will appear in the 28th and 29th positions of the same field, with spaces in the 26th and 27th positions.
C07 Routing Nbr, Acct Nbr and Transaction Code Corrected The Routing Number, Account Number, and Transaction Code are all incorrect and must be changed;  for example, an entry posting to a savings account should actually be going to a demand account or vice versa, and the Routing Number and account number are also incorrect. The correct Routing Number (including Check Digit) appears in the first nine positions of the Corrected Data Field; the correct Account Number appears in the 10th through 26th positions of the same field; the correct Transaction Code appears in the 27th and 28th positions of the same field. This change code should not be used for outbound cross-border entries due to field length limitations.
C09 Individual Identification Nbr Corrected Individual's account number with the Originator is incorrect. The correct Account Number appears in the first 22 positions of the Corrected Data Field. (NOTE: This Change Code is used for CIE, MTE, POS, and SHR entries only. Before using this code, the RDFI should verify the Standard Entry Class Code on the original entry. The information identified by this code (Individual ID Number) has a different meaning for these applications than the same field in other applications.) NOTE: Change Code 09 is used for CIE, MTE, POS, and SHR entries. Before using this Code, the RDFI should verify the Standard Entry Class Code on the original entry. The information identified by this code (Individual ID Number) has a different meaning than the same field in other applications.
C10 Company Name Corrected  
C11 Company Identification Corrected  
C12 Company Name and Identification Corrected  
C13 Corrected Addenda Format Information in the Entry Detail Record was correct and the entry was able to be processed and posted by the RDFI. However, information found in the Addenda Record was unclear or was formatted incorrectly. Example: An entry is received with an "05" Addenda Type Code, but the addenda information does not contain ANSI ASC X12.4 data segments or a NACHA endorsed banking convention.
R01 Insufficient Funds The available fund 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 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.
  Invalid Account Number (No such number) It's an invalid account number.  More than likely the result of the card holder closing the account or the bank issuing a new card.
R05 Prenote Required  
R06 Returned Per ODFI's 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 RDIFI according to Article Five (Return, Adjustment, Correction, and Acknowledgment of Entries and Entry Information) of these Results.
R07 Authorization Revoked By Customer 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 debt. 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 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 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

For entries to Consumer Accounts that are not ARC 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 or her 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 fraud.

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 fo 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 ret.

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 Safekeeping Entry Returned 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 filed in the addenda record to specify the reason for the 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.
R13 ACH Not Allowed By This Bank RDFI not qualified to participate or the Routing Number is not valid.
R14 Account Holder Deceased 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 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 are unavailable due to specific action taken by the RDFI or by legal action.
R17 File Record Criteria 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 fields(s) causing the processing error must be identified in the addenda record information field of the return.
R18 Improper Effective 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.
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.

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 ID 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 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 Payment Refused By Biller 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 point.
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 should be used with extreme care. The RDFI should be aware that if a file has been duplicated, the Originator may have already generated a reversal transaction to handle the situation.
R25 Addenda Error

Addenda Record Indicator value is not 0 or 1

or...

Addenda Record Indicator value is 0 but Addenda Record follows.

or...

Addenda Record Indicator value is 1 but no Addenda Record follows.

or...

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.

or...

The Addenda Record Indicator for notifications of change, refused notifications of change, returns, dishonored returns, contested dishonored returns, CBR, DNE, ENR, MTE, PBR, POS, SHR, TRX, and zero dollar entries other than prenotifications is not equal to "1".

or...

Addenda Type Code is not valid if not equal to "01" for CBR or PBR entries, "02" for MTE, POS, or SHR entries; "05" for ACK, ATX, CCD, CIE, CTX, DNE, ENR, PPD, TRX or WEB entries; "98" or "05" (TRX only) on Automated Return, Automated Refused Notification of Change; or "99" or "05" (TRX only) on Automated Return, Automated Dishonored Return, or Automated Contested Dishonored Return Entries.

or...

Total number of Addenda Records exceeds the maximum number allowable (9,999) per Entry Detail Record (CTX, ENR, or TRX).

or...

The number of Addenda Records exceeds one (1) for CBR, CCD, CIE, DNE, MTE, PBR, POS, PPD, SHR, WEB, notifications of change, refused notifications of change, returns, dishonored returns, and contested dishonored returns.

or...

Addenda Sequence Number is not valid.

or...

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 Records (ENR, TRX)

R26 Mandatory Field Error Individual Name contains all spaces or all zeros (MTE Entry)

or...

Individual Identification Number contains all spaces or all zeros (MTE entries or CIE entries.)

or...

Check Serial Number contains all spaces or all zeros (ARC entries, POP entries, RCK entries, or XCK entries.)

or...

Terminal City contains all spaces or all zeros (POP entries only.)

or...

Terminal State contains all spaces or all zeros (POP entries only.)

or...

Card Transaction Type Code is not a valid code as specified in Appendix Two (ACH Record Format Specifications) (POS and SHR entries only.)

or...

Number of Addenda Records in a Corporate Entry Detail Record is not numeric.

or...

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.)

or...

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.)

or...

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.

or...

In a dishonored return or contested dishonored return, the original RDFI Routing Number is not numeric, 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.

or...

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 valued for dishonored returns.

or...

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.
R27 Trace Number Error Original Entry Trace Number is not present in the Addenda Record on an automated return.

or...

Trace Number of an Addenda Record is not the same as the Trace Number of the preceding Entry Detail Record.
R28 Transit/Routing Check Truncation Program The Check Digit for a Routing Number is not valid.
R29 Corporate Customer Advises Not Authorized  
R30 RDFI Not Participate In Check Truncation  
R31 Permissible Return Entry  
R32 RDFI Non-Settlement The RDFI has been notified by the ODFI that the ODFI agrees to accept a CCD or CTX return entry in accordance with Article Seven, section 7.3 (ODFI Agrees to Accept CCD or CTX Return).
R33 Return Of XCK Entry  
R34 Limited Participation DFI The RDFI determines at its sole discretion to return to return an XCK entry. This return reason code may only be used to return XCK entries.
R61 Misrouted Return  
R62 Incorrect Trace Number  
R63 Incorrect Dollar  
R65 Incorrect Transaction Code  
R66 Incorrect Company Identification  
R67 Duplicate Return  
R68 Untimely Return  
R69 Multiple Errors  
R70 Permissible Return Entry Not Accepted  
R71 Misrouted Dishonored Return  
R73 Timely Original Return  
R74 Corrected Item  
R36 Credit Not Allowed for Transaction Code  
R37 Source Document Presented for Payment  
R38 Stop Payment on Source Document  

Back to top

 

 










0 Comments
Powered by Zendesk