Receiver and payment values
Review receiver name, routing data, account value, amount, transaction code, identification, trace number, and addenda.
Open an ACH file and export its entries to CSV.
Continue with a tool that fits the next step in this workflow.
Each Entry Detail Record becomes a row with its related batch values. Addenda information is attached where the flat export supports it rather than being mistaken for a separate payment.
Review receiver name, routing data, account value, amount, transaction code, identification, trace number, and addenda.
Company name and ID, SEC code, effective date, entry description, service class, and batch number explain how each row was originated.
CSV does not preserve the original fixed-width record layout or every hierarchy rule. Keep the source file when raw records, controls, signatures, or exact byte-for-byte evidence matter.
Yes. Relevant batch values are repeated with each entry so the flat rows retain useful originator and classification context.
Not necessarily. A flat export may omit raw formatting and file-level metadata, so it is not a byte-for-byte round trip.
No. Supported addenda are associated with their parent entry in the export.
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.