ACH and E-Checks: When They Beat Cards for B2B

ACH beats cards on B2B invoices for one reason: the fee is usually flat, so it stops scaling with the invoice. Put a 50 cent per item ACH fee against a 2.5% card rate and the two lines cross at a $20 ticket, which means every real B2B invoice you send is cheaper by bank transfer. A $12,000 invoice costs $300 on a card and 50 cents on ACH. What you give up is speed and certainty. ACH clears in scheduled batches over 1 to 3 business days with no instant approval, so a failed payment reaches you days after you thought the money was in.

Most of what's written about ACH payments for small business is written by companies selling ACH. You'll find "up to 70% savings versus credit cards" in about seven places. No primary source sits behind that figure, so we're not repeating it.

The arithmetic is better than the marketing anyway.

ACH in plain terms

ACH stands for automated clearing house. It's the network American banks and credit unions use to move money between accounts in batches, and it carries direct deposit, mortgage autopay, supplier payments and most recurring billing.

Nacha governs it. Nacha writes the Nacha Operating Rules, and if you originate ACH transactions you're agreeing to follow them whether or not anyone hands you a copy.

Two institutions sit either side of every entry. Yours is the originating depository financial institution (ODFI), your customer's is the receiving depository financial institution (RDFI), and your ACH provider or payment gateway sits in front of the ODFI. That provider is the only part of the chain you'll ever talk to.

Debit pulls, credit pushes

ACH runs in two directions and people mix them up constantly.

An ACH debit pulls money out of your customer's account. You originate it, you need their authorization, and you hold the risk if it comes back. That's the one for collecting invoices.

An ACH credit pushes money out of your account to someone else. Payroll, supplier payments, commission runs. Nobody disputes a credit, because you sent it on purpose.

Collecting is much harder than paying.

An eCheck is an ACH debit with a web form in front of it

There's no separate eCheck network. An eCheck is an ACH debit where the routing and account numbers were typed into an online payment form instead of printed on a paper check.

So "which is better, eCheck or ACH" is a question with one side. If you accept eCheck payments you're originating ACH debits. Same rails, same timing, same return codes. What changes is how you captured the bank details, not the transaction.

Why the timing is different from a card

A card payment has an authorization step. You run it, a request goes out, and seconds later you have an answer and a hold on the funds. You know at the counter.

ACH has no equivalent. Entries go into a file, the file into a batch, the batch settles on a schedule.

Standard settlement

Standard ACH settles in 1 to 3 business days depending on when you submit and what your provider's cutoff is. Business days, not days. Submit on the Friday before a bank holiday and do the counting yourself. Card funding timelines are a separate question, covered in when do I get paid.

Same Day ACH

Same Day ACH moves qualifying entries inside same-day settlement windows rather than overnight.

There's a per-transaction dollar limit and there are submission deadlines. Both have moved over the years, and your provider applies its own earlier cutoff on top of the network's. We're not printing a number, because a stale one costs you a payroll run. Get the current limit and deadline in writing.

No authorization means no instant decline

This is what bites people coming from cards.

When you submit an ACH debit, nothing checks whether the money is there. The entry goes out, settlement happens, and if the account was empty or closed or mistyped you find out when the return lands days later. By then you may have shipped.

A card decline is immediate. An ACH return isn't. If your business can't wait, that matters more than the fee does.

The arithmetic, done properly

Card pricing is a percentage of the ticket. ACH pricing is usually a flat per item fee. A percentage grows with the invoice and a flat fee doesn't, so there's a ticket size above which ACH wins and below which it loses.

Market per-transaction ACH fees commonly fall between 20 cents and $1.50. Some providers quote a percentage instead, typically in the 0.5% to 1.5% band. Market ranges for context, not our pricing.

For scale on the other rails, a domestic wire transfer commonly runs around $14 on the sending side, varying by bank, which is why nobody wires routine invoices. ACH is domestic only, so international payments need a different instrument.

For the card side use your own effective rate, total fees divided by total volume off your statement. Not the rate you were quoted. The effective rate calculator does the division.

Where the two lines cross

At a 50 cent flat ACH fee against a 2.5% card effective rate:

0.50 / 0.025 = $20

Above a $20 ticket, ACH is cheaper. Below it, the card is. If your card pricing also carries a per-item fee, which most does, the crossover drops lower still.

For anyone invoicing other businesses this is settled before you start. Your tickets are nowhere near $20.

A $12,000 invoice

Say you send 40 invoices a month averaging $12,000, so $480,000 of monthly volume.

Those numbers look absurd because they are. It's why nobody in wholesale distribution takes a card on a six-figure invoice.

Two honest caveats. Not every customer will switch, so your real saving is on the share that does. And some pay by card to float the balance on their own credit line, so moving them to ACH means asking them to give up working capital. Expect pushback from anyone with tight cash flow.

Percentage pricing with no cap

If your ACH provider quotes 1% with no cap, that same $12,000 invoice costs $120 instead of 50 cents. You've bought a card rate with worse timing and no instant decline. Say no.

Capped, percentage pricing is fine. Capped at $5, the $12,000 invoice costs $5 and the maths still works. Uncapped percentage ACH on large tickets is the worst ACH deal in the market and it sells constantly, because the merchant compares 1% to 2.5% and never checks what happens at scale.

Ask one question: what's the most I can pay on a single transaction?

What returns add back

Your per-item fee isn't your real cost. Returns carry their own fee.

Say your ACH return fee is $10 and 2% of your debits come back. Twenty returns per thousand transactions is $200, spread across the thousand, so 20 cents each. Add that to the 50 cent item fee and your true cost is 70 cents.

Still cheaper than $300. Get your return fee in writing, because it varies a lot by provider.

Where cards still win

Being straight: ACH is the wrong answer for plenty of businesses.

Small tickets. On a $9 transaction a card beats a 50 cent ACH fee, and the interchange under a regulated debit card is capped at 21 cents plus 0.05%, plus a cent for issuers meeting the Federal Reserve's fraud-prevention standard. That cap covers issuers holding $10 billion or more in assets and it's still in effect as of October 2026. Small debit payments are not where your money goes.

Point of sale. If someone is standing in front of you, you need an answer in two seconds.

Consumer retail. Ask a retail customer for their routing and account numbers at checkout and you'll lose the sale.

New customers you don't know yet.

Check your Level 2 and Level 3 data first

Before you move B2B card volume to ACH, find out whether that volume is qualifying properly.

Commercial, corporate and purchasing cards have interchange tiers that reward passing extra data: tax amount, customer code, line item detail. Pass it and they qualify lower. Don't and they downgrade.

Nine times out of ten, a merchant complaining about the cost of B2B card acceptance is on a setup passing none of it. Fix that first. The mechanics are in Level 2 and Level 3 processing.

Authorization is the part people get wrong

Every ACH debit needs documented customer authorization before you submit it. Not implied, not "they've always paid this way". Documented and retained.

The rules set a retention requirement for proof of authorization, commonly cited as two years after the authorization ends. Confirm the current one with your provider.

If you can't produce the authorization when a customer claims an unauthorized debit, you lose.

Entry class codes

Every entry carries a standard entry class code telling the network what kind of transaction it is and which authorization rules apply.

CCD is corporate credit or debit, for entries against a business account, and most B2B collection runs on it. CTX is the corporate variant carrying structured remittance data, which matters if your customer's AP system matches payments to invoices automatically. PPD covers consumer accounts with a written authorization. WEB is an internet-initiated debit against a consumer account.

The mistake worth avoiding: an online payment form debiting a business checking account is not a WEB entry. WEB is consumer only. Merchants get boarded under the wrong code more often than you'd expect, and the code decides which requirements apply.

What the authorization has to cover

The amount, the timing, who's debiting them, and how to revoke it. For recurring payments that means the schedule plus either the amount or how it gets calculated. Keep the record somewhere you can retrieve it. A checkbox that logs nothing is not a record.

Account validation and ACH debit blocks

The rules require a commercially reasonable account validation method for WEB debits, which is why gateways sell bank account verification. Corporate entries don't carry that requirement the same way, but validate anyway and you'll avoid the administrative returns a transposed digit causes.

Then there's the one nobody warns you about. Business bank accounts very often carry an ACH debit block that rejects any debit not pre-approved, and your customer has to give their bank your company ID and tell them to permit it.

The usual version: you board, you submit your first debit run, a third comes back, and you spend a week finding out half your customers' controllers never whitelisted you. Put the company ID in your onboarding email.

Returns, codes and ceilings

An ACH return is the RDFI sending the entry back with a reason code. Insufficient funds and wrong account information are the two most common by a wide margin.

The split that matters is administrative against unauthorized. R02, R03 and R04 are data problems, they're your fault, and validating accounts up front fixes them. R10 and R29 are the customer saying they never agreed, and those get measured separately and watched harder.

Take your definitions from Nacha's own code list, not a vendor reference page.

Return rate ceilings

Nacha sets ceilings on originator return rates. The numbers quoted everywhere are 0.5% unauthorized, 3% administrative and 15% overall.

Treat those as commonly cited thresholds. They're version-dependent, and enforcement carries a minimum-volume condition, so twenty debits a month isn't the same position as twenty thousand. Confirm the current figures, the measurement window and the volume condition with your processor against the current Nacha Operating Rules before relying on them.

The direction isn't in dispute. Let unauthorized returns climb and you'll hear from your ODFI, then you'll lose origination.

What BE06 means

It isn't an ACH return code, despite turning up as a question people ask.

BE06 belongs to the Federal Benefit Enrollment code set, a different system. If you've been handed a BE06 and you're hunting for it on a list of ACH return codes, you're in the wrong document.

The dispute window

Here's the ACH advantage almost nobody sells, and it's the strongest B2B argument on this page.

Most ACH returns have to reach the ODFI by the opening of the second banking day after settlement. Two banking days. A consumer claiming an unauthorized debit gets a much longer window, commonly cited as 60 calendar days, but a business debited under a corporate entry doesn't get that.

Compare a card. A card dispute can land months later, commonly out to 120 days and longer under some reason codes, and you'll be assembling evidence for a sale you've forgotten. Our guide on fighting chargebacks covers that process.

Short return window, documented authorization, business counterparty. For recurring B2B billing that's hard to beat.

Can you charge a fee for ACH payments?

Card brand surcharge rules don't reach this transaction, because Visa and Mastercard aren't in it. Those caps and signage requirements govern card payments.

Three other things govern an ACH fee. Your authorization, because the customer has to have agreed to the amount you're debiting and a fee changes that amount. Your agreement with your ACH provider, which may restrict it. And state law, which varies and has changed, so ask your own attorney rather than any blog.

In B2B the more common move runs the other way. Post the invoice at one price and take something off for paying by bank transfer. A posted discount is a different instrument from a fee added at the end, and easier to explain to accounts payable.

Recurring billing: ACH against card on file

Card-on-file billing fails for reasons that have nothing to do with your customer's finances. The card expires, or gets reissued after a breach, or the issuer changes the number. Your charge declines and nobody warns you.

Bank accounts change far less often. A business keeps the same operating account for years, so recurring ACH sees fewer involuntary failures, which is an operational saving on top of the fee saving. Fewer failed payments, fewer dunning emails, a monthly number you can forecast.

The trade is that when an ACH debit does fail, you hear about it later.

Where we come into it

We're an independent sales organisation. We don't run a processing platform, and because no single processor owns us we can shop an account to the partner that fits it. Our contribution is the hands-on part: one named contact instead of a call-centre queue.

On ACH the useful thing we do is the arithmetic. Send three months of statements and we'll work out what share of your volume sits above the crossover point, what your card effective rate really is, and whether your B2B cards are qualifying for the tiers they should be.

Our own program has no contract, no early termination fee and no monthly fees of any kind. No program fee, no statement fee, no annual fee. Approval can land in as little as 24 hours with three months of statements up front, and the first terminal is free for most businesses.

Send a statement, get the arithmetic

Get a free savings analysis. We'll tell you where your volume sits, what moving the large invoices to bank transfer would save, and what it would cost you in timing.

If you're already well priced and your B2B cards qualify correctly, we'll say so and you can get back to work.