Migrate to ISO 20022 with confidence
Achieve compliance and streamline processes as you embrace the biggest change to interbank payments in decades
From November 2025, Swift will start to retire MT messages and migrate fully to the new ISO 20022 standard.
Banks and other financial institutions will be affected first, but eventually all organizations will have to send payment instructions using ISO 20022 messages. This will mean sending and receiving payments becomes simpler and more transparent thanks to more rich and structured data. But it also means you’ll have to make fundamental changes to payment operations – particularly for cross-border transactions.
We’re here to help you navigate this change and the challenges it brings. From process changes to training needs and the usual hurdles of change management. We’ve developed products specifically to create a smooth transition and workflow for an ISO 20022 compliant organization. And our consultants are on hand to guide your IT and finance teams through even the most complex implementations.
On this page you’ll find all the resources you need to better understand ISO 20022, what it means for you, and how we can help you make the move.
The ISO 20022 migration impact for corporates
Navigating the transition to the new ISO 20022 standard
This eBook includes everything you need to know about the new standard, how it works, what it means for your organization’s payments, and introduces our unique SAP-embedded solution that helps expedite compliance while eliminating manual workloads from your teams.
ISO 20022 with Serrala pain.001-FileCreator
Automate pain.001 XML File Creation
Navigating the complexities of ISO 20022 compliance is seamless with our innovative product, pain.001-FileCreator. Designed specifically to alleviate the workload for your accounts payable and payments teams, this tool automates the intricacies of managing ISO 20022 messages efficiently. Discover the full capabilities of pain.001-FileCreator on our dedicated product page.
Customer use case example
ERP SWIFT MT payment initiation messages
Different Formats
Different language / characters
Initiators defined field use in ERP
Limited field availability
ERP pain.001 migration challenges
Required fields not available
Complex & expensive to change SAP ERP fields
Maintaining field library and meeting bank specific requirements
ERP pain.001 migration challenges
Simple add-on layer to SAP
Data field library ongoingly maintained
Always meeting bank specific payment initiation requirements
No need for expensive ongoing ERP configurations