Last reviewed: · Curated by Ohmyfin Organisation editorial.
Same day for SWIFT GPI in 95% of cases. Once an MT103 is sent, GPI banks process it within minutes. Delays are caused by sanctions screening, missing fields, or correspondent-bank cut-offs.
Settlement system: Per-currency RTGS.
For most cross-border payments today, "slow" is rarely the SWIFT messaging — it is the compliance and screening layer at the receiving bank, plus the cut-off times of each currency's domestic RTGS.
If your payment is taking longer than expected, the first step is to look it up by UETR on Ohmyfin. The latest available SWIFT status will show you exactly which bank is holding it, so you can chase the right party.
An MT103 is a SWIFT FIN message used for cross-border customer credit transfers — it is the universal format for international wire payment instructions. From the moment a bank releases an MT103 into the SWIFT FIN network, delivery to the receiving bank's SWIFT interface is near-instantaneous (typically under 30 seconds). The meaningful processing time — from MT103 receipt to beneficiary account credit — depends on sanctions screening, the receiving bank's internal batch cycle, and the cut-off time of the local RTGS.
Under SWIFT GPI (Global Payments Innovation), participating banks commit to processing GPI-enabled MT103s within the same business day (or within the business day of the receiving bank's local RTGS, which may differ by time zone). When a SWIFT GPI bank receives an MT103 with a valid UETR in field 121, it must either credit the beneficiary or pass the payment to the next bank within the prescribed SLA window. SWIFT's observer role monitors adherence to this commitment and publishes anonymised performance data. Approximately 50% of GPI MT103 payments credit the end beneficiary within 30 minutes.
Sanctions screening is the primary source of MT103 delays. Multiple layers of automated screening run in parallel: SWIFT Sanctions Screening (a network-level service), the individual bank's own engine (Fircosoft, Accuity / LexisNexis Risk Solutions, Oracle Financial Services, etc.), and in some cases a manual review step. These engines compare beneficiary name, originator name, and intermediary bank names against OFAC SDN, EU Consolidated List, UK HMT Consolidated List, UN Sanctions, and numerous domestic lists. A potential match (even a false positive from a common name) triggers a manual compliance hold, typically adding 1-2 business days.
Field 23B (Bank Operation Code) and field 71A (Details of Charges) are two of the most frequently misconfigured fields in an MT103. Field 23B must contain CRED for a standard customer credit transfer — incorrect codes cause automated rejection. Field 71A controls who pays correspondent bank charges: OUR (sender pays all fees), SHA (shared, each party pays their own bank), or BEN (beneficiary pays all fees). An unexpected 71A code can cause a correspondent bank to return the payment for amendment, adding 1-3 days. Always confirm the expected charges code with your bank before sending.
The cut-off cascade is a well-documented phenomenon in cross-border payments: even a GPI MT103 can arrive at the beneficiary bank's NOSTRO account just after the local RTGS cut-off, meaning T2/Fedwire/CHAPS/BOJ-NET settlement slips to the following business day even though the SWIFT messaging leg was same-day. This is why a payment sent at 16:30 CET may show ACSP (pending) overnight and ACCC (completed) the following morning — the SWIFT leg settled that day, but the local RTGS leg settled next-day.
SWIFT is progressively migrating MT103 to pacs.008 (ISO 20022 MX message) under the SWIFT Standards Release coexistence period. During the coexistence period (November 2022 – November 2025), both MT103 and pacs.008 are valid for cross-border payment instructions. After November 2025, MT103 will be available only as a legacy format in certain market infrastructure configurations. The transition to pacs.008 does not change the processing timeline, but the richer structured data in pacs.008 (legal entity identifiers, purpose codes, ultimate parties) is expected to reduce sanctions-screening false positives over time.
| Topic | MT103 processing |
|---|---|
| Typical time | Same day for SWIFT GPI in 95% of cases. |
| Settlement system | Per-currency RTGS |
Sanctions screening on a new beneficiary, missing remittance data, or arrival after the day's RTGS cut-off. Weekends and local public holidays also pause settlement.
Yes — paste the UETR (or bank reference) on Ohmyfin and you will see the latest available SWIFT status for the MT103 processing.
SWIFT FIN message delivery is near-instantaneous — typically under 30 seconds from the sending bank's interface to the receiving bank's SWIFT interface. The delay between MT103 receipt and account credit is entirely in the receiving bank's internal processing: sanctions screening (minutes to hours), RTGS queuing, and the cut-off times of the local settlement system.
The main causes are: (1) sanctions screening — a potential name match triggers a manual compliance review taking 1-2 business days; (2) missing or incomplete fields — especially field 50 (ordering customer) or field 59 (beneficiary) triggering a return for amendment; (3) the local RTGS cut-off — the payment arrived in the bank's NOSTRO after the same-day cut-off; (4) KYC requirements at the receiving bank for a first-time large transfer.
Field 23B is the Bank Operation Code — it must be CRED for a standard customer credit transfer. Any other code triggers automated rejection. Field 71A specifies who pays correspondent fees: OUR (sender pays all), SHA (shared), or BEN (beneficiary pays all). If the field 71A code does not match what the correspondent bank expects, the payment may be returned for amendment. Both fields should be confirmed with your bank before sending to avoid bounce-backs.
Classic SWIFT MT103 (before GPI) had no tracking, no SLA commitment, and no obligation for banks to pass on payments the same day. Under SWIFT GPI (active since 2017), GPI-member banks sign a multilateral agreement committing to same-day processing and real-time status updates via UETR. This transformed MT103 from a black-box message to a tracked payment. Today approximately 95% of SWIFT cross-border payment value flows through GPI-enabled channels.
Yes — SWIFT's ISO 20022 migration programme is replacing MT103 with pacs.008 (the ISO 20022 MX equivalent for customer credit transfers). During the coexistence period (November 2022 – November 2025), both formats are valid. After November 2025, MT103 will be available only as a legacy format in certain infrastructure configurations. The underlying RTGS settlement infrastructure and timing remain the same; only the message format changes.
Every GPI-enabled MT103 carries a UETR (Unique End-to-End Transaction Reference) in field 121. Paste that UETR on Ohmyfin to see the latest available SWIFT GPI status: ACSP (processing), ACWP (pending RTGS), ACCC (completed), or RJCT (rejected). If you do not have the UETR, ask your bank for the payment's UETR or the MT103 copy, which will contain the UETR in field 121.
No card needed. Free for ordinary users — completely free for individuals — no daily limit, no card required. Track any international wire across 11,000+ banks.
Track a payment now — completely free Or try the tracker now →