Why this matters

ISO 20022 provides a common framework for describing and exchanging financial information. One of its advantages is the ability to represent information with greater precision. Instead of relying on free-text address lines, structured addresses identify individual elements such as street names, building numbers, towns and countries.

The difficulty lies in the existing payment ecosystem. Address information may originate in corporate ERP systems, pass through treasury applications and banking platforms, and ultimately reach multiple banks and payment infrastructures. Data that has worked for years in established processes may not be sufficiently structured for more automated processing, including compliance checks and straight-through processing.

For banks, the challenge extends beyond supporting a new message format. Different payment communities, including SEPA and SWIFT CBPR+, apply ISO 20022 through their own market practices and implementation requirements. Ensuring that payment data remains consistent, meaningful and usable across these environments is therefore an important part of payment modernisation.

Key Takeaways

ISO 20022 is about meaning, not just messaging

ISO 20022 goes beyond defining how financial messages are represented. It provides a common semantic foundation for financial information, enabling systems to identify what individual data elements mean. This distinction is essential for automation, interoperability and the reliable exchange of payment information across different systems.
 

Structured addresses expose underlying data quality challenges

An address can be complete and understandable to a person while remaining difficult for another system to interpret. Moving towards structured information makes existing inconsistencies in master data more visible and requires banks and corporates to consider how that data is captured, maintained and transferred.

Implementation requirements depend on the payment environment

There is no single global ISO 20022 deadline for structured addresses. Payment communities establish their own requirements and transition schedules, which can change over time. Banks and corporates therefore need to understand the rules that apply to their specific payment schemes, message versions and banking relationships.

Better payment data supports automation and compliance

Structured information reduces the need for downstream systems to interpret free text. This can support more reliable payment processing, sanctions screening and other compliance activities. The underlying objective is not simply to introduce additional fields, but to preserve the meaning of payment information throughout the processing chain.

In this Episode

We explore how structured addresses illustrate some of the wider challenges of ISO 20022 adoption, including:

  • SO 20022 beyond XML
  • structured, unstructured and hybrid addresses
  • automation and payment transparency
  • master-data quality across payment systems
  • SEPA and SWIFT CBPR+ requirements
  • changing implementation timelines
  • implications for corporates and multibanking platforms

The central question is not simply how banks and corporates can comply with new address-format requirements. It is how they can improve the quality and consistency of payment data across existing systems while adapting to evolving standards without disrupting established payment processes.

Related Insights

Continue exploring ISO 20022, structured addresses and payment-data quality:

Blog Article

Structured Addresses: Why Is Something So Simple Becoming So Complicated?

Read the article

Listen to this Episode

Choose your preferred platform: