# Why international wire transfers take so long What actually happens inside an international wire, why it passes through several banks, and why the money takes days to arrive. --- ## Why international wire transfers take so long When a deal closes across borders — a commercial property sale, an M&A transaction, a cross-border advisory — the wire goes out and then the waiting begins. One business day passes, then two, then someone calls asking why the funds haven't landed. The honest answer requires understanding what actually happens inside an international wire from the moment it's initiated to the moment it's credited, because the mechanics are far more layered than the phrase "wire transfer" suggests. This article breaks down every stage of that journey: the correspondent banking chain, the nostro and vostro account system that underlies it, the compliance stops built into every hop, and the structural reasons why time zones, cut-off windows, and banking calendars can turn a three-day transfer into a seven-day one. If you're coordinating disbursements on a deal, understanding this is not optional. ## What SWIFT actually is — and what it isn't Almost every international wire runs over the SWIFT network, but the most important thing to understand about SWIFT is what it does not do. The SWIFT network serves as the main communication system for international wire instructions. SWIFT doesn't move money itself — it sends secure payment messages between banks. A common misconception is that SWIFT moves money directly from one bank account to another. In reality, SWIFT moves messages — and the actual settlement of funds happens through a parallel system of pre-funded correspondent banking relationships. That distinction sits at the core of why international wires take as long as they do. When you initiate a wire, your bank sends an instruction — typically a standardized MT103 message — telling the receiving institution to credit a beneficiary's account. SWIFT itself does not move money; it transmits standardised messages between banks. In essence, a SWIFT transfer involves a sending bank issuing a payment order to a receiving bank where the intended recipient's account is located. The actual value — the money — moves separately, through a web of pre-existing account relationships that banks have established with one another over decades. Understanding that web is the key to understanding the delays. ## The correspondent banking chain Most banks do not hold direct bilateral accounts with every other bank in the world. Instead, they maintain accounts at a small number of large international banks — known as correspondent banks — that act as intermediaries. Think of it as the difference between a direct flight and a connecting itinerary. Some payments go through intermediaries — also known as corresponding banks — almost like taking a series of connecting flights to arrive at your destination. When a sending bank and a receiving bank have a direct relationship, the wire is relatively straightforward. When they don't, the payment routes through one or more correspondent banks — third-party institutions that handle the settlement on their behalf. Instructions for the transfer are normally moved through the SWIFT network, passing through even up to three intermediary or correspondent banks before finally landing at the final destination. Each of those stops is not a passive relay — it's an institution that receives the message, processes it, runs its own checks, and then passes it forward. They may pass through one or more intermediary banks, each of which adds its own processing time. If an intermediary bank flags the transaction for a compliance review or encounters a technical issue, the delay compounds. What makes this particularly opaque from the sender's side is that if an intermediary bank flags the transaction for a compliance review or encounters a technical issue, the delay compounds, and you typically have no visibility into these intermediary steps unless you request a trace from your bank. A useful way to think about the scale: a single payment from the US to Brazil might pass through two or three correspondent banks before reaching the beneficiary, with each hop adding cost and latency. Multiply that by a transaction that crosses an additional currency zone or routes through a less-developed banking corridor, and the chain grows longer. ## Nostro and vostro accounts: the actual plumbing Behind the SWIFT messaging layer sits a system of pre-funded accounts that is, in many ways, the true engine of international settlement. Every international wire transfer passes through accounts most people have never heard of. Nostro and vostro are two names for the same type of correspondent bank account viewed from opposite sides. The terms come from Italian ("ours" and "yours") and date back to medieval merchant banking. They help banks hold and move money in foreign currencies, which makes international payments possible even when two banks don't have a direct relationship in the same country. Here is how the settlement actually works: when a UK bank sends a SWIFT payment to a bank in Mexico, each institution in the chain holds pre-funded accounts at the next bank in the sequence — known as nostro accounts (accounts held abroad, in the other bank's currency) and vostro accounts (accounts held for foreign banks on your behalf). Each correspondent bank debits the sending institution's nostro account and credits the next bank's account in the chain. The final bank in the chain credits the beneficiary's account. The key word is "pre-funded." These accounts must already hold sufficient balances to facilitate settlement. Funds must be available in the recipient bank's nostro account — this can be immediate if pre-funded, or take longer if funds need to be moved. Settlement between correspondent banks happens through nostro/vostro account reconciliation, which may occur on a different timeline than the payment message itself. That gap — between when the message arrives and when the account entries are reconciled — is one of the least-appreciated sources of delay in cross-border payments. A wire can appear "sent" on the originating bank's records while the recipient is still waiting because a wire can appear "sent" from the originating bank's records while still being unresolved from the recipient's perspective. The funds are somewhere in the correspondent chain, but the ledger entries haven't caught up across all institutions in the sequence. This reconciliation lag is structural. It is not a malfunction. It is how the correspondent banking system has always operated, and it is not going away any time soon. ## Compliance screening at every stop Every institution in the correspondent chain is independently obligated to screen the payment under its own jurisdiction's rules. This is not a formality — it is a serious regulatory requirement that each bank enforces for its own legal protection. At each stop, the receiving institution runs the payment through anti-money laundering (AML) and sanctions screening. Any mismatch or flag can trigger a hold. For large, structured deal transactions — the kind that professionals in this space typically move — the combination of deal size, multiple beneficiaries, and sometimes unfamiliar remitting entities increases the likelihood of a closer look at any one of those stops. To minimize the risk of fraudulent transactions, banks and financial institutions have security measures in place that can delay transfer times. Know Your Customer (KYC) verifies the sender's and recipient's identities. Transactions are also monitored under Anti-Money Laundering (AML) policies for unusual or suspicious activity. Banks additionally screen both the sender and recipient against government sanctions lists and watchlists before processing the transfer. The practical implication: even a wire that is completely clean — correct beneficiary details, no sanctions exposure, fully documented — can still sit in a compliance queue at a correspondent institution for hours or a full business day. That bank has no obligation to process your payment on your timeline. It processes payments on its own schedule, according to its own risk framework, staffing levels, and cut-off windows. You are not its customer. You have no direct line to its wire desk. This is the correspondent chain's central structural vulnerability from the perspective of a dealmaker trying to close on time: your payment is in the hands of institutions that have no direct relationship with you and no particular incentive to prioritize your transaction. ## Cut-off times and the compounding effect of time zones Every bank has a daily processing deadline — the latest time a transfer can be submitted and still be processed that day. Submit after the cut-off, and the payment waits until the next business day. Cut-off times vary by bank and transfer type, typically falling between 2 pm and 5 pm local time. For international wires, they're often earlier than domestic ones. This matters more than most people appreciate, because the cut-off time represents the "point of no return" for a bank's daily ledger processing. A bank being "open" differs from its "wire desk" being active; many branches stay open until 6:00 pm but process international wires only until 2:00 pm or 3:00 pm. Now layer time zones on top of that. A payment initiated in the US afternoon is already after-hours in Europe or Asia, automatically triggering a value date of the following day. If that payment then routes through a correspondent bank in a second time zone before reaching the recipient's bank in a third, each leg of the journey has its own cut-off to clear. Miss one, and the payment sits overnight — effectively burning a full calendar day without moving forward in any meaningful sense. The Friday problem compounds all of this. Banks don't process SWIFT transfers on weekends or public holidays. A transfer sent on Friday afternoon may not actually begin moving until Monday morning, which means two days have effectively been added to the total travel time. For deals that close late in the week, this is not an abstract concern — it is a predictable cost of the system. A wire initiated Friday at 3:00 pm Eastern time may not be processed at the sending bank until Monday, routed to the correspondent bank Tuesday, and credited to the recipient Wednesday. That is five calendar days for a wire that feels like it should have been same-day. Banks typically do not process transfers on public holidays in either the sending or receiving country, and some banks observe additional bank holidays that can further impact processing times. On transactions moving between North America and the Middle East, or between Europe and parts of Asia, the mismatch in holiday calendars is a real operational hazard. The weekend isn't the same all over the world — in many Middle Eastern countries like Egypt, the weekend falls on Friday and Saturday, which means that a wire heading into or through that region can lose days simply because the banking week is structured differently. ## How the currency conversion layer adds time If the wire involves a currency conversion — and on most cross-border transactions it does — that introduces another structural delay entirely. Currency conversion typically cannot happen instantaneously within the correspondent chain. It requires involvement from the sending bank's or an intermediary's foreign exchange desk, which operates on its own schedule and cut-off windows. Banks often have earlier cut-off times for the "FX desk" compared to the wire desk, meaning a transfer requiring currency exchange may be delayed until the foreign market reopens. That means a wire that misses the FX desk cut-off on Tuesday may not even begin conversion until Wednesday morning — adding a day to the timeline before the converted funds are available to move forward through the correspondent chain. The liquidity of the currency pair matters significantly here. Converting from one currency to another adds meaningful time to an international transfer. Not all currencies are equally liquid — less frequently traded pairs require more steps, more counterparties, and more time to settle. A USD-to-EUR transfer on a major corridor between two well-connected banks moves faster not just because the banks are sophisticated, but because the currency pair itself is deeply liquid, with more correspondent institutions prepared to handle it. Currency conversion can add one or more days to the processing timeline, and longer if the currencies involved are less commonly traded. In practice, on uncommon corridors — Central Asian currencies, parts of sub-Saharan Africa, certain Latin American markets — the conversion chain can require two or three intermediary steps of its own, entirely separate from the payment routing. ## Why the receiving bank is often the last bottleneck There is a tendency, when waiting for an international wire, to focus on the sending side — did the bank process it, did the SWIFT message go out, can we get an MT103? Those are valid concerns. But 80% of delays happen in the recipient's bank, which is a figure that surprises most people when they first encounter it. Once the funds arrive at the recipient's bank, there can still be processing time on that end of the transfer that holds things up. That means it can take even longer for the transfer amount to actually appear as usable funds in the recipient's bank account — even if the money's already there. The receiving bank needs to match the incoming payment instruction against the beneficiary's account, run its own compliance checks, and reconcile the incoming settlement against its own nostro accounts. Even if the sending bank processes the transfer quickly, the recipient bank may have longer processing times before crediting the funds to the account. This is particularly relevant when the beneficiary account is at a smaller or less technologically sophisticated institution. The technological sophistication of the banks involved influences processing time. Advanced banking systems with automated workflows streamline the process, whereas institutions in regions with less developed infrastructure may rely on manual systems, adding delays. In deal contexts where one of the beneficiaries — a local counsel, a regional agent, an advisor in a smaller market — banks at a regional institution, that final credit step can add a day or more after the rest of the chain has settled. ## When correspondent chains fail silently The most stressful scenario for any deal professional is not a wire that fails with an error — it's a wire that disappears into silence. The funds leave the sending bank, the MT103 is confirmed, and then nothing. No credit. No rejection notice. No update. This happens because even a small error, like a typo in the SWIFT code or mismatched beneficiary name, can delay the entire chain. And unlike local transfers, there's no single system managing this from start to end. SWIFT is just a messaging system, not a clearinghouse. When a payment stalls or is returned at a correspondent bank, the sending bank may not receive notification for 24 to 48 hours, and the notification, when it comes, often contains limited information about what triggered the hold. Even a minor typo in recipient information can cause the transfer to bounce back, requiring the sender to reinitiate it with corrected details. If the account number, SWIFT code, or International Bank Account Number (IBAN) is incorrect, the transfer will likely be rejected or rerouted and require manual intervention. SWIFT GPI — the Global Payments Innovation overlay introduced to address precisely this opacity — has improved the situation meaningfully for member institutions. SWIFT gpi is the most significant enhancement to cross-border payments in a generation. It addresses three long-standing weaknesses of traditional SWIFT payments: lack of transparency, unpredictable settlement times, and difficulty tracing in-flight payments. A unique end-to-end transaction reference (UETR) is assigned to every gpi payment, enabling real-time tracking at every point in the correspondent chain. You can ask your bank for the SWIFT GPI tracker reference — also called the UETR (Unique End-to-End Transaction Reference). This number lets your bank trace exactly where the payment is in the SWIFT chain. Not every bank across every corridor participates in GPI at the same level of sophistication, but for major currency corridors between developed banking systems, the GPI tracker has substantially reduced the black-box problem. ## What GPI changes — and what it doesn't The picture has improved. SWIFT gpi has transformed the settlement landscape: 75% of gpi-enabled payments reach the beneficiary bank within 10 minutes, and 90% settle within 24 hours — on the corridors and between the institutions where gpi is fully implemented. As of recent figures, over 4,000 banks are live on gpi, and 50% of gpi payments are credited within 30 minutes. But GPI is not universal. It accelerates and makes visible the movement through the correspondent chain — it does not eliminate the chain. The nostro/vostro settlement layer is still there. The compliance screening is still there. The cut-off windows at each institution are still there. GPI improves tracking and has pushed institutions to process faster because they are now on the record at each hop. It does not change the fundamental architecture of how international settlement works. SWIFT GPI's payment tracker has reduced opacity at the bank level by giving each payment a UETR, but the underlying double-bookkeeping that nostro and vostro accounts represent still creates timing gaps that have to be reconciled. For deals running through the major USD, EUR, GBP, and CHF corridors between well-capitalized banks, the GPI era has largely delivered on its promise. For transactions that touch smaller currencies, emerging market corridors, or regional institutions that have adopted GPI in name but not in full operational practice, the traditional delays remain very much alive. ## The practical reality for deal professionals When you are managing the disbursement side of a closing, the latency in international wires is not a random occurrence — it is a predictable output of a specific set of structural conditions. The length of the correspondent chain for your specific sending-bank-to-receiving-bank pair. The cut-off windows in each relevant time zone. Whether currency conversion is required and how liquid the pair is. Whether either bank or any correspondent in the chain has any reason to flag the transaction for a closer look. Whether the receiving bank is a large institution with automated incoming wire processing or a smaller institution that batches its posting at the end of the business day. None of these factors are within your control once the wire is in motion. What is within your control is how you structure the disbursement before it goes out. Clean beneficiary details — verified SWIFT codes, confirmed account numbers, correctly spelled beneficiary names that match exactly what the receiving bank has on file — eliminate an entire class of avoidable delays. Timing initiation early in the week and early in the business day, accounting for the recipient bank's local time zone, removes the cut-off risk. For transactions that require currency conversion, confirming that the FX desk at the sending institution can handle the conversion before the wire desk cut-off prevents a day from being lost at the very first step. When multiple parties are receiving proceeds from the same closing — a structure that is common in commercial real estate, M&A advisory, and complex structured deals — the traditional approach of sending sequential wires multiplies every one of these latency risks. Each wire travels its own path through the correspondent chain, clears its own compliance gates, and lands on its own timeline. That is where tools built specifically for multi-party disbursement add real operational value. When a deal involves proceeds being split among parties across different jurisdictions, Shaka handles the routing logic in a single transaction — the professional closes the deal, and Shaka determines how the money lands, eliminating the need to initiate separate wires and track each one through its own correspondent journey. The international wire system is not broken. It is doing exactly what it was designed to do — moving large sums of money across sovereign banking systems with full compliance screening and settlement finality at every step. The delays are the cost of that architecture. Understanding them in detail is what separates a professional who sets realistic closing expectations and structures disbursements cleanly from one who is still on the phone with their bank's wire desk at 4:45 pm on a Friday, wondering where the money went.