What Is ACH? How Automated Clearing House Payments Work

ACH is an electronic funds transfer network that moves money directly between bank accounts in the United States, usually through the Federal Reserve or a private clearing house. ACH payments are typically batch-processed, which is why they settle in a day or two rather than in real time.

If you sell to US customers or pay US suppliers, ACH is likely the cheapest way to move money between accounts. Understanding how a transfer travels from one bank to another helps you choose it correctly, set the right expectations on timing, and avoid the reversals that catch finance teams off guard.

What Is ACH in Plain Terms

ACH stands for Automated Clearing House. The name refers to the clearing system, not a single company. In the US, two operators run ACH processing: the Federal Reserve's FedACH network and the Electronic Payments Network, a private facility. Both clear the same way: files of debits and credits move between banks and are netted and settled in batches.

An ACH payment is any transfer initiated through this network. That includes payroll direct deposits, recurring subscription charges, utility bill payments, tax refunds, and business-to-business invoices. An ACH transfer moves funds from one account to another without a card network, wire network, or check in the middle.

ACH is domestic. It works between US bank and credit union accounts, and the network also connects to some US territories. Cross-border transfers that look similar usually ride on separate rails, so don't assume a European or Asian counterparty can receive an ACH payment.

ACH transactions move through a batch-based, next-day (or same-day) cycle that differs by direction. The table below maps the main stages for a standard next-day ACH debit and credit.

Each row matters because ACH is not instant in the way card or wire transfers can be: the gap between origination and posting is where most problems surface. A payroll credit is generally completed on the settlement date the originator specifies, while a debit can still be reversed by a return days later, which is why businesses often hold incoming funds before treating a payment as final. Same-day ACH compresses the first three stages into a handful of intraday windows, but the return process and the RDFI's posting rules still determine when the money is genuinely usable.

How an ACH Payment Works, Step by Step

Every ACH transaction involves four roles: the originator (the party sending or collecting money), the originating bank (often called the ODFI, Originating Depository Financial Institution), the receiving bank (the RDFI), and the ACH operator that clears the batch. Here is what happens in sequence.

1. The originator collects bank details from the counterparty: routing number, account number, account type, and account holder name. For recurring debits, the originator also needs written authorization.
2. The originator builds an ACH file with the payment instructions and submits it to its bank, usually through online banking or an API.
3. The originating bank validates the file, checks authorization records, and forwards it to an ACH operator before the daily cutoff.
4. The operator sorts entries by receiving bank and delivers them. The receiving bank posts the credit or debit to the account.
5. The operator nets the totals between banks and settles the balances, so the money actually changes hands between institutions.
6. If a payment fails (closed account, wrong account number, insufficient funds), the receiving bank returns it through the same path. Returns can take several business days.

Settlement follows a schedule set by the ACH rules. Same-day ACH exists and processes multiple windows per day, but it carries a fee that varies by provider and is not available for every transaction type. Standard ACH typically settles on the next business day, with some entries taking two. Confirm current cutoffs and windows with your bank, since these are operational rules that change.

Key ACH Terms You Will See on Statements and Files

The vocabulary in ACH files is narrow but confusing for newcomers. These are the terms that matter most in day-to-day operations.

• NACHA: the rulemaking body that governs the ACH network. Its operating rules define formats, return codes, authorization standards, and dispute handling.
• Entry: a single debit or credit instruction in an ACH file.
• Batch: a group of entries submitted together, usually by the same originator and type.
• Originating bank (ODFI): the bank that submits the file on your behalf and takes on compliance responsibility for your entries.
• Receiving bank (RDFI): the bank holding the account being credited or debited.
• Return: a payment that bounces back, for example because the account is closed or the authorization was revoked.
• Reversal: a correction of a payment already sent, used to fix errors rather than to cancel a legitimate charge.
• Prenote: a zero-dollar entry that verifies account details before the first live payment.
• Return code: a short identifier that explains why a payment failed, used for reconciliation and fix-up.

Two directions matter operationally: an ACH credit pushes money out (payroll, supplier invoices), and an ACH debit pulls money in (subscriptions, bill collection). Debits carry stricter authorization requirements, because the originator is reaching into someone else's account.

A Worked Example of an ACH Transfer

Suppose a US software company with 40 employees runs monthly payroll. On the 28th, its finance lead uploads a file to its bank containing 40 credit entries: one per employee, each with a routing number, account number, and amount. The numbers here are illustrative.

The bank validates the file and sends it to the ACH operator before the cutoff. The operator sorts the entries by each employee's bank and delivers them. On payday, each employee's bank posts the credit; the operator nets the company's outgoing total against the flows of every other participant and settles the net position between banks.

If one employee closed their account without telling HR, that entry comes back as a return, often within two business days. The finance lead reissues it to a new account or pays it by another method. Recurring subscriptions work the same way in the other direction: the merchant sends debit entries, and a customer's bank posts the charges or returns them if funds are short.

Common Misconceptions About ACH

A few persistent misunderstandings create real operational problems. Clearing them up saves failed reconciliations.

• ACH is not a card payment. It bypasses card networks entirely, so chargeback rules, card fees, and card fraud tools do not apply. Disputes are handled through the ACH return rules instead.
• ACH is not a wire. Wires are settled individually and are typically same-day and irreversible once sent; ACH batches and settles through a netting process. Fees and cutoff times differ sharply between the two.
• ACH is not instant by default. Same-day ACH exists but costs more and has its own limits. Standard ACH takes one to two business days.
• A successful submission is not a confirmed payment. The money is only cleared when the receiving bank posts it and no return arrives. Treat the return window as part of your receivables plan.
• ACH is not a consumer protection umbrella. Consumer debit authorizations are protected by rules, but business-to-business ACH has fewer safeguards. Diligence rests with your bank and your own controls.

Why ACH Matters for Merchants and Finance Teams

ACH is usually the lowest-cost way to collect recurring payments and pay suppliers inside the US. Because it lacks card network fees, it often makes sense for subscription billing, utility-style payments, and high-volume payroll. It also plays well with accounting systems, since bank files and return codes can be reconciled automatically.

The trade-offs are real. Settlement is not instant, returns can happen days after you count a payment as received, and debit authorizations must be documented. Unauthorized debits carry serious consequences under the ACH rules, including the risk of your originating bank restricting your account. Fraud controls matter too: ACH fraud typically involves stolen account details used for unauthorized debits or vendor impersonation, so verify banking changes by phone and monitor return codes for patterns.

How a US buyer pays a supplier in another country depends on the corridor. The counterpart may prefer local rails or a wire. For a quick comparison of common methods and where they fit, see the guides on this site covering international payment options.

Practical Takeaways Before You Use ACH

If ACH fits your flow, set up the operational basics first: dedicated bank validation for new accounts, written authorization records for any debit, agreed return handling with your originating bank, and reconciliation rules that treat a payment as received only after the return window closes. Ask your bank about same-day ACH availability, current cutoffs, entry limits, and fees before you promise customers a timing.

For recurring billing, test with a prenote before the first live debit and monitor return codes early. For payroll and supplier payments, keep a manual fallback for failed entries so a single closed account does not delay the whole file. These steps are not optional overhead; they are what separates a smooth ACH program from one that creates cleanup work every cycle.

This is general information, not financial, legal, or tax advice. Rules, fees, and timing vary by institution and jurisdiction, so verify current ACH requirements and operational details with your bank and the NACHA rules.