Most payments in the US are not real time, and most never need to be. Payroll, rent, supplier invoices, insurance premiums, loan payments: these move on the ACH network, a batch system designed in the 1970s that still carries the bulk of recurring money in the country. If you build a funding model, an ACH primer is not optional background. It is the default rail, and its quirks shape everything that sits on top of it.
The defining trait of ACH is that it does not settle one payment at a time. It collects payments, groups them, and processes the group on a schedule. Understanding that schedule, and the return window that hangs off it, is the whole game.
Two banks, two roles
Every ACH entry has two financial institutions. The ODFI (Originating Depository Financial Institution) is the bank that submits the entry on behalf of an originator, the party that wants to move money. The RDFI (Receiving Depository Financial Institution) holds the account on the other end.
The ODFI warrants the entry to the network. It vouches that the originator is authorized to debit or credit the receiver's account. That warranty is why the ODFI carries the risk and why your bank cares so much about who you onboard as an originator.
Nacha writes the rules both sides agree to follow. Nacha does not move money or operate the rails. Settlement runs through two operators: the Federal Reserve's FedACH and The Clearing House's EPN. Nacha governs; the operators clear and settle.
Credits and debits
ACH carries both directions, and the direction matters.
An ACH credit pushes money out. Payroll is the canonical case: the employer's bank debits the employer and credits each employee's account. A credit is a push the originator controls.
An ACH debit pulls money in. A utility that bills your account, a lender collecting a loan payment, a SaaS vendor charging a subscription: these are pulls. The originator reaches into the receiver's account under a standing authorization.
The risk profile is not symmetric. A debit pulls funds the originator does not yet hold, which is exactly why the return rules are strictest for unauthorized debits.
Batch windows and settlement timing
Standard ACH is not instant. The ODFI collects entries, batches them, and submits files against the operator's processing schedule. Traditional next-day ACH settles one or two banking days after submission. That lag is a feature of the design, not a defect.
Same Day ACH adds three same-day windows on top, run by the operators. The submission deadlines and settlement times, in Eastern, are:
- First window: submit by 10:30 a.m., settle at 1:00 p.m.
- Second window: submit by 2:45 p.m., settle at 5:00 p.m.
- Third window: submit by 4:45 p.m., settle at 6:00 p.m.
Even "same day" is batched. You do not get instant settlement. You get faster batches with intraday settlement points. The per-entry limit for Same Day ACH is $1 million, rising to $10 million in September 2027.
Settlement itself happens on the operators' books and, ultimately, across Federal Reserve accounts. The receiver's bank may make funds available on its own schedule, which is why a customer can see a deposit before final settlement has cleared.
The return window is the catch
Here is what separates ACH from a wire and from instant rails. An ACH entry can come back days or weeks after it posted.
Most administrative returns move fast. Codes R01 through R04 and R09 (insufficient funds, account closed, unable to locate, invalid account number, uncollected funds) must be returned within two banking days of the settlement date. These are the routine bounces.
Unauthorized consumer debit returns are the long tail. Codes R05, R07, R10 and R11 carry up to 60 calendar days from settlement. R10 means the receiver says the originator was never authorized to debit the account. R11 means the debit did not match the terms the receiver agreed to. A consumer can dispute a debit two months after it cleared, and the RDFI returns it.
This is why ACH is reversible in a way that finality-focused rails are not. The money posts, but the originator's claim to it is provisional for weeks.
A concrete example
A subscription business runs a $40 monthly debit against 100,000 customers on the 1st. The batch submits, settles, and the cash lands. Looks done.
Over the next two banking days, R01 returns roll in from customers with insufficient funds. Then, across the following 60 days, a thin stream of R10 and R11 returns arrives from customers disputing the charge. Each return claws back $40 plus exposes the originator to Nacha's return-rate thresholds. Unauthorized debit returns must stay under 0.5 percent, measured over the trailing 60 days. Cross that line and the ODFI gets a call, then a remediation plan, then a shutdown.
If your model treats the day-one settlement figure as final revenue, you will misread your own book by exactly the returns you have not received yet.
Why batch survives
Real-time rails exist. ACH still carries the volume. The reason is economics and fit.
ACH is cheap because batching amortizes the cost of processing across millions of entries. A single same-day window clears an enormous file at near-zero marginal cost per payment. Instant rails price each transaction individually and cost more.
ACH is reversible because the return window gives consumers and banks a remedy long after a debit posts. That is a liability on a real-time push rail and a feature on a recurring-debit rail. For payroll, billing, and B2B settlement, nobody needs the money to move in four seconds. They need it to move cheaply, predictably, and with a path to undo a mistake.
Batch is not a legacy compromise waiting to be replaced. It is the right shape for high-volume, scheduled, reversible money.
Takeaway
ACH gives you cheap, reversible, scheduled money at the cost of speed and finality. The ODFI carries the warranty, the batch schedule sets your timing, and the return window (two days for most codes, up to 60 for unauthorized consumer debits) means settlement is provisional long after funds post. Model the returns, not just the day-one deposit, and ACH becomes the most reliable funding rail you have.