Headers and controls
Type 1 and 5 records open the file and batches; type 8 and 9 records close them and store counts, hashes, and monetary totals.
Read an ACH file and inspect every batch, entry, addenda and raw NACHA record.
Continue with a tool that fits the next step in this workflow.
The summary shows batch and entry counts, debit and credit totals, SEC codes, service classes, and parser findings. Batch views expose company identifiers, descriptions, effective dates, ODFI data, and their related entries.
Entry rows make receiver names, routing data, account values, amounts, transaction codes, trace numbers, and addenda easier to review than the original 94-character text.
Type 1 and 5 records open the file and batches; type 8 and 9 records close them and store counts, hashes, and monetary totals.
Type 6 records carry payment instructions. Eligible type 7 records follow their entry and carry payment-related, Return, or Notification of Change information.
Use the validator when the goal is to determine whether controls and structure reconcile. Use the editor only when a supported field requires an authorized change. Viewing alone does not certify the file or modify its records.
Yes. The viewer parses a text-based NACHA file locally and presents fixed-width fields in readable summaries and tables.
The supported browser workflow processes the selected file on the device. Continue to handle screenshots and exported information as sensitive data.
No. CSV and Excel are tabular source formats, not fixed-width ACH files. Use the corresponding converter when those formats contain payment rows.
No. Parsing means records could be interpreted. Validation separately checks lengths, relationships, routing checksums, controls, totals, traces, and padding.
Technical explanations are checked against these primary sources. Bank-specific requirements can be narrower than general format guidance.
Sources reviewed August 20, 2026. Nacha owns and maintains the linked materials.