The SWIFT messaging workflow describes the ordered series of steps a bank follows to send an international payment instruction through the SWIFT network. Each step has a purpose, from capturing the payment details to confirming that the funds reached the beneficiary’s account. Understanding this sequence helps everyday customers see why a transfer can take a day or two.
SWIFT is a secure messaging network that banks use to exchange standardized payment instructions. It does not hold or move money itself. Instead, it carries structured messages between banks, which then settle the funds through their own accounts and correspondent relationships, as described below.
Why the Sequence of Steps Matters for Every Transfer
When you ask your bank to send money abroad, your instruction does not travel as a simple email. It is converted into a standardized message that other banks can read automatically. The workflow is the set of stages that turns your request into a message, checks it, routes it, and records its outcome.
Each stage exists to reduce errors and prevent fraud. A mistake in an account number or currency code can delay a payment for days, so banks check details at several points before anything leaves the building. Knowing the order of these checks makes it easier to understand where a payment might pause.
Think of the workflow as a relay race rather than a single jump. Every bank in the chain must receive, verify and pass along the message correctly. A delay at any one handoff affects the final arrival time, which is why transfers sometimes take longer than customers expect.
The Core Stages of a SWIFT Payment Instruction
The first stage begins when the customer submits a payment request, usually through online banking, a branch or a business payment system. The bank captures the beneficiary name, account number, beneficiary bank identifier, amount and currency. Accuracy at this point is essential because every later stage relies on these details.
The second stage is internal validation. The sending bank checks that the account has enough funds, that the payment complies with its policies, and that the screening processes for sanctions and fraud are satisfied. This is where many payments are held for review, particularly those involving unfamiliar countries or large sums.
The third stage is message creation. The bank formats the instruction into a standard SWIFT message type, such as an MT103 customer credit transfer. Once formatted, the message is signed and sent to the SWIFT network, where it is delivered to the receiving bank for processing.
Key Checks Banks Perform During the Workflow
Banks run several checks at different points in the workflow. These checks protect both the institution and its customers, and they explain many of the questions a bank may ask before releasing a payment.
- Format validation, confirming that every required field is present and correctly structured
- Account and balance checks, verifying the sender has sufficient available funds
- Sanctions and watchlist screening, comparing names and countries against official lists
- Authentication, confirming the instruction came from an authorized user or system
- Currency and routing checks, ensuring the beneficiary bank can receive the chosen currency
Most of these checks happen automatically within seconds, but flagged items require a person to review them. A payment that fails a check is usually returned or held rather than sent with errors. If your transfer is delayed, the bank can often tell you which stage it is waiting at, and your account agreement describes how such holds are handled.
How Correspondent Banks Keep the Message Moving
Many international payments do not pass directly from the sending bank to the receiving bank. Where no direct relationship exists, the message is routed through one or more correspondent banks. These intermediaries hold accounts with each other, which allows the payment to move across borders.
Routing decisions depend on the currency, the destination country and the banks’ existing agreements. A payment in US dollars, for example, often passes through a US correspondent account even if neither party is in the United States. Each intermediary adds a step, and each can apply its own checks before forwarding the instruction.
This structure explains why a transfer may show different fees or exchange rates along the way. Customers should review their bank’s fee disclosure, since intermediary charges are not always visible in advance.
What Happens on the Receiving Side
Once the message reaches the beneficiary’s bank, that institution performs its own validation. It confirms the account exists, checks that the name and details match its records, and runs its own compliance screening. This second layer of review is one reason a payment may be paused even after leaving the sending bank.
If everything is in order, the receiving bank credits the beneficiary’s account and typically sends a confirmation or status update back through the network. Settlement between the banks happens through the correspondent accounts, which may occur on a different schedule from the message itself.
Not every payment completes on the first attempt. If a detail is missing or an account is closed, the receiving bank may return the funds, and the amount is sent back along the same chain. Returned payments can take additional time, and fees may apply depending on the bank’s policies.
Common Message Types Within the Workflow
Different steps in the workflow use different message formats. The most widely discussed for consumers and small businesses are the customer transfer and bank statement messages. The three examples below show how each message supports a specific part of the process.
MT103 Customer Credit Transfer
The MT103 is the standard message used to instruct a payment from one customer to another across borders. It carries the sender and beneficiary details, the amount, the currency and the charges instruction. Most international customer transfers you request are sent using this format.
Banks generate the MT103 after internal checks are complete. Because it contains the complete payment record, it is also used later when a payment is traced or questioned. Keeping your reference number helps your bank locate the matching message quickly.
The MT103 format evolved over time, and banks now use structured fields that support better screening. Your bank can explain which fields apply to your particular transfer and why some information is required.
MT202 Bank-to-Bank Transfer
The MT202 is used when one bank instructs another to move funds, usually to settle an obligation between the two institutions. It does not carry the customer’s personal payment details in the same way, because the transfer is between financial institutions rather than individuals.
In the workflow, an MT202 often follows a customer payment, providing the settlement leg that moves the money through correspondent accounts. Customers rarely see this message, but it explains how the funds actually cross between banks.
Banks use the MT202 for treasury operations and interbank settlement. Its role is operational, so customers mainly benefit from knowing it exists when reading a payment trace or discussing settlement timing with their institution.
MT940 Account Statement
The MT940 is a message that delivers a customer account statement in standardized form. Businesses often receive it electronically to reconcile transactions with their internal accounting records. It lists opening and closing balances along with individual entries.
This message sits at the end of the workflow for reporting purposes. Once payments settle, the MT940 helps the customer confirm that funds arrived or left as expected. Many accounting systems can import it directly to match incoming and outgoing items.
Reconciliation is especially useful when multiple payments are in progress. By comparing the statement with the original instructions, a customer can spot delays or discrepancies early and raise them with the bank promptly.
Typical Reasons a Payment Slows Down
Delays rarely mean something has gone seriously wrong. More often, a payment is held at a routine checkpoint, such as sanctions screening or a missing field that needs clarification. Recognizing the common causes can help you respond quickly and avoid repeated attempts.
Incomplete beneficiary information is a frequent source of holds. An incorrect or missing account number, an unclear beneficiary address, or a mismatch between the name and the account can all trigger manual review. Cutoff times also matter, since a payment submitted late in the day may not enter the workflow until the next business day.
Public holidays in either country can extend processing time, because banks in one or both markets may be closed. Currency choice affects timing too, and some currencies settle less frequently than others. Your bank can confirm expected timelines before you submit a transfer.
Protecting Your Payment as It Moves Through the Network
Security is built into every stage of the SWIFT messaging workflow. Messages are authenticated so that receiving banks can verify they came from a legitimate source, and sensitive data is protected during transmission. These measures reduce the risk that a payment instruction is altered in transit.
Customers play a role as well. Scammers often pressure people into sending urgent transfers to unfamiliar accounts, sometimes posing as a bank employee or a supplier. Verifying any change to payment instructions through a known phone number, rather than the contact details in an unexpected message, is a simple and effective safeguard.
If you suspect an unauthorized or mistaken transfer, contact your bank immediately. Prompt reporting gives the institution the best chance to trace the payment and, where possible, request its return. Your account agreement explains the timelines and responsibilities that apply.
Practical Checks Before You Send an International Payment
A little preparation can prevent most avoidable delays. Reviewing the following details before submitting an instruction helps the workflow run smoothly from the first stage onward.
- Confirm the beneficiary’s full legal name exactly as it appears on their bank account
- Double-check the account number or IBAN and the beneficiary bank identifier code
- Choose the correct currency and understand whether a conversion will apply
- Submit the request before your bank’s daily cutoff time to avoid next-day processing
- Keep the reference number and confirmation so you can trace the payment later
Taking these steps reduces the chance of a returned or delayed payment. If you are unsure about a required field, ask your bank before submitting, since it can usually explain the requirement. Fees and timelines vary by institution, so reviewing your bank’s published information or account agreement is worthwhile before you send.
Looking Ahead: Where the SWIFT Messaging Workflow Is Heading
The SWIFT messaging workflow continues to evolve. Banks are gradually moving toward richer, more structured data formats that make screening more accurate and reduce manual review. These changes aim to speed up legitimate payments while keeping security checks strong.
For everyday customers, the practical takeaway is that complete and accurate information remains the most effective way to keep a transfer on track. Understanding the stages helps you ask better questions when something is delayed and set realistic expectations for arrival times.
As you plan your next international payment, consider speaking with your bank about the expected timeline, the fees involved and any documents it may require. Clear communication at the start is often the simplest way to make the workflow work in your favor.