Guide · CBPR+ 2026

Unstructured addresses: what the Swift and EPC delay changes

On 27 August 2026, Swift agreed to extend the structured-address migration for ISO 20022 payment messages. On 10 September 2026, the EPC in turn delayed the end of unstructured addresses in its five SEPA rulebooks. The migration is still planned, and finance teams gain from reviewing master data, exports and payment files now.

Written by Struct20022 · updated September 23, 2026

What the delay means for you

Swift is due to publish its revised schedule by December 2026 at the latest. The EPC removed the 15 November 2026 date from its SEPA rulebooks, and its Payment Scheme Management Board is set to fix a new date in October 2026.

Neither Swift nor the EPC has cancelled the migration. Fully structured remains the recommended target, including for the EPC, and hybrid remains an accepted transition format in the flows that allow it.

You now have time to review supplier, employee and customer master data, fix issues at the source and test with your bank before the next cut-off date.

What becomes risky

The pattern to watch is the fully unstructured address: one or more free-text lines where town and country are buried in the text.

When an address is transmitted in the relevant flows, teams need at least town and country to be identifiable in dedicated fields.

Start with a review

Historical files often mix full addresses, postcodes, country names, abbreviations and irrelevant columns.

A review keeps the transition from turning into an oversized project: you see which rows are usable, which need targeted cleanup and where to focus the effort.

The right sequence

Start with the files you submit to the bank, then work back to the master data sources that feed them.

The goal is to reduce rejection risk on priority flows during the transition, without rebuilding everything at once.

Preparation plan

  1. 1Identify in-scope pain.001 files and payment exports.
  2. 2Find blocks or rows that are only free text.
  3. 3Separate urgent fixes from cleanup that can wait.
  4. 4Test a sample with your bank or payment partner.
  5. 5Set a rule for new third parties created after the review.

FAQ

Does every address need to be fully structured?

Fully structured is the cleanest target. Hybrid can remain a practical transition when critical elements are provided correctly.

Should we start with the ERP?

Not necessarily. It is often faster to start with the files you submit to the bank, then work back to the sources that create the issues.

Does the delay cancel the migration?

No. Swift and the EPC only moved the timetable: fully structured remains the recommendation and hybrid remains an accepted transition in the flows that allow it. New dates are expected in October 2026 from the EPC and by December 2026 at the latest from Swift.

Official sources

Related guides

Use the delay to review without rushing

Start with a free audit to see the address risk row by row. Then request a quote if the volume calls for a contract.