ISO 20022: Your D365 Questions. Answered.

Everything Dynamics 365 Banking, Treasury, and Finance teams need to know about the November 2026 structured address deadline – and how to get compliant in time.

From November 2026, financial institutions across Europe must have moved to structured address data for SEPA and SWIFT CBPR+ payment messages. For Microsoft Dynamics 365 customers, this is as much a data quality question as it is a compliance one – whether you are ready largely depends on how address data is currently stored and mapped within your D365 environment.

This FAQ walks through what is changing, why it specifically affects D365 customers, what needs to be assessed before the deadline, and how SKG Services Europe can help you get compliant in time.

This FAQ will give you the answers you need to be prepared for the ISO 20022 update.

Q: What Is ISO 20022 and what changes in November 2026?

ISO 20022 is a global messaging standard used for exchanging electronic payment data between financial institutions. From November 2026, the standard requires structured – rather than free-text – address data for SEPA payments and cross-border transactions processed via SWIFT CBPR+.

Q: What Is structured address data under ISO 20022?

From November 2026, financial institutions are required to have transitioned to structured address data. After that date, fully unstructured addresses – a single free-text line – will no longer be accepted. In practice, this means an address must be broken into separate tagged fields – street, building number, postal code, and so on – rather than submitted as one block of text. Hybrid formats, where structured fields are present alongside a free-text component, remain permitted; it is the fully unstructured case the deadline specifically targets.

Q: Does ISO 20022 apply to SEPA Payments, or only Cross-Border?

The structured address requirement applies specifically to SEPA payments and cross-border transactions. That covers both intra-EU SEPA payments and cross-border transactions processed via SWIFT’s CBPR+ messaging standard, so any organisation making or receiving payments through either channel needs to prepare – not only companies with cross-border-heavy banking relationships.

ISO 20022 compliance checklist for D365

Q: Is there an ISO 20022 compliance checklist for Microsoft Dynamics 365?

Companies need to review the addresses used for payments and collections, and ensure the payment format has been updated to the structured version. In practice, this means auditing vendor and customer master data for free-text addresses, correcting the underlying fields, and confirming that outbound and inbound payment formats are configured to use the structured tags rather than the legacy single-line format.

Q: How long does ISO 20022 remediation take in D365?

Testing the new structured address formats is required, and this step can be time-consuming. The data cleanup itself can often be scoped and completed relatively quickly once the affected records are identified. Testing the updated payment formats end-to-end with your banks is usually the longer part of the process, since it depends on your banking partners’ own testing windows and response times.

How SKG SE helps achieve ISO 20022 compliance

Q: How does SKG support ISO 20022 compliance for D365 customers?

For companies that are not already TAS (Treasury Automation Suite) customers, SKG can support TAS implementation, which brings the structured ISO 20022 payment format capability. Alongside this, SKG reviews the underlying D365 address data so the new formats have accurate data to work with.

Q: What is TAS Light and how does it support ISO 20022 readiness?

TAS Light is SKG’s entry point into the Treasury Automation Suite, bundling our most-requested modules: Vendor Payment Automation, Payment Factory Automation, and Bank Statement Automation, built on BankFabric – our engine for secure, two-way bank communication – along with two bank formats (inbound and outbound) and bank format development included.
For ISO 20022 readiness specifically, that included format development is what allows SKG to build or update your payment formats to the structured standard as part of the implementation.

Book a demo to see how this applies to your environment: skg-services.eu/contact

Who owns ISO 20022 compliance: Treasury, IT, or Finance?

Q: Who is responsible for ISO 20022 compliance?

Ownership varies by organisation – it can sit with treasury, IT, or finance, depending on how the company is structured. In most cases, it also needs sign-off or awareness from whoever manages D365 master data, since the underlying fix touches vendor and customer records directly.

Q: What should a CFO know about the ISO 20022 deadline?

If this isn’t addressed, payments with unstructured addresses will be rejected outright after November 2026 – a direct, operational consequence for outgoing payments and cash flow, not just a compliance footnote.

Ready to Automate Your Financial Operations?

Schedule a conversation to see how secure automation can improve efficiency and accuracy for your banking and treasury transactions.