ACH Payments Explained: How They Work, What They Cost, and When to Use Them

While the payments world argues about cards and crypto and instant rails, one fifty-year-old network quietly moves the actual money — trillions of dollars a year in payroll, rent, invoices, and subscriptions — for fees measured in cents. ACH is the least glamorous and most underused tool in a small business's payment stack: on a $5,000 invoice, the difference between ACH and a card is roughly the price of lunch versus the price of $150. Here's how the network actually works, where it beats cards decisively, and the return-code and fraud-rule mechanics that keep merchants out of trouble.

How ACH actually moves money

The Automated Clearing House is a batch network connecting essentially every US bank account, governed by Nacha's operating rules. A transaction starts with an originator (say, your business collecting an invoice) instructing its bank — the ODFI, originating depository financial institution — which bundles the day's instructions into batches. The network operators sort and route them to each receiving bank (RDFI), which posts the debit or credit to the customer's account. Two flavors cover everything: ACH debits (you pull money with the customer's authorization — invoices, subscriptions, rent) and ACH credits (you push money out — payroll, vendor payments, refunds). The batch architecture is the whole personality of the rail: enormously efficient and cheap, but scheduled rather than instantaneous — the design trade that separates it from the real-time rails we covered in the pay-by-bank report. For business purposes, ACH is the workhorse lane of the same account-to-account highway.

Timing: standard, same-day, and what "settled" means

Standard ACH settles in one to three business days, depending on submission timing and debit versus credit. Same-day ACH runs multiple settlement windows each business day and clears eligible payments — up to $1 million per payment — in hours, for a modest premium. Two operational truths matter more than the schedule. First, "settled" is not "final": an ACH debit can still come back after settlement — insufficient funds returns arrive within about two banking days, and unauthorized-debit disputes can arrive much later (next section) — so treat fresh ACH funds with a maturity mindset, especially with new customers. Second, cutoffs are real: batches submitted after your processor's daily cutoff ride the next cycle, which is why invoice timing and retry scheduling around business days measurably changes cash-flow outcomes.

The cost advantage — and why it exists

ACH pricing is typically a flat fee in the cents-to-low-dollars range (sometimes a small percentage with a cap), versus the 2–3% all-in card stack we dissected in the fee guide. The reason is structural: cards carry interchange — compensation to the cardholder's bank funding rewards, risk, and the issuing business — plus network assessments; ACH carries none of that, just the marginal cost of batch processing. The arithmetic gets decisive as amounts grow: 2.9% of $80 is a couple of dollars; 2.9% of $8,000 is $232, repeated monthly on a retainer. This is why the canonical ACH conversions are large and recurring: B2B invoices, retainers, rent, memberships, high-ticket subscriptions. A pricing note for the sharp-eyed: because the economics differ so much, steering customers toward ACH with a small incentive (or passing card costs through where lawful — the rulebook in the surcharging guide) is one of the highest-ROI pricing moves available to an invoice-driven business.

Returns, disputes, and how ACH differs from chargebacks

ACH's failure system is returns, each carrying an R-code: insufficient funds, closed account, unauthorized, account not found, and dozens more. Three practical differences from card chargebacks define merchant strategy. First, the dispute scope is narrower: ACH consumer disputes are about authorization — was this debit permitted — not satisfaction; there is no "item not as described" reason code. That makes ACH structurally friendlier for merchants plagued by first-party card disputes. Second, the clocks differ: routine returns (NSF, closed account) come back within about two banking days, but consumers disputing an unauthorized debit have — under Regulation E — generally up to 60 days after the statement showing it, and that unwinding is essentially automatic; business (corporate) accounts, by contrast, have very short return windows. Clean, provable authorization is therefore the entire defense. Third, return rates are policed: Nacha thresholds cap overall, administrative, and unauthorized return rates, and processors monitor them the way card acquirers monitor chargeback ratios — the same discipline economics as our failed-payments playbook, where validation and payday-aware retry timing convert returns into recovered revenue.

The rules that matter: authorization, validation, fraud monitoring

• Authorization, kept on file. Every debit type has an authorization requirement — signed form, checkbox web flow, recorded phone consent — and retention duties. When an unauthorized-debit claim lands, your authorization record is the case.
• Account validation for web debits. Nacha requires commercially reasonable account validation for web-initiated debits — instant account verification via bank connection, or micro-deposits. Beyond compliance, validation is your best returns-prevention tool: most administrative returns are typos and dead accounts caught free at the front door.
• Fraud monitoring, now network-wide. Nacha's amended risk-management rules — phasing in with major obligations effective from March 2026 — require most network participants, originators included, to run fraud-monitoring processes aimed at the scams migrating onto bank rails: business email compromise, payroll redirection, vendor impersonation. The scam economy we mapped in the push-payment fraud report doesn't skip ACH; the network is formally arming against it, and merchants using processors with real-time monitoring inherit that defense automatically.

When ACH wins (and when cards do)

The strategic summary: this isn't ACH versus cards — it's ACH and cards, routed by transaction economics. The businesses that win offer both at checkout and invoice, steer the large and recurring toward the cents rail, keep cards for speed and one-time consumers, and run it all through one stack so settlement, reconciliation, and fraud intelligence see the whole picture instead of fragments.

Frequently asked questions

This guide is educational and does not constitute financial or legal advice. Network rules, pricing, and settlement schedules change over time; confirm current requirements with your processor and Nacha's published rules.