All insights
ISO 20022 & Payment Data

More time to get address data right

The November 2026 deadline for removing unstructured postal addresses from ISO 20022 payment messages has been extended.

August 31, 2026
2 min read
More time to get address data right

Swift announced that it will defer all payments changes planned for Standards Release 2026. For structured addresses specifically, Swift will consult with banks, central banks, payment market infrastructures, market practice groups, and corporates to determine the revised timing and approach, with an update expected by December 2026 at the latest.

For financial institutions, this creates more preparation time. It does not change the direction of travel toward richer, more structured payment data.

Swift continues to encourage institutions to move forward with structured address adoption, noting that organizations that have already upgraded can benefit from using structured data today.

The reason is broader than compliance with a future deadline.

Address information is still frequently held across legacy systems, free-text fields, customer databases, and inconsistent data structures. Moving from an unstructured address to a structured or hybrid format therefore depends not only on the payment message itself, but also on the quality of the underlying data.

An address may contain the necessary information while still being difficult to process automatically if elements such as Town Name, Country, street information, or postal code cannot be identified consistently.

The scale of the challenge remains significant. Swift’s June 2026 data showed that 60.1% of debtor postal addresses and 61.4% of creditor postal addresses in the measured CBPR+ pacs.008 population were still unstructured.

The extension gives institutions an opportunity to address that challenge more systematically.

Use the extension to test your data

Rather than treating the additional time simply as a postponed implementation date, institutions can use it to understand how ready their address data actually is.

Key questions include:

  • How much of the existing address population can already be structured reliably?
  • How consistently can Town Name and Country be identified?
  • Where is information missing, ambiguous, abbreviated, or embedded within free text?
  • Which records can be processed automatically, and which require additional validation or review?
  • Where do recurring address-quality issues originate across customer, payment, and back-office systems?

These questions matter because address transformation becomes significantly more complex at scale.

Address conventions vary by country. The same location can be represented differently across systems. Important elements may appear in unexpected fields, be combined into a single line, or use local abbreviations and formatting conventions.

Testing against real institutional data provides a clearer view of where automation works reliably and where additional controls are required.

Look beyond one-time remediation

The extension also creates an opportunity to think beyond a single migration project.

If address structuring, validation, and enrichment become part of ongoing data and payment processes, institutions can improve information as it enters their systems instead of repeatedly correcting it downstream.

Better structured data can support greater automation, more effective compliance screening, improved transparency, and more consistent downstream processing.

The objective is therefore broader than preparing for the next deadline. It is about establishing a reliable way to maintain usable payment data over time.

Turning more time into better payment data

Catalyst Data Intelligence helps financial institutions structure postal address data for ISO 20022 payment flows.

The solution uses AI to transform unstructured postal addresses into structured address elements and supports the identification and enrichment of key address information, including elements such as Town Name and Country.

Designed for institutional environments, Catalyst Data Intelligence can be adapted to organization-specific data and deployed on-premise, helping institutions retain control of their data and models.

Institutions can use the extended timeline to assess their existing address population, test transformation accuracy against real data, identify records that require additional validation, and build address-quality processes that continue beyond the eventual migration date.

The deadline has moved. The value of better payment data has not.

Explore Catalyst Data Intelligence:
https://catalyst-suite.intellecteu.com/data-intelligence

Talk to our team:
sales@intellecteu.com

Frequently asked questions

Related resources

The Swift payments scheme is changing what banks must deliver, not just how fast payments move
November 23, 2026
5 min read

The Swift payments scheme is changing what banks must deliver, not just how fast payments move

Swift Modernization
Why financial institutions need explainable address structuring
November 19, 2026
2 min read

Why financial institutions need explainable address structuring

ISO 20022 & Payment Data
Preparing financial infrastructure for the post-quantum transition
November 17, 2026
8 min read

Preparing financial infrastructure for the post-quantum transition

Evolving Financial Infrastructure
Assessing the quality of structured address data in ISO 20022 payments
November 16, 2026
2 min read

Assessing the quality of structured address data in ISO 20022 payments

ISO 20022 & Payment Data
Why structured address goes beyond compliance
October 8, 2026
4 min read

Why structured address goes beyond compliance

ISO 20022 & Payment Data
Better address data, better payments: putting AI performance into practice
September 18, 2026
2 min read

Better address data, better payments: putting AI performance into practice

ISO 20022 & Payment Data
More time to get address data right
August 31, 2026
2 min read

More time to get address data right

ISO 20022 & Payment Data
Discuss your next integration challenge

Modernize what needs to change.
Preserve what already works.

Talk to our team about payment integration, Swift modernization, Alliance Cloud migration, ISO 20022, or evolving financial network requirements.