ISO 20022 was never really about the schema

The industry just spent years migrating payment messaging to ISO 20022, and a lot of the coverage framed it as a plumbing upgrade — swap the old fixed-width, cryptic message formats for structured XML. True, but that framing misses the point. The format was the easy part. The interesting part is the data the format finally lets you carry.

First, the state of play, because it’s further along than people realize. The Eurosystem moved its real-time gross settlement to ISO 20022 back in March 2023. The Clearing House migrated CHIPS in April 2024. The Fed’s Fedwire Funds Service adopted it in July 2025. This isn’t a someday-migration anymore; for high-value payments it’s largely the present.

So what actually changes? The old formats were starved for space. Names got truncated, remittance information got dropped, everything was squeezed into fields never meant to hold it. ISO 20022 messages are structured and roomy — they carry rich, labeled remittance data, properly separated parties, and purpose codes describing what a payment is for.

That last bit is where I think the real value hides, and where most institutions haven’t caught up yet. Consider what richer, structured payment data unlocks:

Reconciliation that mostly does itself. Structured remittance data means an incoming payment can carry the invoice it’s paying, cleanly. Less “which invoice was this 4,000 for?” guesswork — the matching the ledger needs, handed to you.
Sharper compliance signals. Properly separated parties and purpose codes give fraud and sanctions screening real fields to reason about, instead of scraping a free-text blob.
Straight-through processing. Fewer payments falling out to a human because a field was ambiguous or missing.

Here’s my actual take: the migration deadline forced everyone to accept the new envelope, but accepting an envelope and using its contents are different projects. Plenty of banks are shipping ISO 20022 messages while still throwing away most of the structured data on the receiving end — mapping it straight back down to the impoverished model their downstream systems already had. They did the hard integration work and kept the old habits.

The migration was mandatory. Actually using the data is optional, and that’s exactly why it’ll be the thing that separates the institutions that treated this as compliance from the ones that treated it as an opportunity. The schema was never the point.

Archie