Swift has extended the deadline for the migration to structured postal addresses in ISO 20022 payment messages, following requests from banking communities and domestic payment market infrastructures for more time.
The change was originally expected to take effect in November 2026 as part of Standards Release 2026. However, Swift has confirmed that payment-related changes under this release will be deferred while it consults further with banks, central banks, payment market infrastructures, market practice groups and corporates.
For correspondent banks, the extension provides useful breathing room — but it should not be treated as a reason to slow down. The move towards structured, high-quality payment data remains firmly in place.
Structured addresses are more than a formatting change. They are part of the wider shift towards richer, cleaner and more transparent payment data under ISO 20022.
Today, many addresses still sit in free-text fields. This creates inconsistency and ambiguity across payment chains, especially in cross-border and correspondent banking relationships. Address details may be incomplete, abbreviated, placed in the wrong order or formatted differently across systems and jurisdictions.
For correspondent banks, this creates real operational and compliance challenges. Poor address quality can affect:
Structured address data helps reduce ambiguity by separating key address elements into defined fields, such as town, country, postal code, street name or building details where available. This supports more effective screening, better payment routing and stronger data governance.
Swift’s structured address requirement for ISO 20022 payment messages was originally due to form part of Standards Release 2026. Following industry feedback, Swift has deferred payment-related changes and will confirm the revised timing after further consultation.
An update on the structured address timeline is expected by December 2026 at the latest, as part of Swift’s governance cycle.
Importantly, not all Standards Release 2026 changes are moving on the same timeline. Securities and trade-related updates, including changes supporting the move to T+1 settlement in certain markets, have been decoupled from the payments timeline and are expected to proceed separately in the first quarter of 2027.
This means institutions need to manage two tracks: a revised timeline for payment-related structured address changes, and a separate implementation path for securities and trade updates.
The extension does not change the direction of travel. Swift has encouraged institutions that are already able to support structured addresses to continue using them across the network.
The wider ISO 20022 migration is already well advanced, with the vast majority of payment instructions now sent in ISO 20022 format. The next stage is about improving the quality, completeness and usability of the data within those messages.
For correspondent banks, this is especially important. Correspondent banking depends on trust, transparency and accurate counterparty data. Weak or inconsistent address data can create friction across the payment chain and increase exposure to financial crime, operational and regulatory risk.
The deferral gives banks more time to prepare, but the most effective institutions will use this period to strengthen their data foundations.
Banks should start by assessing the quality of address data across customer, counterparty and correspondent banking records.
Key questions include:
This audit should cover upstream and downstream systems, including onboarding platforms, customer due diligence systems, payment gateways, screening engines and reference data repositories.
Many institutions still rely heavily on legacy address fields. These may work today, but they create challenges when data needs to be mapped into structured ISO 20022 formats.
Banks should identify where free-text addresses are used and where parsing, cleansing or enrichment will be required. This is particularly important for correspondent banking relationships, where incomplete or inconsistent data can affect screening outcomes and payment processing.
Structured messages are only as good as the data used to populate them. Banks need access to accurate, current and well-governed reference data for legal entities, financial institutions, counterparties and addresses.
High-quality reference data can help institutions:
For correspondent banks, reference data quality is central to understanding who they are transacting with, where counterparties are located and how relationships are connected.
Structured address migration is not just a payments technology project. It affects compliance, financial crime, operations, onboarding, client data, reference data and relationship management teams.
Institutions should establish clear ownership across functions, with governance covering:
Without cross-functional governance, firms risk solving the message-format problem without addressing the underlying data-quality issue.
A successful transition requires coordinated action across the payment chain. Banks should communicate early with corporate clients, respondent banks, technology vendors and payment partners about future data expectations.
This may include updating onboarding forms, client portals, payment templates and data submission requirements. Clients and counterparties should understand that generic, incomplete or unstructured address formats may eventually create payment delays, repairs or rejections once new rules are enforced.
Institutions that are already prepared should not wait for the revised deadline. Using structured addresses now can help reduce future technical debt and allow teams to test data quality, workflows and screening performance ahead of mandatory enforcement.
Early adoption also gives banks more time to resolve edge cases, such as jurisdictions with unusual address formats, incomplete registry data or inconsistent customer records.
Structured address adoption can deliver clear benefits for financial crime controls.
Better address data can improve sanctions screening, reduce false positives and support more accurate customer and counterparty matching. This is particularly important where names are common, transliterated or shared across multiple entities.
For correspondent banks, richer and more structured data can also support better visibility into payment chains and nested relationships. This can strengthen due diligence and improve the quality of information available for investigations, reviews and regulatory reporting.
The structured address deferral highlights a broader point: ISO 20022 is not simply a messaging standard. It is becoming a catalyst for better financial data.
The institutions best prepared for the next phase will be those that treat ISO 20022 as part of a wider data strategy covering:
As payment data becomes more structured, poor source data will become more visible. Firms that invest now in clean, governed and well-structured data will be better positioned for future payment, compliance and regulatory requirements.
Swift’s decision to defer the structured address deadline gives the industry more time, but it does not change the destination.
For correspondent banks, the message is clear: use the extension wisely. Audit address data, strengthen reference data, align internal teams, engage counterparties and continue implementation where possible.
Structured address migration should not be viewed only as a compliance requirement. Done well, it can improve payment transparency, reduce operational friction, enhance screening performance and create stronger foundations for the future of cross-border payments.
