Settlement Timing · Free calculator

Settlement Time Estimator

International payments do not have a speed — they have an itinerary. A cross-border transfer’s arrival time is the sum of identifiable legs: whether you caught the day’s cutoff, how many correspondent banks the route passes through, how the destination country’s clearing works, and whether a weekend or holiday sits in the path. Each leg is estimable; "3–5 business days" is what providers say when they have not decomposed the route.

This calculator builds an itinerary from your route’s components: cutoff status, correspondent hops, destination clearing days and non-business days in the window. The output is an estimated settlement time and the fastest plausible case — useful both for setting expectations and for diagnosing which leg of a slow route deserves fixing.

Quick answer

Settlement time ≈ cutoff delay + (hops × processing time per hop) + destination clearing + weekend/holiday days. A wire with 2 correspondent hops (½ day each), 1 day of destination clearing, a missed cutoff and a weekend in the window takes ≈ 5 calendar days. Fewer hops is the biggest lever: direct routes routinely settle days faster than three-correspondent chains.

Interactive estimate

In-flight (correspondent legs)2 hops × 0.50 days
1.0 days
Estimated settlement time
5.0 days
Fastest plausible (cutoff made, no weekend)
2.0 days
Calendar consumed by cutoff + weekend
3 days

Estimates only, based entirely on the assumptions you enter. This is not a quote or an offer — actual pricing is route-dependent and depends on corridor, payment method, amount and applicable fees, and is disclosed in full on a KeyBS Pay quote before you approve anything.

Get a Business Quote

The formula

Days = Cutoff + (Hops × Days/hop) + Destination clearing + Non-business days

Each correspondent hop is a bank applying its own compliance screening, batch schedule and cutoff to your payment. Half a business day per hop is a workable planning figure for clean payments; any hop can stretch to days if the payment is queued for manual review — which is why the estimate is a plan, not a promise.

The non-business-day input matters twice: origin and destination weekends differ (some markets close Friday, others Saturday–Sunday), and a payment arriving at a correspondent on its weekend waits until it reopens. Same-currency, same-region payments over instant rails avoid the whole itinerary — which is the structural argument for routing over rails rather than chains where available.

How to use this calculator

  1. 1

    Check the cutoff

    Every sending institution has a daily cutoff for same-day processing. Initiating after it adds a full day before the payment even departs.

  2. 2

    Count the correspondents

    Ask your provider how many intermediary banks the route uses, or infer from past payments’ MT103 traces. Direct is fastest; two or more hops is where delays live.

  3. 3

    Add destination clearing

    Local crediting speed varies: instant-rail markets credit in minutes once funds arrive in-country; batch-clearing markets add a day or more.

  4. 4

    Overlay the calendar

    Count weekends and public holidays — in both countries and, for exotic routes, in the correspondent’s country (usually the US for dollar legs).

Why routes differ so much on the same corridor

Two providers sending the same corridor can differ by days because they hold different account relationships. A provider with a direct account at a destination-country bank sends one instruction; one without routes through one, two or three correspondents, each adding processing time and potential review queues. This is invisible at quote time unless you ask — and worth asking, because the slow route usually also carries more deduction risk.

Modern alternatives compress the itinerary structurally. Providers with local payout networks receive your funds domestically and pay out from in-country balances — the international leg becomes internal bookkeeping. Stablecoin settlement replaces the correspondent chain with a blockchain transfer measured in minutes, leaving only the on/off-ramp legs. Both models turn a 5-day itinerary into same-day or next-day on supported corridors.

Planning around the estimate, not on it

Settlement estimates should drive initiation dates, not promises to suppliers. The working discipline: estimate the route, add a buffer of at least one business day for payments that matter (two for first payments to a new beneficiary, which attract extra compliance attention), and initiate against the buffered date. The Value Date Planner on this site runs that back-calculation.

When a payment misses its estimate, the itinerary tells you where to look: a payment that left on time but has not credited is sitting at a correspondent or in destination compliance review — your provider can trace which. Payments with complete, accurate beneficiary details and clear purpose documentation clear review queues dramatically faster, which is the sender’s biggest controllable lever.

Common use cases

Supplier expectation setting

Give suppliers an arrival estimate built from the route, with a buffer, instead of guessing.

Route comparison

Compare providers by itinerary — hops and payout model — not just by quoted fee.

Late payment diagnosis

Identify which leg a delayed payment is most likely stuck at before contacting support.

Cutoff discipline

Quantify what same-day initiation is worth, and build payment runs around cutoffs.

Automate this with the API

Check indicative settlement paths and timing for a corridor in one call.

curl "https://keybs.io/api/v1/tools/settlement?from=GH&to=CN" \
  -H "x-api-key: YOUR_FREE_KEY"
Free Tools API docs and key registration

Frequently asked questions

Why do banks quote "3–5 business days" instead of an exact time?

Because the classical correspondent route has legs the sending bank does not control: intermediary processing, compliance queues and destination clearing. The range covers the plausible outcomes. Decomposing the route as this calculator does gives you a tighter planning estimate than the blanket range.

What makes a payment stop mid-route?

Compliance review is the dominant cause: name mismatches, incomplete beneficiary details, unclear payment purpose, or screening hits that need human review. Each correspondent screens independently, so more hops means more chances to be queued. Complete documentation at initiation is the best prevention.

Are instant international payments real?

On specific corridors, yes — where providers hold local payout capability at the destination or the route runs over connected instant rails. The international "payment" is then a provider-internal transfer plus a domestic instant credit. Availability is corridor- and provider-specific, not universal.

Do weekends at the correspondent matter if both endpoints are open?

Yes. A payment routed through New York for a dollar leg waits if it arrives during a US weekend or holiday, even when both endpoint countries are working. Dollar routes effectively inherit the US banking calendar — worth remembering for Thanksgiving-week and July-4th payments.

Does payment size change settlement speed?

Not mechanically — rails process large and small payments alike. Indirectly, yes: larger payments cross compliance thresholds that trigger review more often, and first-time large payments to new beneficiaries attract the most attention. A test payment followed by the balance is a common de-risking pattern for new supplier relationships.

How does KeyBS Pay report settlement timing?

Each quote shows an estimated settlement window for the specific route before you approve, and payments carry status tracking through execution. Where local payout or stablecoin settlement is available on your corridor, the quote reflects the faster route. Timing estimates are route-dependent, not guarantees.

Replace assumptions with a committed quote

Executable rate, disclosed fee, committed receive amount — before you pay anything.

Request a Quote
Keep exploring

Recommended for you

Ask AI about this page