ISO20022 - Structured Address Change
The ISO 20022 structured address requirement is one of those changes that can easily be underestimated. It sounds like a bank format topic. Something for the payments team, or maybe for the integration team. But in practice, it reaches much further.
By 15 November 2026, payments that contain postal address data need to use a structured or hybrid address format. Fully unstructured address lines, where the town or country is hidden somewhere in free text, will no longer be accepted for many payment types. If the required address elements are missing or not mapped correctly, payments may be delayed or rejected.
For insurers, this is especially relevant. Payment processes are often spread across SAP FI-AP, FI-CA, FS-CD, mainframe systems, HR/Salary systems, treasury systems, policy systems, claims platforms, broker solutions and bank portals. Address data can come from multiple sources and may have been built up over many years of migrations, conversions and local process exceptions.
So this is a good moment to check whether your organisation has actually done what is needed. Are your payment formats ready? Is your business partner and vendor data clean enough? Are town and country available as proper fields? Are your DMEE/DMEEX trees adjusted? Have your banks confirmed their exact requirements and timelines?
This blog is a practical heads-up for insurers running SAP finance and insurance subledger processes. What is changing, why does it matter, where are the risks, and what should you verify before the November 2026 deadline?
Do not wait for rejected payments
From November 2026, unstructured address data can stop payment processing. For insurers, this is not just a bank format update. It touches FS-CD, FI-CA, FI-AP, master data, payment media and every interface feeding your payment runs.
Background and drivers…
ISO 20022 payment standards are moving away from unstructured postal addresses to improve data quality and regulatory compliance.
Several regulatory and industry initiatives underpin this change:
FATF Recommendation 16 and European law
regulators require that the sender and beneficiary addresses used in payments include, at minimum, town/city name and country. Unstructured addresses often leave these elements missing or hidden in a free‑text line. BNP Paribas notes that unstructured addresses create false positives in sanctions screening and therefore payments containing only free‑text addresses will be rejected after 15 Nov 2026.
ISO 20022 data quality
the standard introduces dedicated fields (e.g., department, street name, building number, post code, town name, country) which improve straight‑through processing and reduce manual intervention. Nordea’s guidance explains that structured addresses have been available since Nov 2025; hybrid and structured formats improve sanction screening and fraud detection, while unstructured addresses will no longer be accepted after Nov 2026.
Clearing system migration
SWIFT’s cross‑border payments (CBPR+), SEPA schemes and domestic high‑value systems (e.g., UK CHAPS, Danish instant payments, Swedish Swish) are migrating to ISO 20022. JP Morgan’s FAQ notes that, since Nov 2026, if an address is provided for any party in a payment instruction, it must be delivered in a structured or hybrid manner with at least town name and country; incomplete or missing elements will cause the transaction to be rejected..
Unstructured postal addresses will be rejected
ISO 20022 introduces dedicated XML elements for street name, building number, post code, town name and country. From 15 November 2026 banks and clearing systems will reject payments that contain only free‑text address lines without at least the town and country information.
Payment types affected…
At least the following payment types are affected by the ISO 20022 structured address requirement. The exact scope can differ per country, payment channel and bank, so you should always confirm your own impact with your banking partners:
SEPA Credit Transfers
If address data is included for the debtor, creditor, ultimate debtor or ultimate creditor, it must be provided in a structured or hybrid format.SEPA Direct Debits
Address data used in SEPA direct debit files must also follow the structured or hybrid approach when included, especially in cross-border or non-EEA related scenarios.Cross-border SWIFT / CBPR+ payments
International payments are clearly in scope. Address data for the payment parties can no longer be sent as fully unstructured free text.Urgent domestic and RTGS payments
High-value or urgent domestic payments processed through real-time gross settlement systems are also affected.Swedish domestic payments
Swedish domestic payment flows, including relevant bank file and domestic clearing channels, should be checked for structured address readiness.Danish domestic and instant / express payments
Danish local and urgent payment types are also moving away from unstructured postal address data.UK CHAPS payments
CHAPS payments are part of the wider ISO 20022 structured data movement and should be included in the impact assessment.Polish high-value domestic payments
Polish high-value payment flows should also be reviewed for structured or hybrid address requirements.
Keep the money flowing
Use the action plan below to find your gaps in master data, payment formats and bank readiness before November 2026.
Your action plan…
So, what are the next steps?
Audit every payment channel
List all systems that generate payments: SAP systems like FS‑CD, FI‑AP, FI‑CA, but also Mainframes, Salary, treasury, payroll and manual bank portals. Identify which payment methods (SEPA, cross‑border, instant) they use and which file formats (pain.001 v3, pain.001 v9, domestic DTAZV etc.) they generate.
Verify impact of your file formats
If you use old file formats like pain.008.001.02/pain.001.001.03 for now (always check at your bank and don’t trust a random blog online). So, if these already use Hybrid or Structured adresses then you might be good for November 15th.
Upgrade your file formats
Move from legacy/outdated formats to ISO 20022 version 2019 (pain.001.001.09 for credit transfers, pain.008.001.08 for direct debits). This version supports fully structured addresses and will soon be mandatory.
Cleanse your master data
Ensure that every business partner, policy holder and vendor record contains town/city and country fields. Where possible, capture street name, building number and post code separately. Consider using address‑normalisation tools or third‑party services to infer missing details. The longer you wait, the larger this data‑quality project will become.
Adapt your SAP format trees
In ECC and S/4HANA, payment files are built with DMEE/DMEEX format trees. The standard CGI templates for pain.001.001.09 are comprehensive but rarely plug‑and‑play. Clone them and remove unused segments. If needed (standard does have them), add the StrtNm, BldgNb, PstCd, TwnNm and Ctry fields to the Creditor/Debtor and Ultimate Creditor/Debtor segments. Set conditional logic for hybrid vs fully structured addresses. Import any OSS notes delivering the V09/V08 templates if they are missing.
Update payment method Customizing
Assign the new file formats to your payment methods in FI‑AP and FI‑CA/FS‑CD. Define instruction keys for express payments and specify whether addresses are mandatory. Test across all banks you use – some may request additional fields or reject files with duplicate address lines.
Test early and often
Don’t wait for November 2026. Book testing slots with your banks now. Validate that your new payment files contain the correct address elements and pass the bank’s validation. Use pain.002 and camt.054 messages to monitor acceptance and fix issues quickly.
Get help if you need it
If this feels overwhelming, you’re not alone. Your bank can help you in this change. If needed, a short discovery call can help you map the gaps, decide between hybrid and fully structured addresses and plan the necessary OSS notes and DMEE adjustments.
Conclusion…
The impact may be small. Maybe your banks already handle most of it. Maybe your SAP payment formats are already close to where they need to be. But you only know that after you have checked your payment flows, master data and bank requirements.
Finding out on 16 November 2026 means rejected payments…
Sources I used for this blog post:
BNP Paribas — ISO 20022 for Corporates Newsletter 2026 #1: The End of the Beginning, February 2026.
https://cashmanagement.bnpparibas.com/sites/default/files/2026-03/ISO20022%20Newsletter-1%202026%20English.pdf
ING Netherlands — Nieuw bestandsformaat SEPA-betalingen, versie 2019, Q&A.
https://www.ing.nl/zakelijk/betalen/betalingen-doen/nieuw-bestandsformaat-sepa-betalingen
Nordea — Navigating payment changes: ISO 20022 and address requirements in 2026.
https://www.nordea.com/en/news/navigating-payment-changes-iso-20022-and-address-requirements-in-2026
Nordea — Corporate Payments Service Payment Initiation Message: Postal Address Changes, version 1, April 2026.
https://www.nordea.fi/Images/147-567869/cps_postal_address_changes_2026_en.pdf
Cambridge Currencies — ISO 20022 in 2026: Critical Deadlines After November 2025, Complete Guide, updated February 5, 2026.
https://cambridgecurrencies.com/iso-20022-guide-2026/
Danske Bank — Payments: Changes to Postal Address Requirements.
https://danskeci.com/ci/transaction-banking/instructions/integration-services/postal-address
J.P. Morgan — ISO 20022 Frequently Asked Questions.
https://www.jpmorgan.com/insights/payments/fx-cross-border/iso-20022-faqs
Banking.Vision — DTAZV will be phased out in November 2026 — Here’s what Corporates and SAP Customers need to prepare for now, April 7, 2026.
https://banking.vision/en/dtazv-iso-20022-corporates-and-sap-customers/
