Banks only have a short time to go until Swift’s 22nd November deadline. Across the industry, financial institutions are on a mission to make sure payments continue smoothly as ISO 20022 goes live.
This blog marks the first in our two-part series exploring ISO 20022 adoption. Over the coming weeks, we’ll look at what the Swift mandate entails, what it means for banks before and beyond the deadline, and how institutions can plan effectively.
In this instalment, we focus on the choice banks are facing today: should they rely on translation tools to bridge legacy systems, or take the step toward full native ISO 20022 migration? We explore why moving to native ISO 20022 will best allow banks to unlock the messaging standards full potential.
Getting set for ISO 20022
On 22nd November, the Swift coexistence period ends, and several FIN messages will be replaced by their ISO 20022 equivalents. The transition is a major challenge. These aren’t just new codes – they’re richer and more structured than legacy MT formats. That means banks’ systems now need to handle additional fields and detailed data. Market-specific ISO 20022 variations add complexity, requiring banks to align payment, settlement, and reporting processes across regions.
Translation tools to bridge the gap
To tackle these challenges, institutions may turn to translation tools. These tools convert legacy FIN messages into ISO formats for outbound flows, and vice versa for inbound messages. Translation tools are a fast, cost-effective way to meet Swift’s deadline. They can maintain payment operations while avoiding the complexity and expense of a full system upgrade, making them attractive for institutions with tight timelines or complex IT environments.
However, translation tools aren’t a long-term solution. They require months of maintenance and can strip out or simplify much of the rich data ISO 20022 supports. We’re already seeing the short-lived nature of translation tools. From November 2026, Swift will require full structured data – including post addresses – in CBPR+ messages. Translation tools can’t deliver this level of data quality or structure. Banks relying on them risk failed validations and rejected payments once the new rules take effect.
Going native with ISO 20022
A different approach to ISO 20022 compliance is native adoption. This means banks process ISO 20022 messages directly in their systems, rather than converting them from legacy formats. By handling messages natively, banks can fully take advantage of the standard’s structured data. This opens the door to faster straight-through processing, reducing manual intervention and minimising errors.
Of course, native adoption isn’t without difficulties. Legacy infrastructure can make upgrading or replacing existing software, databases, and operational processes costly and time-consuming. It can also increase the risk of outages. With millions of customers relying on these systems daily, downtime could disrupt payments and damage trust. As a result, many banks may hesitate to adopt native ISO 20022 fully.
Taking it step by step
The good news is that banks don’t need to overhaul everything at once. There are options to make the transition manageable. A gradual, modular approach allows banks to modernise core systems bit by bit. They can bring in automation and real-time data incrementally and add cloud-ready messaging without disrupting daily operations. This method reduces risk and spreads costs over time, and ensures systems remain compatible with ISO 20022’s richer data.
Banks also don’t have to undertake this process alone. Partners can help to streamline the migration, implementing modular platforms that integrate with core banking systems, Swift, and third party applications. Institutions should work with partners that provide a messaging hub that can automate transaction processing across any source and deliver configurable payment orchestration. With the right guidance, rollout can be faster, manual work can be minimised, and compliance can stay on track.
By working with partners, like Aqua Global, banks can tackle the challenges of legacy infrastructure while fully reaping the benefits of native adoption, making the investment in ISO 20022 truly worthwhile.
Stay tuned for part two of this series where we explore why ISO 20022 is more than just a messaging standard, but a real opportunity to modernise corporate payment systems and processes for the future.
