Same-day settlement changes what treasury holds

The hidden balance sheet of slow rails

Look at the balance sheet of a company that pays out in many markets and you will find a set of accounts that exist for one reason: the rails are slow. Each corridor gets a local balance sized not for an average week but for a bad one — a payout spike, a banking holiday on either end, a wire that takes an extra day to arrive. That is safety stock, the same logic a warehouse uses, applied to cash. The longer and less predictable the resupply time, the bigger the stock you hold.

The cost is not only the idle cash. Multi-day settlement means the consolidated position is always partly fiction: some of the money is in flight, and nobody can say precisely where it is or when it lands. So treasury builds process around the uncertainty — funding runs scheduled days ahead of need, forecasts maintained per corridor, reconciliation that trails the payments it describes. A meaningful share of the treasury calendar is spent estimating the location of the company's own money.

A pre-funded buffer is a forecast you were forced to fund.

None of this is a failure of discipline. Given rails that take days and can still surprise you afterward, pre-positioning is the correct answer. The buffers are rational. They are just rational responses to a constraint that no longer has to hold.

Finality is the load-bearing property

Same-day is not the property that lets the buffers shrink. Final is. A payment that arrives in hours but can still be recalled or returned leaves the receiving balance conditional — treasury cannot spend against money that might come back, so the buffer stays. What changes the balance sheet is settlement that is both fast and irrevocable: the funds arrive, and the question of whether they arrived is closed the same day.

The case for why finality differs so much across rails — batch windows and return rights on ACH, operating hours on wires, on-chain settlement that is final in minutes at any hour — is made in Settlement finality is a compliance property, and this essay will not re-argue it. The point here is narrower: every operational claim that follows depends on that property. Same-day rails without finality just move the waiting from the transit to the return window.

The treasury workflow on same-day rails

With settlement that completes and closes the same day, corridor funding can follow the payment calendar instead of running ahead of it. The workflow inverts on three fronts.

• Fund on demand. A corridor is funded when there is something to pay, from a central balance, arriving in time to be used that day. The buffer stops being the default and becomes a choice — held where a corridor genuinely warrants one, released where it does not.
• Sweep back. Money that used to sit at the spokes because retrieving it took days can return to the hub as soon as it is idle. Concentration stops being a month-end exercise and becomes continuous, and the centralized balance can sit somewhere deliberate — a Deposit Account rather than a dormant corridor float.
• One view. When transfers are final the day they happen, a real-time consolidated position is trustworthy, not aspirational. The spreadsheet assembled from yesterday's statements gives way to a ledger that is simply current — which is the foundation global treasury management on Infinite (infinite.net) is built on.

Treasury stops forecasting where the money will be and starts deciding where it should be.

The skill mix shifts with the workflow. Forecasting float — predicting arrival times, padding for variance, reconciling the misses — recedes. Managing balances — deciding what each corridor should hold, what the idle position should earn, when to rebalance — takes its place. That is a better job, and a smaller one.

What to check before relying on it

Shrinking a buffer is a one-way decision in the short term: if the rail disappoints, the payout misses. Before treating same-day settlement as a planning assumption rather than a happy surprise, verify four things about the specific path a payment takes, not the rail's headline claim.

• Cutoffs. A stablecoin transfer settles at any hour, but a leg that touches banking rails — funding the transfer, or converting it to local currency on arrival — inherits that leg's business hours and cutoff times. The end-to-end window is set by the slowest leg.
• Redemption. Same-day is only real if the receiving side can convert to spendable local currency on the same clock. Confirm how the off-ramp works in each corridor, and what its own settlement timing looks like.
• Finality in practice. Ask what can still reverse the payment after it settles — and who bears it if something does. A rail that is final on paper but disputed in practice has not earned the smaller buffer.
• Reporting. Just-in-time funding runs on records that arrive with the payment, not after it. Confirm that every transfer produces a settlement record complete enough for reconciliation to close the same day the money moves — the mechanics are walked through in our stablecoin settlement guide.

Where those checks pass, the buffers become what they always should have been: a decision, sized against real risk, instead of an artifact of transit time. The cash that slow rails held hostage goes back to being cash.

Frequently asked questions