8.3 Reversing Entries & Reversal Files: 5-Day Deadline & Erroneous Reasons
Key Takeaways
- Under Nacha Operating Rules Sections 2.8 and 2.9, a Reversal is limited to an enumerated error: duplicate, wrong receiver, wrong amount, a debit dated earlier than intended, a credit dated later than intended, or the specific permitted PPD employment-termination/separation case.
- Reversing entries and reversal files must be transmitted to the ACH Operator within five (5) banking days following the Settlement Date of the original erroneous entry.
- Reversal batches require the exact word 'REVERSAL' in the Company Entry Description field (positions 54–63 of Record Type 5 Batch Header).
- When reversing a credit via a reversing debit entry, the Originator must make a reasonable effort to notify the Receiver of the reversal and the reason on or before the Settlement Date.
- The ODFI provides statutory warranties and full indemnification to the RDFI and ACH Operator for reversals; however, the RDFI is under no obligation to create an overdraft to honor a reversing debit and may return it (e.g., R01).
8.3 Reversing Entries & Reversal Files: 5-Day Deadline & Erroneous Reasons
Core Principle: In the Automated Clearing House (ACH) Network, payments are designed to be final, reliable, and predictable. However, when an Originator or ODFI makes a bona fide operational error—such as transmitting a duplicate payroll file or mistyping a payment amount—Nacha Operating Rules Section 2.8 (Reversing Files) and Section 2.9 (Reversing Entries) provides a strict, standardized legal remedy. A Reversal allows the Originator to pull back or correct an Erroneous Entry. Because reversals alter settled funds flows, Nacha strictly confines their use to enumerated error conditions and enforces a rigid 5-banking-day transmittal deadline.
1. Permissible Reversal Reasons vs. Prohibited Commercial Justifications
Reversing an ACH entry is an extraordinary corrective measure, not a general cancellation right or dispute resolution mechanism. An Originator or ODFI may initiate a Reversing Entry or Reversal File ONLY if the original transaction satisfies the formal definition of an Erroneous Entry under Sections 2.8 and 2.9.
+---------------------------------------------------------------------------------------------------------+
| NACHA REVERSAL RULES (SECTIONS 2.8 / 2.9): PERMISSIBLE VS. PROHIBITED REVERSALS |
+---------------------------------------------------------------------------------------------------------+
| PERMISSIBLE REASONS (ENUMERATED BY THE RULES) |
+---+-----------------------------------+-----------------------------------------------------------------+
| 1 | Duplicate Entry / File | The Entry or File duplicates one previously initiated. |
| 2 | Incorrect Receiver | Payment was directed to a Receiver other than the one intended. |
| 3 | Incorrect Dollar Amount | The amount differs from the Originator's intended amount. |
| 4 | Debit Dated Too Early | A debit orders payment on a date earlier than intended. |
| 5 | Credit Dated Too Late | A credit orders payment on a date later than intended. |
| 6 | Certain PPD Employment Credits | The specific Rule conditions for termination/separation apply. |
+---+-----------------------------------+-----------------------------------------------------------------+
| PROHIBITED REASONS (STRICTLY ILLEGAL UNDER NACHA RULES) |
+---+-----------------------------------+-----------------------------------------------------------------+
| X | Customer Lack of Funds | Originator attempts to reverse an entry because Receiver's |
| | | account lacks funds for a subsequent transaction. |
| X | Commercial / Contract Disputes | Originator reverses payment due to disagreement over delivered |
| | | goods, services, quality, or contract milestones. |
| X | Buyer's Remorse / Payment Regret | Originator changes its mind after transmitting a valid entry. |
| X | Disguised Chargeback Remedy | Originator attempts to bypass customer authorization dispute or |
| | | stop payment procedures. |
| X | Failure to Obtain Authorization | An unauthorized debit cannot be 'reversed' by Originator; it |
| | | must be resolved via RDFI Written Statement of Unauthorized |
| | | Debit (WSUD) and Return code R10/R11! |
+---+-----------------------------------+-----------------------------------------------------------------+
2. The Strict 5-Banking-Day Transmittal Deadline
Timing is paramount in reversal processing. Under Nacha Operating Rules Sections 2.8 and 2.9, the ODFI must transmit the Reversing Entry or Reversal File to the ACH Operator within five (5) banking days after the Settlement Date of the original erroneous entry.
+---------------------------------------------------------------------------------------------------------+
| CALCULATING THE 5-BANKING-DAY REVERSAL DEADLINE |
+---------------------------------------------------------------------------------------------------------+
| Scenario: An erroneous payroll credit settles on Monday, October 5 (Banking Day 0). |
| |
| - Monday, Oct 5: Day 0 (Original Settlement Date) |
| - Tuesday, Oct 6: Banking Day 1 |
| - Wednesday, Oct 7: Banking Day 2 |
| - Thursday, Oct 8: Banking Day 3 |
| - Friday, Oct 9: Banking Day 4 |
| - Saturday / Sunday: Non-Banking Days (Do not count) |
| - Monday, Oct 12: Federal Holiday (Columbus Day / Indigenous Peoples' Day - Does not count) |
| - Tuesday, Oct 13: Banking Day 5 ===> FINAL DEADLINE FOR TRANSMISSION TO ACH OPERATOR! |
+---------------------------------------------------------------------------------------------------------+
Exam Trap: The 5-day deadline is measured in banking days, not calendar days, and runs from the Settlement Date of the original entry, NOT the origination date or batch creation date. If an Originator attempts to transmit a reversal on Banking Day 6, the reversal violates Nacha Rules and exposes the ODFI to return liability and warranty breach penalties.
3. Technical Formatting Requirements: The "REVERSAL" Header
To ensure all downstream participants and automated processing engines recognize the transaction as a corrective reversal, Nacha Rules mandate strict formatting in the Company/Batch Header Record (Record Type 5):
+---------------------------------------------------------------------------------------------------------+
| BATCH HEADER (TYPE 5) FORMATTING FOR REVERSING BATCHES / ENTRIES |
+--------+---------+-----------------------------------+--------------------------------------------------+
| Pos | Length | Field Name | Required Value for Reversal Batches |
+--------+---------+-----------------------------------+--------------------------------------------------+
| 01-01 | 1 | Record Type Code | '5' (Batch Header Record) |
| 02-04 | 3 | Service Class Code | '200' (Mixed), '220' (Credits Only), '225' (Deb) |
| 05-20 | 16 | Company Name | Originator's recognizable commercial name |
| 21-40 | 20 | Company Discretionary Data | Optional Originator internal tracking data |
| 41-50 | 10 | Company Identification | Originator's 10-digit identification number |
| 51-53 | 3 | Standard Entry Class Code | Same SEC Code as original erroneous entry |
| 54-63 | 10 | Company Entry Description | MUST BE EXACTLY: 'REVERSAL ' (Left-justified) |
| 64-69 | 6 | Company Descriptive Date | Optional batch origination date |
| 70-75 | 6 | Effective Entry Date | Target settlement date for the reversing entry |
| 76-78 | 3 | Settlement Date (Julian) | Inserted by ACH Operator |
| 79-79 | 1 | Originator Status Code | '1' |
| 80-87 | 8 | Originating DFI Identification | First 8 digits of ODFI routing number |
| 88-94 | 7 | Batch Number | Sequential batch number |
+--------+---------+-----------------------------------+--------------------------------------------------+
Formatting Rules for Reversal Entry Detail Records (Record Type 6):
- Opposite Transaction Code: The reversing entry must carry the opposite transaction code of the erroneous entry. For example:
- An erroneous checking credit (Tran Code
22) is reversed using a checking debit (Tran Code27). - An erroneous checking debit (Tran Code
27) is reversed using a checking credit (Tran Code22).
- An erroneous checking credit (Tran Code
- Exact Dollar Amount: The reversing entry must match the exact dollar amount of the erroneous entry (or the exact duplicate amount).
- Correcting Entry Pairing (Wrong Amount Scenario): When reversing an entry that had an incorrect dollar amount (e.g., intended $200, but sent $2,000):
- The Originator originates a Reversing Debit for $2,000.00 (with
REVERSALin the batch header); - Simultaneously or sequentially, the Originator originates a Correcting Live Credit for $200.00 (under standard batch description, e.g.,
PAYROLL).
- The Originator originates a Reversing Debit for $2,000.00 (with
4. Receiver Notification Obligation for Debit Reversals
When a reversal involves a debit to the Receiver's account (such as reversing an accidental overpayment or duplicate Direct Deposit credit), the sudden withdrawal of funds creates a severe risk of consumer overdrafts, uncollected funds fees, and bounced checks.
Mandatory Notice Standard:
Under the Reversing Entries rule, if an Originator transmits a reversing entry that debits a Receiver's account, the Originator MUST make a reasonable effort to notify the Receiver of the reversing entry and the reason for the reversal on or before the Settlement Date of the reversing entry.
- Acceptable Delivery Channels: Telephone call, direct SMS text alert, email notification, in-app mobile banking push message, or secure electronic communication.
- Content of Notice: The notification must clearly state the dollar amount being reversed, the date of the reversal settlement, and the specific erroneous reason that necessitated the reversing debit.
5. ODFI Warranties, Indemnity & RDFI Rights
Because reversals are initiated unilaterally by the ODFI/Originator, Nacha Rules allocate legal risk strictly to the originating party:
+---------------------------------------------------------------------------------------------------------+
| ODFI WARRANTIES & INDEMNIFICATION SUMMARY |
+---------------------------------------------------------------------------------------------------------+
| 1. Warranty of Erroneous Purpose | ODFI warrants the reversal was originated solely to correct an |
| | erroneous entry permitted under Sections 2.8/2.9. |
| 2. Warranty of Timeliness | ODFI warrants the reversal was transmitted within 5 banking days. |
| 3. Warranty of Receiver Notice | ODFI warrants reasonable effort was made to notify Receiver of deb. |
| 4. Full Indemnification | ODFI unconditionally indemnifies the RDFI, ACH Operator, and every |
| | Participating DFI against all claims, losses, liabilities, and legal|
| | fees arising from the reversal. |
+---------------------------------------------------------------------------------------------------------+
RDFI Rights and Return Options:
- No Obligation to Overdraw: The RDFI is under no legal obligation to create an overdraft or extend credit to accommodate a reversing debit entry if the customer's account has insufficient funds. If funds are unavailable, the RDFI returns the reversing debit using standard return codes:
R01(Insufficient Funds) — Customer already withdrew the funds;R08(Payment Stopped) — Customer placed a stop payment against the reversing debit;R02/R03— Account closed or unable to locate account.
- Unauthorized Reversals: If an Originator transmits a reversing debit without meeting the Section 2.8/2.9 criteria, the consumer can dispute the debit via a Written Statement of Unauthorized Debit (WSUD), and the RDFI may return it under
R10orR11within 60 calendar days.
Which of the following scenarios represents a PERMISSIBLE reason for an Originator to transmit a Reversing Entry under the Nacha reversal rules?
What is the maximum deadline permitted under Nacha Operating Rules for an ODFI to transmit a Reversing Entry or Reversal File to the ACH Operator?
What specific string MUST appear in the Company Entry Description field (positions 54–63) of the Company/Batch Header Record (Type 5) for an ACH reversal batch?
An employer mistakenly credits an employee's checking account with $5,000 instead of $500. The employer transmits a reversing debit for $5,000 within 5 banking days, but the employee has already withdrawn the entire balance, leaving the account with $10. What action should the RDFI take?