Every US bank offers its own batch-payment interface — NACHA files, bill pay, Zelle for Business, wire templates. Platforms vary. Reconciliation is manual. Here's why the current AP stack is broken for growing small businesses — and how to fix it.
Friday Morning: The AP Run
It's Friday morning. Your bookkeeper has 47 vendor bills approved for payment this week. The workflow goes like this:
- Open the AP queue. Filter by "approved."
- Log into the bank portal. Open bill pay.
- For each of the 47 vendors: look up the payee, enter the amount, confirm the account number, schedule the send date.
- After an hour, 38 payments are queued. 9 vendors aren't in bill pay — their remit-to is a different entity or the bill-pay provider can't find them. Those 9 need a check printed and mailed.
- Another 30 minutes printing checks, signing them, stuffing envelopes, running to the post office.
- Go back to the books. Update each bill status to "paid." Match the bank transfer confirmation IDs back to the bill numbers.
- Next week: reconcile.
Total time: 2–3 hours. Error rate: inevitable. A vendor gets paid twice. A check amount is transposed. A bill pay entry goes to the wrong account because two vendors have similar names.
This isn't a small-business problem. It's a growing-small-business problem. Once you have 50+ vendor bills a month, the per-bill friction multiplies.
Why Batch Payments in the US Are a Patchwork
The US payment rails are fragmented. Here's the lineup a small business typically touches:
Paper Checks
Still 30%+ of B2B payments in the US. Main problem: positive pay fraud requirements and the slow clear cycle (3–5 business days). Main benefit: universal — every vendor accepts them.
ACH (PPD for individuals, CCD for businesses)
The Automated Clearing House is the closest thing the US has to a universal batch payment rail. Banks process ACH batches overnight. Standard ACH credits settle in 1–2 business days; Same-Day ACH settles within hours.
The industry-standard batch format is a NACHA file — a fixed-width text file specifying sender, receiver, amount, and routing data for each payment. Submit one NACHA file with 200 vendor payments, and all 200 go out overnight.
The problem: most small-business banking portals do NOT accept NACHA file uploads. You have to use their web UI (one vendor at a time) or pay for an "ACH Manager" tier that does. Larger business banking portals (Bank of America Cash Pro, Wells Fargo CEO, Chase Connect Premier) do support NACHA — but they require a business banking relationship and often minimum balance requirements.
Wires (Fedwire / SWIFT for international)
For high-value or time-sensitive payments. Typically $15–$40 per wire. Same-day settlement. Not practical for batch AP.
Zelle for Business and Real-Time Payments
Zelle for Business is available from many major banks, but has per-transfer limits (typically $5,000–$15,000) and no batch mode. Real-Time Payments (RTP) through The Clearing House is growing but coverage is uneven — not every bank is on RTP.
Bill Pay Services
Most banks offer bill pay as an included feature. The catch: bill pay is still one-at-a-time in most portals. Some use ACH, some actually print and mail checks on your behalf (which is why the recipient sometimes gets a paper check even though you sent it "electronically").
Third-Party AP Platforms (Bill.com, Ramp, Melio, Tipalt)
These add a payment layer on top of the rails above. They accept your approved bills, handle vendor communications, and send payments via the best available rail. Monthly fees range from $50 to $500+ depending on volume.
The Three Failure Modes of the Current Stack
Failure Mode 1: Manual Re-Entry at the Bank
Your approved bills are in your accounting system. Your payments have to be entered in the bank portal. Every copy/paste is a chance to transpose a digit. Every vendor lookup is a chance to pay the wrong account.
Failure Mode 2: Three-Way Reconciliation
After payments clear, your bookkeeper has to match:
- The bill in the accounting system
- The payment in the bank statement
- The remittance confirmation (if any)
For a 50-bill batch, that's 50 manual matches. If confirmation numbers don't carry through clean (very common with bill pay), the reconciliation becomes a puzzle.
Failure Mode 3: Positive Pay Mismatches
For paper checks, most business banks require positive pay: a list of the check numbers, amounts, and payees you've issued, submitted before the check clears. If a check arrives that doesn't match the list, the bank rejects it.
Positive pay is a fraud defense — but it's also an operational burden. Miss uploading the file and legitimate checks bounce. Enter the wrong amount and the bank rejects a valid check, the vendor calls angry, and you spend an hour on the phone with the bank.
What a Working AP Workflow Looks Like
The goal is one approval and one file upload, with reconciliation built in.
Step 1: Bills Are Approved in Your AP System
Vendor bills come in, get approved according to your approval matrix (manager for under $5K, CFO for over), and move to a "ready to pay" queue.
Step 2: Select the Batch, Choose the Rail
The bookkeeper selects which bills to pay in this batch. The system asks: NACHA/ACH? Check? Wire? The choice is per-vendor based on what the vendor accepts, set once during vendor onboarding.
Step 3: Generate the Output Files
- For ACH vendors: the system generates a NACHA file (PPD or CCD record format), ready to upload to the bank's cash management portal.
- For check vendors: the system generates a positive-pay CSV in your bank's exact specification (Chase uses one format, Wells Fargo another, BOA another), plus the checks themselves for printing.
- For wire vendors: the system generates a wire template, ready to import into the bank portal.
Step 4: Upload to Bank, Reconcile Back
Upload the NACHA file to the bank. The bank processes overnight. The next day, the bank returns a settlement report. The AP system imports the settlement, matches it back to the bills, and marks them paid.
Step 5: Positive Pay Is Automatic
Every time a check is printed, its number, amount, and payee go into a queue. At end-of-day, the queue exports as a positive-pay file and uploads to the bank automatically.
How Pleelo Handles AP Batches
Pleelo's AP module eliminates the bank-portal detour for standard bills.
NACHA file generation: Pleelo produces a compliant NACHA PPD (for 1099 contractors) or CCD (for vendor companies) file. Upload once to your bank's cash management portal — Chase Connect, Wells Fargo CEO, Bank of America Cash Pro, or any bank that accepts NACHA — and the entire batch goes through.
Positive-pay exports: Pleelo knows the positive-pay file format of every major US business bank. When you print a check batch, Pleelo generates the matching positive-pay file. Upload to the bank, and every check is pre-cleared.
Vendor rail preferences: during vendor onboarding, each vendor is tagged with their preferred rail — ACH, check, wire, or a third-party platform. Every batch runs against those preferences, so you don't have to remember who takes ACH and who requires a check.
Three-way reconciliation: Pleelo matches the bill record, the bank-side transaction, and any remittance confirmation automatically. See our guide on bank reconciliation in Pleelo for how this flows into monthly close.
Approval trail: every bill has an approval log showing who approved it, when, and for how much. If your bank or auditor asks for the approval trail on a specific vendor payment, it's one click.
Dual control on high-value batches: optional — require a second user to release batches over a configurable threshold ($10K, $25K, $50K).
The Migration from Bill.com / Melio / Ramp to In-House AP
If you're paying a third-party AP platform $200–$500 a month and your bank supports NACHA uploads, there's an alternative: run AP directly from your accounting system and upload NACHA files to your bank yourself.
The tradeoffs:
| Third-party AP | In-house NACHA |
|---|---|
| Handles vendor onboarding | You maintain vendor ACH details |
| Pays via ACH, check, or virtual card | ACH + your bank's check-printing or positive-pay |
| Monthly subscription | No subscription, but bank may charge per transaction |
| Bill approval workflow built in | Use your accounting system's approval flow |
| Handles 1099 filing | Manage 1099s in your system (see our guide on W-9 and 1099-NEC compliance) |
For businesses with 100+ vendor bills a month, the in-house route with NACHA generation typically saves money. For businesses with complex vendor onboarding (many 1099 contractors, international vendors, or security constraints), third-party platforms still earn their fee.
What to Verify Before You Migrate
Before committing to an AP workflow change:
- Confirm your bank accepts NACHA uploads — call cash management, not retail support. Ask for the exact file specification (PPD/CCD, header lengths, effective date rules).
- Test the NACHA file with a small batch — 2–3 payments — before running a full batch.
- Verify positive-pay format — every bank has its own. Your system should match it exactly.
- Set up dual control — even if not required, require two sign-offs for large batches. ACH fraud is increasing, and operational controls prevent more problems than technology.
- Check your W-9 file completeness for ACH recipients — you need the vendor's legal name and TIN, not just their DBA and account number.
Stop Paying for the AP Headache
The right AP workflow is measured in minutes, not hours, per batch. Approve bills in the system, select the batch, generate the NACHA file, upload once, done.
Pleelo's AP module generates the files your bank expects — NACHA for ACH, positive-pay exports for checks, wire templates for high-value — and reconciles back automatically.
See how Pleelo handles batch payments →
One upload. One reconciliation. No more Friday-morning bank portal rotation.
