Required receiver data
Map receiver name, routing number, account number, amount, account type, and credit or debit direction.
Convert structured CSV payment rows into a bank-ready NACHA-formatted ACH file.
Continue with a tool that fits the next step in this workflow.
Use one header row and one payment per row. Keep routing numbers and account numbers as text so spreadsheet software does not remove leading zeros, and keep amounts in a consistent decimal format.
Map receiver name, routing number, account number, amount, account type, and credit or debit direction.
Confirm company ID, SEC code, entry description, effective date, service class, and ODFI identification separately from row data.
Map receiver IDs and payment-related information only when the source and selected SEC code support them.
The export creates file and batch headers, entry records, eligible addenda, batch and file controls, and type 9 padding. Counts, hashes, totals, trace sequences, and block count are calculated from the mapped rows.
Each payment needs a receiver name, routing number, account number, amount, account type, and credit or debit direction; the batch also needs approved originator settings.
The rows can be imported, but PPD and CCD belong in separate batches. Split or group them before creating the final file.
Spreadsheet software may coerce identifiers into numbers. Format those source columns as text and export the CSV again.
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.