2023 ACH Origination Guide
ACH Facts & ACH Originator Responsibilities
Page 5 of 11
Reinitiation of Return Entries
An Originator may reinitiate an entry that was returned if:
• the entry was returned for insufficient or uncollected funds (the entry cannot be reinitiated more than two times
following the return of the original entry);
• the entry was returned for stopped payment and reinitiation has been authorized by the Receiver; or
• the Originator has taken corrective action to remedy the reason for the return.
All reinitiated entries must include the description
“RETRY PYMT”
in the Company Entry Description field
to identify entries that are permissible resubmissions of returned entries under the rules for reinitiation. This
description supersedes any existing entry description and notifies the Receiver that the entry relates to a
previously returned entry; it will facilitate research and dispute resolution for RDFIs. Except for reinitiated
reversals, the description “RETRY PYMT” must replace the original content of the Company Entry
Description field transmitted in the original entry, even in cases where the original entry contains a description
required by the Rules, such as REDEPCHECK, RETURN FEE, etc.
The Rules explicitly prohibit the reinitiation of entries outside of the limited circumstances stated above. The
Rules clarify four categories of entries that are not considered reinitiations. First, a debit entry in a series of
preauthorized recurring debit entries will not be treated as a reinitiated entry, even if the subsequent debit entry
follows a returned debit entry, as long as the subsequent entry is not contingent upon whether an earlier debit
entry in the series has been returned. For example, if a consumer arranges for his minimum payment on a credit
card balance to be paid monthly from an account based on a preauthorization for recurring debits, and the
consumer’s debit entry for the September minimum payment is returned for insufficient funds, the debit entry
for the October minimum payment would not be considered a reinitiation of the debit entry with respect to the
returned September entry.
Second, a debit entry is not be considered a reinitiation if the Originator obtains a new authorization for the debit
entry after the receipt of the return. For example, if an Originator has twice attempted to re-present an entry
returned as NSF, and the consumer later provides a new authorization because he now has funds in his account,
the Originator is permitted to debit the account. The timing requirement is important, however, since
Originators will not be permitted to obtain advance approval to debit an account in a manner that would
otherwise violate the reinitiation rule.
Third, an entry that has been returned due to invalid or incorrect routing and account information (i.e., R03/R04)
is not considered to be a reinitiated entry when corrected and subsequently transmitted into the ACH Network.
By definition, a Reinititated Entry is an entry to the same Receiver’s account. In this situation, a new entry with
corrected routing and/or account number information would be the first presentment to the correct Receiver’s
account and should not be identified as a reinititated entry. To identify the correct entry as a reinitiated entry
would cause confusion to the Receiver, since there was no previous attempt to post the entry to the correct
Receiver’s account.
Lastly, if the RDFI returns an entry using R11 - Customer Advises Entry Not in Accordance With the Terms
of the Authorization, and the Originator is able to correct the reason for the return, the Originator can submit a
new entry without obtaining a new authorization. The new entry must be submitted within sixty days of the
Settlement Date of the R11 return entry. The new entry will not be treated as a reinitiated entry if the defect is
corrected to conform to the terms of the original authorization.