How does a 94-byte NACHA ACH file validate before bank upload?
Every uploaded .ach, .nacha, or .txt transmission up to 25 MB is sliced into fixed 94-character ASCII records inside a browser Web Worker, accepting both newline-delimited files and continuous un-newlined mainframe streams divisible by 94 bytes. The validator checks Type 1 through Type 9 structural order, blocking rules, Mod-10 routing numbers, and batch control totals offline.
Parsing separates file headers, batch envelopes, individual debits and credits, and optional addenda strings while verifying exact character positions specified under NACHA fixed-width formatting. Catching short lines, out-of-sequence records, or unbalanced totals locally helps treasury teams clean batches prior to secure bank portal transmission.
Checking RDFI routing numbers against valid Federal Reserve prefixes (01-12, 21-32, 61-72, 80) catches transposed bank digits before treasury submission. Those prefixes align with regional US Reserve Bank territories mapped in the Federal Reserve System Structure overview, covering District 01 Boston through District 12 San Francisco.
If you need to audit standalone vendor bank identifiers before generating a batch in your ERP or payroll software, test individual routing numbers or lists up to 5,000 entries inside our Routing number checker. Pre-screening routing digits saves multi-day ACH return fees after batch cutoff windows.
ACH record types, entry hashes, and return code decoding
NACHA files follow a strict nested envelope where file headers wrap company batches, detail entries, optional addenda, batch trailers, and a final file control summary. One misplaced column offset or miscalculated control total causes bank gateways to reject the entire transmission.
| Record Name | Record Code | Line Width | Primary Structure & Validation Checks |
|---|---|---|---|
| File Header | 1 | 94 bytes | Checks Priority Code 01, Immediate Destination ABA, 094 size, and 10 blocking |
| Company / Batch Header | 5 | 94 bytes | Validates Service Class (200, 220, 225, 280), 15 SEC codes, and YYMMDD dates |
| Entry Detail | 6 | 94 bytes | Checks 24 Transaction Codes, 9-digit RDFI Mod-10 checksum, and prenote amounts |
| Addenda | 7 | 94 bytes | Verifies parent Type 6 addenda indicator 1 and decodes Type 98 NOC / Type 99 Returns |
| Company / Batch Control | 8 | 94 bytes | Reconciles entry+addenda counts, batch Entry Hash, and total debit/credit cents |
| File Control | 9 | 94 bytes | Checks batch count, 10-record block count, file Entry Hash, and grand cent totals |
File header, batch header, and 10-record blocking rules
Type 1 File Headers must declare Priority Code 01, a valid 9-digit Immediate Destination routing identifier, record size 094, and blocking factor 10. At file completion, total lines must form an exact multiple of 10 records, using trailing 94-character 9999... blocking padding after Type 9 without placing padding lines early.
Batch headers (Type 5) enforce standard Service Class Codes (200 Mixed, 220 Credits Only, 225 Debits Only, 280 Automated Accounting) alongside 15 recognized SEC codes including PPD, CCD, CTX, WEB, TEL, and IAT. Corporate cash teams reconciling cleared payments alongside daily account reports can also extract corporate BAI2 treasury reports to Excel.
Entry Detail Mod-10 routing and 10-digit Entry Hash checks
Each Type 6 Entry Detail record must pair a valid 24-code Transaction Code (21-24, 26-29, 31-34, 36-39, 41-42, 47, 51-52, 55-56) with a 9-digit RDFI routing number passing weighted Mod-10 arithmetic (3*(d0+d3+d6) + 7*(d1+d4+d7) + (d2+d5+d8) mod 10 === 0). Zero-dollar and prenote codes (23, 24, 28, 29, 33, 34, 38, 39) trigger errors if given non-zero cent amounts.
At batch and file trailers, the validator sums all 8-digit RDFI routing prefixes and compares the lowest 10 digits modulo 10,000,000,000 against the declared Entry Hash, matching clearing controls described in the Federal Reserve FedACH Services overview. It also flags debit entries inside 220 batches or credit entries inside 225 batches.
Decoding Type 98 NOC and Type 99 ACH return addenda
When an Entry Detail record flags an attached Type 7 addenda (addendaIndicator === '1'), the parser inspects addenda type 99 for Return entries and 98 for Notifications of Change. Standard return reasons (R01-R17, R20-R24, R29, R31, R33) and change codes (C01-C07, C09) decode automatically into readable labels, while unfamiliar bank codes fall back cleanly to generic Return or NOC labels.
Inspecting Entries, Batches, and Validation tabs in the UI
Raw fixed-width text files pack company IDs, trace numbers, discretionary fields, and cents without delimiters into continuous 94-character lines. The browser viewer separates those fields into three synchronized tabs alongside live sidebar totals for Total Credits, Total Debits, Entries + Addenda, and Errors / Warnings.
Filtering entries and testing with Load sample ACH batch
Click Load sample ACH batch (harbor-payroll-sample.ach) to inspect a multi-entry payroll batch before opening live treasury transmissions via Choose another file. Inside Entries (N), type any payee name, RDFI routing number, or 15-digit trace number into the "Filter receiver, routing, trace..." box to isolate disputed transactions immediately.
Tip: Keep Mask DFI account numbers (
****1234) enabled whenever exporting spreadsheets for managers or external bookkeepers so full employee and vendor bank account numbers remain hidden inside shared reports.
The Batches & Hashes (N) tab summarizes each Type 5/8 pair with declared versus computed Entry Hashes, debit totals, credit totals, and effective dates (YYMMDD). Meanwhile, Validation (N) groups every structural error and warning with line numbers (UNPADDED_BLOCK, BLOCK_COUNT, hash mismatches, or prenote errors) aligned with Nacha Operating Rules updates.
Exporting three-sheet Excel workbooks and masked CSVs
Under Export format, Excel workbook (.xlsx) is selected by default and writes three structured worksheets inside one file: Entries, Batches, and Validation Issues. Selecting Entries CSV (.csv) outputs a UTF-8 BOM comma-delimited report spanning 14 columns ready for external ledger matching.
Accounting teams reconciling outgoing ACH payroll or vendor batches against incoming retail bank statements can inspect statement downloads through our bank statement OFX and QFX spreadsheet converter in the next close step. Clicking Export ACH report writes 100% of parsed entries cleanly to disk.
Security masking, offline audit scope, and ACH file privacy
NACHA transmissions concentrate employee direct-deposit numbers, vendor bank accounts, company EIN prefixes, and payroll totals inside one plain-text file. Processing inside a local Web Worker ensures zero bytes cross the network, while Mask DFI account numbers (****1234) defaults to checked so exported spreadsheets redact leading account digits automatically.
Entries CSV exports also pass every receiver name, company name, and addenda note through CWE-1236 formula sanitization before saving, neutralizing leading =, +, -, or @ characters. Interactive previews intentionally render up to 300 entries in the Entries (N) table so large files stay responsive while downloads export every entry.
Offline validation verifies syntax, Service Class constraints, ABA Mod-10 checksums, Entry Hashes, and block counts, matching federal technical formatting standards referenced in the U.S. Treasury Fiscal Service ACH program overview. However, offline checks cannot query live bank directories, confirm bank names, or verify account funding status.
Multinational treasury desks managing European wire batches alongside US FedACH files can also inspect ISO 20022 CAMT.053 statements ready for SEPA reconciliation. All checks here support technical pre-flight review for informational purposes only and do not constitute financial, legal, or compliance advice; confirm production files with your originating bank and a qualified accountant.