Money movement

SWIFT Payment System: What Banks Do Behind the Message

SWIFT carries payment instructions; banks move and credit the money. Understanding that division helps finance teams set realistic delivery expectations, control costs, and investigate international payments.

Layered banking network showing payment messages traveling separately from settlement balances and recipient account credit.

The SWIFT payment system is a secure financial messaging network that banks and other financial institutions use to exchange standardized instructions, including instructions for international payments. SWIFT does not hold your funds or directly transfer money between accounts. The banks and payment systems connected to the transaction handle settlement and beneficiary credit.

For finance teams paying vendors, contractors, or sellers internationally, that distinction matters. A successfully transmitted message does not establish that a recipient has usable funds. This guide explains the banking arrangements behind a SWIFT payment, the information you need, and the questions to ask your provider before a payment run.

What is SWIFT—and what is a SWIFT code?

SWIFT stands for the Society for Worldwide Interbank Financial Telecommunication. Its network provides standardized, secure communication between participating financial institutions. Businesses generally access SWIFT-based payment services through a bank or payment provider rather than interacting directly with the network.

A SWIFT code, commonly called a BIC, identifies an institution and may identify a particular branch. It is not the recipient's account number. An IBAN, where used, identifies a bank account; a BIC identifies the institution involved.

Three concepts should remain separate:

  • Messaging: communicating payment instructions and related information.
  • Settlement: discharging payment obligations through movements in bank balances or payment systems.
  • Beneficiary credit: posting funds to the recipient's account, subject to applicable controls and availability rules.

A bank can receive the instruction before it completes the checks or processing needed to credit the customer.

How the SWIFT payment system works

Consider a hypothetical company paying an overseas supplier in the invoice currency. Its sending bank and the supplier's receiving bank do not necessarily maintain accounts with each other. They may use correspondent banks to connect their banking relationships.

  1. The business submits an instruction. It supplies beneficiary details, amount, currency, remittance information, and the requested treatment of charges.
  2. The sending bank validates and funds the payment. It checks the instruction, applies its controls, and debits the relevant account or uses an agreed funding arrangement. Currency conversion may occur here.
  3. Payment messages travel between institutions. SWIFT carries standardized information that identifies the parties and describes the payment.
  4. Banks arrange settlement. They use correspondent account balances and, where relevant, domestic payment systems. The exact route depends on currency, bank relationships, and service arrangements.
  5. The receiving bank processes the incoming payment. It may conduct additional checks, request information, convert currency, and credit the beneficiary.

A correspondent account is an account one bank holds with another. The account-holding bank calls it a nostro account; the bank maintaining it calls it a vostro account. These balances help banks settle payments without every institution needing a direct relationship with every other institution.

The message route and settlement route need not be identical. Some arrangements send a customer payment instruction to the receiving bank while moving the funding through a separate correspondent chain. A single message receipt therefore cannot describe every financial handoff.

Who controls each part?

ParticipantMain responsibilityWhat it does not establish alone
Sending businessCorrect details, authorization, fundingReceiving-bank acceptance
Sending bank or providerValidation, execution, routing, updatesImmediate recipient availability
SWIFT networkSecure standardized messagingMovement of customer funds
Correspondent bankProcessing and settlement servicesFinal beneficiary credit
Receiving bankIncoming checks and account creditSupplier invoice allocation

How long does a SWIFT payment take?

There is no universal end-to-end delivery time. SWIFT reports that 90% of cross-border payments reach beneficiary banks within an hour. That measures arrival at the bank, not necessarily availability in the recipient's account.

The full journey can also depend on submission cutoffs, funding readiness, holidays, intermediary processing, compliance reviews, and receiving-country requirements. A request for supporting documents can interrupt an otherwise fast route.

Ask your provider what its delivery estimate measures: acceptance of the instruction, arrival at the beneficiary bank, or credit to the beneficiary account. An ETA without a defined endpoint is difficult to use for invoice due dates.

For payment scheduling across markets, use a country-specific payment ETA framework rather than applying one global processing assumption.

What does a SWIFT payment cost?

There is no single business-facing SWIFT tariff that determines the final cost. Your bank or provider prices its service, while other institutions may apply charges along the route.

  • Sending fee: the charge for initiating the transfer.
  • Intermediary charges: fees associated with correspondent processing, potentially deducted from the payment.
  • Receiving charges: fees imposed by the beneficiary's bank.
  • FX cost: the exchange-rate spread and any separate conversion charge.
  • Exception costs: potential charges for investigations, amendments, recalls, or returns.

Common charge instructions include OUR, where the sender is instructed to bear charges; SHA, where charges are shared; and BEN, where the beneficiary bears charges. Availability and handling depend on the route and applicable rules.

Do not treat OUR alone as a universal full-value guarantee. Ask whether the provider contractually guarantees the recipient amount, which fees that guarantee covers, and whether the receiving bank can still charge the account separately.

If the supplier needs an exact invoice amount, compare total sender debit against net beneficiary credit. Holding invoice currency in multi-currency global accounts can help separate funding and conversion decisions from payment execution, but does not by itself eliminate correspondent or receiving-bank fees.

What information do you need to send one?

Start with the beneficiary's verified bank-issued payment instructions. A usable payment record typically includes:

  • Beneficiary legal name and required address details.
  • Account number or IBAN, as applicable.
  • Receiving-bank BIC and any required local bank or branch identifier.
  • Payment currency and confirmation that the account can receive it.
  • Invoice reference, payment purpose, and any required supporting documentation.
  • Intermediary-bank instructions when specifically required by the receiving bank.

A valid BIC does not verify account ownership, currency compatibility, or beneficiary eligibility. Independently verify bank-detail changes through a trusted channel before release.

What ISO 20022 changes

SWIFT's ISO 20022 milestone on 22 November 2025 ended MT–ISO 20022 coexistence for cross-border payment instructions. The standard supports richer, more structured payment data; it does not make missing or incorrect beneficiary information acceptable.

For businesses, the practical requirement is to preserve separate fields for names, addresses, account identifiers, and remittance information. Confirm your bank's current submission requirements: a bank's corporate upload format is not necessarily the same as the interbank message format.

How tracking works—and where it stops

SWIFT GPI adds payment tracking and visibility into processing and charges. A Unique End-to-End Transaction Reference, or UETR, helps participating institutions identify the payment throughout its journey.

Your access to that information depends on your bank or provider. Ask whether it exposes the UETR, underlying tracking events, timestamps, deductions, and the meaning of its customer-facing statuses.

For investigations, retain both the provider's payment ID and the UETR where available. Supply the amount, currency, beneficiary details, submission date, and latest confirmed event. A payment instruction copy is useful evidence of what was sent, but is not automatically proof of beneficiary credit.

If a recipient reports missing funds, investigate before resending. A recall is a request, not a guaranteed reversal. For controlled retry decisions, follow a failed-payment recovery process that distinguishes unresolved payments from confirmed returns.

A preflight checklist for finance teams

Before using a SWIFT service for recurring international payouts, document the answers to these questions:

  1. Account compatibility: Can this beneficiary account receive the instructed currency through the proposed route?
  2. Data requirements: Which fields and documents are mandatory for this destination and payment purpose?
  3. Funding: When must funds be available, and when is any FX rate fixed?
  4. Delivery: What endpoint does the ETA cover, and which exceptions suspend it?
  5. Charges: Is the quote for sender cost, recipient amount, or both?
  6. Tracking: Which events and identifiers will the provider expose?
  7. Exceptions: Who owns investigations, and what evidence authorizes a retry?

Buy a defined payment service, not just SWIFT access

SWIFT provides essential messaging infrastructure. Your operational outcome still depends on the banks, funding arrangements, data quality, and service commitments around it.

For the next payment run, document one service specification per material currency and destination: required data, funding deadline, fee treatment, delivery endpoint, and investigation owner. When evaluating Payouts.com payout automation, bring that specification into the discussion. The goal is not merely to send a message—it is to make each international payment predictable and accountable.

Created with AI assistance. Sources are linked in the article; this content is general information, not legal, tax, or financial advice.

Discussion

3 comments
  • Sara Moreau ·

    Would be useful to see more about the OUR vs SHA breakdown in practice. We've been using OUR for supplier payments but still occasionally see deductions, and when we ask the sending bank they point to intermediary fees outside their control. If OUR doesn't actually guarantee full value delivery, what's the point?

    Reply
  • Viktor Ivanov ·

    The nostro/vostro distinction is something I wish more AP teams understood. We had a vendor insist they never received payment even though our bank confirmed SWIFT delivery. Turned out their bank was holding it for KYC review. Now we always ask for confirmation of account credit, not just transmission.

    Reply
  • Bianca Petrov ·

    The one-hour arrival stat from SWIFT is misleading for anyone doing vendor payment operations. Arrival at beneficiary bank and availability to withdraw or allocate against an invoice can be 24-72 hours apart depending on the country. We build in 3 business days minimum for any new corridor until we have real data.

    Reply

Run your entire money cycle on one ledger

Global payouts, AP/AR automation, and AI agents with their own wallets and spend limits.

Get started