Key Milestones

• From November 2026, the Swift network will no longer accept unstructured postal addresses in CBPR+ ISO 20022 payment messages.
• Payment Market Infrastructures (PMIs), including SEPA and CHAPS, are expected to align with these requirements.
• A Hybrid Address option was introduced in November 2025 to support phased adoption ahead of the 2026 deadline.

Introduction

Beginning in November 2026, Swift will reject payment messages that contain fully unstructured (free-text only) postal addresses. To remain compliant, financial institutions must adopt either a Fully Structured or a Hybrid address format in ISO 20022 messages.

This change forms part of the broader ISO 20022 data quality initiative aimed at improving transparency, screening effectiveness, and straight-through processing across the global payments ecosystem.

What is Structured v Hybrid?

Fully Structured Address
All address components are provided in dedicated structured fields. No free-text address lines are permitted.

Hybrid Address
Town/City and Country must be provided in structured fields.
Up to two free-text address lines are permitted for supplementary details.
Free-text lines must not duplicate information already included in the structured Town/City field.

While the hybrid model provides short-term flexibility, the fully structured approach represents the long-term target state.

Which fields are affected?

The mandate applies to customer and agent address information within payment messages, including:

• Debtor / Ordering Customer
• Creditor / Beneficiary Customer
• Ultimate Debtor and Ultimate Creditor, where explicitly identified
• Agents, including:
  • Instructing Agent
  • Debtor Agent
  • Creditor Agent

Although most agents are identified by BIC, any address information provided must comply with the structured or hybrid format rules.

What Happens Next – And How to Prepare

This is not a simple formatting update. For many institutions, the challenge lies in legacy data architecture, upstream customer channels, and internal processing systems.

1. Assess Impact Across Systems

• Identify all systems storing or generating address data.
• Map where unstructured address fields exist.
• Review inbound customer data capture processes.
• Assess screening, compliance, and downstream reporting dependencies.

The core effort will involve restructuring legacy free-text address data into compliant formats.

2. Decide: Hybrid as a Bridge or Full Structured Target?

While hybrid addresses provide a transition path, institutions should carefully consider their long-term strategy:

• Unstructured → Hybrid → Structured creates duplicate transformation effort.
• Moving directly to Fully Structured where possible reduces future remediation costs.

Ideally moving direct to Structured would be the best plan but with a November 2026 deadline this may not be achievable based on the scope of changes internally.

3. Leverage Available Tools

Swift AI Address Structuring Model
Swift has released a free, open-source AI-based tool (available since November 2025) that uses natural language processing (NLP) to extract structured components such as Town and Country from legacy unstructured data.

However:

• It is not a complete solution.
• Manual validation and data governance controls remain essential.
• Ongoing data quality monitoring will be required.

4. Implement Translation and Enrichment Rules within Transformer

Once transformation logic is defined:

• Establish consistent address enrichment and validation rules.
• Apply these rules at ingestion points within Transformer.
• Embed these Transformer Services within your payment processing

The critical task is not the technology itself — it is identifying the data gaps, defining the rules, and embedding governance controls to sustain compliance.  Once this is understood then applying the rules within Transformer to your mappings is key.

Final Thoughts

The remediation effort — particularly for institutions with fragmented legacy systems — required before the November 2026 deadline can be significant.

The key considerations are:

• Data quality over format compliance
• Long-term “structured strategy” vs. short-term “hybrid workaround”
• Governance and validation controls
• Early engagement with upstream data providers

Institutions that treat this as a strategic data quality initiative rather than a technical messaging update will be better positioned to meet regulatory expectations and enhance operational resilience.