When you process an E-Check payment online we fund your landlord's bank account the next business day. However, all banks have a 3-5 business day turn time to either approve the requested payment made from RentTrack or return the payment you made online. All banks will refer to this E-Check payment as an ACH transaction. 

When a bank returns a payment, they will provide a return code which details WHY WAS IT RETURNED OR REVERSED?

You can find the return code and reason on the reversal email we have sent.
[see example below]

Listed below are the most common ACH/E-Check Return Codes:

R01: Insufficient Funds:

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


  • Contact your Property Manager and see if it okay to submit another online payment. If approved submit another payment online when the funds are available. 

R02: Account Closed:

  • A previously active account has been closed by action of the customer or the RDFI.


  • Login into RentTrack and DELETE your current payment source. This account is closed. Call your bank and get the current ACCOUNT and ROUTING information.

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

    What this means:

    When the resident entered the payment, either the Routing Number, Bank Account Number, and/or the Customer Name was entered incorrectly. This account cannot be used to submit another payment.

    What should the property manager do?
    If the resident can still make a payment, inform them that they need to verify their account information and re-enter their payment. If they are not allowed to pay online, you can disable their account from your Dashboard.

    What should the resident do?
    The account information entered is wrong, login into RentTrack and DELETE the "PAYMENT SOURCE" of the invalid account, verify your information and create a new payment.

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.


  • YOU ENTERED YOUR ACCOUNT NUMBER OR ROUTING NUMBER WRONG, login into RentTrack and DELETE your current "PAYMENT SOURCE". Call your bank to get the correct routing and account number.

R08: Payment Stopped or Stop Payment on Item:

  • Account holder has stopped payment on this single transaction.

    What this means:
    The person who owns the bank account (i.e. the resident) has told their bank that this ACH payment was unauthorized.

    What should the property manager do?
    Contact the resident or applicant to find out why they stopped the payment and how they'd like to proceed. Once a transaction has been returned with this code, the same bank account cannot be used in a future transaction. Doing so could result in a fine.

    What should the resident do?
    Verify with your property manager how to make your next payment. If you are allowed to make another payment online, you will need to use a different payment source. Attempting to use the same account will result in an error/failed payment.

R16: Account Frozen

  • The funds in the account are unavailable due to specific action taken by the RDFI or by legal action.

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.


  • The bank account you entered cannot be used for ACH Payments. This account has maxed out its transactions; please use another account.


  • You need to create a new payment source, this one will not work.



To see a list of all return codes, please see below:

R05: Unauthorized Debit to Consumer Account Using Corporate SEC Code

  • An ACH Transaction entered as “CCD” was attempted against a consumer’s personal bank account, and the consumer reported the transaction to the bank as not authorized.
  • Ordinarily a “CCD” transaction has a 3-day window in which the transaction can be disputed, but this code directs the bank to honor the return if it is entered within 60 days of the original transaction. This is done because the transaction was incorrectly coded as “CCD” when entered. “CCD” is used only when charging a business bank account.
  • You cannot re-submit this transaction. Any additional transactions you attempt to process against this account will also be returned unless your customer specifically instructs his bank to accept them.


  • You canceled this payment, this account cannot be used again in RentTrack, DELETE THIS PAYMENT SOURCE. You may make another payment in RentTrack, but not with that account information.

R06: Returned per ODFI's Request

  • 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 RDFI according to Article Five (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 an executed affidavit declaring and swearing under oath 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)

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.


  • There were insufficient funds in your account to complete the transaction.


  • You can try the transaction again (you will need to re-enter it as a new transaction) up to two times within 30 days of the original authorization date.
  • The RDFI (bank who received the consumer payment) has been notified by the Receiver (bank where funds were withdrawn from) that the Entry is unauthorized, improper, ineligible, or pat of an Incomplete Transaction. Any transactions within a 60 calendar days from the same account will also be returned.


  • The customer submitted a signed document, Written Statement Under Penalty of Perjury, to their bank stating that the transaction was not authorized, or that the transaction was entered for an amount different than the authorized amount, or was submitted before the authorized date.


  • All recurring payments from this account are stopped, consumers can not make a payment in RentTrack with this account unless they specifically instruct their bank to authorize a payment.
  • Unfortunately, there is no dispute resolution available to property managers within the ACH Network. If the customer continues to claim the transaction was not authorized, but property managers have proof that it was properly authorized, property managers will need to sue the customer in Small Claims Court to collect. If property manager decides to take this course of action, please contact RentTrack to obtain a copy of the statement your customer submitted to the bank-- you will need this document to pursue your case.


  • Check Truncation Entry Return (Specify) or State Law Affecting Acceptance of PPD Debit Entry Constituting Notice of Presentment or PPD Accounts Receivable Truncated Check Debit Entry [Check Truncation Entry Return (Specify) or State Law Affecting Acceptance of PPD Accounts Receivable Truncated Check Debit Entry]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.).


  • For PPD debit entries constituting notice of presentment or PPD Accounts Receivable Truncated Check Debit Entries, either [For PPD Accounts Receivable Truncated Check Debit Entries, either]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 in a state that requires all canceled checks to a specific type of account to be returned to the Receiver within the periodic statement.


  • A PPD debit entry constituting notice of presentment of an eligible item as defined by Article Two, subsection 2.8.2 (Eligible Item) or a PPD Accounts Receivable Truncated Check Debit Entry as defined by Article Two, subsection 2.9.2 (Eligible Item) 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. [A PPD Accounts Receivable Truncated Check Debit Entry as defined by Article Two, subsection 2.9.2 (Eligible Item) 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.]


  • Branch Sold to Another DFIA 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.


  • Your customer’s account was sold to another bank but the Customer Record in PaySimple was not updated with the new bank information, so the payment you processed was sent to the old bank and cannot be honored.


  • A new transaction has to be entered, please re-enter you routing and account number.


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


  • Beneficiary or Account Holder (Other Than a Representative Payee) DeceasedThe beneficiary is the person entitled to the benefits and is deceased. The beneficiary may or may not be the account holder.


  • The account holder (acting in a non-representative payee capacity) is an owner of the account and is deceased.

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.

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 NumberIn 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: (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 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.

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 CCD or CTX return entry in accordance with Article Seven, section 7.3 (ODFIAgrees to Accept CCD or CTXReturn).

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.

Did this answer your question?