ISO 20022 Consultant and Migration Help
Practitioner-led ISO 20022 consulting for banks and fintechs. I help teams move from MT to MX, map and validate the new messages, and protect the rich data that makes ISO 20022 worth the effort, without breaking the flows that already work.
What is ISO 20022?
ISO 20022 is the global standard for financial messaging. It replaces terse, fixed-format messages with structured, richly described data, so a payment carries far more context: clean party identification, structured addresses, remittance information, and purpose codes.
For cross-border payments it is the foundation of the SWIFT migration from the legacy MT messages to the MX (pacs, pain, camt) message set. The standard is well defined; the hard part is moving real systems onto it without losing data or stalling flows.
Where ISO 20022 migrations actually get hard
The standard is sound. The friction is in your estate: legacy systems that were built around 35-character fields, party data that was never structured, and downstream processes that quietly depend on the old format.
- Truncation and data loss: rich MX data has nowhere to go when an internal system still assumes MT-era field lengths.
- Coexistence: during the migration window you must handle MT and MX in parallel and translate between them without dropping information.
- Structured party data: names and addresses that were free text for years have to be parsed into structured components.
- Validation: message and network rules are stricter, so weak data that used to pass now fails at the gateway.
How I approach an ISO 20022 engagement
I work end to end: scoping which message types and flows are in play, mapping MT to MX (and back, for coexistence), fixing the data quality problems that surface during mapping, and putting validation in place so messages are clean before they leave your bank.
ISO 20022 sits on top of reference data. Clean BIC, IBAN, and LEI data is what lets you populate structured party fields correctly, so the messaging work and the reference-data work are done together, not in isolation.
Why the rich data is the point
It is tempting to treat ISO 20022 as a format change to survive. The value is the structured data: better sanctions screening with fewer false positives, straight-through reconciliation from structured remittance information, and cleaner Verification of Payee and fraud controls.
A migration that just maps fields and truncates the rest passes the deadline but leaves the upside on the table. The goal is to carry the rich data through your estate, not strip it at the first hop.
Frequently Asked Questions
- What is the difference between MT and MX messages?
- MT is the legacy SWIFT message format with terse, fixed-length fields. MX is the XML-based ISO 20022 message set (such as pacs, pain, and camt) that carries structured, far richer data. The migration moves cross-border payments from MT to MX.
- What is coexistence in ISO 20022?
- Coexistence is the migration window during which both MT and MX are in use. Systems must process both formats and translate between them without losing the rich data that only MX can carry.
- Why do ISO 20022 migrations cause data loss?
- Legacy systems were built around short, fixed-length fields. When richer MX data is mapped into them it gets truncated or dropped. Avoiding that means fixing internal data models and party data, not just translating messages.
- How does reference data relate to ISO 20022?
- ISO 20022 needs clean, structured party data to populate its fields correctly. Accurate BIC, IBAN, and LEI data is what lets you fill structured identification and address components, so reference-data quality and the messaging migration are done together.