How SWIFT transfers work: routing, costs and confirmation

Key takeaways

• A SWIFT transfer starts as a bank-to-bank payment instruction. SWIFT carries the message; the sending and recipient banks handle the route, processing and eventual account credit.
• A correspondent bank may sit between the two banks. The recipient’s bank still has to process the incoming instruction before the recipient can use the money.
• Check the currency, the banks’ participation and the account instructions before choosing a route. For an eligible euro payment, SEPA Credit Transfer is a separate scheme; it requires both payment service providers to participate.
• Treat the amount received as a result to verify. Banks in a correspondent chain can charge fees, and currency conversion or market-specific charging can change the final amount. Ask the sending bank for a route-specific quote, then compare it with the recipient’s actual credit.
• Set the deadline at recipient account credit, not when the instruction leaves your bank. Swift’s 2024 network report separately recorded 90% reaching the beneficiary bank within an hour and 43% credited to end-customer accounts within an hour; those figures do not predict an individual transfer.
• If a transfer is late, ask the sending bank for the UETR and the current status. A debit receipt or UETR is not proof of credit: confirm that the recipient’s account was credited, or identify the bank that has the next action.

What a SWIFT transfer actually does

A SWIFT transfer is a bank-to-bank payment instruction carried over the Swift messaging network. It is not, by itself, proof that the recipient has received money. The instruction has to travel through the banks on the route, and the recipient’s bank has to process it before the account is credited.

For a finance team paying a contractor, the completion test is the credit to the contractor’s account. A sending confirmation or arrival at the beneficiary bank is an earlier step.

A message, a bank route and an account credit

Swift carries secure financial messages between institutions. In a payment, the sending bank sends an instruction to the recipient bank; the banks handle settlement and the account-credit step. A correspondent bank may be involved when the route requires one, so a transfer can pass through more than two banks.

The recipient bank processes the incoming instruction under its local conditions before crediting its customer’s account. Confirm that credit with the recipient before closing an invoice or resolving a missing-payment query.

SWIFT transfer, international wire and SWIFT code

“SWIFT transfer” is a practical label for a bank payment that uses the Swift network to carry its instruction. An international wire describes the bank-payment context more broadly; a domestic transfer may use a different national system and no Swift message at all.

A SWIFT code is commonly called a BIC, short for Business Identifier Code. It identifies a business party for message addressing and transaction routing. It does not identify the recipient account, and having a BIC does not by itself prove that a bank is connected to Swift or reachable on the route you need. Confirm the recipient bank’s current instructions with the bank before you release the transfer.

How the payment moves between banks

Follow the payment through the banks, ending with the recipient’s account credit. The route shows which institution can answer the next question when a transfer is delayed.

The diagram shows where the instruction and the account credit fall on the route.

From the sender's instruction to the beneficiary bank

Your bank sends the instruction over Swift. The participating banks handle settlement and the path to the beneficiary bank.

Use the recipient bank’s current instructions when you create the transfer; a BIC alone cannot establish that the required route is available.

When a correspondent bank is involved

Some payments use a correspondent bank between the sending and beneficiary banks. Payment transactions can include multiple banks, so an intermediary step is possible rather than automatic for every transfer.

That matters when you ask about timing or the amount received. A bank in the route may have a processing step or charge associated with the transaction. Ask the sending bank which status it can see and whether it can identify the institution currently handling the payment instead of assuming that every delay sits with the beneficiary bank.

When the recipient's account is credited

The beneficiary bank’s processing is subject to local conditions. Its receipt of the instruction and the subsequent account credit are separate states.

For an invoice or contractor settlement, confirm the amount credited with the recipient. A debit confirmation covers only the sending side.

Check the route before sending

Before comparing routes, check the currency, recipient bank’s instructions and whether the institutions can use each option. An apparent speed advantage is irrelevant if the payment does not qualify.

When SWIFT is suitable

Use a Swift route when the sending and beneficiary banks confirm it is available for this payment. Follow the recipient bank’s current instructions and ask the sending bank to confirm reachability; a BIC alone is insufficient.

Some national payment systems operate without Swift messages. Check the route your bank will use rather than assuming an international instruction must go through Swift.

When a domestic or regional route is available

Ask your bank whether a domestic or regional scheme is available for the currency and the two institutions involved. Compare the eligible routes on the date by which the recipient needs account credit and on the amount the recipient should receive. Do not compare a generic SWIFT estimate with a scheme name: a bank’s cutoff, currency conversion and route-specific charges can change both results.

We are actually in the process of moving most of our international payments/payouts into cross-border ACH

— Francisco Meyo, Corporate Controller, Masterworks

The example describes one company’s route choice. It does not establish that another payer or recipient has access to the same option. Your bank can confirm the routes available for the specific payment.

SEPA eligibility for euro payments

SEPA Credit Transfer is a euro-payment scheme. It applies only when the payment service providers executing the transfer formally participate in the scheme. For an eligible transfer, the scheme rules say the original transfer amount is not deducted within the scheme, while each customer may be charged by its own payment service provider.

That does not make every euro transfer a SEPA transfer or set a universal bank price. Confirm participation, bank instructions and charges with both sides before choosing it over another route.

Compare the deadline and amount received

Set the deadline at recipient account credit. For a contractor invoice, the recipient’s confirmation establishes the end state that dispatch or bank arrival cannot.

Ask the sending bank for a current quote that states the route, charges and any currency-conversion terms. Then retain the bank record and compare the credited amount with the approved invoice. Without those payment-specific terms, there is no reliable generic fee, exchange-rate spread or delivery deadline to use in a forecast.

Why a transfer instruction may fail

A familiar-looking recipient identifier does not guarantee an accepted instruction. Banks still have to route the payment and check the data required for that route. Use instructions for the specific bank and currency.

A valid code does not prove reachability

A BIC identifies a business party for message addressing and transaction routing. It is not the recipient account number. Swift also distinguishes between connected BICs with access to its network and non-connected BICs without that access.

Ask the sending bank to confirm the current route before release. The recipient bank’s instructions establish what to provide for this payment; the BIC alone cannot establish reachability.

Bank requirements differ by route

The payment data a bank may need can include creditor account and identity details, remittance information and purpose codes. The relevant fields depend on the bank and route, so a generic checklist cannot prove that an instruction will be accepted.

a missing country code in the payers address details, for example, has been enough for transactions to be rejected

— Arne Thomessen, Principal Expert, Finance LoB, Itelligence Nordic

That example illustrates why the bank’s current instructions matter. It does not create a universal requirement for every route.

Resolve uncertainty before releasing the transfer

Ask the recipient to confirm the bank instructions that apply to this payment, then have the sending bank resolve any uncertainty about the route, recipient details or remittance information before it releases the instruction. Swift describes prevalidation as a way to reduce downstream automation breaks; it does not guarantee acceptance.

If the transfer is rejected or held, ask the sending bank which detail or institution needs action. Resolve that point before creating a second instruction.

Fees, exchange rates and the final amount

The sent amount may differ from the credited amount after bank charges and currency conversion. For an individual payment, compare the bank’s current quote with the recipient’s actual credit.

Charges at each bank in the route

When a correspondent route includes more than one bank, each bank in the chain can charge transaction fees. That is why a sending-bank charge does not necessarily describe every deduction that may affect the payment.

Ask the sending bank for the expected route and its quoted charges. After credit, compare the received amount with the approved invoice and bank record; a generic estimate cannot establish the net result for an unspecified route.

What OUR, SHA and BEN tell you

OUR, SHA and BEN are charge-allocation codes used in payment instructions. They provide useful context for discussing charges, but their operation can be affected by local rules, customs or bilateral agreements.

An OUR selection does not itself guarantee that the beneficiary will see no charge. Swift’s published payment-practice guidance describes a case where a domestic clearing leg does not carry the code forward and the beneficiary may still be charged. Use the code as part of the instruction, then check the bank’s current terms and the final credited amount.

Currency conversion and a usable bank quote

Conversion can change the final amount, and the charging approach can vary by market. A generic exchange-rate spread, fee total or net received amount cannot be set for an unspecified route.

Request the sending bank’s current conversion terms and expected charges. If the invoice requires a particular received amount, verify the credit after the transfer.

How long a SWIFT transfer takes

There is no reliable universal delivery time. Set the deadline by when the recipient needs account credit, then ask the bank which earlier milestones it can confirm.

Three different completion states

The three states are instruction released, beneficiary bank reached and recipient account credited. Ask which state the bank has confirmed before deciding that a payment is late.

Swift’s October 2024 report separately said that 90% of cross-border payments on its network reached the beneficiary bank within one hour and that 43% were credited to end-customer accounts within one hour. The bank-arrival measure excludes receiving-country holidays and non-banking days. Swift did not provide a shared denominator or observation window for the two reported datasets, so they are not a conversion rate or a prediction for an individual transfer.

Use the account-credit measure when setting a recipient-facing deadline; bank arrival measures an earlier step.

An independent BIS/CPMI study of credited Swift gpi MT103 payments in September and October 2020 found a median of 1 hour 38 minutes from the originating bank’s instruction to beneficiary credit. The sample excluded sender-bank preparation and held or returned payments, so it cannot set a current deadline for a particular contractor payment.

Where delays arise

Delay after dispatch can occur at several points. Swift’s 2025 network analysis identifies reporting requirements, currency and other risk controls, limited 24/7 processing, and manual processes as possible last-mile causes. Ask the relevant bank which, if any, applies to this payment.

Cutoffs, calendars and intermediary handling

Published clocks leave out parts of the payer’s wait: the 2024 beneficiary-bank-arrival measure excludes receiving-country holidays and non-banking days, while Swift’s 2025 elapsed-time measure omits originator preparation. Ask about the sending bank’s cutoff and the route’s calendar before promising a date.

An intermediary bank can be part of the route, but it is not automatically the source of a long wait. In the BIS/CPMI study’s 2020 sample, 78% of observed intermediary processing episodes took under five minutes; 33% of beneficiary-bank processing episodes did so. Those historical observations cover processing episodes where an intermediary was present, not every current transfer.

Beneficiary-bank checks and the last mile

The beneficiary bank still has to process the instruction and credit its customer. Swift’s 2025 analysis attributes more than 80% of average global elapsed journey time in its network observations to the last mile. That population was mostly corporate and financial-market traffic, and the figure is not an estimate for a particular payment.

An observational IMF/Swift working paper examined credited MT103 customer transfers aggregated by recipient country-year across 176 countries in 2020–2022. Its model associated a one-standard-deviation increase in its inflow-restriction index with about 4.3 more average beneficiary-leg hours after controls. The study excluded held, returned and future-dated flows, measured country-year averages, and cannot establish causation or predict the timing of one contractor payment.

That country-level association cannot explain a particular delay. If the beneficiary bank has the payment but the recipient has no credit, ask the sending bank which check or institution has the next action. Keep the recipient informed until credit is confirmed.

Track a delayed or missing payment

If the recipient has no credit, ask the sending bank for the UETR and current status. The UETR is a stable reference in specified Swift payment messages that banks can use to trace the payment across the chain.

The decision tree identifies the next question for the sending bank: credited, on hold or transferred outside Swift?

Ask the sending bank for the UETR and current status

Ask the sending bank to state what its UETR-based trace shows. The reference alone is not proof of account credit.

If the payment was credited, confirm with the recipient. If it is held, find out who must act; if it moved outside Swift, ask what status the bank can still see.

Find out which institution holds the next action

For a hold, ask the sending bank which institution needs to act and what information or response is outstanding. It can explain the status visible along the bank chain.

Do not assume a correspondent bank, beneficiary bank or recipient caused the hold. Get the named status and the institution responsible for the next action before correcting details or asking the recipient to take action.

Confirm account credit with the recipient

Customer-payment confirmation can report beneficiary account credit. Confirm it with the recipient before closing an invoice or contractor settlement.

Swift’s Basic Tracker is for financial institutions, and whether a customer can see status depends on the bank’s own interface. If the recipient has not received a credit, continue through the sending bank and keep the recipient updated until the account credit is confirmed.

Correct an error or request a recall

If you find an error after sending, contact the sending bank promptly for status and next steps. A recall request between banks does not prove that the payment was stopped or recovered.

Act on incorrect details before reissuing

Tell the sending bank which part of the instruction may be wrong and ask whether the transfer has been credited, is on hold or has moved outside Swift. If the bank can identify the institution that needs action, use that response to resolve the issue before you decide whether to send a replacement payment.

For a payment that has not yet been completed, the bank may need to correct or investigate the existing instruction. Preserve the bank’s payment reference and the recipient’s invoice records so the next action stays tied to the original transfer.

What a cancellation request can and cannot establish

Swift’s current exception workflow has separate cancellation request and response messages. Wait for the bank’s response before treating a request as successful.

Swift permits Stop and Recall requests for customer credit transfers with an active UETR, and banks can also exchange cancellation messages bilaterally. Whether the particular payment can be corrected, recalled or recovered depends on the banks and the payment’s current state.

Ask the sending bank to confirm the outcome in writing: whether the payment was cancelled, whether funds were recovered, or whether another action remains. Do not close the incident until the bank gives that outcome and the recipient’s account status is clear.

Reconcile a contractor payment

Close a contractor payment with two linked records: the bank’s instruction, status and credited amount; and the approved invoice with applicable engagement documents. Together they show what was paid and why.

Match the bank trail to the approved invoice

Match the recipient and credited amount to the approved invoice. Keep the payment status until account credit is confirmed.

For an eligible SEPA Credit Transfer, remittance information can help the recipient reconcile incoming funds with invoice-related information. Use the remittance field and the payment reference consistently where the bank’s instructions permit it, then retain the bank record with the invoice.

If the received amount differs from the invoice, check the bank’s route, charges and conversion terms. A charge code or sending-bank debit does not establish the final credit.

Keep payment and engagement records together

Keep the bank confirmation and invoice with the engagement records that apply to the work. The exact record set depends on the jurisdiction and the terms of the contractor arrangement, so do not assume that a payment record alone closes every obligation.

For a US small-business expense, IRS guidance calls for records showing the payee, amount, proof of payment, date and service description. It gives an account statement and invoice as examples of supporting documents. That is a US example, not a global rule and not proof that rights to work product were transferred.

Make the record owner and storage location clear before payment day. Then a finance review can follow the bank trail to account credit and the operating team can retrieve the approved invoice and supporting engagement records without reconstructing the transaction from chat messages.

Frequently asked questions

Do all international bank transfers use SWIFT?

No. Some national payment systems do not use Swift messages. Ask the sending bank which route it will use for the currency, recipient bank and account involved.

Do I need a SWIFT code for a local transfer?

There is no universal requirement to use a BIC for a local transfer. A BIC identifies a business party for message addressing and transaction routing, while some domestic systems do not use Swift messages. Follow the receiving bank’s current instructions for the specific local route.

Can I track a SWIFT transfer myself?

Ask the sending bank for the UETR and the current status. The UETR lets banks trace status across the payment chain, but Swift’s Basic Tracker is for financial institutions and customer visibility depends on the bank’s interface. A UETR or debit receipt is not confirmation that the recipient account was credited.

Can a SWIFT transfer be cancelled after it is sent?

Your bank can make a cancellation request, and Swift permits Stop and Recall requests for customer credit transfers with an active UETR. A request is separate from the bank’s response, so it does not establish that the transfer was cancelled or that funds were recovered. Ask the sending bank for the outcome and the recipient account status.

What is SWIFT gpi?

Swift gpi stands for Global Payments Innovation. It is Swift’s cross-border payment service for participating financial institutions, with end-to-end tracking and payment-confirmation tools.

Ask the sending bank how it shares UETR-based status with customers. The recipient still needs to confirm account credit.

Why did the recipient receive less than expected?

Banks in a correspondent chain can charge transaction fees, and currency conversion or market-specific charging can affect the amount received. An OUR charge selection does not guarantee that the beneficiary will avoid a charge, because a domestic clearing leg may not carry the code forward. Compare the recipient’s account credit with the sending bank’s current route and currency-conversion terms.

Sources

• What is Swift? — Swift
• The role of correspondent banks — Swift
• Business Identifier Code (BIC) — Swift
• SEPA Credit Transfer — European Payments Council
• Why ISO 20022 matters for payments businesses — Swift
• Spotlight on speed, October 2024 — Swift
• Spotlight on speed, September 2025 — Swift
• Swift gpi data indicate drivers of fast cross-border payments — Bank for International Settlements
• Surpassing two million messages: Swift gpi sets a new standard for cross-border payments — Swift
• Inflow restrictions and cross-border payment delays — International Monetary Fund
• What is a UETR? — Swift
• Universal confirmations — Swift
• ISO 20022 exceptions and investigations — Swift
• PMPG guidelines on charges claiming process — Swift
• What kind of records should I keep? — Internal Revenue Service
• Swift: corporates voice payments frustration — Treasury Today
• Payments disruptions: prevention is better than cure — Treasury Today