File and company settings
Enter the immediate destination and origin, company name and ID, ODFI identification, file creation values, and any bank-supplied reference code exactly as approved.
Use this NACHA file creator to build an ACH file for PPD or CCD payments.
Enter your ACH settings, or load fictitious sample data to explore the generator.
Your bank or ACH provider should give you these file-sender values. They are required even when the receiver is an individual. Enter them exactly as approved and do not guess.
| Row | Receiver | Routing | Account | Amount | Payment type | Trace | Addenda | Actions |
|---|---|---|---|---|---|---|---|---|
| 1✓ |
Complete the file details and entry fields, then select Generate ACH file to run validation.
Enter the name only. The .ach extension is added automatically.
Continue with a tool that fits the next step in this workflow.
Use the form when you have a small payment run or need to assemble a controlled PPD or CCD batch without mapping CSV or Excel columns. The page separates file settings, company and batch settings, and receiver entries so each layer can be reviewed before download.
For a recurring export with many rows, a CSV or Excel converter may be more efficient. The generator is intended for direct entry, not for removing report headings, subtotal rows, formulas, or worksheet formatting.
Enter the immediate destination and origin, company name and ID, ODFI identification, file creation values, and any bank-supplied reference code exactly as approved.
Choose the service class, PPD or CCD SEC code, Company Entry Description, effective entry date, and discretionary data for the purpose of this batch.
Add the receiver name, routing number, account number, amount, account type, credit or debit direction, identification value, and optional addenda supported by the selected entry.
The generated text includes a File Header, a Batch Header, one Entry Detail per receiver, eligible Addenda Records, a Batch Control, a File Control, and type 9 padding. Counts, entry hashes, debit totals, credit totals, block count, batch numbers, and trace sequences are rebuilt from the current form values.
In this workflow, yes. The creator builds an ACH payment file using the fixed-width NACHA record format, controls, and padding.
Yes. Each receiver entry uses a transaction code based on account type and credit or debit direction. Review the service class and totals before download.
No. The SEC code belongs to the Batch Header. Create separate batches when consumer and corporate entries require different classifications.
Yes. The output rebuilds entry and addenda counts, routing hashes, debit and credit totals, batch and file controls, block count, and padding.
Not automatically. The structure can be valid while company IDs, effective dates, balancing rules, or transmission settings differ from the ODFI profile.
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.