As correspondent banks prepare for the global migration to ISO 20022, they face two key challenges. The first involves making the necessary changes to their IT infrastructure. Should they replace their legacy systems, apply an intelligent wrap or turn to managed services? This was the topic of my first blog in this two-part blog series. In part 2, we address the second challenge—providing dual support for both legacy MT messages and the new MX messages during the transition to ISO 20022.
Between the years 2022 to 2025, as ISO 20022 goes into effect, the current SWIFT MT messaging network will undergo massive change. During this transition phase, correspondent banks will need to support both legacy SWIFT MT messages and new ISO 20022 MX messages. This period of duality will be difficult to manage.
Essentially, if your core processing solution is legacy MT and you receive an enriched MX message that you need to pass on to a correspondent bank, there are a few key requirements:
- Completing regulatory and risk scanning of the full MX message
- Storing full MX messages for both regulatory and reconstruction purposes
- Reconstructing an outgoing MX message by combining the original incoming MX message with the downgraded MT message that you have processed
- Validating that your reconstructed message is still compliant with the MX rules.
What is the best approach for meeting these requirements and managing dual support for MT and MX messages? Below are two paths for consideration.
A case for rapid renewal
Modern deployment methods, agile processes and cloud technologies now make it possible to replace core legacy infrastructure in 12 months or less. Deploying a modern, highly available, service-based solution will vastly reduce your operational costs, and putting that solution into cloud infrastructure will further reduce costs while driving business agility.
While the investment in translation and reconstruction technology is tempting, this is inevitably throwaway work with no shelf life beyond 2025. If you can commit to a rapid deployment renewal and be ready ahead of the November 2022 duality phase, then your bank will be in a strong position.
Ideally, to achieve this, you need a solution that meets the following criteria:
- Is truly ISO-native, with an XML data store
- Is ready to be deployed on cloud infrastructure
- Is supported by implementation and managed service resources
A case for modernization-in-place
Modernization-in-place (MIP) is an alternative to rapid renewal that focuses on achieving immediate performance gains while preserving the value of legacy technologies. By proceeding incrementally and using extensive testing along the way, successes accumulate in a series of small project steps, leading to better operational continuity and quality outcomes with reduced risk.
The MIP approach offers several key advantages:
- Protects past knowledge investments
- Creates a more open and nimble architecture
- Significantly reduces risk by leveraging the same hardware and external interfaces, as well as the same people
- Facilitates the migration of capable components to the cloud while leaving other legacy components in place
- Supports a clear vision and path for modernization
However, to succeed with MIP as a correspondent bank, you need to have a service that goes beyond translation and can successfully reconstruct a message from the incoming MX and processed MT. ISO 20022 will take effect beginning in November 2022. While that may seem a ways off, the timeline for change is short at best. CGI is working with correspondent banks to help them prepare. To learn more about our work, feel free to contact me. More in-depth information on the migration to MX messages also is available in our new white paper, From Heritage to Hypernew: Exploring MX Options for Correspondent Banks.