Corridor latency is not a fixed property of a payment rail. It is a function of where in the settlement chain a payment lands, what time of day it is submitted relative to system cut-offs, and how many intermediary institutions handle it. Published SLAs from correspondent banks and payment networks describe best-case conditions. What treasury teams actually experience varies by corridor, by time zone, and by the specific correspondent chain in use. This piece sets out the latency factors we watch on the corridors most common to our users, and how we frame them for treasury planning purposes. None of these figures are presented as measured performance by Birch Hill; they reflect published network behavior and industry-observed ranges from publicly available data.
USD-EUR: The Benchmark Corridor
The USD-EUR corridor is the highest-volume cross-currency corridor globally and has the most developed infrastructure. A payment routed via SWIFT gpi from a US sender to a EUR-denominated beneficiary in the Eurozone typically reaches the beneficiary bank within four hours during business day overlap between Eastern US time and Central European time. gpi tracker data published by SWIFT shows that over 40% of gpi-enabled payments in major corridors settle within five minutes. USD-EUR during the overlap window is among the fastest.
The constraint shifts when payments are submitted outside the TARGET2 operating window (07:00 to 18:00 CET). A USD wire instruction submitted at 17:00 New York time arrives at the EUR correspondent after TARGET2 has closed for the day. Settlement queues until the next operating day. This is not a failure. It is an expected behavior of the RTGS settlement model. Treasury teams that need to make same-day EUR payments must submit instructions by approximately 13:00 to 14:00 Eastern time to allow correspondent processing time before the CET cut-off.
EBA STEP2 provides an alternative for non-urgent payments. STEP2 processes multiple cycles per day and extends the EUR settlement window beyond the T2 18:00 cut-off for lower-value flows. But STEP2 settlement is not RTGS; it is multilateral net, and the finality timing depends on which cycle the payment catches. A treasury team routing a EUR 500,000 supplier payment should not assume STEP2 timing without confirming which cycle applies.
USD-MXN: SPEI and the Pre-Convert Step
The USD-MXN corridor introduces a pre-convert step not present in USD-EUR. USD arrives at the Mexican correspondent, converts to MXN at the interbank FX rate, and then settles via SPEI to the beneficiary. SPEI itself operates from approximately 06:00 to 17:30 Mexico City time (Central time), Monday through Friday, with settlement near real-time during operating hours.
Industry-observed latency for USD-MXN from instruction to SPEI credit is typically two to four hours for morning submissions. Late-day submissions that arrive after SPEI's operational cut-off queue for next-day settlement. The FX conversion step is where the most variability occurs, because the rate applied depends on when the conversion is executed at the Mexican correspondent, not when the instruction was submitted. For treasury teams that need rate certainty, the timing of the FX conversion step matters as much as the settlement cut-off.
USD-BRL: The BACEN Registration Effect
As covered in our Latin America regulatory piece, Brazil's USD-BRL corridor carries a SISBACEN registration requirement on the FX contract. This adds an additional processing step at the Brazilian bank that receives the USD. The net effect on observed settlement latency is an additional one to two business days compared to corridors without a mandatory registration step. USD wires submitted Monday morning will typically result in BRL credit on Wednesday, assuming no documentation queries from the beneficiary's bank.
Corridors with mandatory FX registration are not slower due to technical limitations. They are slower because the regulatory requirement imposes a manual or semi-automated step before credit can be released. Treasury teams planning BRL disbursements should model T+2 from the USD instruction date as the conservative planning horizon, not the T+1 that applies to simpler corridors.
USD-GBP: CHAPS and FPS
GBP settlement for high-value payments uses CHAPS (Clearing House Automated Payment System), which is the Bank of England's RTGS system. CHAPS operates during UK business hours, Monday through Friday, with settlement finality during the operating window. Same-day GBP settlement for USD originations is achievable if the instruction reaches the UK correspondent before approximately 14:00 UK time. Beyond that, the payment settles next business day.
The Faster Payments Service (FPS) handles lower-value GBP transfers, up to GBP 1 million per transaction for most participants, with near-continuous availability. FPS is available 24 hours but is limited by the sterling amount cap, which constrains its use for large intercompany transfers. For most corporate treasury cross-border payments, CHAPS is the relevant rail for GBP, and the CHAPS operating window is the determinant of same-day finality.
Key Variables That Affect Any Corridor
Three variables shift latency regardless of the corridor:
- Submission time vs. local cut-off: Every settlement system has a daily cut-off. Missing it by minutes adds a full business day. Treasury teams should track local cut-offs for each active corridor, not just the nominal SWIFT instruction deadline at their home bank.
- Number of hops: SWIFT MT payments that traverse two or more intermediate banks add processing time at each hop and add the risk that one intermediary takes charges, reducing the net credited amount and triggering a reconciliation break.
- Weekends and holidays: Most RTGS systems do not operate on weekends or local public holidays. A payment submitted Thursday afternoon for a EUR beneficiary in Germany will not settle until at least the following Monday if Friday is a German public holiday. Holiday calendars for each corridor, not just the US banking calendar, matter for value dating.
We are not saying that correspondent banking is too slow for corporate treasury needs across the board. For the majority of routine supplier payments and intercompany transfers, T+1 or T+2 settlement is operationally fine. The latency question becomes critical for same-day funding obligations, FX hedge settlements, and any payment where a missed cut-off creates a material financial impact. For those transactions, knowing the specific corridor timing model in advance, before the instruction is submitted, is what allows treasury to plan rather than react.