ACH/NACHA File Validator + Return Code Decoder

ACH/NACHA File Validator parses NACHA-formatted flat files according to the official 94-character fixed-width record specification.

The validator checks: record type identifiers (1, 5, 6, 7, 8, 9), batch control hash totals, entry/addenda counts, file control debit/credit balance, mandatory field presence, and sequential batch numbering.

• Record Type 1 — File Header: identifies originating/receiving DFIs, file creation date/time.
• Record Type 5 — Batch Header: company name, SEC code, effective entry date.
• Record Type 6 — Entry Detail: routing number, account, amount, name, trace number.
• Record Type 7 — Addenda: additional payment information (IAT, POP, etc.).
• Record Type 8 — Batch Control: entry/addenda count, hash, debit/credit totals.
• Record Type 9 — File Control: batch count, block count, entry count, hash, totals.

This tool does not validate routing numbers against the Federal Reserve database, nor does it parse all SEC code-specific addenda rules. It is intended for structural pre-flight checks prior to submission.

Return Code Decoder covers all 85 NACHA standard return reason codes (R01 through R85), including timeframes, initiating parties, and recommended corrective actions.

• Retry — The originator may resubmit after correcting the identified issue (e.g., R10 – Customer Advises Not Authorized, after obtaining new authorization).
• Contact — Reach out to your customer or RDFI to resolve before retrying (e.g., R02 – Account Closed).
• Stop — Do not retry; the entry is definitively invalid (e.g., R14 – Representative Payee Deceased).
• Review — Internal review required before further action (e.g., R62 – Return of Erroneous or Reversing Debit).

Timeframes shown are standard NACHA Operating Rules return windows. Your ODFI may have additional requirements. Always consult your ACH agreement and the current NACHA Operating Rules for authoritative guidance.