Skip to content

Free NACHA file viewer & ACH validator

Read any NACHA file, field by field.

Drop in an ACH file to see every record decoded, color-coded and checked against the NACHA format — then build a reversal in a few clicks. Parsing happens entirely in your browser.

  • Field-level decoding
  • Control totals & check digits
  • Reversal files

Drop a NACHA file here

Accepts .ach and .txt — any file of 94-character records

Read locally by your browser — never uploaded

100% in-browser.

Your ACH file never leaves this device.

Parsed on your device

JavaScript on this page reads the file. Nothing is uploaded, stored or transmitted.

No account, no cost

Viewing, validating and building reversals are free. No sign-up, ever.

Open about usage

Our public analytics show exactly what we count — never what your files contain.

0 bytes of your file are uploaded; the only requests are anonymous counters (a page view, a file opened). See for yourself in your browser’s developer tools (Network tab).

Anatomy of a record

Ninety-four characters, fully accounted for.

Every line of a NACHA file is a fixed-width record. Navigator names each field, colors it by what it holds and measures exactly where it sits — so you can see at a glance where the routing number ends and the amount begins.

Line 03Entry detail · PPD checking credit, from the sample file94 characters · 11 fields
03Entry detail
6220655033481111111 0000000010000001309 JOHN M SMITH 0065503680000001

What each field holds

1Record Type Code
Identifies the type of record in the file.
2–3Transaction Code
Identifies the type of account and whether the entry is a credit, a debit, a prenote, a zero-dollar entry or a return/NOC.
4–11Receiving DFI Identification
First 8 digits of the routing number of the Receiver's financial institution (the RDFI).
12Check Digit
The ninth digit of the RDFI routing number, computed from the first eight.
13–29DFI Account Number
The Receiver's account number at the RDFI.
30–39Amount
The amount of the entry, in cents.
40–54Individual Identification Number
Number the Originator uses to identify the Receiver, such as an employee ID, customer or loan number.
55–76Individual Name
Name of the Receiver.
77–78Discretionary Data
For the ODFI or Originator to use as they agree; it has no meaning to the ACH Network.
79Addenda Record Indicator
Shows whether one or more Addenda Records follow this entry.
80–94Trace Number
Uniquely identifies the entry within the file and lets it be traced through the ACH Network.

Routing & IDs

Routing and account numbers, company, trace and batch IDs

Amounts & totals

Amounts in cents, counts and entry hashes

Dates

Creation, effective and settlement dates and times

Names & text

Company, receiver and description fields

Codes

Record, transaction, service-class and SEC codes

Reserved

Blank by specification; dots mark padding

Every record type, field by field: the NACHA file format reference

What it does

Catch it here, before your bank does.

The same checks your bank runs before it accepts a file — record lengths, control totals, hashes and check digits — explained in plain language, line by line.

No. 01

Decode

Every record type — File Header (1), Batch Header (5), Entry Detail (6), Addenda (7), Batch Control (8) and File Control (9) — split into named, color-coded fields, with the right layout for PPD, CCD, CTX, WEB, TEL, IAT, returns and NOCs.

No. 02

Validate

Record length, control totals, entry hash, routing check digits, effective dates, SEC and transaction codes, and blocking-factor padding. Each problem is pinned to its line and column, with the expected value when there is a single right one.

No. 03

Reverse

Pick the entries to undo — one, a whole batch or the entire file — and download a reversal file: transaction codes flipped, control totals recalculated and the REVERSAL company entry description set.

No. 04

Audit

Reconcile debit and credit totals, entry and addenda counts and entry hashes against your payment register before you send, then export the entries to CSV or JSON.

More samples

No file handy? Open one of ours.

Each sample shows a different corner of the format. All names, account numbers and amounts are made up; nothing is uploaded either way.

  • CCD · Remittance addenda

    Vendor payments with addenda

    A credits-only CCD batch paying vendors with one type 05 addenda each, and a debits-only CCD batch collecting invoices.

    • Service Class Codes 220 and 225
    • Type 05 addenda with X12 RMR segments and plain text
    • A zero-dollar remittance entry (Transaction Code 24)
    sample-ccd-addenda.ach
  • CTX · EDI 820

    Corporate trade exchange

    Two CTX payments whose ANSI X12 820 remittance advice spans several type 05 addenda records.

    • Number of Addenda Records (positions 55–58)
    • Addenda sequence numbers 0001–0004
    • Receiving Company Name/ID Number layout
    sample-ctx.ach
  • Returns · NOC

    Returns and notifications of change

    A file sent back by an RDFI: a PPD batch of returns (R01, R02, R03, R10, R15) and a COR batch of NOCs (C01, C02, C05).

    • Return Transaction Codes 21, 26 and 36 with type 99 addenda
    • Date of death on an R15 return
    • Type 98 addenda with corrected account, routing number and transaction code
    sample-returns-noc.ach
  • Validation demo

    A file with 12 deliberate problems

    A small payroll file damaged on purpose: totals that don’t add up, a bad check digit, an impossible date and more. Open it to see each problem pinned to its line and column, with the expected value when there is a single right one.

    • Control totals that do not add up
    • Routing, trace and addenda problems
    • A record with its trailing blanks stripped
    sample-with-errors.ach
  • Reversal demo

    Undo a payroll run

    Payroll credits, membership debits and a vendor payment, dated the previous banking day so the five-banking-day reversal window is open. Built in your browser for today’s date.

    • Credits and debits across three batches
    • A prenote that can’t be reversed
    • A CCD payment with a remittance addenda
    generated for today
  • Building a file from scratch?

    The NACHA Generator writes a valid file from a form or JSON — totals, entry hash and block fill included.

    Open the NACHA Generator

Related tools

More free tools for payment files.

The same private, in-browser approach for the other formats that land on an operations desk.

X9.37 · Image cash letterNew

X9 Viewer

Open X9.37 check image files in your browser. See every item’s front and back images, its MICR line and the record behind it — inspected the same field-by-field way, with bundle and cash letter totals checked.

Opens.x9.x937.iclfiles

BAI2 · Balance reporting

BAI2 Viewer

Turn BAI2 bank reports into readable account summaries and transaction detail, with every type code explained.

Build files · Builder and REST API

NACHA Generator

Build a valid NACHA file in the visual builder — or send JSON to the free REST API. Control totals, entry hash and block padding are done for you, and the result opens right here in the viewer.

Questions

Before you open a file.

Short answers to what people ask most. The full answers, with real-world use cases for payroll, banking, treasury and compliance teams, are on the use cases page.

Why was my NACHA file rejected by my bank?
Common rejection causes include incorrect record lengths (lines must be exactly 94 characters), unbalanced batch or file control totals, invalid routing number check digits, bad effective entry dates, missing blocking-factor padding (files must contain a multiple of 10 records), and malformed Standard Entry Class (SEC) codes.
How do ACH reversals work?
Under Nacha rules, an originator may reverse an erroneous entry (duplicate, wrong amount, wrong account, or wrong date) by submitting a reversing entry within five banking days of the settlement date of the original entry.
Is my ACH file data secure when I use NACHA Navigator?
Yes. NACHA Navigator parses your file entirely in your browser using client-side JavaScript.
What is a NACHA file?
A NACHA file is a fixed-width text file format defined by Nacha (the National Automated Clearing House Association) for submitting ACH payments in the United States.

Read every answer and the use cases

Need More Than File Analysis?

Looking for enterprise-grade NACHA file generation, batch processing, or automated ACH workflows? We’re developing advanced tools for financial institutions and treasury departments.