How ACH Works
The ACH Network operates as a store-and-forward batch system, meaning transactions are collected throughout the day, bundled into files, and transmitted to a clearing house — either the Federal Reserve's FedACH or The Clearing House's EPN — at set intervals. Understanding the mechanics helps merchants anticipate settlement timing and manage cash flow accurately.
Origination
A business (the Originator) instructs its bank (the ODFI — Originating Depository Financial Institution) to initiate an ACH entry. This requires a valid authorization from the account holder, a correct routing and account number, and the appropriate SEC code identifying the transaction type.
Batch Submission
The ODFI aggregates ACH entries into a NACHA-formatted file and submits it to an ACH operator (FedACH or EPN) by one of several daily cutoff windows. Entries missing a cutoff are held for the next processing cycle.
Clearing
The ACH operator sorts entries and routes each transaction to the appropriate RDFI (Receiving Depository Financial Institution) — the bank holding the recipient's account. This step typically completes within hours of submission.
Settlement
Funds move between the ODFI and RDFI. For standard ACH, settlement occurs on the next business day or up to two business days later. For Same-Day ACH, eligible entries submitted before cutoff windows settle the same business day.
Credit or Debit to End Account
The RDFI posts the funds to the recipient's account. For ACH credits, the receiver sees money deposited. For ACH debits, funds are withdrawn. The RDFI has a window to return the entry if problems arise (wrong account, insufficient funds, unauthorized).
Why ACH Matters
ACH is the backbone of US domestic payments, moving more money annually than any other retail payment rail. For merchants and finance teams, the economics and scale of ACH are impossible to ignore when building a payment strategy.
The ACH Network processed 31.5 billion payments totaling $80.1 trillion in 2023, according to NACHA — a volume that underscores its central role in the US economy. Average transaction value exceeds $2,500, reflecting heavy use in payroll, B2B, and recurring billing contexts.
Cost is the primary driver of adoption. ACH transaction fees typically range from $0.20 to $1.50 per transaction through most processors, compared to card interchange rates of 1.5%–3.5% plus fixed fees. On a $500 B2B invoice, that difference can exceed $10 per transaction. For companies processing thousands of payments monthly, the savings compound quickly.
Same-Day ACH has dramatically accelerated adoption. Since NACHA expanded Same-Day ACH in 2021 to include transactions up to $1 million, usage has grown sharply — same-day volume hit 1.1 billion payments in 2023, growing over 20% year-over-year. This narrows the gap between ACH and real-time payment rails for time-sensitive use cases.
ACH Return Rate Thresholds
NACHA enforces strict return rate limits. Overall return rates must stay below 15%. Unauthorized debit returns (return codes R05, R07, R10, R29, R51) must stay below 0.5%. Breaching these thresholds can result in audit, remediation requirements, or loss of ACH origination privileges.
ACH vs. Wire Transfer
Both ACH and wire transfers move money between US bank accounts, but they serve different use cases. Choosing the wrong rail adds unnecessary cost or settlement delay.
| Feature | ACH | Wire Transfer |
|---|---|---|
| Processing model | Batch | Individual / real-time |
| Settlement time | 1–3 days (same-day available) | Same day, often within hours |
| Cost (sender) | $0.20–$1.50 per transaction | $15–$35 domestic |
| Cost (receiver) | Often free or minimal | $10–$20 incoming fee |
| Reversibility | Yes — returns possible up to 60 days | Generally irrevocable |
| Dollar limits | $1M per entry (same-day); no cap for standard | No standard cap |
| International | US domestic only | Domestic and international (SWIFT) |
| Best for | Recurring billing, payroll, B2B | Large, time-critical, irrevocable payments |
For most subscription businesses and recurring payment scenarios, ACH wins on cost. For large one-time payments where speed and finality matter — real estate closings, M&A escrow releases — wire transfers remain the standard.
Types of ACH
ACH is not a single product but a network supporting distinct transaction types, each with specific rules, SEC codes, and use cases.
ACH Credit pushes funds from the originator to a recipient. Payroll direct deposit is the canonical example — employers push money into employee accounts. Government benefit payments, tax refunds, and marketplace seller payouts also use ACH credits.
ACH Debit pulls funds from a customer's account with their authorization. Subscription billing, insurance premium collection, mortgage payments, and utility auto-pay all run on ACH debits. This is where return risk concentrates.
Same-Day ACH is not a separate rail but a faster processing tier available for both credits and debits. Entries must be submitted before NACHA-defined cutoff windows and must be under the per-entry dollar cap. Banks may charge a premium for same-day processing.
International ACH Transactions (IAT) handle cross-border entries that touch the US ACH network. These carry additional OFAC screening requirements and more complex formatting rules, and are distinct from standard domestic ACH entries.
Best Practices
Implementing ACH well requires different disciplines depending on your role. Sloppy implementation leads to high return rates, compliance exposure, and failed payments.
For Merchants
Collect strong authorization before initiating any debit. Written or digital authorization must clearly state the payment amount, frequency, and the account to be debited. Store authorization records — NACHA requires them to be available for at least two years. Use account validation tools (micro-deposits, instant bank verification, or account verification services) before the first debit to reduce insufficient-fund and invalid-account returns. Monitor your return rates by return code weekly; spikes in R10 (unauthorized) returns are a compliance red flag. Consider direct debit agreements with a clear retry logic — most processors allow one retry on a failed ACH debit.
For Developers
Use the correct SEC code for each transaction type — PPD for consumer debit with written authorization, WEB for online-initiated consumer entries, CCD for B2B. Implement idempotency on payment submission: ACH files can be re-submitted accidentally, and duplicate entries are costly to unwind. Build webhook handling for return notifications — your processor will deliver return codes asynchronously, sometimes 2–4 days after the original transaction. Map each NACHA return code to an actionable status in your system (retryable vs. terminal). Test with real sandbox environments that simulate return scenarios, not just successful flows.
Common Mistakes
Skipping account validation. Initiating ACH debits without verifying the account exists and is active is the single largest source of avoidable returns. Instant bank verification via electronic funds transfer APIs adds seconds to onboarding and prevents days of settlement delay.
Using the wrong SEC code. Submitting a WEB entry for a phone-authorized transaction, or using PPD for a B2B payment, violates NACHA rules. Processors may reject misclassified entries or flag them during audits.
Ignoring return code specifics. Treating all returns as equivalent is a mistake. R01 (insufficient funds) is often retryable. R10 (customer advises unauthorized) is a compliance event requiring immediate investigation and counts against your unauthorized return rate threshold.
Poor retry logic. Retrying a failed debit too aggressively — or at all when the return code indicates a terminal error — antagonizes customers and worsens return rates. Build retry rules per return code category.
Inadequate authorization records. NACHA audits require merchants to produce authorization records on demand. Storing only a checkbox state without timestamp, IP address, and agreement version is insufficient.
ACH and Tagada
Tagada is a payment orchestration platform that sits above processors and acquirers, routing transactions intelligently across multiple payment methods and providers. ACH fits naturally into orchestration strategy for US-focused merchants.
Optimize ACH with Payment Orchestration
Tagada can route high-value or recurring US transactions to ACH automatically when cost savings outweigh settlement speed requirements, while keeping card rails available for time-sensitive or international payments. Combined with real-time success rate monitoring, orchestration reduces the operational overhead of managing ACH return logic across multiple processors.
For SaaS and subscription platforms, Tagada's orchestration layer can apply smart fallback logic: if an ACH debit returns R01 (insufficient funds), the platform can automatically retry via a configured card method on the next attempt cycle — reducing involuntary churn without manual intervention. This kind of cross-rail intelligence is difficult to build in-house but is a core capability of a well-configured orchestration setup.