Where banks really stand on the ISO 20022 migration
Coexistence deadlines keep shifting and readiness varies widely across institutions. We survey where banks actually are on mapping, testing and structured data adoption today.
A migration measured in years, not months
The move from SWIFT's legacy MT message standard to the richer, structured ISO 20022 MX format has been underway across cross-border payments for some time now, coordinated through the CBPR+ program.
On paper, the case is straightforward: MX messages carry more structured data — cleaner party information, better remittance detail, less ambiguity for screening and reconciliation — than the free-text fields MT institutions have relied on for decades.
In practice, moving an entire correspondent banking network onto a new message standard without breaking anything along the way has proven to be a much longer exercise than the industry's data quality ambitions might suggest.
Coexistence, extended again
SWIFT's response has been a coexistence period, allowing MT and MX messages to run in parallel rather than forcing every institution to cut over on a single date.
That was the right call operationally, but it has also meant the coexistence period has been extended more than once as banks worked through mapping legacy fields to structured MX equivalents, testing translation layers, and getting counterparties ready at a similar pace.
Each extension buys time, but it also pushes the industry's full realisation of ISO 20022's benefits further out, since much of the value of richer data depends on it surviving the whole payment chain intact.
Where the friction actually sits
The gap between the standard's promise and today's reality shows up in a few recurring places. Structured data still gets truncated or flattened when a payment passes through a system still built around MT-era assumptions, which quietly erodes the benefit the migration was meant to deliver.
Adoption timing is uneven across correspondent networks, so a bank's own readiness only goes so far when its counterparties are moving at a different pace. And the operational and testing burden weighs disproportionately on mid-size banks, which often have fewer dedicated resources for mapping, testing and remediation than their larger peers.
None of this is a sign the migration is failing — it is a sign of how much operational plumbing sits underneath a messaging standard change, and why institutions are still working through it.
Run Ventures works with banks on exactly these mapping, translation and readiness challenges as the transition continues.