What is ISO 20022, and why did every bank have to change?

What was actually wrong with the old format

The MT formats were designed when message length cost money. Addresses, names and payment purposes were crammed into a small number of free-text lines, and there was no reliable way to know which line held the beneficiary's city and which held their street.

For a human reading one payment, this is fine. For a machine screening ten million payments a day against a sanctions list, it is a catastrophe. Systems could not distinguish a person from a place from a reference number, so they matched on strings and generated enormous volumes of false positives, each of which a human had to clear.

ISO 20022 fixes that by giving every element its own labelled field. A name is in the name field. A country is in the country field. The screening system stops guessing.

The three things it actually buys you

Better screening. Structured parties mean fewer false hits and fewer payments held for manual review. This is the reason regulators pushed hardest.

Reconciliation that works. The standard carries far more remittance information, so a corporate receiving a payment can match it to an invoice automatically instead of ringing the customer to ask what it was for.

A common language across rails. Domestic instant systems, high-value systems and cross-border messaging converge on the same vocabulary. Aani in the UAE was built on ISO 20022 from day one. A payments engine written once starts to work in more than one place.

Why the deadline was necessary

Migration was slow because the work is unglamorous. It is not a feature, it is a data project, and it touches every system that has ever stored an address as a single string.

Coexistence began in March 2023 with both formats accepted, and translation services in between. Adoption crept rather than jumped. The deadline of 22 November 2025 existed precisely because a voluntary standard with a translation fallback gives every institution a reason to be last. Beyond that date, in-scope cross-border payment instructions must be exchanged in ISO 20022, with contingency handling for stragglers that is deliberately made expensive.

For years, everyone sent parcels with a handwritten note taped to the lid. It worked, because a person read the lid. Then the volume grew past what people could read, and a machine had to sort them. The machine cannot read handwriting. So everybody had to start filling in the form, and there had to be a date after which the handwritten lid was refused.

What comes after the deadline

The standard is not finished with anyone. Unstructured postal addresses are being retired in stages, with the fully unstructured form disappearing from cross-border messaging during November 2026 and a hybrid form permitted in the interim.

If you are building anything that touches a bank, treat address capture as a first-class data model rather than a text box. The systems that are struggling right now are almost all struggling with the same thing: thirty years of addresses stored as one long line, and no way to work out where the city was.

Where you meet it

Every cross-border payment sent today. Every address form that suddenly grew four new required fields. Every corporate that quietly stopped calling you to ask what a payment was for.