ISO 20022 structured addresses

Prepare your payment environment for structured address requirements

Financial institutions increasingly exchange payment messages in ISO 20022, but the underlying address information often remains incomplete, inconsistent, or unstructured.

Moving to structured postal addresses requires institutions to review how data is collected, validated, and exchanged across corporate channels, internal applications, and payment systems.

What is changing with structured addresses

The transition to structured postal addresses is part of the financial industry’s broader adoption of ISO 20022 and efforts to improve the quality of cross-border payment information.

Under the planned CBPR+ requirements, postal addresses must use fully structured or hybrid formats where applicable.

Fully structured addresses

Address information is provided in dedicated ISO 20022 elements, with town and country required when a postal address is supplied.

Hybrid addresses

Town and country are provided in dedicated fields, while remaining address details can be included in up to two free-text address lines, subject to the applicable usage guidelines.

Swift extended the original November 2026 deadline following industry requests for additional preparation time. A revised implementation date has not yet been confirmed.

Industry readiness remains a challenge

Despite progress in ISO 20022 adoption, unstructured address information remains widespread. Swift’s October 2026 observations of CBPR+ pacs.008 traffic showed unstructured postal addresses in 46.5% of debtor elements and 49.6% of creditor elements.

This highlights a practical challenge for financial institutions: adopting ISO 20022 message formats does not automatically resolve data-quality issues in the systems that originate payment information.

What financial institutions need to prepare

  • 01
    Customer and corporate data
    Review how debtor and creditor addresses are captured in customer records, corporate payment files, ERP systems, and treasury applications. Identify missing or inconsistent information before it enters payment processing.
  • 02
    Payment channels and message mapping
    Check whether existing interfaces can capture and populate structured or hybrid postal address fields, including when instructions originate in legacy or proprietary formats.
  • 03
    Validation and exception handling
    Determine how incomplete or ambiguous address information should be identified and handled. Converting free-text data into structured fields may require additional validation or enrichment.
  • 04
    End-to-end payment processing
    Test address information across relevant payment flows to identify mapping issues, data loss, or downstream processing dependencies.

Evaluate your address data before implementation

The starting point is understanding how much of your existing address data can support structured or hybrid processing, and where additional remediation is required.

An assessment using representative payment data can help establish:

  • Which source systems and payment flows contain unstructured or incomplete addresses.
  • How reliably town, country, and other relevant elements can be identified.
  • Which records require correction or additional validation.
  • Where automated address processing can be introduced into the existing architecture.

Where automated structuring is needed, Catalyst Data Intelligence can support address correction, structuring, and enrichment. Institutions can evaluate the solution against their own data to assess accuracy and integration requirements.

Assess your structured address readiness

Identify gaps in your existing address data and determine the changes needed to support structured and hybrid ISO 20022 payment processing.