A mid-market controller told me last month that her team spends every Tuesday afternoon printing, signing, and stuffing checks. Four people, four hours, 200 checks. That is 16 person-hours per week — 832 hours per year — feeding envelopes into a printer.

Meanwhile, the ACH Network processed 35.2 billion payments worth $93 trillion in 2025. B2B ACH volume alone grew 9.9% to 8.1 billion transactions. Same Day ACH hit 1.4 billion payments, up 16.7% year-over-year. The payment rails are there. Most mid-market AP teams just have not made the switch.

And when they do make the switch, they usually stop halfway: payments move to ACH, but somebody is still exporting a file and logging into the bank portal every Thursday. That half-migration is the expensive one, because it keeps all the manual risk and gives up most of the savings.

The Real Cost of Cutting Checks

The numbers are not close. According to AFP payment cost benchmarking data, the median cost to issue a paper check is $2.01 to $4.00 per payment. The median cost for an ACH payment is $0.26 to $0.50.

The sticker price understates the gap. Here is what check processing actually costs when you count everything:

Cost Component	Paper Check	ACH Payment
Payment issuance	$2.00-$4.00	$0.26-$0.50
Printing and supplies	$0.50-$1.00	$0.00
Postage	$0.68+	$0.00
Manual reconciliation	$1.50-$3.00	$0.10-$0.25
Fraud investigation (amortized)	$0.75-$2.00	$0.05-$0.15
Total per payment	$5.43-$10.68	$0.41-$0.90

For a company issuing 500 vendor payments per month, that is the difference between $32,580 and $5,400 per year — over $27,000 saved on the payment execution step alone.

The Objection That Actually Blocks This

When I talk to AP managers who have not automated ACH, cost is never the reason they give. The reason is control.

The worry is specific and reasonable: right now, one person builds the payment batch and a different person logs into the bank and releases it. Two sets of credentials, two humans, one clean boundary. Automate that, and the fear is that the boundary quietly disappears — that "automated" means a system fires money out the door and the segregation of duties your auditor signed off on becomes a checkbox in a settings page.

That fear is worth taking seriously, because badly configured automation does exactly that. Here is what good configuration looks like instead.

How Segregation of Duties Survives Automation

Segregation of duties in AP rests on three boundaries. Automation should make each one harder to cross, not easier.

Boundary 1: whoever creates a vendor cannot pay it. This is the one that matters most, because vendor master fraud is where the real money goes. In an automated setup, vendor banking details arrive through a self-service portal during vendor onboarding, get validated against the account, and land in a pending state. A second person approves the vendor record. Nobody in AP can type a bank account number and then send money to it in the same session.

Boundary 2: whoever approves an invoice cannot approve the payment batch. Invoice-level approval happens in the invoice approval workflow, against the invoice and the PO. Batch-level authorization is a separate act by a separate role, reviewing the batch total and the exceptions rather than re-approving each line. Two different people, two different questions.

Boundary 3: whoever can change a bank account cannot release the next payment to it. This is the control most manual processes get wrong. If a vendor's bank details changed in the last 30 days, that vendor's next payment should route to a hold queue for confirmation through a known-good phone number. Automation enforces this every time. A human checking a spreadsheet enforces it on the days they remember.

Write those three boundaries into your internal controls checklist as configuration you can screenshot for an auditor. That is the part manual dual control cannot give you: a control that is provable rather than attested.

The honest trade-off: automated controls fail differently from human ones. A human notices that a $40,000 payment to a landscaping vendor is strange. A rules engine notices that it exceeds a threshold. You need both, which is why the batch authorizer role does not go away — it just stops re-keying.

Drop the Bank Portal Upload

Most teams that have "automated ACH" are still doing this: export a Nacha file from the accounting system, log into the bank portal, upload it, key in a token code, and eyeball a confirmation screen. That step is where the remaining risk lives. A file on somebody's desktop is a file that can be edited before upload, and the upload itself typically runs under one person's credentials.

Here is the workflow once ACH payment processing automation is actually in place:

Step 1: Invoice approved. Approval completes digitally. The payment is queued in a batch with other approved invoices.

Step 2: Batch assembled on schedule. On your payment run schedule, the system groups approved invoices by method. ACH-eligible payments form an ACH batch; the rest route to check or wire.

Step 3: Pre-submission validation. Each payment is checked against the vendor's validated bank details, amounts are matched to approved invoices, and anything unusual is flagged — a changed bank account, an amount outside the vendor's normal range, a possible duplicate. This is where duplicate payment prevention happens without anybody running a report.

Step 4: Batch authorized. The designated approver reviews a batch summary and an exceptions list, not 200 individual payments. One authorization covers the batch, and it is recorded against their identity.

Step 5: File transmitted directly. The system generates the Nacha-formatted file and transmits it to the bank over a direct connection. No desktop file, no portal login, no token typed into a browser. Standard ACH settles in 1-2 business days; Same Day ACH settles within hours.

Step 6: Automatic reconciliation. On settlement confirmation, transaction IDs match back to invoices automatically. Your payment reconciliation is done before your team starts their day.

The weekly cycle gets shorter because the batch review replaces the batch assembly, not because a control was removed.

Nacha Compliance: The 2026 Rules

Nacha's Phase 1 fraud monitoring rule took effect March 20, 2026. If you originate ACH credits, you are required to monitor outbound transactions for signs of fraud.

Specifically, you need:

Fraud detection monitoring on outbound ACH credit transactions
Account validation procedures to verify payment details before submission
Documentation showing your monitoring processes and any actions taken

If you are still running payments through a bank portal, compliance means adding manual review steps and keeping evidence of them. If your pre-submission validation is automated, the monitoring and the documentation are the same artifact. Our guide to ACH fraud detection covers what those checks should look for.

Why AP Teams Stay Stuck

Three reasons, and none of them are technical:

Vendor banking details are missing. You cannot send ACH without a routing and account number, and most vendor master files never collected them. Start with the 20% of vendors that account for 80% of spend, collect through a secure portal, and validate before the first payment.

Approval workflows assume paper. The CFO signs checks over $10,000; the controller signs the rest. Those checkpoints feel like controls but run at 14-17 day payment cycles. Digital approvals with recorded identity are faster and produce a better audit trail than a wet signature ever did.

Nobody owns the migration. It is not an IT project or a finance project — it is both. Successful migrations name one owner in AP, set a target (80% of payment volume on ACH within 90 days), and review weekly.

The 30-Day Migration

Week 1: Audit your payment mix. Pull three months of payment data. How many checks, what dollar volume, which vendors. That is your conversion opportunity.

Week 2: Collect banking details. Top 20 vendors by volume, secure enrollment requests, self-service portal. Most respond within a week — they want ACH too, because it pays them faster.

Week 3: Configure and test. Batch schedules, approval thresholds, the three segregation boundaries above, direct bank transmission. Run a test batch of 5-10 payments end to end.

Week 4: Go live. Switch the regular run to ACH for enrolled vendors, keep checks for the rest, track conversion weekly.

Most companies reach 60-70% conversion within 30 days and 85% or more within 90. The long tail is small vendors slow to send details, not a technical limit.

The Early Payment Discount Bonus

Faster payments unlock early payment discounts. When your cycle drops from 14 days to 1-2, you can consistently capture 2/10 net 30 terms that were previously impossible to hit.

A 2% discount on $5 million in annual spend is $100,000. That is not a rounding error. And it only becomes available when payment execution is fast enough to land inside the discount window.

FAQ

Does automating ACH payments weaken segregation of duties?

No, if it is configured correctly. Automation should enforce three boundaries: whoever creates a vendor cannot pay it, whoever approves an invoice cannot authorize the payment batch, and whoever changes bank details cannot release the next payment to that account. Each boundary becomes a configured rule that applies every time rather than a habit somebody has to remember, and the enforcement is provable to an auditor.

How long does it take to switch from checks to ACH payments?

Most mid-market companies convert 60-70% of payment volume within 30 days. The bottleneck is collecting vendor banking details, not technical setup. Start with your top 20 vendors by spend, use a secure portal for self-service enrollment, and track conversion weekly. Reaching 85% or more typically takes 90 days.

What does ACH payment processing cost compared to paper checks?

ACH costs $0.26 to $0.50 per transaction according to AFP benchmarking, against $2.00 to $4.00 for a check. Including printing, postage, reconciliation, and amortized fraud investigation, the fully loaded cost is $5.43 to $10.68 per check versus $0.41 to $0.90 per ACH payment. At 500 payments per month that is over $27,000 saved per year.

Do we still need someone to release payments at the bank?

You need someone to authorize the batch, but not to re-enter it. Direct bank transmission removes the portal upload while keeping the authorization step, which is the actual control. The person who assembles the batch and the person who authorizes it remain different people.

Is ACH more secure than paper checks?

Yes. A check exposes your account and routing number on every payment, can be intercepted in the mail, and is vulnerable to check washing. ACH moves through encrypted banking networks with fraud monitoring required under Nacha's 2026 rules. Check fraud remained the most-reported payment fraud method in AFP's 2025 survey, while ACH fraud rates stayed materially lower.

ACH Payment Processing Automation: Faster Payments, Same Controls