ISO 20022 Migration: What Actually Breaks in Year Two
The message mapping is the easy part. The failures cluster in reconciliation, structured party data and downstream reporting.
Banking Infrastructure Architect
Beyond the mapping table
Most institutions treat ISO 20022 migration as a translation problem. The translation layer is delivered on time. The pain arrives when structured data meets systems that were built for free-text fields.
Where projects stall
- Party data. Structured name and address is a data quality programme, not a schema change.
- Remittance information. Richer remittance data is only valuable if the receiving reconciliation engine can consume it.
- Truncation on legacy hops. Any intermediary still on MT will silently drop the very data the migration was meant to preserve.
If your payment repair queue did not shrink after go-live, the migration delivered format compliance without operational benefit.
Callout: sequencing that works
Run native ISO end to end on one low-volume corridor for a full quarter before scaling. The defects you find there are the defects you would otherwise find in production at volume.
Content is provided for general informational purposes only and does not constitute legal, regulatory, tax, investment or financial advice.
Related analysis
Nostro, Vostro and Net Settlement Mechanics
A precise walk through of the account relationships, mirror ledgers and netting cycles that sit behind a single international payment.
The briefing