Generate US ACH payment files without an ERP

To submit a generated file, yes — your business needs to be set up with your bank for ACH origination, with a Company Identification Number assigned and ACH file upload (or SFTP transmission) activated on your account. PayFile Pro generates the file; your bank’s enrollment of you as an ACH Originator is what authorizes you to upload it. If you’re not sure whether your account supports ACH origination, your bank’s business banking or treasury management team can confirm and provision it if needed. Most US banks with business banking offer ACH origination as a service tier — sometimes free, sometimes a flat monthly fee, sometimes per-transaction — and require you to sign an ACH Origination Agreement before you can submit your first live file.

ACH (Automated Clearing House) is the US payment network that moves electronic credits and debits between bank accounts — direct deposit, vendor payments, bill pay, and so on. Nacha is the rule-making body that governs the ACH network; it publishes the Nacha Operating Rules that define how ACH transactions must be formatted, processed, and settled. The file format the network uses is informally called the “NACHA file” — it’s a fixed-width, 94-byte-per-line text file with a specific record structure (File Header, Batch Header, Entry Detail, Batch Control, File Control). PayFile Pro generates this NACHA file format for credit entries (vendor payments, payroll, disbursements) using the PPD and CCD Standard Entry Class (SEC) codes — the two codes that cover the vast majority of SMB outbound disbursement workflows.

Nacha approved a Risk Management package of rule changes that take effect across 2026. Four of them matter for ACH originators. Two are already in effect (since March 20, 2026); two more are coming up.

1. Standardized Company Entry Descriptions: PAYROLL and PURCHASE. Effective March 20, 2026 — already in effect. PPD credit entries that pay wages, salaries, or similar compensation must use PAYROLL in the Company Entry Description field (positions 54–63 of the Batch Header record). E-commerce WEB debits must use PURCHASE. Other Company Entry Descriptions you’ve used historically (ACH PMT, VENDOR PAY, BONUS, etc.) remain valid for non-payroll, non-e-commerce ACH entries — the rule only mandates PAYROLL for PPD wage credits and PURCHASE for WEB e-commerce debits. The PAYROLL change is directly relevant to PayFile Pro’s PPD payroll workflow: when you generate a PPD wage batch, fill PAYROLL into the Company Entry Description column of your CSV template. PURCHASE doesn’t apply to PayFile Pro since we don’t generate WEB debits.

2. Risk-based fraud monitoring obligations for originators — Phase 1. Effective March 20, 2026 — already in effect. All ODFIs (your bank), and every non-consumer Originator, Third-Party Service Provider, and Third-Party Sender that originated 6 million or more ACH entries in 2023, must establish and implement risk-based processes and procedures reasonably intended to identify ACH entries initiated due to fraud (Business Email Compromise, vendor impersonation, payroll diversion). Phase 1 is the high-volume tier — most SMB originators won’t hit the 6M-entry threshold, so Phase 1 doesn’t apply to them directly, though their bank (the ODFI) is covered.

3. Risk-based fraud monitoring obligations for originators — Phase 2. Effective June 19, 2026 — practical compliance Monday, June 22, 2026, since June 19 is Juneteenth (a federal holiday). Phase 2 eliminates the volume threshold entirely. Every non-consumer Originator, Third-Party Service Provider, and Third-Party Sender — regardless of volume — must have documented, risk-based fraud monitoring in place. For most SMBs originating ACH credits, this is a procedural requirement (a written ACH fraud risk assessment, monitoring controls aligned to your risk areas, exception handling and escalation procedures, an annual review cycle) rather than a file-format change. The Nacha rule doesn’t prescribe a specific monitoring tool; it requires that the controls be reasonable for your volume, payment types, and risk profile. Your bank may ask you for documentation of your monitoring procedures as part of their own Phase 2 compliance work — worth getting ahead of before June 22.

4. Funds availability for non–Same Day ACH credits (RDFI side) and IAT definition update. Both effective September 18, 2026. The funds availability rule eliminates the existing 5:00 p.m. local-time receipt condition: receiving banks (RDFIs) will need to make non–Same Day ACH credits available to receivers no later than 9:00 a.m. local time on settlement date for all non–Same Day ACH credits, not just those received by 5 p.m. the prior banking day. This affects how quickly your payees see deposits — not what is in the file you generate. The IAT (International ACH Transaction) definition update clarifies when a transaction must be classified as IAT; it doesn’t apply to PayFile Pro’s current scope, since we don’t generate IAT entries.

Net effect for PayFile Pro users: the only change you need to make in your template today is using PAYROLL for PPD wage credits in the Company Entry Description column (already required since March 20, 2026). The Phase 2 fraud monitoring deadline on June 22 is a procedural compliance task on your end (documented monitoring, not a file change). The September funds availability rule benefits your payees by accelerating funds availability for next-day ACH credits — no action required on your side.

PayFile Pro generates files using the PPD (Prearranged Payment and Deposit — for individual payees: employees, contractors, individual vendors) and CCD (Cash Concentration or Disbursement — for business payees: corporate vendors, suppliers) Standard Entry Class codes. Together these cover the disbursement workflows most SMBs run: payroll direct deposit (PPD) and vendor payments (CCD). We don’t currently generate WEB (consumer-authorized internet debits), TEL (consumer-authorized telephone debits), IAT (International ACH Transactions), CTX (Corporate Trade Exchange — EDI 820 with structured remittance), or addenda-heavy codes like CCD+ (CCD with single addenda) or PPD+ (PPD with single addenda). If you need any of those, Treasury Software’s ACH Universal handles them — the Corporate edition adds WEB, TEL, ARC, BOC, POP, RCK, CCD+, PPD+, and addenda records; the Advanced edition adds IAT, CTX, and TXP (tax payment addenda). PayFile Pro’s PPD + CCD scope matches their Standard edition.

Yes. PayFile Pro generates the NACHA file; your bank’s portal is what you use to submit it. They’re complementary tools — no integration or API connection required. The portal varies by bank: Chase Business Online’s Payment Center, Bank of America’s CashPro (ACH module via the Validator feature), Wells Fargo CEO Payment Manager, U.S. Bank SinglePoint, PNC PINACLE, M&T Online Treasury Center, KeyBank’s Key2Business, and so on. Most have an ACH or payment-center module with a “Browse → Upload File” flow and a confirmation step before the file is released to the ACH operator. If your bank has dual approval enabled (often required above a monthly limit, optional below), a second user approves before the file goes live. If your bank uses SFTP transmission instead of (or alongside) portal upload — common at higher transaction volumes — PayFile Pro generates the same NACHA file; you transmit it via your existing SFTP tooling.

Not currently. PayFile Pro generates credit files — vendor payments, payroll, supplier disbursements (Service Class Code 220, credits-only batches). ACH debit files for customer collections, bill pay, or pre-authorized debits aren’t supported. If debit file generation is something you need, email us — it’s on the roadmap and customer demand is what moves it up. Note that originating ACH debits has its own approval and risk requirements with your bank: most US banks underwrite credit and debit origination separately, and debit origination usually requires a higher level of risk review. Confirm with your bank’s business banking team that your account is enabled for ACH debit origination before you start generating debit files anywhere — PayFile Pro included, when we add the feature.

Yes. PayFile Pro generates files entirely in your browser. Routing numbers, account numbers, amounts, and payee lists never leave your machine — no upload to our servers, no storage on our disk, no transmission anywhere. The only data we store is your account info: email, company name, primary bank, credit balance.

PayFile Pro validates files against the NACHA PPD/CCD spec before generation, which catches most common rejection causes (wrong field length, missing required fields, invalid characters, malformed dates, mismatched record counts, Entry Hash that doesn’t tie to the routing-number sum, batch totals that don’t tie to the entry totals). If your bank still rejects a file after generation, the most likely causes are bank-specific and not in the format spec itself: an Immediate Origin value that doesn’t match what your bank expects (some banks want your Tax ID, some want their own routing number, some want a specific 10-digit assigned value), a Company Identification Number mismatch with the value on file with the bank, an effective entry date that’s too aggressive (most banks require ≥1 business day for vendor credits and ≥2 business days for payroll), a missing bank-specific security record ($$ADD or LOGDX header records — Chase, Wells Fargo, and a handful of others require these), a file that contains debits when your account is enabled for credits only, or a cutoff miss for Same Day ACH (cutoffs vary by bank, typically between 11:30 a.m. and 4:45 p.m. ET). Email hello@payfilepro.com with the rejection message and we’ll help you debug — if the rejection is bank-specific and frequent enough, it gets documented on the bank’s dedicated PayFile Pro page so the next person hits a known-resolved issue.

Most US bank portals save your originator information — Company Name, Company ID, settlement account, batch templates, payee profiles — and let you key transactions directly into the platform or release pre-saved records. What they don’t have is a per-payee template layer that lives outside the system. Every run, you’re either keying transactions in or releasing pre-entered records that you have to maintain inside the portal — and the portal UI for editing 30 vendors at once is, in most banks, slower than editing a spreadsheet. With PayFile Pro, your Excel sheet is the template. Leave an amount blank to skip a vendor — their row stays in next week’s template. Add a row to add a vendor — they’re part of your reusable template from then on. The spreadsheet is the state; each run is just what’s in the amount column. You still upload the file through your bank’s portal — but the variance management lives in your spreadsheet, where editing is easier than navigating the portal UI.

PayFile Pro uses prepaid credits. One credit per generated file. Credits never expire. Packs start at $10 USD for 5 credits ($2.00 per file) and scale to $1.50 per file at 50 credits. No subscription, no monthly minimum, no auto-renewal. Buy credits when you need them.