Decoding the ISO 20022 Migration

In November 2026, the ISO 20022 deadline for decommissioning SWIFT's current postal address schema comes into effect. This means every payment instruction will now include a structured address. This changes the free-text block into discrete, defined fields. If the address is unstructured, it will be rejected and returned. This marks the final step in the ISO 20022 migration.

On the surface, this is a data schema change. That may be true, but underneath, there are a few interesting things to note.

First, SWIFT has been in effect since the 1970s, so all address data used today is in free text. This data now has to be parsed, validated, and restructured into the new discrete fields. This is an extra-large-scale data migration program. While generative AI will make it easier, human validation is still needed because the liability won't shift away from the institutions. If the migration doesn't happen cleanly, the only option is to go back to the customer and ask them for the address. This means creating a new flow to gather this data from customers. Some customers will not respond on time, which means their payments will fail. This becomes a large customer-facing outreach effort, which may not have been factored in.

Second, the free-text address field was a common reason for false positives in sanctions screening. Using structured, discrete data fields will improve automation rates, enhance sanctions quality, and reduce the number of flags routed to manual review. This will have a positive impact overall on the industry's cost structure.

Third, it will also impact the evolution of stablecoins in cross-border payments. One of the USPs of stablecoin rails was the ability to carry much richer data. After the SWIFT migration, this advantage for stablecoins narrows. SWIFT will also have structured purpose codes, remittance data, and identifiers for both the parties. ISO 20022 will also become the standard messaging format, and stablecoins will be expected to match it. This clarity should likely increase the rate at which stablecoin rails become mainstream.

Fourth, this migration is likely to highlight the gap between smaller and larger institutions. Smaller companies are more likely to have treated this as a one-off migration or done the minimum to keep messaging flowing, whereas larger institutions would have treated this as a multi-year data migration project. The absence of clean, structured data in the right format will lead to higher rejection rates and customer frustration. This could mean a shift in market share of larger vs smaller institutions.

And lastly, as the data becomes standardised, the rail becomes standardised. Value capture will shift from the rails to the orchestration layer, making faster, cheaper, and compliant processing more valuable than it is today.