ISO 20022: address requirements change in November 2026

Address requirements in payment messages will change in November 2026. For many payment types, unstructured address lines will no longer be sufficient, and address details will need to be provided in either a structured or hybrid format.

The change may affect more organisations than initially expected. Address information used in payments often originates in ERP systems, payroll solutions, accounts payable platforms, expense management tools, vendor master data and other source systems long before a payment reaches the bank.

When will the ISO 20022 address change take effect?

The new requirements are expected to take effect in November 2026. From that point onwards, payment messages relying solely on unstructured address fields will no longer be accepted in payment types covered by the new rules.
According to Swift, unstructured addresses will no longer be supported in CBPR+ ISO 20022 payment messages from 14 November 2026. The European Payments Council (EPC) has set 15 November 2026 as the date when unstructured address formats will be phased out for SEPA payments.

As implementation details may vary, organisations should confirm the exact requirements and timelines with their banking partners and payment solution providers. Banks may introduce their own validation rules, guidance and readiness schedules.

Who will be affected?

The change affects organisations that send payment files to banks through ERP systems, accounts payable solutions, payroll systems, travel and expense platforms, treasury tools or other financial management applications.
The impact extends beyond bank connectivity or payment execution. It may affect vendor records, customer data, business partner information and the way address details are collected, stored and transferred between systems.

Based on current guidance, the change will affect international payments and many domestic and euro payments, including SEPA transactions. For this reason, organisations should review the entire payment process rather than focusing solely on payment files or bank interfaces.

What is changing in payment address data?

In many scenarios, address information will no longer be accepted as a free-text address entered into one or more address lines.
Instead, key address components, including at least the city and country, must be provided in dedicated data fields.

Going forward, address information can generally be supplied in two accepted formats:

Structured address
A fully structured address contains separate fields for individual address elements, such as:

• Street name
• Building number
• Postal code
• City
• Country

This is the preferred long-term approach where source systems and integrations support structured address data.

Hybrid address

A hybrid address combines structured and free-text data. City and country are provided in dedicated fields, while certain additional address details may still be included in limited free-text lines.

For organisations that are not yet able to fully structure all address information, a hybrid approach may provide a practical transition path.

For applicable payment messages, the use of purely unstructured addresses will be discontinued in November 2026.

Why does this matter?

The change is more than a technical format update. Structured address data improves payment quality, supports straight-through processing and enhances transaction screening and compliance checks.

When information such as city and country is available in clearly defined fields, payment participants can be identified more accurately and payment journeys become more transparent.

From a business perspective, the risk is straightforward: if address data does not meet the required format, payments may be delayed or rejected.
This can lead to additional manual work, delays in supplier payments and unnecessary disruptions to financial operations.

How should organisations prepare?

Preparation should begin well before the November 2026 deadline. In many cases, the largest effort will not be related to payment transmission itself, but to the quality of master data and the systems that generate payment information.
Address data may originate in vendor master records, be enriched during invoice processing and eventually flow into a payment file. If the underlying information is incomplete or unstructured, issues may only become visible when the payment is submitted.

1. Identify systems that generate payment files

Review all systems involved in payment processing, including:

• ERP platforms
• Accounts payable solutions
• Payroll systems
• Travel and expense systems
• Vendor master data repositories
• File-based or spreadsheet-driven payment processes

2. Assess the current address data structure

Determine whether key information such as city and country is stored in dedicated fields or embedded within free-text address lines.
Pay particular attention to international counterparties and supplier records.

3. Review integrations and data flows

Having the correct information in a source system is not enough if integrations or payment file generation processes fail to pass the data through in a structured format.

4. Clean and enrich master data

Create a plan for completing missing country and city information and, where necessary, converting unstructured addresses into structured data fields.

5. Test with your banking partners

Run validation checks and test payments well before the deadline. Early testing helps identify issues while there is still time to resolve them.

6. Update data governance and processes

Review data-entry practices for suppliers, customers and business partners to ensure address information is captured correctly from the outset.
A simple rule of thumb: if an address currently exists only as a single free-text line in a payment process, it should be reviewed. Ensuring that city and country information is available in dedicated fields should be a priority.

How Azets can help

Azets helps organisations understand how the ISO 20022 address requirements may affect payment processes, source systems and master data quality.
Through our payment and treasury services, we help businesses assess payment file readiness, review data flows and identify areas requiring remediation before the November 2026 deadline.

We can support organisations in:

• Mapping payment-generating systems and processes
• Identifying incomplete or unstructured address data
• Assessing the readiness of source systems and integrations
• Validating payment files against bank-specific requirements
• Planning and coordinating testing activities
• Establishing controls to identify issues before payments are rejected
• Monitoring payment processes during the transition period
• Providing post-implementation hypercare support

Preparing early reduces risk, minimises disruption and helps ensure a smooth transition to the new ISO 20022 address requirements.

Would you like to ensure your payment files comply with the upcoming ISO 20022 address requirements? Contact us on +358 10 756 4500 or email us at myynti@azets.com