Compliance

SWIFT (Society for Worldwide Interbank Financial Telecommunication)

SWIFT is the global member-owned messaging cooperative that banks use to instruct cross-border payments, with cross-border interbank messaging migrated to the ISO 20022 MX format (pacs.008, pacs.009) on November 22, 2025 and legacy MT message formats retired.

Globe with currency notes and a laptop showing a cross-border wire confirmation

What Is SWIFT?

SWIFT is the member-owned cooperative that operates the dominant cross-border interbank messaging network. It is headquartered in La Hulpe, Belgium, connects more than 11,000 financial institutions across more than 200 countries, and is the layer through which most international wire payments are instructed. SWIFT does not move money itself. It transmits standardised payment messages between member banks, which then settle the underlying funds across correspondent-bank accounts or through central-bank real-time gross settlement systems. The authoritative source on the network, its standards, and its governance is https://www.swift.com.

For a US business paying international contractors or EOR employees outside the United States, SWIFT is almost always the rail behind the scenes. The originator’s bank generates a SWIFT message, routes it through correspondent banks until it reaches the beneficiary bank, and the beneficiary bank credits the receiver’s account.

MT to MX: The 2025 ISO 20022 Migration

SWIFT messages historically used the MT (Message Type) format, a fixed-field text standard dating to the 1970s. Cross-border customer credit transfers used MT103, and bank-to-bank transfers used MT202. These formats are now retired for cross-border interbank messaging.

On 22 November 2025, SWIFT completed the Cross-Border Payments and Reporting Plus (CBPR+) migration to the ISO 20022 MX message standard. From that date:

  • MT103 is replaced by pacs.008 (FIToFICustomerCreditTransfer) for customer credit transfers.
  • MT202 is replaced by pacs.009 (FinancialInstitutionCreditTransfer) for bank-to-bank transfers.
  • MT category 1 and 2 messages are no longer supported for cross-border use.

ISO 20022 is an XML-based open standard maintained by ISO and adopted across major payment systems globally (Fedwire, CHIPS, TARGET2, CHAPS, India’s NPCI rails, and others have all migrated or are migrating). It carries materially richer structured data than MT, including separated debtor and creditor names, structured postal addresses, purpose codes, ultimate-debtor and ultimate-creditor fields, and remittance information that supports automated reconciliation and screening.

SWIFT has set a deadline of November 2026 for full structured-address compliance. After that date, fully unstructured addresses are no longer permitted in cross-border ISO 20022 messages, and a hybrid model (town and country mandatory, other fields optional) applies in the interim. The authoritative migration plan is published on the SWIFT standards portal at https://www.swift.com/standards/iso-20022.

Correspondent Banking and Why Fees Stack

When the originator’s bank does not hold an account directly with the beneficiary’s bank, the SWIFT payment routes through one or more correspondent banks. Each correspondent maintains a nostro account (the sender bank’s holding at the correspondent) and a vostro account (the correspondent’s holding at the sender bank) in the relevant currency, and debits and credits flow along this chain.

Each intermediary in the chain typically deducts a fee from the payment, known as a lifting fee, and may apply an FX margin where a currency conversion occurs at its leg. The combined effect is that a $1,000 USD payment sent from a US bank to an Indian beneficiary in INR can land with $20 to $50 less in nominal USD-equivalent value and at an FX rate that is 1 to 4 percent below the live mid-market rate, before the beneficiary bank’s own inbound charge.

The MX pacs.008 message exposes more of this detail than the legacy MT103, including a charge-bearer indicator and structured remittance information, but the underlying correspondent-bank economics are unchanged.

Settlement Timing

A cross-border SWIFT payment typically arrives in the beneficiary account within one to five business days, with the spread driven by:

  • Number of correspondent banks in the chain (more hops, more time).
  • Currency of the payment (major currencies clear faster).
  • Sanctions, AML, and PEP screening holds at each correspondent.
  • Time-zone gaps between sender and receiver.
  • Weekend and holiday calendars in each country.

SWIFT gpi (Global Payments Innovation), embedded in the CBPR+ ISO 20022 flow, attaches a Unique End-to-End Transaction Reference (UETR) to each payment and provides tracking across the chain. SWIFT publishes that the majority of gpi payments credit within 30 minutes and almost all within 24 hours, although emerging-market corridors and screening holds can extend timing.

SWIFT Alternatives for USD

For domestic USD large-value payments inside the United States, two rails dominate:

Together CHIPS and Fedwire handle roughly 96 percent of large-value USD payments in the US.

For cross-border USD payments to non-US beneficiaries, SWIFT still carries the messaging layer, but the underlying USD settlement between US correspondent banks usually clears on Fedwire or CHIPS, with the foreign correspondent then crediting the beneficiary in local currency or holding the USD in a vostro account.

SWIFT and US Contractor Payments

For US businesses paying contractors or EOR employees outside the United States, SWIFT is the default cross-border rail. The originator pays in USD, the chain converts to local currency at a correspondent or at the beneficiary bank, and the beneficiary receives local currency one to five business days later. The combined cost of correspondent fees and FX margin typically lands in the 2 to 4 percent range for major corridors. See our guide on paying international contractors from the US for a corridor-by-corridor cost view.

How Omnivoo Helps

Omnivoo Contract Management routes US contractor payments on ACH where the contractor is US-based, and on bank rails messaged through SWIFT (with FX disclosed at origination) where the contractor or EOR employee is outside the US. Our payout flow batches invoices, validates IBAN or SWIFT BIC and beneficiary data before origination, attaches a UETR for tracking on supported corridors, and surfaces the all-in cost including correspondent fees and FX margin so finance teams see the real landed cost before approval.

Frequently asked questions

What is SWIFT and what does it actually move?
SWIFT (Society for Worldwide Interbank Financial Telecommunication) is a Belgium-headquartered member-owned cooperative that operates a secure messaging network connecting more than 11,000 banks and financial institutions in over 200 countries and territories. SWIFT does not move money or hold customer accounts. It transmits standardised payment instructions and reporting messages between member institutions, which then settle the underlying funds across correspondent-bank accounts (nostro and vostro), through central-bank real-time gross settlement systems, or through net-settlement systems such as CHIPS for USD-USD. The authoritative description of the network and its standards sits on https://www.swift.com.
What changed on 22 November 2025 with ISO 20022?
On 22 November 2025, SWIFT completed the Cross-Border Payments and Reporting Plus (CBPR+) migration to the ISO 20022 MX message standard for cross-border interbank messaging. From that date, MT category 1 and 2 customer-credit-transfer messages (notably MT103 for single customer credit transfers and MT202 for bank-to-bank transfers) are no longer supported for cross-border payments on the SWIFT network. The equivalent MX messages are pacs.008 (FIToFICustomerCreditTransfer) and pacs.009 (FinancialInstitutionCreditTransfer). MX carries far richer structured data including separated debtor and creditor names, structured addresses, purpose codes, and ultimate-party fields, supporting better screening, reconciliation, and regulatory reporting. SWIFT's standards portal at https://www.swift.com/standards/iso-20022 is the authoritative source for the migration plan.
How does correspondent banking actually work?
When a sender's bank does not hold a direct account with the receiver's bank, the payment routes through one or more intermediary correspondent banks. Each correspondent maintains nostro accounts (the sender bank's account at the correspondent) and vostro accounts (the correspondent's account at the sender bank) in the relevant currency. The MX pacs.008 message instructs the chain, and each correspondent debits and credits along its books. Every correspondent typically deducts a fee from the payment amount (lifting fees) and may apply an FX margin if a currency conversion takes place at its leg. This is why a USD payment from a US sender to an Indian beneficiary can arrive with $20 to $50 less than the originated amount, and why the foreign-currency converted amount can be 1 to 4 percent below the live mid-market rate.
What are SWIFT alternatives for USD large-value payments?
For USD-USD large-value domestic payments inside the United States, the two operative rails are Fedwire Funds Service (operated by the Federal Reserve Banks, real-time gross settlement, used for high-value time-critical wires) and CHIPS (Clearing House Interbank Payments System, operated by The Clearing House, a private multilateral-netting system). CHIPS and Fedwire together carry roughly 96 percent of large-value USD payments in the US (https://www.theclearinghouse.org/payment-systems/CHIPS, https://www.federalreservehistory.org/essays/fedwire). Cross-border USD payments to non-US beneficiaries still typically traverse SWIFT for the messaging layer, but the actual USD settlement between US correspondent banks usually clears on Fedwire or CHIPS. For domestic euro, GBP, and other major currencies, the equivalent RTGS systems are TARGET2 / T2 (euro), CHAPS (sterling), and similar national infrastructures.
How long does a SWIFT wire take to arrive?
A cross-border SWIFT payment typically arrives in the beneficiary account within one to five business days. The variation depends on the number of correspondent banks in the chain, the currency, time-zone overlap between sender and receiver, sanctions and AML screening at each intermediary, and the beneficiary bank's posting cutoff. SWIFT gpi (Global Payments Innovation), now substantially embedded in CBPR+ ISO 20022 messaging, provides end-to-end payment tracking and unique end-to-end transaction reference identifiers (UETR) so the sender can see status across the chain. SWIFT publishes that the majority of gpi payments are credited within 30 minutes and almost all within 24 hours, but holiday calendars, weekend gaps, and screening holds can extend timing for emerging-market corridors.

Related Terms

Compliance

ACH (Automated Clearing House)

The Automated Clearing House is the batched US electronic funds-transfer network governed by Nacha rules, used for direct deposit of payroll, vendor and contractor payments, and consumer debits, with a Same Day ACH per-payment limit of $1 million effective March 18, 2022.

Compliance

ESIGN Act (Electronic Signatures in Global and National Commerce Act)

The ESIGN Act is the US federal statute, codified at 15 USC 7001 et seq. and enacted in 2000, that gives electronic signatures and electronic records the same legal effect as their paper equivalents for transactions in or affecting interstate or foreign commerce, subject to specific consumer-consent and retention requirements.

Compliance

Force Majeure

Force majeure is a contractual doctrine that excuses or suspends a party's contractual performance when an extraordinary event beyond the party's reasonable control prevents performance, with US contracts relying on negotiated force-majeure clauses backed by the common-law doctrines of impracticability (Restatement (Second) of Contracts 261-262) and, for sale-of-goods contracts, the Uniform Commercial Code 2-615.

Compliance

FX Margin

FX margin is the spread that a bank or payment provider adds above the live interbank mid-market rate when converting one currency to another, and it is typically the largest single cost in a cross-border payment, often 1 to 4 percent and frequently disclosed only as a built-in rate rather than a separate fee.

Compliance

UETA (Uniform Electronic Transactions Act)

The Uniform Electronic Transactions Act is a 1999 model law drafted by the Uniform Law Commission that gives electronic signatures and electronic records the same legal effect as paper, adopted in 49 US states, the District of Columbia, and the US Virgin Islands, with New York the only state that operates a separate electronic-signatures statute (NYESRA) instead.

Related articles

Omnivoo handles this for you

Stop worrying about Indian payroll and compliance terms. Omnivoo manages everything (PF, ESI, TDS, professional tax, and more) across all 28 states.

Get started