ACH Is Not a Card Dispute
Most dispute teams are built around card disputes — Reg E timelines, chargeback networks, provisional credit windows. ACH disputes sit in the same queue, processed by the same staff, but governed by a completely different framework: NACHA Operating Rules.
The misclassification risk is real. An ACH dispute handled with card-dispute logic may meet internal SLAs while missing the actual NACHA return deadline. The case closes cleanly. The violation doesn’t surface until an audit or an examiner looks at the return submission timestamps.
NACHA Return Timeline Basics
NACHA return timeframes are measured from the settlement date, not the cardholder notification date. Unauthorized debit returns must be submitted within 60 calendar days of the statement date. Extended return timeframes apply to specific entry classes. The consumer claim process for certain transaction types has its own window, separate from the institution’s return right.
These deadlines don’t flex. A return submitted one day late is no return at all — the RDFI loses its right to return, and the consumer’s ability to recover the funds depends entirely on voluntary cooperation from the ODFI.
Entry Class Codes Matter
ACH entry class codes determine which return codes apply, which timeline governs, and how the dispute should be categorized and investigated. PPD, CCD, WEB, TEL, and POP each carry different authorization implications. A team that doesn’t classify by entry class is applying the wrong rule to a meaningful percentage of its ACH dispute volume.
The Workflow Problem
The underlying issue is workflow design. Most dispute management systems weren’t built to branch ACH cases into a separate timeline and procedural track. The ACH dispute enters the queue, gets a case number, and follows whatever standard workflow the institution built for card disputes. If nobody built an ACH-specific branch, the case gets card-dispute treatment — which means card-dispute deadlines and card-dispute documentation.
What a Correct ACH Workflow Requires
Proper ACH dispute handling requires intake that captures and validates the ACH entry class, routing logic that branches the case into an ACH-specific workflow, deadline enforcement based on NACHA return windows rather than Reg E investigation periods, return code selection logic, and documentation that captures the consumer authorization claim in the format NACHA requires for R10 and R11 returns.
None of this is optional. And none of it happens automatically when an ACH dispute enters a card-dispute queue.
