ISO 20022 will become the de-facto standard for high-value payment systems for reserve currencies and is already used in over 70 countries. Globally, financial institutions are identifying payment journeys, processes, and underlying IT architecture to build capability, allowing the processing of SWIFT cross-border payments and reporting (CBPR+) messages.
The advantage of ISO 20022 is that it supports secure and rich payment data, enabling straight-through processing, and a range of possibilities via the intelligent use of enhanced structured data.
Until the end of 2022, the MT payments format will remain the most commonly used format for cross-border payments. However, firms need to use this time to prepare back-office systems for native ISO 20022 support.
It's important that firms have an independent expert review of their overall payments landscape and understand how to build a cost-effective and successful implementation for November 2022. This is crucial for establishing confidence in the quality of the migrated system and verification of the business-identified processes and flows.
CBPR+ is scheduled to go live on 21 November 2022 and all financial institutions must be capable of receiving ISO 20022 format messages from this date. In addition, they must continue to support SWIFT MT and MX payment and non-payment messages until November 2025.
In a big bang approach, the EuroSystem Single Market Infrastructure Group (ESMIG) is adopting ISO 20022 for all its payment and non-payment journeys, also from 21 November 2022. Directly participating financial institutions must have the capability to manage ISO 20022 ESMIG-compliant payments from that date.
The Bank of England is adopting ISO 20022 for the UK the high-value payment system (CHAPS) and low-value payment systems (BACS, FPS). CHAPS will migrate to ISO 20022 in April 2023, with domestic payments scheduled to migrate between 2023 and 2025.
Financial institutions and corporates face several challenges in adopting ISO 20022.
Interoperability
Payment journeys involving multiple financial institutions (FIs) at different levels of implementation may result in issues with payment data exchange, ie, missing, or truncated data transmitted between the party agents.
Sanctions and compliance checks
The proposed solution for handling missing and truncated data may require FIs to build non-STP processes during the co-existence phase for compliance checks.
Identifying impacted payment journeys
FIs face the complex task of scoping and de-scoping impacted payment journeys built up in their operations over several years.
Maturity and effectiveness of the transformation and deployment lifecycle
The ISO 20022 journey cuts across multiple internal and external stakeholders, which requires a mature framework for communication and deployment of people, technology and processes.
Testing
Availability of support in the form of Test Sparring Partners, Bank of England, and Target2 simulators may offer limited capabilities for a complete suite of testing inbound/outbound capabilities. In addition, there are multiple challenges to ensure adequate functional and non-functional testing of internal and external interfaces, end-to-end, cross-impact transaction, and application testing. It’s important to note that acceptance testing levels will comprise several phases covering varied market infrastructure groups (MIGs).
There are several measures that can help firms mitigate the impact of these challenges.
They can adopt strategies that prioritise implementation in line with market infrastructure (Target2, CHAPS) ISO 20022 go-live schedule and additionally and/or use payment volume by currency to plan ISO 20022 migration.
An additional option is defining strategic and/or tactical solutions to enhance processes and systems with capabilities to handle structured and enhanced (eg, structured address, remittance information or purpose of payment, etc) data sent and received in the ISO 20022 message.
Reviewing SWIFT-published data integrity and market practice guidance on interoperability (MT/MX) for payments with missing or truncated data can also help. As can developing a solution that addresses the firm's risk appetite for accepting and processing payments with missing/truncated data.
Finally, they can prepare a test strategy that examines the firm's IT capability to process payments, utilises the ISO 20022 message simulator support offered by MIGs and takes advantage of support/engagement from other friendly banks for end-to-end testing capability.
As the banks gear up for ISO 20022 implementation in Target2 and CBPR+ inbound (November 2022) with CHAPS in April 2023, it's important that firms are adopting an agile delivery model to manage the stages of ISO 20002 implementation over five years and across multiple countries. We have already seen a majority of payment market infrastructure groups publish their respective standards aligned to the CBPR+ release, so it’s crucial to identify a key subset of prioritised MIGs.
Once banks hit the 2022 milestone, it's also important that they review their data strategies and are prepared for the challenges that are likely to occur during the process of implementation. After acknowledging the learning curve to come after the November 2022 deadline and adopting the new payment scheme, banks must also keep an eye on their respective domestic schemes, specifically upgrading their infrastructure to move to ISO20022's latest set of payment message standards, such as FPS/BACS.
For leading advice on PSD2 and upcoming regulatory updates for payment service providers, please contact Paul Olukoya and Terry Taylor.
This article was originally published through The Payments Association.
