When a bank in Lima pays a supplier in Frankfurt, that payment crosses several systems, each built in a different era with its own rules. For a long time, getting all those systems to understand each other was an exercise in translating dialects: every payment network had its own format, with its abbreviations and truncated fields. ISO 20022 is the attempt —serious, global and already underway— to have them all speak the same language.
What ISO 20022 is
Before discussing migrations and message families, it's worth pinning down what the standard actually is. And the surprise is that its core isn't a file format, but a data model.
ISO 20022 is a global standard for financial messaging, built on a common, rich data model. Messages are usually expressed in XML (and also JSON) and describe concrete financial operations.
In one sentence: a single language so systems, banks and payment infrastructures understand each other with structured data, instead of translating between dozens of incompatible formats.
Why it exists
ISO 20022 didn't emerge in a vacuum. It was born from a concrete pain: the legacy standards were starting to fall short for today's payments world.
The earlier formats —SWIFT's MT messages and many national formats— carry limited data and don't interoperate well with each other. Each one trims the information in its own way, and crossing from one to another means truncating fields, guessing and losing detail. In the era of anti-money-laundering and end-to-end automation, that data poverty became an expensive problem.
ISO 20022 carries far more structured and rich information: for example, much more remittance detail (the "what for" of the payment) and about all the parties involved. That translates directly into three improvements:
- Compliance (AML). With complete, structured data on who pays whom and why, anti-money-laundering controls have something real to work with, instead of ambiguous fields.
- Automation. A message the machine understands unambiguously is a message that doesn't need manual intervention to be processed.
- Interoperability. A single language instead of many dialects: systems stop translating formats and start sharing the same model.
How it's organized
ISO 20022 isn't one giant message, but a catalog organized by purpose. Messages are grouped into families, and knowing three of them is enough to get your bearings in the payments world:
pain(payment initiation). The start of a payment: the instruction that goes from the customer to their bank to order a transfer. It's where the money's journey begins.pacs(payments clearing and settlement). The clearing and settlement between banks: the messages institutions exchange to actually move the money between them.camt(cash management). The cash management: account statements, notifications and reports about balances and movements.
A pacs.008 is, roughly, the modern equivalent of an MT103: the customer-to-customer credit transfer between banks, the most common operation in the payments world. The name changes; the purpose stays, but with far more structured detail behind it.
The global migration (happening now)
What makes ISO 20022 an urgent topic —and not a standards curiosity— is that the migration isn't a future plan: it's happening as you read this.
The world is moving from MT messages to ISO 20022 for cross-border payments. During the transition, both formats coexist: systems translate and route MT and ISO 20022 in parallel. That coexistence period with MT messages ends toward 2025, from which point ISO 20022 becomes the reference language for those flows.
It's not one isolated player's change: major infrastructures are adopting it in parallel —the Federal Reserve systems in the United States, TARGET2 in Europe and various national payment systems. When the money's backbone pipes switch languages at once, we're talking about one of the biggest changes to payment infrastructure in decades.
Legacy MT vs ISO 20022
| Feature | MT (legacy) | ISO 20022 |
|---|---|---|
| Format | Rigid text | Structured XML/JSON |
| Data richness | Limited | High, structured data |
| Interoperability | Low | High, global standard |
| Status | Being retired for cross-border payments | Standard adopted worldwide |
Common mistakes
The most frequent confusion about ISO 20022 is reducing it to a syntax change. It's a mistake that leads to completely underestimating the project.
"ISO 20022 is just a new format: XML instead of text." No. It's much more: a common data model. The real value isn't in the syntax, but in the rich, structured data that enables compliance, automation and less manual intervention. Stopping at "it's XML" is missing the change.
On top of that base idea hang two more misunderstandings that turn out costly:
- Believing "it's optional." For cross-border payments the migration is, in practice, mandatory: when the backbone infrastructures change, staying on MT stops being a viable option.
- Underestimating the challenge of translating and enriching data between MT and ISO 20022. Since MT carries less information, translating both ways means dealing with data truncation: rich ISO 20022 fields that don't fit into an MT, and MT fields that must be enriched to populate an ISO 20022. That "bridge" is where many projects stumble.
The banking angle
Seen from inside a bank, ISO 20022 is not a library update: it's a huge modernization project that touches payment systems, channels, reconciliation and compliance all at once.
The real work concentrates on four fronts:
- Data translation and enrichment between the old (MT) and the new (ISO 20022), handling truncation with surgical care.
- Testing exhaustively: every payment flow, every counterparty, every edge case, validated before touching production.
- Coexistence with the old throughout the transition: the two languages live side by side, and you have to route and translate without losing a single payment.
- Leveraging the rich data —not just meeting the format— to genuinely improve AML and interoperability. That's where the project's return lies.
ISO 20022 doesn't change what money does; it changes how we describe it. And speaking the same financial language —with rich, structured data— is the foundation for automating, at global scale, the movement of money. That's why, more than a format change, it's a change of foundations.
