What is SWIFT?
How SWIFT works
The vast majority of cross-border payment transactions rely on the correspondent banking model – as most banks do not have a direct relationship with every other bank around the globe, they use intermediaries. A typical transaction using SWIFT might therefore look like this:
- Instruction: To begin, a corporate treasurer might initiate a payment via their Treasury Management System (TMS) or Enterprise Resource Planning (ERP) system, formatted according to SWIFT’s standards.
- Messaging: The treasurer’s (i.e., the sender’s) bank transmits a secure SWIFT message to the recipient’s bank, or more likely to an intermediary bank if no direct relationship between the sender’s bank and the recipient’s bank exists.
- Settlement: The banks settle the underlying debt by adjusting their respective ‘nostro’ and ‘vostro’ accounts – the records of funds held by one bank at another.
- Confirmation: Once the receiving bank credits the beneficiary’s account, it sends a confirmation message back through the SWIFT network, closing the loop.
Evolving standards
Historically, SWIFT messages have used the Message Type (MT) format (e.g., MT103). This format is character-limited and often relies on unstructured text fields, frequently leading to manual intervention, reconciliation errors, and delays. Essentially, the antithesis of straight-through processing (STP).
The industry has now largely migrated to a modern, XML-based messaging standard: ISO 20022. ISO 20022 messages carry significantly richer and, crucially, structured data. This enhances reconciliation as the automated matching of invoices and payments becomes far more accurate. Better data also means better regulatory compliance, as it enables more robust screening, and structured fields reduce the need for any manual correction of payment messages, improving operational efficiency and speeding up settlement times.
SWIFT gpi
SWIFT has been around since the 1970s, but has seen a significant advancement in recent years with SWIFT gpi (global payments innovation). Before gpi, cross-border payments often had a serious visibility issue. Once a payment left the sending bank, treasurers had little sight of where it was, the reasons for any delays, or how much was deducted in fees by intermediaries.
SWIFT gpi changed this by introducing:
- A Unique End-to-End Transaction Reference (UETR) making real-time, end-to-end tracking of payments possible in a similar way to how you can track parcels out for delivery.
- Clear visibility of fees and processing times, which enables better cash flow forecasting.
- Real-time notifications confirming when funds have been credited to the beneficiary.
- The capacity to stop or reverse payments ‘mid-flight’ in any instances of fraud or error.
Strategic benefits of SWIFT
Connecting to SWIFT or using a SWIFT-enabled service bureau offers significant strategic advantages to corporate treasuries. For one, by consolidating bank communications into a single, standardised channel, treasurers have a single ‘source of truth’. This means treasury teams can rely on automated daily reporting to view their global cash position in real time, optimising liquidity management across multiple jurisdictions and currencies.
This standardisation and capacity for automation also allows companies to replace fragmented, proprietary banking portals with a unified interface. This means bulk payment processing can be facilitated, with potentially thousands of payments able to be sent to multiple banks through a single file, drastically increasing the speed and reliability of disbursements.
Standardisation also offers security alongside efficiency. SWIFT’s protocols are among the most robust in the world, providing a secure environment for sensitive financial data and reducing the risks associated with disparate bank connectivity methods.