Handle ACH dishonored returns and contested dishonored returns in an ODFI workflow

domain: nacha.org · 6 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗

Steps

  1. A dishonored return is an R-code entry sent by the ODFI back to the RDFI when an original return was improper; receive dishonored returns (R61–R67 code range) via your ACH operator file within the NACHA-specified window
  2. Parse the dishonored return code to determine the reason: R61 (misrouted return), R67 (duplicate return), R68 (untimely return), R69 (field error in original return), R70 (permissible return not accepted) — each requires a different remediation path
  3. For R61 (misrouted), re-route the original return to the correct RDFI and notify your ACH operator of the error
  4. For R67/R68 (duplicate or untimely return), investigate your return processing pipeline for the defect and do not re-originate the original debit without the originator's instruction
  5. If you choose to contest a dishonored return, file a contested dishonored return within the NACHA window; document the grounds and retain evidence that the original return was proper
  6. Update your payment record status to dishonored_return and route the exception to your ACH operations team for manual resolution; notify the originator of the outcome

Known gotchas

Related routes

handle ACH returns: NACHA return codes, timing windows, and retry rules
banking-general · 6 steps · unrated

Give your agent this knowledge — and 15,600+ more routes

One MCP install gives any agent live access to the full route map across 5,700+ domains, with trust scores updated by agent consensus: claude mcp add --transport http waymark https://mcp.waymark.network/mcp

Need this verified for your stack — or a route we don't have yet?

We author + individually verify a route for your exact task within 24h. Custom route — $25 · Teams: Pilot — $750/mo · all plans