At 5:00 p.m. Pacific, Toyota Financial's payment system flips same-day payments to 'Pending' — locked, uneditable, and no longer arriving today. That hard wall isn't unique to auto loans; payroll batches hit identical cutoffs, and most treasury teams learn about them the expensive way. The gap between settling by 5pm and slipping to next morning is decided hours earlier, at submission.
Speed on any rail carries a visible price tag. Lyft's Express Pay, a consumer same-day payout option, sets a $5.50 minimum threshold before drivers can tap their earnings instantly — proof that instant money is never free. Corporate rails work the same way: Same-day ACH, RTP, and wires each charge per payment, and each enforces its own cutoff, so the right rail depends on when the file lands and what lateness costs.
Start with the wire — the dumbest, most reliable machine of the three. A wire is a push in its purest form: per the push-versus-pull framing laid out in the Medium explainer "Push vs. Pull Payments," a push carries source, destination, and amount in a single request, so nothing waits on an authorization round-trip. Through Fedwire's gross settlement, each instruction settles individually during operating hours, and finality is effectively immediate once released. The binding constraint is human, not technical: wire desks typically stop accepting outbound traffic well before the network closes, and that internal deadline varies by institution. One 2026 wrinkle — the Federal Reserve has been extending Fedwire toward longer operating sessions, but bank desk hours lag the network's, sometimes by a lot, so verify rather than assume.
How It Works
Same-day ACH is not a faster batch rail; it is the same batch rail with more departure times. Files still aggregate, net, and settle at scheduled intraday windows, and anything missing the last usable window does not fail — it rolls silently into the next business day's cycle. Standard ACH can trail up to 2 days, which is precisely the tail a slipped run falls into. Here is the part worth tattooing on your treasury team: a rejected wire screams; a rolled ACH file says nothing. Silence is how a payroll run slips without anyone noticing until morning.
RTP, operated by The Clearing House, clears and settles continuously rather than in scheduled windows, with per-message finality and richer structured data. It also supports pull flows via request-for-payment, but pulls require the payer to authorize, an extra hop a payroll credit never takes. Payroll is pure push, so RTP's payroll value is its always-on settlement, not its collection features.
This is where the lazy critique — that keeping three rails is wasteful redundancy, the conventional approach burning money on unnecessary steps — deserves to die. As "Behind the ACH's Sizzling Growth" recounts, US bankers once convened to weigh building a faster alternative to ACH and deliberately declined; the cheap batch rail survived by choice, and faster rails were layered on later for jobs batching handles poorly. Each rail earns its slot. Your job is matching each payment's urgency to the rail whose settlement event lands before your bank's internal clock — not deleting steps.
Before your next run, get two answers from your ODFI in writing: the internal file deadline for each rail on a normal business day, and whether a same-day ACH submission after the final window rejects or rolls. Those two answers — not the published schedules — decide whether the last tranche of your run posts by 5pm or becomes tomorrow's problem.
Rail selection for a payroll run is decided by exactly three criteria, and the posted per-payment fee is not one of them. The criteria that actually determine whether funds land by 5pm: effective cutoff alignment, all-in per-item economics scaled by headcount, and loss allocation when settlement slips or a return lands. Miss any of the three and the fee you saved is trivia on the invoice.
| Term | What it mechanically means | Why it decides the 5pm question |
|---|---|---|
| Push payment | Source, destination, and amount travel in one request; no authorization hop | Every payroll credit is a push, so all three rails can carry it |
| Pull payment | Receiver initiates; payer must authorize before funds move | Extra hop — decisive for collections, irrelevant to payroll |
| Batch/net settlement | Nacha-netted ACH items settle together at scheduled windows | Miss the last window and the file rolls — up to 2 days on standard ACH |
| Gross settlement | Each wire or RTP message settles individually | One bad employee record delays one payment, not the whole run |
| Finality | The point after which funds are irrevocable | Immediate on wire/RTP release; reached only at ACH's settlement event |
| Network vs. bank cutoff | The rail's published deadline vs. your ODFI's earlier internal deadline | Your bank's clock governs, and it varies by institution |
| ODFI / RDFI | Originating vs. receiving depository financial institution | Your ODFI's internal schedule, not the network poster, is your real deadline |
Criterion one: two clocks, one binding. Every rail runs two cutoff clocks — the network's and your ODFI's. NACHA publishes the Same-day ACH submission windows; your bank's internal last-submission time typically sits earlier and almost never appears in product literature. Request it in writing from your treasury representative. If payroll approvals routinely land after that internal time, Same-day ACH cannot deliver same-day at any fee. Wire retains late-afternoon submission capacity at most banks, and RTP availability hinges on receiving-bank participation — verify each employee's institution before routing a run through it, because reachability gaps surface at the worst moment, mid-run.
Key Factors to Consider
Criterion two: fee times headcount, plus slip cost. According to the ACH vs SWIFT analysis ("Which Rail Fits Your Business Payments"), the decision should include the cost of a late delivery, not merely the fee. Operationalize that: multiply each rail's per-item fee by headcount, then add the estimated cost of a next-morning slip — employee overdrafts, HR ticket volume, an off-cycle correction run. The rail with the lowest total wins, not the rail with the lowest line item.
Criterion three: who eats the loss. RTP is irrevocable once acknowledged; wire settles finally per transfer; Same-day ACH leaves a return window open over subsequent business days after funds appear delivered. The number that matters is the length of that exposure — ask your ODFI for its return-processing schedule rather than assuming the network maximum, because your bank's window can differ from the theoretical one.
The four numbers for the ledger. First, the ODFI's written cutoff. Second, the all-in per-item fee including exception and return lines — according to the consumer protection in financial services review (prices area), pricing structures commonly bundle base prices, preferential tiers, and price-change risk, so the headline rate understates true per-item cost. Third, headcount, which turns small per-item deltas into material totals. Fourth, the late-delivery cost estimate. According to research on credit repayment decisions, information on long-term consequences is often unavailable for flexible facilities; rail pricing shows the same opacity — the consequence data is not printed anywhere, so you reconstruct it yourself.
One behavioral note worth stealing: according to published active-choice experiments on payment decisions, requiring an explicit selection changed reported choices relative to defaults. Treat rail assignment as a per-run decision, not a standing default. And retire the persistent myth that the cheapest per-payment rail is the correct default — when the cheap rail misses the cutoff, the expensive rail that lands on time is cheaper in total. Run the matrix below against your own fee schedule:
Action for this week: obtain the written ODFI cutoff, pull the exception-fee lines from each rail's current schedule, and reprice your most recent run as fee times headcount plus slip cost. That single reframe — deadline first, fee second — keeps the mosaic of cash settled on time and the payroll conversation boring, which is exactly what you want it to be.
Most blown payroll deadlines are not caused by picking the wrong rail. They are caused by reading one clock and assuming it speaks for everyone. Pitfall one: treating "the cutoff" as a single, universal 5 p.m. Every hop in a payment keeps its own deadline, enforced in its owner's time zone — your bank's submission desk, the network's processing windows, and the one almost nobody maps: the receiver's edit lock, the moment a payment becomes uncorrectable.
| Factor | Number to obtain | Where it lives | Rail favored when binding |
|---|---|---|---|
| Effective cutoff | ODFI's written last-submission time | Cash management agreement | Wire, once the ACH window closes |
| All-in per-item fee | Base plus exception fees, multiplied by headcount | Current fee schedule | Same-day ACH, on routine runs |
| Reachability | Employee-bank RTP participation | Receiving-institution directory | RTP, where the roster is covered |
| Slip cost | Estimated late-delivery cost | HR and operations estimates | Wire or RTP, on hard deadlines |
| Return exposure | Business days until returns close | ODFI return schedule | Wire or RTP, when certainty is priced in |
The clearest public specimen of a receiver-side lock comes from outside payroll entirely. According to Toyota Financial's payment-support documentation, a same-day payment changes to "Pending" at 5:00 p.m. PST, and once it shows Pending, the payment information can no longer be changed. Read that as a treasury document, not a consumer one: the correction window on that payment closes on Pacific Time. A payments lead in New York gets until 8:00 p.m. local to fix a bad routing detail; a teammate in Portland gets exactly 5:00 p.m. Same policy, three hours apart, decided purely by geography.
Common Mistakes
Map that lock against desks planning around a naive "5 p.m. everywhere":
Any desk outside the contiguous zones must recompute from scratch, because offsets to Pacific shift with daylight-saving rules: a Honolulu desk faces that lock in the mid-afternoon, while a San Juan desk gets a 9:00 p.m. reprieve. The winning habit is mechanical — record every external deadline in the enforcing party's zone, convert it once, in writing, and treat the converted time, never the posted one, as your deadline.
Pitfall two: grading the run by the settlement report instead of by employee-visible cash. Settlement is the rail's event; availability is the receiving institution's decision, and the two are not the same event. A faster rail can place good funds in an account within seconds, yet when an employee's account sits behind a payroll-card program or an institution that queues faster payments into its overnight posting cycle — common enough that mixed populations are the norm — the balance moves the next business day. The run passes on paper and still slips past 5 p.m. where it actually matters: the employee's app. The costly version of this mistake is upgrading an entire population to the higher-priced rail because a slice of account types posts late, when segmentation solves it — premium speed only for accounts proven to post in real time, the standard rail for the rest.
| Where the desk sits | When the 5:00 p.m. PST lock lands locally | Slack vs. a "5 p.m." mental model | Operational read |
|---|---|---|---|
| New York (Eastern) | 8:00 p.m. | +3 hours | Full evening to catch and correct errors before the lock |
| Chicago (Central) | 7:00 p.m. | +2 hours | Comfortable, but the buffer shrinks every cycle you don't map it |
| Denver (Mountain) | 6:00 p.m. | +1 hour | Corrections need same-hour turnaround or they die in the lock |
| Los Angeles (Pacific) | 5:00 p.m. | None | The lock coincides exactly with the deadline you planned around |
Both pitfalls share one root: believing the deadline you can see is the deadline that governs. Before the next cycle, ask every receiver one question in writing — "At what local time does an incoming payment become uneditable?" — and sample actual posting timestamps across account types (core bank, credit union, neobank, payroll card) on a live run. That clock map, not the fee schedule, tells you where your real 5 p.m. lives.
The timing tactic is window-stacking. Under Nacha's same-day framework, originating banks get multiple submission windows spread across the business day, which means a file rejected in a morning window can be corrected and resubmitted the same afternoon. Submit in the final window and you have converted every later window from a free retry into a wasted asset. Apply the same discipline to wire: the minute that matters is your bank's posted operations cutoff, which typically sits earlier than the network's technical close and varies by institution — get the exact time from your treasury management representative and hard-code it into the runbook. And remember that The Clearing House's RTP network clears around the clock, so a missed wire cutoff is usually recoverable the same evening; what is not recoverable is discovering that night that your RTP integration has never carried a live payment.
Expect pushback that running one payroll across three rails "wastes money on unnecessary steps." The arithmetic runs the other way. The split costs a handful of per-item fees on the repair tranche; the unified alternative costs a blown cycle — reissued credits, overtime for the finance team, and employees refreshing their banking apps past the 5pm landing benchmark this guide uses throughout. The edge case that makes the barbell non-negotiable is holiday compression: when a bank holiday lands the day after payday, the wire rail loses its next-morning fallback, the RTP backstop shifts from optional to mandatory, and the first ACH window moves from best practice to the only safe slot.
Insider Tactics
Verdict, stated plainly: Same-day ACH wins the bulk leg on cost, wire wins nothing except repairs, RTP wins only the clock, and EFTPS takes the tax leg out of contention altogether. Concrete next pass: confirm your bank's exact wire cutoff minute, identify your first Same-day ACH window, and push one live RTP credit of token size through production before you ever need it in anger — then write the tranche map below into the runbook.
According to "9 Best Apps That Pay You the Same Day," Lyft holds its Express Pay instant payout behind a $5.50 minimum earnings threshold — a useful reminder that even consumer-grade instant rails gate speed behind threshold math. The corporate rails in this guide gate speed the same way, just with bigger gates: per-item pricing shape and window schedules instead of dollar minimums. Put the three side by side and the tracked run's economics separate cleanly.
The posted per-payment fee is the number everyone quotes and the worst possible selector — the Key Factors section already settled that. What the fee actually controls is the invoice, and invoices multiply. Send the several-thousand-credit tranche described in the tactics section by wire and a per-item fee applies once per gross settlement, thousands of times over. Route the identical credits through Same-day ACH and the per-item charge is a small fraction of a wire's, billed inside one batched net file. RTP also prices per item — typically landing between the other two — but confirms each credit in seconds rather than holding it for an afternoon window. Banks publish these shapes unevenly, which is why the honest comparison below is structural, not cents-based.
One status-quo belief dies right here: "Same-day" on the ACH label does not mean instant. That rail moves credits inside scheduled afternoon windows on business days only; miss the last window and the run slips to next morning — precisely the failure this guide tracks. RTP has no window to miss, clearing continuously through weekends and holidays, while Fedwire closes early evening on business days. Speed labels are marketing; window schedules are physics.
| Run tranche | Rail | Trigger | Fee behavior |
|---|---|---|---|
| Bulk net pay | Same-day ACH | First processing window of the day | Per-item fee; typically the cheapest of the three, varies by bank agreement |
| Repair tranche | Wire | Only on a rejected batch, before your bank's posted cutoff | Flat per-transfer charge; IRS guidance flags that bank fees may apply |
| After-cutoff rescue | RTP | Any time, including evenings and holidays | Per-credit fee set by your institution; no cutoff exists |
| Federal tax deposit | EFTPS | Scheduled in advance of payday | Bypasses same-day wire charges on the tax leg |
Comparison
So when does each rail actually win? Match the rail to the tranche's item count, value, and clock position:
Concrete next step: pull two lines from your bank's current fee schedule — per-item wire and per-item Same-day ACH — multiply the wire figure by your headcount, and set it against the ACH batch total. If that spread exceeds what any premium rail would cost you for the year, the small-credit tranche never rides wire again. That single multiplication, refreshed annually, is the entire fee half of this thesis done in ten minutes.
One status-quo belief dies right here: "Same-day" on the ACH label does not mean instant. That rail moves credits inside scheduled afternoon windows on business days only; miss the last window and the run slips to next morning — precisely the failure this guide tracks. RTP has no window to miss, clearing continuously through weekends and holidays, while Fedwire closes early evening on business days. Speed labels are marketing; window schedules are physics.
So when does each rail actually win? Match the rail to the tranche's item count, value, and clock position:
| Situation | Winning rail | Why the math favors it |
|---|---|---|
| Thousands of small employee credits, ordinary payday | Same-day ACH | Per-item cost is a small fraction of wire's and batches into one net file; lands in an afternoon window inside the same business day |
| A handful of high-value credits needed in hands before the 5pm deadline | Wire | Per-item fee is immaterial across few items; earliest same-day finality of the three |
| Submission missed the last ACH window — evening, weekend, or holiday | RTP | The only one of the three running continuously; no window exists to miss |
| Recipient's bank is not reachable on the RTP network | Wire | Reach beats speed; an undeliverable instant payment settles nothing |
| Credit that may need repair or recall after sending | Same-day ACH | Carries a next-business-day return path; wire and RTP are final the moment they confirm |
| Gig-style instant payout programs for flexible workforces | Threshold-gated payout apps | Lyft's Express Pay requires a $5.50 minimum balance per "9 Best Apps That Pay You the Same Day" — thresholds gate every rail, not just corporate ones |
Concrete next step: pull two lines from your bank's current fee schedule — per-item wire and per-item Same-day ACH — multiply the wire figure by your headcount, and set it against the ACH batch total. If that spread exceeds what any premium rail would cost you for the year, the small-credit tranche never rides wire again. That single multiplication, refreshed annually, is the entire fee half of this thesis done in ten minutes.
What to do next
| Step | Action | Why it matters |
|---|---|---|
| 1 | Before noon, pull your own bank's internal wire-release cutoff from your treasury portal or cash-management rep — not the network's published 5 p.m. window. | The architecture that wins is decided by your bank's internal cutoff, a variable most operators never ask about. The gap between settling by 5pm and slipping to next morning is decided hours earlier, at submission. |
| 2 | Run the lateness math on the full payroll run: price the per-payment fee on Same-day ACH, RTP, and wire against what one missed day of payroll costs the business. | Rail-selection guidance says the decision must include the cost of late delivery, not just the sticker fee. Instant settlement is always priced — the real question is whether the fee beats the cost of lateness. |
| 3 | Treat 5:00 p.m. as a hard wall the way Toyota Financial does: file and finalize every edit before the window flips same-day payments to 'Pending'. | At 5:00 p.m. Pacific, Toyota Financial locks payments as 'Pending' — uneditable and no longer arriving today. Miss the wall and the run rides standard ACH's timeline of up to 2 days. |
| 4 | If the same-day window is already missed, do not re-file into standard ACH — push the batch over RTP, which clears continuously, around the clock. | A post-cutoff batch falls back to standard ACH and settles in up to 2 days. RTP clears message by message with no batch clock, so it's the escape hatch when the wall has already passed. |
| 5 | Benchmark your speed premium against Lyft's Express Pay: its $5.50 minimum threshold is what a consumer rail charges drivers for instant access to earnings. | Instant money is never free — consumer rails put an explicit price on speed, and corporate rails price it per payment the same way. Use the $5.50 floor as a sanity check on whether your per-payment fee is market-rate. |
| 6 | Confirm you're choosing between architectures, not speeds: wire settles each payment gross the moment the bank releases it; Same-day ACH still batches and nets; RTP clears continuously. | These are not three speeds of one pipe — they are three architectures. Matching the architecture to when your file lands and what lateness costs is what makes the 5pm settlement routine instead of luck. |
```
Frequently Asked Questions
What actually happens if my payroll batch misses the same-day ACH window?
It does not fail outright — the file rolls silently into the next business day's cycle, falling back to standard ACH settlement that can trail up to 2 days.
Is there any real-world example of instant money having an explicit price?
Lyft's Express Pay same-day payout option carries a $5.50 minimum threshold before drivers can tap their earnings instantly.
When do servicers like Toyota Financial cut off same-day payments?
At 5:00 p.m. Pacific, Toyota Financial flips same-day payments to 'Pending' — locked from further edits and no longer arriving that day.
What are the three criteria that determine whether funds land by 5pm?
Effective cutoff alignment, all-in per-item economics scaled by headcount, and loss allocation when settlement slips or a return lands.
Which rails let me reverse a payment after it appears delivered?
RTP is irrevocable once acknowledged and wire settles finally per transfer, while Same-day ACH leaves a return window open over subsequent business days after funds appear delivered.
Can I trust NACHA's published submission windows as my real deadline?
No — your ODFI's internal last-submission time typically sits earlier than the published windows and almost never appears in product literature, so request it in writing from your treasury representative.
Quick answers
| What are the three criteria that decide rail selection for a $2M payroll run? | Effective cutoff alignment, all-in per-item economics scaled by headcount, and loss allocation when settlement slips or a return lands. |
| What happens to a payroll batch filed after the last usable same-day ACH window? | It does not fail — it rolls silently into the next business day's cycle, falling into standard ACH's timeline of up to 2 days. |
| Is the posted per-payment fee one of the criteria that determines whether funds land by 5pm? | No — the posted per-payment fee is explicitly not one of them; what matters is fee times headcount plus slip cost. |
| Why is RTP's pull capability irrelevant for payroll even though it supports request-for-payment? | Payroll is pure push, while RTP's pull flows require the payer to authorize — an extra hop a payroll credit never takes. |
| What two answers should you get from your ODFI in writing before your next run? | The internal file deadline for each rail on a normal business day, and whether a same-day ACH submission after the final window rejects or rolls. |
Also worth reading: RTP vs ACH 2026 Payouts: Early-Pay Discount Math: RTP vs ACH 2026 Payouts: · DSO in 2026: Same-Day ACH, Rail Routing, and Benchmarks: DSO in 2026: Same-Day ACH,