Settlement timelines are one of those infrastructure details that feel boring until a merchant calls your support team at 8 AM asking why their Thursday service revenue is not in their bank account yet. We have heard this question hundreds of times. The answer is almost always buried in ACH network mechanics that most platform builders never need to think about — until suddenly they do.
This is the practical guide to settlement timing for SMB platforms: how standard ACH works, what same-day ACH actually changes, where instant payout rails fit, and how to choose the right option for your platform and your merchants.
How Standard ACH Settlement Works
The ACH (Automated Clearing House) network is the backbone of US electronic funds transfer. When a merchant on your platform initiates a payout to their business bank account, the transaction moves through the following sequence:
- Your platform (or your embedded finance provider) originates an ACH credit entry via an ODFI (Originating Depository Financial Institution).
- The ODFI submits the entry to an ACH operator — either the Federal Reserve's FedACH or the Electronic Payments Network (EPN) operated by The Clearing House.
- The ACH operator sorts and routes the entry to the merchant's RDFI (Receiving Depository Financial Institution) — their business bank.
- The RDFI posts the credit to the merchant's account and makes it available based on their own funds availability policy.
Standard ACH batches are processed three times daily. For a debit or credit entry submitted before the 5 PM Eastern cut-off on a business day, the receiving bank typically posts the credit the following business day (T+1). In practice, many banks make the funds available overnight, so a payment submitted Monday afternoon might be accessible Tuesday morning. But "might" is doing a lot of work in that sentence — the actual availability depends on the RDFI's policy, whether the entry was flagged for additional review, and whether there are any holiday processing schedules in effect.
For a restaurant operator waiting on Tuesday's dinner service to hit their account before Wednesday morning payroll, a T+1 cycle that actually delivers on Thursday due to a processing queue delay is not a minor inconvenience. It is a payroll problem.
Same-Day ACH: What It Buys You
NACHA expanded same-day ACH processing significantly between 2016 and 2021. As of March 2021, same-day ACH handles transactions up to $1,000,000 per entry — up from the original $25,000 cap — and covers both credits and debits.
Same-day ACH adds two additional processing windows to the standard schedule: a morning window (with funds typically available by early afternoon) and a midday window (with funds typically available by end of day). For a merchant submitting a payout before 10:30 AM Eastern, funds can be available at the receiving bank by approximately 1:00 PM. For a payout submitted before 2:45 PM Eastern, funds are typically available by end of business.
The fee premium for same-day ACH is real but modest — NACHA assessed a 4.5 cents-per-entry surcharge for same-day processing through 2023, and ODFI pricing to platforms typically adds a further 5-15 cents per entry depending on volume. For a platform processing 5,000 payouts per month, upgrading to same-day adds roughly $50-$100 per month in origination costs. For most platforms, this is absorbed rather than passed through to merchants — the retention value exceeds the fee impact.
Instant Payouts: A Different Rail
Same-day ACH and instant payouts are different products. Instant payouts — where funds are available in seconds rather than hours — run over card networks (push-to-debit via Visa Direct or Mastercard Send) or over real-time payment rails like RTP (The Clearing House's Real-Time Payments network) or FedNow.
Here is a comparison across the main options:
| Rail | Speed | Cost per transaction | Max transaction | Coverage |
|---|---|---|---|---|
| Standard ACH | T+1 to T+2 business days | $0.20-0.30 | $1M (effectively no cap) | All US bank accounts |
| Same-Day ACH | Same business day | $0.45-0.60 | $1M | All US bank accounts |
| RTP (push) | Seconds, 24/7/365 | $0.35-0.60 | $1M | ~75% of US DDA accounts (2025) |
| FedNow | Seconds, 24/7/365 | $0.25-0.50 | $500K | Expanding; ~40% of DDA accounts as of early 2025 |
| Visa Direct / MC Send | Seconds to 30 minutes | $0.50-1.50 | $50K-$250K depending on card type | Must have debit card linked to receiving account |
For SMB platforms, the practical recommendation is to offer same-day ACH as the default for standard payouts, with RTP or Visa Direct as an optional "instant" tier that merchants can elect. Most SMB merchants — restaurants, contractors, field-service operators — will find same-day ACH sufficient for daily cash-flow management. A subset with urgent or weekend cash needs will pay a small premium for instant access, particularly if they are holding balances in a platform wallet where you can absorb the instant-payout cost internally.
Return Risk and Merchant Risk Management
ACH returns are an underappreciated source of platform operational complexity. NACHA permits returns for a range of reason codes — insufficient funds, account closed, invalid account number, authorization revoked — and return rates above 15% for debit entries or 3% for credit entries can result in the ODFI flagging your origination activity for review.
For merchant payouts (ACH credits), returns are less frequent than debit-side risks, but they do occur when merchants provide incorrect external account information or when the receiving bank closes the account between submission and settlement. Handling returns gracefully — posting the credit back to the merchant's platform wallet, notifying the merchant, and providing a flow to enter corrected account details — is a support-cost issue as much as a technical one.
We handle return processing as part of the embedded infrastructure, but platform engineers need to build the merchant-notification and account-correction flows. Return reason codes are surfaced via webhook with enough specificity to distinguish "wrong account number" from "account closed" from "insufficient funds" in the RDFI — different communication flows are appropriate for each.
What to Build vs. What to Configure
If you are using an embedded finance provider for your payout infrastructure, most of the NACHA compliance, ODFI connectivity, and return processing is handled at the infrastructure layer. What the platform is responsible for building:
- Merchant-facing payout initiation UI, with clear disclosure of expected settlement timing per rail
- External bank account collection and micro-deposit or instant verification flow (Plaid Link or equivalent)
- Return handling notification logic (webhook → merchant email/in-app notification → re-entry flow)
- Payout scheduling rules — do you want to auto-sweep balances at a certain threshold, or require explicit merchant-initiated payouts?
- FedNow and RTP coverage checks — before attempting an instant payout, your system should verify the receiving account supports the rail, to avoid a failed attempt that delays the merchant further
Settlement mechanics are infrastructure. But the product experience around settlement — clear timing expectations, proactive status updates, graceful return handling — is where platforms differentiate. Merchants do not think about ACH windows. They think about whether the money showed up when they expected it. Build the experience around that expectation, and the underlying plumbing mostly disappears.
