Six months ago, the end of Swift’s coexistence period made ISO 20022 the mandatory standard for cross-border payments. Before the deadline, we looked at how banks were preparing to make that switch. Now it has passed, we can analyse how banks got there and what it means for the road ahead.
Our report, From Compliance Burden to Competitive Advantage, found that migration was anything but smooth. Almost all banking leaders surveyed (97%) ran into difficulties migrating away from legacy MT formats, and 1 in 5 saw downtime or payment disruption during the move. As well as needing to meet the tight Swift timelines, banks faced significant challenges due to complex IT estates and core systems that were never built to support ISO 20022 requirements. With the clock running down, banks needed a way to comply without a major overhaul.
The short-term fix that became the default
For most banks, the answer was translation tools. These convert legacy messages into ISO formats so existing systems can keep sending and receiving payments. It was the low-risk route to meet the deadline, with a full migration seen as too costly and disruptive. However, our data found that in the months following the deadline, 65% of institutions still depend on translation tools to remain compliant.
This presents a long-term challenge. While a translation layer meets today’s requirement, it limits the value of ISO 20022 in the long run. The extra detail carried in the new format is stripped back by translation tools, leaving banks with fragmented data and inconsistent audit trails. Our data found that 83% of banks believe quick fixes like translation tools will ultimately cost financial institutions more in the long term.
What native ISO 20022 processing delivers
Treating ISO 20022 as a box-ticking exercise only creates challenges as new data and validation rules arrive. The alternative is native processing inside a flexible workflow framework, handling ISO 20022 messages directly rather than converting around them. Asked why they ultimately want to make the move, banks pointed to key benefits including:
- Higher STP and fewer errors. Processing structured data directly improves straight-through processing rates and cuts the errors that creep in through conversion.
- Less manual work and clearer visibility. Teams spend less time on manual intervention and gain better visibility into where each payment is in the process.
- Stronger integration and fewer rejections. Native messages integrate more cleanly with third-party tools such as AML and fraud systems, reducing the risk of failed validations and rejected payments.
- Lower costs and faster settlement. Removing rework and friction brings down operational costs and supports faster settlement times.
- A future-ready foundation. Native processing helps banks stay ready for upcoming Swift mandates rather than scrambling to meet each one.
Moving forward without ripping out core systems
Thankfully, this does not mean ripping everything out at once. A modular approach lets institutions add native ISO 20022 capability on top of their existing core systems, spreading cost and risk while keeping compliance on track.
This is where the right partner makes the difference. Aquila, Aqua Global’s cloud-native messaging and orchestration hub, delivers native ISO 20022 processing and connects to Swift and core banking systems, alongside third-party services such as AML and fraud screening. It also embeds controls directly into payment workflows without a costly rip and replace.
The deadline may have passed, but the risk has not. And the cost of standing still on a temporary fix only grows. Working with a partner like Aqua Global, banks can move beyond the stopgap and finally make their ISO 20022 investment worthwhile.
