# When Does the Money Actually Arrive? Settlement Cycles, Reserves and Cash Forecasting Across Providers

Canonical URL: https://y.uno/en/blog/when-does-the-money-actually-arrive-settlement-cycles-reserves-and-cash-forecasting-across-provi

> This is the markdown rendition for AI agents. The canonical page is served as HTML at the URL above.

By Yuno · Published 2026-11-04 · Payment strategy

Payment providers hold your funds for days or weeks before they arrive, and every provider does it differently. This piece teaches you to map settlement timing, model reserves, and build a cash forecast that reflects your actual payment stack.

What you will learn: How to map settlement timing per provider and payment method, account for rolling reserves and payout thresholds, model FX conversion timing, and assemble those inputs into a cash forecast that reflects your actual payment stack. Mapping settlement cycles is not an accounting exercise. It is a treasury discipline.
The thesis here is direct: payment providers are part of your treasury whether you manage them that way or not. The moment you run more than one provider, settlement timing becomes a forecasting problem. Each provider deposits on its own schedule, withholds reserves on its own terms, and applies FX at a different moment. Add a second provider and a third rail, and the gap between revenue and available cash widens in ways a single-line "net settlement" entry will never show.

## Key takeaways

- Every provider is a short-term creditor. The money it holds is your working capital, temporarily locked.
- Settlement timing varies by rail, provider, weekend calendar, and reserve policy. Map these explicitly, never assume them.
- Rolling reserves create a receivable outside your bank balance for a provider-defined hold period. It must appear in your forecast, not as a vague deduction.
- FX conversion timing adds a second source of settlement variance on cross-border volume.
- Multi-provider setups require a consolidated settlement view. Without one, reconciliation tells you what happened; forecasting tells you what will happen.

## The mental model in one sentence
Treat every provider's settlement pipeline as a receivable ledger with its own maturity schedule, then sum those ledgers to get your real cash position. This reframe matters because most payment teams manage settlement reactively, checking what arrived rather than projecting what will.
The model comes from treasury practice, specifically the discipline of aging receivables. A sales team maps days-sales-outstanding by customer. A payments team should map days-settlement-outstanding by provider and method. The mechanics are identical. The inputs are just different.

Image: Four stacked inputs build your real cash position. Hypothetical framework; apply your own provider terms. Cash Position: Sum daily expected deposits across all providers. This is the number treasury can act on. FX Layer: Note which provider converts at auth vs. settlement. Flag rate variance as a sensitivity line. Reserve Ledger: Record rate, hold period, and release dates per provider. Project withheld amounts as dated receivables; releases as future inflows. Settlement Cal.: Record base lag, cut-off time, payout frequency, and minimum threshold per provider and rail. Apply the acquiring-country business-day calendar.
Four stacked inputs build your real cash position. Source: Illustrative

## Where the delays actually come from
Settlement delay has three distinct sources: the rail's clearing cycle, the provider's internal funding schedule, and calendar effects. Conflating them makes the forecast wrong in different directions.

### Rail clearing cycles
Different payment rails carry different base settlement timelines. ACH transfers in the United States can settle within one to two business days after initiation, excluding weekends and federal holidays, according to Nacha. The Federal Reserve Board's FedNow Service enables funds transfer in near real-time, any time, any day of the year. For domestic wire transfers, the EFA Act requires funds to be available no later than the business day following receipt, according to Federal Reserve Regulation CC Commentary. International wires add two to five business days, depending on correspondent banking relationships across time zones, according to Visa. Card settlement timelines vary by market and acquiring agreement; verify your specific schedule contractually with each provider.
The practical implication: a business running cards, local bank transfers, and international wires simultaneously receives deposits from the same day's sales across a multi-day window. That spread is not a problem. It is a known, mappable quantity.

### Calendar effects
Business-day schedules compress settlement further. A T+2 card settlement on a Thursday becomes T+4 in calendar days. A Friday sale on an ACH rail clears Monday at the earliest, per Nacha. Public holidays in the acquiring country extend every timeline. Providers in different time zones apply different cut-off times, so a transaction authorised at 23:00 local time may fall into the next business day's batch.
Map these cut-offs per provider. A simple rule: assume the worst-case calendar-day count, then treat anything faster as upside.

### Provider funding schedules
Even after the rail clears, providers apply their own payout schedules. Some fund daily. Others fund weekly or at a minimum balance threshold, holding small amounts until they reach a floor before releasing. That threshold creates a timing mismatch: the rail settled, but the provider has not yet paid out. This is a provider policy, not a network rule, and it varies widely. Verify it contractually for each provider you use.

## Rolling reserves: the receivable you are probably not forecasting
A rolling reserve is a percentage of gross settlement withheld by the provider as a buffer against future chargebacks, released after a contractually defined hold period. It is real money owed to you. It is not in your bank account.
The chargeback window makes this exposure material. According to the American Express Disputes Reference Guide, card members have up to 120 days from the transaction date to dispute a charge. That window is precisely why providers hold reserves: a transaction that settled 90 days ago can still be reversed. The hold period on reserves is typically aligned to or extends beyond that 120-day dispute window (American Express Disputes Reference Guide). Your forecast must carry the withheld reserve as a dated receivable, not as a write-off and not as cash.
Two things make reserve forecasting tractable. First, the reserve rate is contractual and therefore known. Second, the release schedule is fixed. A 5% rolling reserve on a defined hold releases predictably. You can project the release dates from your settlement history and plot them as cash inflows.

## FX conversion timing
When a provider converts currency affects the amount you receive, not just the exchange rate applied. Some providers lock the FX rate at authorisation. Others convert at settlement, one or two days later.
If the currency pair moves between those dates, your deposit changes. This is not purely a risk management question. It is a forecasting input. For cross-border volume, your projection should state: which rate is applied, at which event, and by which provider. Without that, your forecast carries an unacknowledged variable. For more on managing FX exposure across rails, see Reducing FX Costs on Cross-Border Transactions: Routing Between Bank Rails and Stablecoins.

## Worked example: mapping settlement for one sales day across three providers
This example shows how three providers create three distinct deposit events from a single day of sales. The company below is hypothetical. All inputs are stated assumptions. Every derived number is listed in the calculations for this article.
Assumptions: $100,000 gross sales on a single Monday, split 70% card (Provider A, T+2), 20% local APM (Provider B, T+1), and 10% international wire (Provider C, T+3, within Visa's two-to-five-business-day range). Fee rates: Provider A 2.0%, Provider B 1.2%, Provider C 0.5%. Provider A applies a 5% rolling reserve on gross card volume. Providers B and C hold no reserve.
The table below shows each provider's settlement assumptions for that Monday.

| Provider | Rail | Gross ($) | Fee | Net ($) | Reserve ($) | Cash deposited ($) | Deposit day |
| --- | --- | --- | --- | --- | --- | --- | --- |
| Provider A | Card (T+2) | 70,000 | 2.0% | 68,600 | 3,500 | 65,100 | Wednesday |
| Provider B | Local APM (T+1) | 20,000 | 1.2% | 19,760 | 0 | 19,760 | Tuesday |
| Provider C | International wire | 10,000 | 0.5% | 9,950 | 0 | 9,950 | Thursday |

The formulas applied: net settlement equals gross multiplied by one minus the fee rate. Cash deposited equals net settlement minus reserve withheld. For Provider A: $70,000 × 0.98 = $68,600 net; $70,000 × 0.05 = $3,500 reserve; $68,600 minus $3,500 = $65,100 deposited. By end of Tuesday, $19,760 has arrived from Provider B. By end of Wednesday, a further $65,100 arrives from Provider A, bringing the running total to $84,860. Provider C's $9,950 arrives Thursday. Total cash in bank from Monday's $100,000 in sales: $94,810 by Thursday close, four business days after the transaction.
The $3,500 reserve withheld by Provider A is a receivable. At a $3,500 daily reserve on five consecutive business days, the cumulative reserve balance reaches $17,500 before the first release begins. Those funds return on a rolling basis after the contractual hold period.

Image: Monday's $100,000 in sales arrives across four business days. Hypothetical schedule; assumptions stated in worked example. 1. T+0: $70,000 authorised. 2. T+0: $20,000 authorised. 3. T+0: $10,000 authorised. 4. T+1 Tue: $19,760 deposited. 5. T+2 Wed: $65,100 deposited. 6. T+3 Thu: $9,950 deposited.
Monday's $100,000 in sales arrives across four business days. Source: Illustrative

## Building the forecast
A settlement cash forecast is a matrix of sales dates, provider splits, rail timings, and reserve release dates, summed to a daily expected cash position. Build it in three layers.

### Layer one: settlement calendar
For each provider and rail, record the base settlement lag, the cut-off time, the payout frequency, and the minimum threshold. Apply the business-day calendar for the acquiring country. Output: a lookup table that converts any transaction date to an expected deposit date per provider.

### Layer two: reserve ledger
For each provider that withholds reserves, record the rate, the hold period, and the release mechanism. Project withheld amounts forward as dated receivables. Project release dates as dated cash inflows. This layer makes the reserve visible as working capital, not as a vague deduction.

### Layer three: FX adjustment
For cross-border volume, note which provider converts at authorisation versus settlement. Apply a conservative rate assumption for the settlement date. Flag the variance between your assumed rate and the spot rate as a sensitivity line, not as a fixed number.
Stacking these three layers gives a daily cash projection per provider. Sum across providers to get a consolidated position. That consolidated position is the number your treasury team can actually use.

## How Yuno's Reconciliations module supports this
The hardest part of building this forecast manually is that every provider reports in its own format, on its own schedule, with its own fee structure. That fragmentation compounds as your provider count grows.
Yuno, the AI-native intelligence system of global payments and financial services, has processed over one billion payments across 150-plus currencies since January 2025 and operates across 190-plus countries. Its Reconciliations module pulls settlement data from every connected provider into one view, normalises different fee structures, and surfaces discrepancies automatically. For related context on managing cross-border complexity, see how payment orchestration optimises cross-border transactions.
Critically, Yuno stays out of the funds flow entirely. Providers settle directly to the merchant. What Yuno provides is the data layer: a consolidated, accurate record of what each provider settled, when, in what currency, and at what fee. That data is the input your forecast depends on. Without it, you are forecasting from incomplete information. With it, the three-layer model above becomes a live projection rather than a monthly reconstruction.
Merchants running multi-provider stacks across many markets need exactly this kind of unified settlement visibility. McDonald's through Arcos Dorados, for example, operates across 21 countries. Manual reconciliation across that many provider relationships is an error-prone, full-time job. Automated consolidation turns it into a reporting feed.

## Start here
Pull your last 90 days of settlement reports from every active provider. For each one, record: the rail used, the settlement lag in business days, the reserve rate and hold period, the payout threshold, and the FX conversion point.
If any of those fields are blank, that provider is an unquantified variable in your cash position. Contact the provider and get the contractual terms in writing. Once you have those inputs, the forecast builds itself. The mental model is simple: every provider is a debtor with a known payment schedule. Map the schedule. Project the cash. Manage the gap. Payment providers have always been part of your treasury. The only question is whether you are running that position deliberately or by default.