
ACH (Automated Clearing House) is the US network that moves money between bank accounts in batches. It’s how most Americans get paid, pay bills and pay suppliers. It isn’t instant, but it’s cheap, reliable and reaches every US bank and credit union.
ACH is how US banks move money in batches, like a mail truck that collects many letters and delivers them together. It is cheap and reliable, but not instant. This post explains how it works and when to use something faster.
ACH in numbers
In 2025, the ACH Network carried 35.2 billion payments worth $93 trillion, about 141 million payments every day. Business-to-business payments grew almost 10%, to about 8.1 billion, as companies kept moving away from paper checks.
Who runs ACH
| Role | Who | What they do |
|---|---|---|
| Rule maker | Nacha | Writes and updates the ACH rules that every bank must follow |
| Operators | The Federal Reserve (FedACH) and The Clearing House (EPN) | Receive files from banks, sort the payments and pass them to the receiving banks |
| Sending bank | ODFI (Originating Depository Financial Institution) | Collects payments from its customers and sends them in files |
| Receiving bank | RDFI (Receiving Depository Financial Institution) | Posts the money to the receiver’s account, or returns it if something is wrong |
How an ACH payment moves
- A company or person starts a payment, such as payroll or a bill payment, through their bank.
- The sending bank batches it with other payments into a file and sends the file at set times during the day.
- The operator sorts the file and forwards each payment to the right receiving bank.
- The receiving bank posts the money to the account on the settlement date (the day the money actually moves).
- If something is wrong, the payment comes back as a return with a reason code, for example R01 (not enough money) or R03 (no account found).
ACH vs wire: which one when?
| Feature | ACH | Wire |
|---|---|---|
| Speed | In batches; money arrives the same day or the next day | One at a time, in real time during operating hours |
| Cost | Low, often cents | Higher, often dollars per payment |
| Can it come back? | Yes, through returns within set time limits | No, final once sent |
| Best for | Payroll, bills, regular supplier payments | Large, urgent or one-off payments like a house closing |
ACH-type systems around the world
Most countries have their own “ACH”, a low-cost batch system for everyday payments:
| Region | System | Who runs it |
|---|---|---|
| United States | ACH | Nacha (rules); Federal Reserve and The Clearing House (operators) |
| Euro area (SEPA: the euro-area system for bank transfers) | SEPA Credit Transfer | European Payments Council (writes the rules). Payments arrive within one business day. |
| United Kingdom | Bacs | Pay.UK. Uses a three-working-day cycle. |
| India | NACH (India’s system for bulk payments like salaries and bills) and NEFT (India’s batch bank transfers) | NPCI (the body that runs India’s retail payment systems) runs NACH; the Reserve Bank of India runs NEFT, which settles in half-hourly batches around the clock |
| Canada | Automated Funds Transfer (AFT) | Payments Canada |
| Australia | BECS (Direct Entry) | Australian Payments Network (AusPayNet) |
| Singapore | GIRO | Association of Banks in Singapore |
| Japan | Zengin System | Japanese Bankers Association |
Settlement times differ by system and by bank, so always check the local rules before promising a delivery date.
When to upgrade ACH to wire
Start on the left. The customer starts an ACH payment and the bank checks it. If it is under the ACH limit and on time (“No”), it goes as ACH in a low-cost batch. If it is over the limit, or has missed the cut-off but must arrive today (“Yes”), it is upgraded to a wire, which is real time and final. Both paths end with the business getting paid. The bar at the bottom is the audit rule: the original ACH trace number stays linked to the wire.
In my work, many banks move a payment from ACH to wire automatically in three cases: it is above a set amount, it missed the ACH cut-off but must arrive today, or the receiver needs final funds. Here is how a product team can write those rules as clear, testable scenarios:
For engineers: the technical detail below is optional; the rest of the post makes sense without it.
Scenario: Payment amount is above the ACH limit
Given a customer starts an ACH payment
And the amount is above the configured ACH limit, for example $100,000
When the payment is validated
Then the system flags it for a wire upgrade
And the ACH instruction is not sent
And a wire instruction is created
Scenario: ACH details are carried into the wire
Given the original ACH payment details
When the payment is upgraded
Then a wire message is created for Fedwire or Swift
And the beneficiary details stay the same
And the payment reference is kept
And the original ACH trace number is linked for audit
Scenario: The wire fails
Given an ACH payment was upgraded to a wire
When the wire fails with a network or validation error
Then the payment is not resent as ACH automatically
And the customer is told
And the funds are held or returned according to policy
And an exception case is opened
Scenario: Audit trail for the upgrade
Given a payment was upgraded
When the maker and checker run the audit report
Then the report shows the original ACH request
And the reason for the upgrade
And the wire reference number
And the time and the user or system that made the change
Scenario: Customer can track the payment
Given a payment was upgraded after the ACH cut-off
When status updates are sent
Then the ACH status shows "Upgraded to wire"
And the wire status moves from Initiated to Sent to Settled
And the customer can track it in real time
My take
ACH is the quiet workhorse of US payments: low cost, huge scale and very reliable. Wire is the fast, final option for big or urgent money. A good payments product uses both, and makes the switch between them automatic, traceable and clear to the customer.
Working on a payments project?
I help banks and fintechs deliver real-time payments, ISO 20022, and AI-driven AML and compliance change, from strategy to go-live.
Connect on LinkedInSee how I can help