The ACH reinitiation rules set by Nacha let a business retry a failed ACH debit up to two more times after the original attempt, for a maximum of three submissions total, and every attempt must land within 180 days of the original settlement date. The retry is only allowed for certain return reasons, the entry has to be labeled clearly, and several data fields must stay identical to the original. Getting any piece wrong is treated as an improper reinitiation practice and can draw enforcement action.
Three Attempts, 180 Days
The count is absolute: the original entry plus two reinitiations. It is not per return code, not per billing cycle, not reset by a change in circumstances. If the first retry bounces, you get one more attempt and that is the end of the line for that entry.
Every reinitiation also has to occur within 180 days of the settlement date of the original entry. Once the six-month window closes, the original authorization no longer supports another attempt on that transaction. Collecting after that point requires a fresh authorization from the customer for a new entry, not a resubmission of the old one.
A fourth submission, or any submission after the 180-day deadline, is considered an improper reinitiation practice. That can lead to fines and, in serious cases, a directive to the originating bank to suspend the offending company from ACH origination entirely.
Which Return Codes Allow a Retry
Reinitiation is limited to returns that suggest a temporary funding problem rather than a fundamental issue with the account or the customer’s consent. In practice, two codes cover almost all eligible retries:
- R01 (Insufficient Funds): the account did not have enough money to cover the debit. The shortfall may resolve within a few days, which is why the retry is allowed.
- R09 (Uncollected Funds): the funds exist in the account but have not cleared yet. Like R01, this is a timing issue.
The list of codes that block reinitiation is longer and more important to internalize. Any return indicating the account itself is invalid or closed cannot be reinitiated, because retrying will not fix a nonexistent account. R03 (no account or unable to locate account) and R04 (invalid account number) both fall in this bucket. Resubmitting against these codes is a rules violation.
Returns flagged as unauthorized are completely off-limits. Nacha is explicit on the point: an unauthorized debit cannot be remedied through reinitiation. The unauthorized return codes are R05, R07, R10, R29, and R51. Retrying any of these is treated as an improper practice regardless of the circumstances. The only path forward is a brand-new authorization from the customer and a separate entry.
Stop payment returns (R08) follow the same logic. The customer actively instructed their bank to block the payment. Resubmitting the same entry without new authorization ignores that instruction and exposes you to enforcement risk.
How to Format a Reinitiated Entry
Reinitiated entries must be clearly labeled so receiving banks and account holders can tell the difference between a new charge and a retry. Nacha Operating Rules Subsection 2.12.4.2 requires the Company Entry Description field to read “RETRY PYMT” for any permissible resubmission of a returned entry.1Nacha. ACH Network Risk and Enforcement Topics That description shows up on the customer’s bank statement and signals to the receiving institution that the debit is a second or third attempt rather than a duplicate or fraudulent charge.
Three data fields must remain identical to the original entry: Company Name, Company ID, and Amount.1Nacha. ACH Network Risk and Enforcement Topics Changing any of these turns the entry into something other than a reinitiation under the rules.
The amount requirement is where businesses most often trip up. You cannot roll late fees, NSF penalties, or convenience charges into the reinitiated entry. Those costs have to be billed as a separate, independently authorized transaction. Reinitiating an entry for an amount greater or less than the original is considered improper.
Other fields can be modified only to the extent necessary to correct an error or help the entry process correctly. Updating the effective entry date to a new settlement date is expected. Changing the receiving account number because you have updated information is not reinitiation at all; that is a new entry requiring its own authorization.
The R11 Correction Path Is Different
Return code R11 (“Customer Advises Entry Not in Accordance with the Terms of the Authorization”) sits between reinitiation and a completely new entry. When the return reflects a correctable error, such as a wrong amount or a debit that settled earlier than authorized, the originator can fix the error and transmit a corrected entry without obtaining a new authorization.2Nacha. Differentiating Unauthorized Return Reasons
The corrected entry must be transmitted within 60 days of the R11 return’s settlement date, a much tighter window than the standard 180-day reinitiation period. The originator carries a warranty that the corrected entry actually conforms to the original authorization. If the error cannot be corrected, this process does not apply and you cannot resubmit.
What Does Not Count as Reinitiation
If one debit in a series of recurring payments bounces, the next scheduled debit in that series does not count as a reinitiation. Nacha’s rules carve out recurring debits, provided the subsequent entry is part of the preauthorized schedule and not contingent on whether the earlier entry was returned.1Nacha. ACH Network Risk and Enforcement Topics A customer’s January subscription payment can return R01 while February’s scheduled debit still stands on its own authorization. You retain the option to reinitiate the failed January entry separately, as long as you stay within the three-attempt limit and label it “RETRY PYMT.”
Scheduling an extra debit disguised as a recurring payment to sidestep the reinitiation limits is exactly the pattern Nacha’s enforcement team watches for.
RCK entries, which represent bounced paper checks electronically through the ACH network, follow a different framework than standard reinitiation. Nacha also excludes RCK entries from its return rate calculations because establishing a valid baseline for check representments is impractical.1Nacha. ACH Network Risk and Enforcement Topics The “RETRY PYMT” description applies to reinitiated ACH debits, not to RCK check conversions, and mixing the two up can lead to mislabeled entries and compliance problems.
Return Rate Thresholds Tied to Bad Retries
Nacha monitors return rates at the originator level, and exceeding certain thresholds triggers a review of your ACH activity. Three benchmarks apply:
- Overall return rate: 15% of all debit entries (excluding RCK) returned for any reason.1Nacha. ACH Network Risk and Enforcement Topics
- Unauthorized return rate: 0.5% of debit entries returned under codes R05, R07, R10, R29, or R51.3Nacha. How to Calculate Unauthorized Return Rate
- Administrative return rate: 3% of debit entries returned for administrative reasons like invalid account numbers.
Exceeding a threshold does not automatically mean you have violated the rules or that a fine is coming. A rate above the level is a starting point for review to determine whether a reduction is warranted.1Nacha. ACH Network Risk and Enforcement Topics Improper reinitiation habits inflate return rates quickly, because each failed retry generates another return. An originator that habitually reinitiates entries under ineligible return codes can blow past the 15% overall threshold in a single billing cycle.
Penalties for Getting It Wrong
Enforcement typically starts with a complaint from one financial institution about another. When a receiving bank notices repeated debits hitting a closed account or unauthorized reinitiations flowing through, it contacts Nacha’s Rules Enforcement Department. Nacha encourages the institutions to resolve the issue between themselves first. If that fails, the department steps in.4Nacha. How Nacha Enforces Its Rules
A first-time violation usually draws a warning letter to the originating institution. Recurring violations are escalated to the ACH Rules Enforcement Panel, which can impose fines and operational restrictions. Particularly egregious violations can be classified as Class 2 or Class 3, with Class 3 violations carrying sanctions up to $500,000 per occurrence and a directive to the originating bank to suspend the offending company from ACH origination.5Nacha. ACH Network Rules – Reversals and Enforcement
Fines are not the only risk. Your originating bank has its own exposure when you violate the rules, because it carries warranties on every entry you submit. Banks that see rising return rates or enforcement complaints from a customer often terminate the relationship on their own, well before Nacha formally acts. Losing an ACH origination relationship can freeze an entire receivables operation while you find a new banking partner willing to onboard you.