Supported ACH formats
The generator covers the slice of the NACHA specification that businesses actually upload to their own bank: single-batch, unbalanced CCD and PPD credit files. Everything it handles, and everything it deliberately leaves out, is listed below.
Supported
| Capability | Details |
|---|---|
| Input files | CSV, XLSX, and rows pasted straight from a spreadsheet. Columns are mapped in the browser, and the mapping can be saved for reuse. |
| Entry class codes | CCD for payments to business accounts and PPD for payments to consumer accounts, one class per file. CCD vs PPD covers the choice, and all SEC codes lists the classes that exist. |
| Transaction direction | Credits only — money leaving your account to recipients. Payroll, vendor payments, reimbursements, and commissions all fit here. |
| Batch structure | One batch per file, unbalanced (no offsetting entry). Most banks that accept customer-originated NACHA uploads expect exactly this. |
| Account types | Checking and savings, on live entries and prenotes alike. |
| Addenda | One optional type 05 addenda record per live entry, for invoice numbers or other free-form remittance text. |
| Prenotes | Zero-dollar credit prenotes for verifying account details before the first real payment. See the prenote generator. |
| Output | Fixed-width .ach or .txt downloads, blocked to 10-line boundaries, plus an optional local remittance CSV report. |
Not supported
| Not covered | Why |
|---|---|
| ACH debits | Pulling funds from someone else's account. Debit origination normally needs a separate bank agreement. |
| Balanced files | Files containing an offsetting entry for your own account. Ask your bank whether it requires balanced files before you start. |
| Other entry classes | WEB, TEL, CTX, and IAT are out of scope. They carry authorization and formatting rules beyond CCD and PPD. |
| Multiple batches | One file holds one batch. Split differing effective dates or entry classes into separate files. |
| Reversals and NOC | Reversal files and notifications of change are handled by your bank, not here. |
| Canadian EFT | The generator writes US NACHA records only. |
| API and transmission | There is no API, and no file is ever transmitted to a bank. You download the file and upload it yourself. |
Check your file against this list
If you are unsure whether an existing file fits the supported subset, run it through the ACH file validator — it reports the entry class, batch count, and record structure. The annotated ACH file format guide explains what each field position means, and how it works walks through the full path from spreadsheet to bank upload.