What columns does a CSV need for ACH?
At minimum: recipient name, routing number, account number, account type, and amount. Recipient ID, addenda, and remittance details are optional.
Turn a comma-separated payment list into a NACHA ACH credit file. Import vendor or payroll data, map the columns, validate every row, and download a CCD or PPD file without uploading bank data to a server.
CSV works well when your accounting system, payroll provider, or internal export already produces a flat payment list. If you only have Excel, you can also upload .xlsx on the Excel to ACH page or paste tab-separated rows directly into the importer.
| Column | Required | Description | Example |
|---|---|---|---|
| Recipient name | Yes | Payee or employee name as it should appear on the bank statement. | FICTIONAL VENDOR |
| Routing number | Yes | Nine-digit ABA routing number including check digit. Store as text so leading zeros are preserved. | 990000000 |
| Account number | Yes | Recipient bank account number, up to 17 characters. Store as text so leading zeros are preserved. | 000EXAMPLE001 |
| Account type | Yes | Use checking or savings. | checking |
| Amount | Yes | Payment amount in dollars. Use 0 for prenote files. | 123.45 |
| Recipient ID | No | Optional employee or vendor ID carried in the entry detail record. | VENDOR001 |
| Addenda | No | Optional 80-character payment reference written to an addenda record. | INVOICE 1001 |
| Remittance details | No | Optional invoice or credit memo text used only for the downloadable remittance CSV report. | INVOICE 1001 AND CREDIT MEMO 20 |
You do not need exact header spelling. The generator suggests mapping from common export labels such as:
| Common CSV header | Maps to |
|---|---|
| Recipient / Payee / Vendor / Employee name | Recipient name |
| Routing / ABA / Bank routing number | Routing number |
| Account / Bank account number | Account number |
| Account type / Type | Account type |
| Amount / Payment / Total | Amount |
| Employee ID / Vendor ID | Recipient ID |
| Invoice / Memo / Reference | Addenda |
All sample data below is fictional.
| Recipient name | Routing number | Account number | Account type | Amount | Recipient ID | Addenda | Remittance details |
|---|---|---|---|---|---|---|---|
FICTIONAL VENDOR | 990000000 | 000EXAMPLE001 | checking | 123.45 | VENDOR001 | INVOICE 1001 | INVOICE 1001 AND CREDIT MEMO 20 |
Choose a CSV/XLSX file or paste rows copied from a spreadsheet. The first row must contain column names. Data is read only in this browser. In Excel, format routing and account number columns as Text to preserve leading zeros. For recurring rosters, leave the amount blank to mark a recipient as unpaid in this run; the app will show every skipped row for confirmation.
ACH file upload is not included with every business bank account. Ask your bank whether your account can upload NACHA files and request its current ACH file instructions before entering configuration values.
After mapping, the generator checks each row locally before you create the NACHA file:
Need to inspect an existing file instead? Use the ACH file validator.
At minimum: recipient name, routing number, account number, account type, and amount. Recipient ID, addenda, and remittance details are optional.
Yes. Copy rows from Excel or Google Sheets and paste them into the importer. Tab-separated pasted data works the same way as a CSV upload.
No. The file is parsed in your browser. Routing numbers, account numbers, and generated ACH files are not uploaded to a server.