CBPR+ 2026: how to prepare while Swift updates the timetable
On 27 August 2026, Swift announced an extension for the payment changes linked to structured addresses. The timing and approach will be clarified by December at the latest, while finance teams should continue reviewing master data, exports and payment files.
Written by Struct20022 · updated August 29, 2026
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.
Why start with a review
Historical files often mix full addresses, postcodes, country names, abbreviations and irrelevant columns.
A review prevents the transition from becoming an oversized project. It shows which rows are usable, which need targeted cleanup and where effort should be concentrated.
The right sequence
Start with the files actually submitted to the bank, then work back to the master data sources that feed them.
The goal is not to rebuild everything at once, but to reduce rejection risk on priority flows during the transition.
Preparation plan
- 1Identify in-scope pain.001 files and payment exports.
- 2Find blocks or rows that are only free text.
- 3Separate urgent fixes from cleanup that can wait.
- 4Test a sample with your bank or payment partner.
- 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 files actually submitted, then work back to the sources that create the issues.
Official sources
Related guides
Prioritize rows to fix while Swift updates the timetable
A Struct20022 review gives you a clear row-by-row view of address risk before launching a broader project.