Your Bank Transfer Still Travels in an Overnight Batch
Direct deposit, bill payment, and most transfers between banks run on a system designed for magnetic tape. It is slow by construction, and the design choice that makes it slow is also what makes it cheap.
What the System Is
The automated clearing house, universally shortened to ACH, is the network that moves most routine payments between bank accounts. Salaries, bill payments, and transfers between your own accounts almost all travel this way.
Its defining feature is that it does not process payments individually. Instructions are collected, grouped into batches, and processed on a schedule. That single design decision explains nearly everything about how it behaves.
Why Batching Made Sense
The system dates to an era when processing meant physically handling tapes and running jobs overnight. Grouping thousands of instructions into one file and processing them together was the only economical approach.
The economics still hold. Processing a batch of a hundred thousand payments costs very little more than processing a batch of a thousand, so the cost per payment falls toward nothing. ACH transfers typically cost a fraction of a cent to a few cents, against card payments costing a percentage of the transaction.
The slowness is not neglect. Batching is what makes the cost per payment negligible, and for payroll or a utility bill, arriving tomorrow is perfectly acceptable.
Push and Pull
ACH carries two different kinds of instruction and the distinction matters more than most people realise.
A credit is a push. The sender instructs their bank to send money out. Payroll works this way, which is why your employer needs your account details rather than the reverse.
A debit is a pull. The receiver instructs the network to take money from someone else account, based on authorisation given earlier. Direct debits for subscriptions and utilities work this way.
Pull payments are convenient and they are also why account details are more sensitive than they appear. Someone with your account number and routing number has much of what is needed to attempt a debit, which is a different security model from cards.
The Reversal Window
ACH payments are not final when they arrive. Under network rules a payment can be returned for a period afterwards, for insufficient funds, for an account that does not exist, or because a consumer disputes that they authorised it.
| Property | ACH | Wire transfer |
|---|---|---|
| Processing | Batched on a schedule | Individually, in real time |
| Cost | Cents or less | Ten to fifty dollars |
| Finality | Reversible for a period | Effectively final on receipt |
| Typical use | Payroll, bills, transfers | Property purchases, large settlements |
That reversibility is a genuine feature for consumers and a genuine risk for businesses. A merchant that ships goods on receipt of an ACH payment can find the payment returned days later, which is why large or irreversible transactions use wires despite the cost.
Why the Money Appears Before It Arrives
Banks frequently credit your account before the funds have actually settled, which creates the impression that the transfer was instant. It was not. The bank advanced you the money against an expectation of settlement, and it bears the risk if settlement fails.
This is why holds exist on larger deposits, and why the same transfer clears instantly for an established customer and slowly for a new one. The difference is the bank appetite for that risk, not the underlying network.
What Replaced It, and What Did Not
Faster systems exist and are growing, processing payments individually and settling within seconds with immediate finality. They cost more per transaction and are irrevocable, which suits different uses.
The batch system persists because for payroll, recurring bills, and routine transfers, nobody is willing to pay meaningfully more for speed that provides no benefit. Infrastructure this cheap and this deeply embedded does not get replaced, it gets supplemented.
The Bottom Line
Bank transfers are slow because the network was built to process payments in scheduled groups rather than one by one, and that batching is exactly what drives the cost to almost nothing. The delay is a deliberate trade, and it is why the fastest option is rarely the one most payments actually use.