7.1 Return Processing Overview: Two-Banking-Day Rule vs. Extended Return Rule
Key Takeaways
- Standard ACH returns must be transmitted by the RDFI so they are available to the ODFI no later than opening of business on the second banking day following the settlement date of the original entry.
- Unauthorized consumer debits qualify for an extended return window: the RDFI must make the return available to the ODFI no later than opening of business on the banking day following the 60th calendar day after the settlement date.
- An ACH Return is constructed using an Entry Detail Record (Record Type 6) paired with a mandatory Return Addenda Record (Record Type 7, Addenda Type Code 99).
- Re-initiation of returned entries is capped at a maximum of two (2) re-initiations (three total attempts) within 180 calendar days of original settlement, requiring identical Company ID, Company Name, Amount, and the 'RETRY PYMT' description.
- Re-initiation is prohibited for entries returned for unauthorized reasons (R05, R07, R10, R11, R29, R51), frozen/OFAC-related accounts (R16), or closed accounts (R02), unless the Rules permit a new Entry supported by a new authorization or corrected circumstances.
7.1 Return Processing Overview: Two-Banking-Day Rule vs. Extended Return Rule
Core Principle: An ACH Return is an electronic exception item originated by a Receiving Depository Financial Institution (RDFI) or an ACH Operator that reverses the monetary exchange and accounting effect of a previously settled original ACH entry. Under the Nacha Operating Rules, exception processing is governed by strict, non-negotiable operational deadlines: the standard Two-Banking-Day Rule for operational, administrative, and corporate exceptions, and the Extended 60-Calendar-Day Return Rule for unauthorized consumer debit entries.
1. Architectural Overview of the ACH Return Mechanism
When an Originator initiates an ACH transaction through its Originating Depository Financial Institution (ODFI), the entry is processed by an ACH Operator (The Federal Reserve Bank's FedACH or The Clearing House's EPN) and delivered to the RDFI for posting to the Receiver's account. If the entry cannot be posted or is disputed by the Receiver, the RDFI creates an ACH Return Entry.
+---------------------------------------------------------------------------------------------------------+
| ORIGINAL ENTRY VS. RETURN ENTRY CASH FLOW |
+---------------------------------------------------------------------------------------------------------+
| Original Transaction: ACH Debit (Pull Payment) |
| [ Originator / ODFI ] <================ (Funds Flow: $ Credited to ODFI) =============== [ RDFI ] |
| |
| Return Exception: ACH Return of Debit |
| [ Originator / ODFI ] ================= (Funds Flow: $ Debited from ODFI) ==============> [ RDFI ] |
| * The RDFI debits the ODFI's settlement account to reclaim the unpostable/disputed funds. |
+---------------------------------------------------------------------------------------------------------+
| Original Transaction: ACH Credit (Push Payment) |
| [ Originator / ODFI ] ================= (Funds Flow: $ Debited from ODFI) =============> [ RDFI ] |
| |
| Return Exception: ACH Return of Credit |
| [ Originator / ODFI ] <================ (Funds Flow: $ Credited to ODFI) ============== [ RDFI ] |
| * The RDFI credits the ODFI's settlement account to return the unpostable credit funds. |
+---------------------------------------------------------------------------------------------------------+
Primary Reasons for ACH Returns
- Account Condition: Insufficient funds (R01), account closed (R02), invalid account number structure (R04), uncollected funds (R09), non-transaction account (R20).
- Receiver Direct Action: Stop payment order placed (R08), authorization revoked directly with Originator (R07), dispute of unauthorized transaction (R10/R11/R29).
- Administrative / Operational Inability: Unable to locate account (R03), account frozen or legal levy/OFAC block (R16), representative payee deceased (R14), beneficiary deceased (R15).
- ODFI / Originator Erroneous Request: Returned per ODFI request (R06).
2. Standard Return Window: The Two-Banking-Day Rule
Under Nacha Operating Rules Subsection 3.8.1 (General Rule for Returns), for all return reasons other than unauthorized consumer debits, the RDFI must transmit the return entry to its ACH Operator within a strictly enforced two-banking-day timeframe.
+---------------------------------------------------------------------------------------------------------+
| THE TWO-BANKING-DAY RULE (FORMAL DEFINITION) |
+---------------------------------------------------------------------------------------------------------+
| The RDFI must transmit the Return Entry to its ACH Operator such that the Return Entry is made |
| AVAILABLE TO THE ODFI by the ACH Operator NO LATER THAN THE OPENING OF BUSINESS ON THE SECOND BANKING |
| DAY FOLLOWING THE SETTLEMENT DATE of the original entry. |
+---------------------------------------------------------------------------------------------------------+
Operational Timeline Breakdown
To satisfy this mandate, the RDFI must factor in the processing schedules and deposit deadlines of its ACH Operator:
- Banking Day Definition: Any day on which a Participating DFI is open to the public for carrying on substantially all of its banking functions (excludes Saturdays, Sundays, and Federal Reserve legal holidays).
- Settlement Date (Day 0): The business day on which the original entry settled and funds were exchanged.
- First Banking Day (Day 1): The business day immediately following the settlement date. The RDFI identifies the exception (e.g., NSF, account closed) during posting and nightly processing.
- Second Banking Day (Day 2 - Opening of Business Cutoff): The return must be in the hands of the ODFI at opening of business. Consequently, the RDFI must transmit the return batch to the ACH Operator on Day 1 or during the early morning processing cycle of Day 2 before the Operator's distribution deadline.
| Day in Cycle | Banking Calendar Status | Operational Event / Requirement |
|---|---|---|
| Monday (Day 0) | Banking Day | Settlement Date of original ACH debit entry. |
| Tuesday (Day 1) | Banking Day | RDFI processing reveals NSF condition. RDFI creates Return Entry (R01). Transmits to ACH Operator by evening cutoff. |
| Wednesday (Day 2) | Banking Day | Opening of Business: ACH Operator makes Return Entry available to ODFI. Return is timely. |
Exam Trap: The rule is NOT simply "the RDFI has two days to decide." The legal standard requires that the return be available to the ODFI by opening of business on the second banking day following settlement. An RDFI that deposits a return with the ACH Operator on the afternoon of Day 2 has missed the deadline, rendering the return untimely and subject to dishonor (R68).
3. Extended Return Window: The 60-Calendar-Day Rule
To comply with the Electronic Fund Transfer Act (EFTA) and Regulation E (12 CFR Part 1005), the Nacha Operating Rules establish an extended return window for consumer receivers who dispute debit entries as unauthorized, improper, or revoked.
+---------------------------------------------------------------------------------------------------------+
| THE EXTENDED 60-CALENDAR-DAY RETURN RULE (SUMMARY) |
+---------------------------------------------------------------------------------------------------------+
| For consumer unauthorized debit returns (R05, R07, R10, R11), the RDFI must transmit the Return Entry |
| to its ACH Operator such that the return is made AVAILABLE TO THE ODFI NO LATER THAN OPENING OF |
| BUSINESS ON THE BANKING DAY FOLLOWING THE SIXTIETH (60TH) CALENDAR DAY after the original settlement date!|
+---------------------------------------------------------------------------------------------------------+
Key Parameters of the Extended Return Rule
- Qualifying Return Codes: R05 (Corporate SEC code to Consumer Account), R07 (Authorization Revoked), R10 (Customer Advises Unauthorized/Improper), R11 (Entry Not in Accordance with Terms).
- Consumer Account Prerequisite: Applies exclusively to consumer asset accounts (and consumer debits erroneously formatted under corporate SEC codes). It never applies to commercial accounts (CCD/CTX corporate debits disputed under R29 must meet the standard 2-banking-day rule).
- Condition Precedent: The RDFI must obtain a signed or similarly authenticated Written Statement of Unauthorized Debit (WSUD) from the consumer prior to transmitting an extended return.
| Feature | Standard Two-Banking-Day Rule | Extended 60-Calendar-Day Rule |
|---|---|---|
| Eligible Entry Types | All ACH credits; all commercial debits; non-fraud consumer debits | Consumer debits disputed as unauthorized / improper |
| Applicable R-Codes | R01, R02, R03, R04, R06, R08, R09, R14, R15, R16, R20, R29 | R05, R07, R10, R11 |
| Dispute Documentation | No formal sworn statement required (internal bank records) | Mandatory Written Statement of Unauthorized Debit (WSUD) |
| Timeframe Standard | Opening of business on 2nd banking day after settlement | Opening of business on banking day following 60th calendar day |
4. NACHA File Record Structure for Returns
An ACH Return file is constructed by the RDFI using standard NACHA fixed-width 94-character records. A return entry consists of a Return Entry Detail Record (Record Type 6) followed immediately by a Return Addenda Record (Record Type 7, Addenda Type Code 99).
+---------------------------------------------------------------------------------------------------------+
| NACHA RETURN RECORD SEQUENCE (94 BYTES) |
+---------------------------------------------------------------------------------------------------------+
| [ File Header Record (1) ] |
| [ Company / Batch Header Record (5) ] |
| [ Entry Detail Record (6) ] <-- Contains Original Amount, Account #, and RDFI Trace # |
| [ Return Addenda Record (7 / 99) ] <-- Contains Return Reason Code (Rxx) & Original Trace # |
| [ Company / Batch Control Record (8) ] |
| [ File Control Record (9) ] |
+---------------------------------------------------------------------------------------------------------+
Detailed Layout: Return Addenda Record (Type 7, Addenda Code 99)
Under Nacha Rules, the Return Addenda Record contains precise fields identifying why the entry is being returned and cross-referencing the original item:
| Position | Field Name | Length | Description / Purpose |
|---|---|---|---|
| 01–01 | Record Type Code | 1 | Always 7 (Addenda Record). |
| 02–03 | Addenda Type Code | 2 | Always 99 (Designates an ACH Return Addenda Record). |
| 04–06 | Return Reason Code | 3 | Standard Nacha 3-character code (e.g., R01, R10, R29). |
| 07–21 | Original Entry Trace Number | 15 | The exact 15-digit Trace Number from the original Entry Detail Record. |
| 22–27 | Date of Death / Reserved | 6 | Date of death (YYMMDD) for R14/R15; otherwise left blank (spaces). |
| 28–35 | Original Receiving DFI ID | 8 | Routing transit number of the original RDFI (first 8 digits). |
| 36–79 | Addenda Information | 44 | Optional explanatory text, or mandatory corrective data for dishonors. |
| 80–87 | Trace Number | 8 | First 8 digits of returning DFI routing number. |
| 88–94 | Sequence Number | 7 | Addenda record sequence counter within the batch. |
5. Re-initiation Rules & Strict Limitations
To protect consumers from relentless, abusive resubmissions of returned debits that trigger cascading overdraft/NSF fees, Nacha Operating Rules Section 2.12 (Re-initiation of Returned Entries) imposes strict statutory and network boundaries on re-submitting returned transactions.
+---------------------------------------------------------------------------------------------------------+
| NACHA RE-INITIATION RULES SUMMARY |
+---------------------------------------------------------------------------------------------------------+
| Maximum Re-initiations: | Maximum of TWO (2) re-initiations (THREE (3) total attempts including original).|
| Time Horizon: | All re-initiations must occur within 180 CALENDAR DAYS of original settlement.|
| Exact Match Required: | Must contain IDENTICAL Company ID, Company Name, and Dollar Amount. |
| Mandatory Indicator: | Company Entry Description MUST contain "RETRY PYMT" in positions 54-63. |
| Permissible Return Codes| ONLY R01 (Insufficient Funds) and R09 (Uncollected Funds), OR corrected R03/R04.|
| STRICTLY PROHIBITED: | R05, R07, R10, R11, R29 (Unauthorized), R16 (Frozen/OFAC), R02 (Closed). |
+---------------------------------------------------------------------------------------------------------+
The "RETRY PYMT" Formatting Standard
When an Originator re-initiates an entry returned for R01 or R09:
- The Company Entry Description field (positions 54–63 of the Company/Batch Header Record, Record Type 5) must contain the exact literal string
RETRY PYMT. - This explicit description notifies the RDFI and the consumer that the entry is a re-submission of a previously returned debit rather than a brand-new recurring billing cycle.
- Amount Integrity: The dollar amount of the re-initiated entry must be identical to the original entry (unless the consumer made a partial payment by other means, reducing the balance). An Originator CANNOT add a return fee or late fee into the re-initiated debit amount. Any return fee must be originated as a separate, distinct transaction under specific return fee rules.
Under the standard Two-Banking-Day Return Rule defined in Nacha Operating Rules Subsection 3.8.1, what is the exact deadline by which an RDFI must make a standard return entry available to the ODFI?
An Originator originates a consumer preauthorized debit that is returned by the RDFI with return code R01 (Insufficient Funds). What is the maximum number of re-initiations permitted under Nacha Rules, and what description must appear in the Batch Header?
Which of the following Return Reason Codes is strictly PROHIBITED from being re-initiated by an Originator under Nacha Operating Rules?
What is the Record Type Code and Addenda Type Code combination used in NACHA file formatting to construct an ACH Return Addenda Record?