How to avoid SWIFT delays on a large transfer
Brokers, advisors, and closing attorneys who work on international deals know the ritual: the paperwork is signed, the deal is done, and then everyone waits. Somewhere in a correspondent banking chain, a wire carrying seven or eight figures has gone quiet, and no one on the professional side of the table can tell their client exactly why or for how long. The delay is not random — it is systematic, and it is triggered specifically by the size of the transfer. Understanding what activates review, what sustains it, and how to architect the disbursement so that money moves with the same certainty the deal itself carries is the difference between a clean close and a damaging, relationship-eroding wait.
Why large transfers are different from ordinary wires
Most professionals understand that SWIFT is a messaging network, not a bank. SWIFT provides the main messaging network through which international payments are initiated. The organisation does not manage accounts on behalf of individuals or financial institutions, does not hold funds from third parties, and does not perform clearing or settlement functions. The actual movement of money happens through correspondent banking relationships — a separate layer of institutions, each with its own processing windows, compliance obligations, and internal risk appetite.
That distinction matters enormously once a transfer crosses certain thresholds, because the compliance decision is not made by SWIFT. It is made by each bank in the chain independently and sequentially. AML and sanctions screening occurs at each bank in the chain. High-risk corridors, flagged entities, or large transaction amounts trigger enhanced review, which can pause settlement for 24 to 72 hours.
For a routine transfer — say, a professional fee of $15,000 moving between two banks in major currency corridors — automated screening often passes the payment through without human intervention. But once a transfer starts carrying numbers that look like a property acquisition, a business sale, or a multi-party disbursement at the closing table, the risk profile changes in the eyes of every bank that touches it. The dollar figure itself becomes a flag.
Every international transfer passes through anti-money laundering (AML) and sanctions screening at both the sending bank and the receiving bank. If the transaction triggers a review flag — an unusual amount, a new beneficiary, a high-risk corridor — it can be held for manual review. The key word there is “manual.” An automated pass takes seconds. A manual review takes however long it takes for a compliance officer to reach the queue, request documentation, evaluate it, and sign off. In a busy institution, that can stretch across multiple business days — and each correspondent bank in a multi-hop chain may repeat the process independently.
The compliance triggers specific to large amounts
Several distinct mechanisms activate when a large transfer enters the SWIFT network.
The reporting threshold effect
Transfers over $10,000 are automatically reported to the government by the financial institution. That reporting requirement — the Bank Secrecy Act’s Currency Transaction Report equivalent for wire transfers — does not delay the payment by itself. But it creates an administrative record, and that record means every institution in the chain has heightened motivation to ensure the transaction is clean before it passes on. The institutional exposure for letting a suspicious high-value wire through is significant. Banks are not wrong to be careful; the problem is that careful looks identical to stalled from the outside.
The review process is not arbitrary. Banks operate under strict regulatory obligations and can face significant penalties for non-compliance. But for the sender, a compliance hold looks identical to a technical delay.
The “unusual amount” flag
Banks screen for transactions that fall outside the ordinary pattern of an account or a customer relationship. Large transaction values that differ from your usual payment pattern, and vague or missing purpose-of-payment information, will cause a bank to raise a Request for Information (RFI). The payment will not move forward until the required clarification or documents are provided. Delays often increase when responses are slow or incomplete.
A broker whose account normally handles transactions in the tens of thousands sending a single wire in the millions triggers exactly this pattern-deviation alert. The bank has no prior context for a transfer of that scale from that account. Without pre-established context, the wire parks.
The new beneficiary problem
To prevent money laundering, terrorism financing, and other financial crimes, all SWIFT transfers go through compliance and KYC/AML checks. Banks screen transactions against international sanctions lists and regulatory databases. If a payment raises a “red flag” due to a name, country, or transaction amount, it will be manually held for investigation.
In a deal environment, beneficiaries are often new: the seller’s attorney in a different jurisdiction, a foreign advisor entity, a split to multiple recipients who have no prior relationship with the sending institution. Each new beneficiary in a large-amount wire is a separate compliance question the bank has to answer before it will release the funds.
The source-of-funds requirement
Banks are subject to strict regulations, and large transactions can sometimes trigger additional compliance checks. These checks may include verifying the source of funds or ensuring compliance with anti-money laundering laws, both of which can extend the time it takes for a wire to go through.
For a deal professional disbursing proceeds — whether from a commercial property sale, a business acquisition, or an investment transaction — the source of funds question is genuinely complex. The money often originated from a lender, passed through a title account or attorney trust account, and is now being split across multiple recipients. Each link in that chain may need to be documented before a correspondent bank will clear the payment.
The correspondent chain multiplier
Large international transfers rarely travel direct. When there is no direct correspondent relationship between the sender’s and recipient’s banks, the payment is processed through one to three intermediaries. Each correspondent bank adds its own checks and cut-off time at each stage. If the payment message arrives after the deadline or the “cut-off,” it will be processed on the next banking day.
This is the compounding problem that catches professionals off guard. A five-day delay is not one five-day review — it is often three separate one-to-two day holds, each at a different institution, sometimes in different time zones, each triggered by the same large-amount flag. Most international SWIFT payments involve at least one intermediary bank, which adds 24 to 48 hours per hop. Each of those hops is an independent compliance decision on the same transaction.
Different time zones overlap, so an extra half a day or a full day is actually added. The number of intermediary banks directly affects both fees and transfer time. A wire from a US-based attorney account to a recipient bank in Southeast Asia or the Middle East may pass through a US correspondent, a regional clearing bank, and then the destination bank — with each institution potentially re-screening the amount independently.
The geography of the destination also matters in ways that are not always predictable. Many countries require supporting documentation for inbound international transfers, particularly above certain thresholds or for business-related payments. Under rules in some jurisdictions, foreign remittances must be classified by purpose, and banks may request additional details to comply with reporting requirements. In parts of Southeast Asia, larger business transfers may also require proof of commercial purpose, such as invoices or contracts. If the required information is not provided upfront, the recipient bank may hold the funds pending compliance review before crediting the account.
What actually creates the hold: anatomy of a stuck large wire
When a large international transfer goes quiet, it is almost always in one of three states.
The first is a compliance hold at the originating bank. This happens before the wire even enters the correspondent chain. The sending bank’s AML system has flagged the amount, the beneficiary, or the combination, and is waiting for a compliance officer to clear the transaction. This is the hold that a well-prepared sender can prevent with the right documentation provided in advance.
The second is a correspondent bank hold mid-chain. The wire has left the originating institution and is sitting at an intermediary. The ACSP status — Accepted, Settlement in Progress — means the payment is valid but waiting in a processing queue, often due to intermediary bank checks or compliance review. From the sender’s side, this looks like the wire simply hasn’t arrived. It has left, it just hasn’t gotten where it needs to go.
The third is a destination bank hold. The funds have arrived at the beneficiary’s institution, but the receiving bank’s own compliance review has not cleared the credit to the account. The recipient’s bank may suspend the transfer for document verification — invoice, contract, agreement — and compliance checks are also possible, including sanctions, blacklists, and AML/KYC screening.
Each state requires a different intervention. The mid-chain hold is the hardest to unstick, because neither the originating bank nor the recipient has control — only the correspondent does. Resolution requires the sender’s bank to engage the correspondent, supply any missing information or documentation, or recall and amend the payment so an alternative route can be used.
The data errors that compound large-amount delays
Large transfers carry more scrutiny, which means data quality matters more than it does for smaller amounts. Small data errors can create big delays. A minor typo in the beneficiary name, account number, or IBAN can stop Straight-Through Processing (STP), which is the automated flow banks rely on for speed. Once STP fails, bank staff must manually review and repair the transaction. This process can add several working days, especially if multiple banks are involved.
For a professional managing a disbursement across multiple recipients — seller proceeds, co-broker splits, attorney fees, advisor compensation — each beneficiary record is an independent data-quality risk. One name mismatch in a set of four wires can hold up all four if they are structured as a single transaction instruction.
The recipient’s full legal name must match exactly what is registered with the recipient’s bank. Mismatches trigger compliance holds. In deal environments, this is a persistent problem: a recipient whose operating entity has a slightly different legal name than the account holder, a law firm whose trust account is registered under a different designation, an advisor who operates under a trade name that doesn’t match their banking relationship.
The answer is not to rush the wire setup at the closing table. It is to collect and verify all beneficiary details days in advance, confirm them against the actual account records, and build the wire instructions from verified information rather than from what a recipient says their details are.
How to structure a large transfer to minimize review
There is a meaningful difference between a large wire that clears in a day and one that parks for a week. The difference is almost always in the preparation upstream of the transfer, not in the transfer itself.
Pre-notify the sending bank
Build a relationship with your bank’s payments team. If you make regular large transfers to the same beneficiaries, let your bank know in advance. This is not a courtesy call — it is a compliance pre-clearance. When the originating bank’s compliance team already has the source of funds, the purpose of payment, and the identity of the beneficiaries on file before the wire is initiated, the automated flag becomes a simple cross-check rather than the opening of a new investigation.
For deal professionals, this means sending the transaction details — the amount, the nature of the transaction, the parties, and the documentation trail — to your bank’s wire or international payments desk at least 48 hours before the closing date. Many banks have a dedicated process for this, and some will issue a pre-clearance confirmation that speeds the wire through their own system on the day of closing.
Load the wire with purpose and documentation
Many jurisdictions require a purpose code describing the nature of the payment — trade payment, service fee, real estate proceeds, and similar categories. Even where a purpose code is not formally required, including one creates machine-readable context that reduces the probability of a manual review at correspondent banks.
The payment reference field is not a formality. It is the only piece of narrative context that travels with the wire through every institution in the chain. A reference that says “REF CLOSING 14072026 – COMMERCIAL PROPERTY PROCEEDS” gives a compliance officer at a correspondent bank something to work with. A blank reference field or an opaque internal reference gives them nothing — and nothing gets flagged.
Prepare a package of documents in advance and include the correct payment designation in English. For transactions moving to jurisdictions that require commercial documentation — contracts, closing statements, proof of transaction — having those documents ready to transmit immediately when a correspondent requests them is the difference between a 24-hour resolution and a week-long one.
Understand cut-off times at every institution in the chain
Submit before cut-off time. Send before your bank’s daily cut-off — typically 3:00–4:00 PM local time — to avoid a full one-business-day delay. For large transactions, this matters more than it does for small ones, because the compliance review that large amounts generate takes time that a late submission simply does not have.
A wire submitted at 3:45 PM for a same-day close may physically leave the originating bank, but the compliance pre-clearance at the correspondent — which closes its processing window at a different time in a different time zone — will not happen until the next business day. In real estate and M&A deal environments where the closing date carries legal significance, a one-day slippage in disbursement settlement is not a minor inconvenience.
If your closing is scheduled around a bank holiday or on a Friday afternoon, there is a higher likelihood that the wire transfer will be delayed. Banks do not process wires on weekends or holidays, which can cause a frustrating wait. For international transfers with multiple correspondent banks across different national calendars, a Friday close can mean a Tuesday or Wednesday settlement, even when every instruction was technically correct.
Choose sending banks with direct correspondent relationships
Transfers between banks with direct correspondent relationships are faster — often same-day or next-day — while those requiring intermediary banks take longer. For a professional handling significant international transactions regularly, the choice of which banking institution you route your professional disbursements through is a strategic decision, not an administrative one. A bank with a direct correspondent relationship to the destination country eliminates one or two hops from the chain, and each eliminated hop is a compliance review that does not happen.
SWIFT GPI still depends on the correspondent banking network, so fees vary and settlement can be delayed outside banking hours. GPI adds tracking visibility and accountability SLAs, but it does not remove the underlying compliance infrastructure. What it does do is give professionals real-time visibility into where in the chain a wire is sitting. SWIFT GPI is the modern standard for tracking international payments with end-to-end visibility. It allows you to see where a transfer is at any point in its journey, rather than waiting blindly for updates. If you or your sending institution is using a GPI-enabled bank, the UETR reference number becomes a diagnostic tool — it tells you whether a delay is at the correspondent, at the destination, or has not yet resolved into a specific bottleneck.
The real estate and deal closing dimension
The large-transfer delay problem has a particular intensity in real estate and deal closings because the wires are not routine business payments. They are often the largest transaction a professional has processed in months, from a trust or attorney account, to a set of beneficiaries with no prior banking relationship to that account, in a single transaction with legal significance attached to the date.
Even on domestic wires, delays can happen due to fraud reviews, large-dollar verification, or bank processing queues. When that same dynamic plays out internationally, across multiple currencies and jurisdictions, the compounding effect is substantial.
For deal professionals structuring multi-party disbursements — commissions split between co-brokers, proceeds split between sellers, advisor fees distributed across multiple advisors at close — the traditional approach is to receive the full proceeds into a single account and then initiate separate wires to each recipient. Each of those secondary wires is its own large-transfer event, its own compliance review, its own potential hold. A six-party disbursement at closing means six separate opportunities for the settlement to stall.
This is precisely the problem that Shaka was built to eliminate. Rather than receiving proceeds and then re-disbursing to each party, a professional sets up a payment link in advance — recipient wallets, split percentages, verified counterparties — and when the deal closes, every party receives their share directly and simultaneously in a single onchain transaction. There is no secondary disbursement queue, no multi-wire compliance gauntlet, no waiting for a trust account to re-send. The professional still owns the structure; the money simply lands where it needs to land, with finality, the moment the deal is done.
When a wire is already stuck: what to do
If a large wire has gone quiet — past the expected settlement window with no confirmation — the clock matters. If a payment stays at ACSP status for longer than one or two working days, contact your bank with the UETR and MT103 instead of waiting. This allows the bank to raise a precise follow-up with the intermediary or beneficiary bank and avoids vague responses.
The MT103 is the payment’s source document — it carries the originator details, beneficiary details, amount, and routing. To track a transaction, you need the UETR, which uniquely follows the payment through the SWIFT system. Enter the UETR in your bank’s SWIFT GPI portal or a trusted public tracker. If you do not have the UETR, ask the sender for the MT103, which contains it.
Armed with the UETR and the MT103, your bank can identify exactly which institution in the chain holds the payment and what is blocking it. Without those references, the most a bank representative can tell you is that the wire “is being processed” — which tells you nothing about what is actually happening or how to resolve it.
The most common resolution actions for a stuck large-value wire are: providing documentation of source of funds directly to the holding institution; clarifying the payment purpose to the correspondent’s compliance desk; and in some cases, amending the wire to correct a data mismatch. If incorrect or incomplete information has been provided — a wrong SWIFT code, account number, or beneficiary name — the payment will be held. The bank will have to investigate the error, or the transfer may be rejected and returned to the sender, which can take days or even weeks.
A return is the worst outcome. A returned large-value wire means re-initiating the full process — with a new compliance review at origination — on a transaction timeline that may already have legal or contractual implications.
The pattern that separates a clean close from a stalled one
Professionals who consistently close international deals without disbursement delays share a common operating pattern: they treat the wire preparation as part of the deal work, not as a post-closing administrative task. They know their bank’s compliance team by name. They pre-clear the transaction type and amount before the closing date. They collect and verify beneficiary details weeks in advance, not hours. They understand their specific recipient corridors — which destinations require documentation, which have currency controls, which correspondent banks their institution uses for that route. And they build closing timelines that account for the fact that a wire submitted on a Thursday afternoon for a Friday close in a cross-border transaction is a wire that will settle the following Monday at the earliest.
The size of the transfer is not the problem in itself. Banks handle large transactions every day. What triggers review is large size combined with missing context — an unfamiliar beneficiary, a vague purpose, a first-time amount, a corridor with elevated risk classification. Every piece of that context that a professional provides proactively is a piece of the compliance review that does not need to happen reactively after the wire is already in flight and the deal table is waiting.
The professionals who understand this do not experience SWIFT as slow. They experience it as a system that rewards preparation. The ones who experience it as slow are the ones who handed an unprepared transfer to a correspondent network and expected speed by default.
