ISO 20022 Migration Is Not a Tech Project — Why Most Banks Are Approaching It Wrong
The ISO 20022 cutover is mostly behind us, but the strategic upside is still ahead. Why most banks are leaving the value of richer payment data on the table — and how to capture it.
For most of the past three years, ISO 20022 sat on bank roadmaps as an integration program. Map MT to MX. Stand up the translation layer. Make sure nothing breaks at the SWIFT gateway. Tick the box.
Now that the SWIFT MT-to-MX coexistence window has effectively closed and domestic high-value rails have moved over, many institutions have done exactly that — and stopped. The wires still clear. The screens still populate. From an operations dashboard, the project looks done.
It isn't. The integration was the easy part.
The Real Prize Was Always the Data
The point of ISO 20022 was never the message format. It was structured, machine-readable payment data — richer remittance information, properly formatted party identifiers, purpose codes, regulatory reporting fields, and the ability to carry context all the way from originator to beneficiary without information loss.
Realizing that prize requires investment well outside the payments engineering team. Product needs to surface the new fields to corporate customers. Operations needs to actually use structured remittance information in reconciliation and exceptions. Risk and AML need to feed the richer data into screening and monitoring models. Data and analytics need to ingest it into the warehouse so the business can see what they now have.
Very few banks have made all of those investments. Many have made none of them.
The Symptoms of a Half-Finished Migration
When a bank has only done the integration layer, the symptoms are predictable:
- Corporate clients still send unstructured remittance data because nothing in the experience rewards them for sending structured data
- Operations still treats remittance as freeform text in exceptions handling
- AML models still rely on the same legacy fields they used pre-migration, because no one has retrained them on the structured payload
- The data warehouse stores the new messages but has no consumer querying the rich fields
Why This Is a Strategy Conversation, Not a Backlog Item
The reason this gap persists is not technical. It is organizational. ISO 20022 was scoped, funded, and governed as a payments-engineering program. The downstream consumers — corporate product, ops, risk, data — were not at the table when scope was set, and they have no funded backlog item to pick up where the engineering team left off.
Closing that gap requires treating ISO 20022 as a multi-year strategy program, not a migration project. The next two to three years should be about answering questions like: Which corporate segments will pay for richer remittance? What does AML look like with structured data as the default? Where does our data warehouse need new pipes? What does the dispute process look like when the message can carry its own context?
The Window Is Open, Briefly
The banks that capture the upside will be the ones who treat the migration as the start of a program rather than the end of one. The window to do that quietly — before competitors and corporate clients start expecting it — is open now. It will not stay open for long.