ISO 20022 address compliance: how legacy formats are impacted

In our previous three articles on ISO 20022 address management, we covered what is changing with the November 2026 deadline, what a global enterprise learned firsthand from their migration, and how banks are planning to respond. The picture that emerged was consistent: the data gaps are real, the timeline is tight, the organizational complexity is underestimated, and banks are not all aligned.

Nowhere is that misalignment more visible than in legacy formats. AFB320 in France, DTAZV in Germany, AEB34 in Spain, all these formats have served corporate treasuries for years. But they were built for a different era of payment infrastructure, and many cannot carry structured address data in the way ISO 20022 now requires.

The response from local regulators has been uneven. Some countries recognized the limitation early and mandated a full migration to ISO 20022 XML. Others have done little, leaving corporate treasury teams in a challenging situation: the November 2026 deadline applies to cross-border payments regardless of which local format you use to submit them. If the format cannot carry a structured address, the answer is migration, not a workaround.

In this article, let’s look at the situation country by country.

Switzerland: the early migration that worked

Switzerland is the clearest example of what an orderly transition looks like. SIX Group, the principal financial market infrastructure operator in the country, began its ISO 20022 migration in 2016, a decade ahead of the cross-industry deadline. The Swiss Interbank Clearing (SIC) system was converted in full, and by 2018 customer-to-bank credit transfers had begun their move to XML pain formats.

In 2024, SIX published guidelines for migrating from the 2009 version of the ISO 20022 standard to the 2019 version, simplifying payment types, adding support for new fields including the Legal Entity Identifier (LEI) and Unique End-to-end Transaction Reference (UETR), and enabling Instant Payment. The legacy DTA formats are now fully decommissioned.

The result is that the Swiss banks approach the November 2026 deadline with considerably more confidence than counterparts in other markets. The migration happened gradually, with time for banks and corporates to adjust and communicate. For treasury teams with Swiss banking relationships, address compliance in this corridor should largely already be resolved.

France: inconsistent application creates real risk

In France, the Comité Français d'Organisation et de Normalisation Bancaires (CFONB) published guidance on how to pre-structure addresses within the AFB320 format. It is a technically sound workaround that would allow corporates to continue using the existing format while meeting the new structured address requirements.

The problem is not the guidance. The problem is adoption.

Not all French banks have implemented the CFONB instructions. A payment carrying a pre-structured address in the recommended format may be accepted by one French banking partner and rejected by another. For treasury teams with multiple French bank relationships, there is no safe assumption of consistent treatment.

The practical implication is direct. If you are submitting cross-border payments through AFB320 in France, you should start a conversation with each bank now. Do not assume continued format acceptance after November 2026. Do not assume that following the CFONB technical guidance is sufficient. Verify with each banking partner individually as soon as possible.

Italy: between regulation and reality

Italy's situation seems to be clearer than the French one. Its Corporate Banking Interbancario (CBI) is the principal consortium coordinating digital payment infrastructure across the Italian banking sector. In November 2025, CBI officially announced the decommissioning of the legacy format CBI PE. The format could be replaced either by the CBI cross border (based on the ISO 20022 XML pain.001 V3 but not fully standard) or the fully standard ISO 20022 XML pain.001 V9. This apparent clarity masks a more nuanced reality: individual banks retain the flexibility to grant exceptions to specific clients, allowing continued use of CBI PE through bank-side converters.

Yet the approaching deadline raises important questions about practical implementation regarding new address requirements. Since CBI PE does not support structured addresses, and such structuring is not even mandatory within the format, doubts remain as to how legacy messages could reliably be converted into valid messages once the new rules take effect. While regulation clearly points toward full migration, market practice often tells a different story, with informal, under-the-radar arrangements between certain banks and clients likely to persist. Some institutions have reportedly continued accepting even older formats such as CBI PC (for domestic high value transfers), suggesting that any bank still supporting CBI PE beyond November 2026 would need sophisticated, possibly AI-driven, conversion logic to structure previously unstructured addresses.

This migration represents a unique opportunity for the Italian banking sector to finally decommission legacy formats altogether, even as pockets of resistance and exception-based practices are likely to remain in the short term.

Germany: forced decommissioning with a hard deadline

Germany is taking the most directive approach of any market in this review. The DTAZV format is being replaced by ISO 20022-based XML payment messages, after being used as a standardized file transfer format for decades to process cross-border and foreign currency payments between corporates and banks.

The German Banking Industry Committee (Deutsche Kreditwirtschaft) has mandated the change, and German banks already support the new formats in parallel with DTAZV during the transition period.

The new format is pain.001 V3 or V9, submitted via EBICS with the AXZ order type. For SEPA direct debits with a cross-border scope, the migration target is pain.008.001.08. From November 2026, the legacy DTAZV format will no longer be accepted.

For German treasury teams, the message is unusually clear: DTAZV has a hard end date. If you have not begun planning your migration to AXZ, that planning needs to start now. The months between now and November are needed for the testing and bank coordination where complications will surface.

United Kingdom: a readiness framework, not just a deadline

The UK took a different approach, with the Bank of England (BoE) playing a direct role in ensuring CHAPS (Clearing House Automated Payment System) participants were prepared well ahead of the transition. The process started in 2018 and progressively included all RTGS (Real-Time Gross Settlement) corridors such as Faster payments (FPS). Recognizing that a single unprepared institution could cause wider market disruption, the BoE introduced an evidence-based readiness framework. Individual relationship managers were assigned to each direct CHAPS participant, working through their preparation plans and verifying that technical connectivity, contingency planning, and senior oversight were in place. In 2024, the BoE even went further than the address structuring by making the purpose code and the LEI a priority to enrich the data transmitted through the payments.

For corporate treasury, this matters because it means UK banking counterparties were held to a higher standard of preparation than in most other markets. Cross-border payments routed through UK banking relationships are therefore less likely to encounter last-minute uncertainty about bank-side readiness. It means that there will be no alternative solutions proposed by their banks. The deadline is firm, and providing correct data is the corporate's responsibility, not the bank's.

United States: infrastructure migrated, data problem remains

The US has moved the furthest at the infrastructure level. CHIPS migrated to ISO 20022 in April 2024 and Fedwire in July 2025, making the two major systems at the center of US large-value and cross-border payments fully ISO 20022 compliant by November 2025. This came as a surprise to many because for years, they worked independently from the rest of the market infrastructure imposing their own rules and regulations and ignoring international recommendations like using the BIC and IBAN as a standard.

What November 2026 adds is an address data enforcement line. After that date, cross-border messages carrying fully unstructured addresses will be rejected. It does not mean that banks will retire their legacy EDI820 format as it contains pre-structured address segments. It means that these segments will become mandatory in order for the banks to map them successfully to the mandatory elements required in the interbank settlement messages. They will have to enforce new controls and their corporate clients need to be ready to comply.

Major US banks are constantly communicating with their clients to ensure their readiness, providing test environments to ensure the future acceptance of their payment files. But even though they look fully ready, they keep announcing new constraints such as the mandatory presence of the name and valid address when the ABA routing code is used instead of the Swift BIC. This is putting a lot of pressure on the corporates to adapt by the short deadline.

Spain: limited public mandate, real underlying risk

Of all the markets covered in this article, Spain has generated the least public regulatory communication about the November 2026 address deadline and its implications for legacy formats.

Spain's legacy payment format is AEB34, coordinated by the Asociación Española de Banca (AEB). Like AFB320 in France, AEB34 predates the ISO 20022 era and has limited capacity to carry structured address data in discrete fields. For SEPA-scope payments, Spanish corporates already operate on standard ISO 20022 pain.001, so the address compliance question is one of data quality. For cross-border non-SEPA payments still submitted via AEB34, the picture is less clear.

What is clear is that the November 15, 2026 Swift CBPR+ requirement applies universally. After that date, any cross-border payment carrying a fully unstructured address will be rejected, regardless of the originating format or country. Spanish corporates routing cross-border payments through AEB34 need to understand whether their banks will continue accepting that format, and if so, how structured address requirements will be applied within it.

The absence of a strong public mandate from Spanish regulators or the AEB does not mean the risk is lower. It means the guidance is less visible. And that, historically, is when corporates are least prepared.

Japan: one market, a two-speed migration

Japan's migration is defined by a sharp divide between its largest institutions and the rest of the market. The three major banks (Mizuho, MUFG, and SMBC) started their migration early and decided to adopt the ISO 20022 XML pain.001 V9 as their new standard for the cross-border payments. In contrast, regional and local banks in Japan have not followed the same path.

The practical consequence for corporate treasury is significant. Companies processing cross-border payments through both mega bank and regional bank relationships must maintain different formats, ERP configurations, and operational processes in parallel, even for the same payment type, in the same country. As a result, the mega banks are capturing most of the cross-border transaction volume, leaving the local banks with domestic low-value Zengin payments.

The complexity does not stop there. Despite aligning on pain.001 V9 as the target format, the three mega banks did not align on how to implement it. Rather than following the Common Global Implementation (CGI) recommendations, each bank defined its own field requirements and mapping rules, leaving corporates with a different implementation per bank even for the same format version.

For treasury teams with Japanese banking relationships, format alignment cannot be assumed even among institutions that have completed their migration. Verify the specific implementation requirements with each bank individually.

What this means for your planning in the next three months

The country-by-country picture confirms a pattern we have seen consistently: this transition does not have a single answer. The same payment, in the same format, carrying the same address data, will be handled differently depending on the banking relationship, the corridor, and the country.

For treasury teams managing cross-border payments across multiple markets:

• Switzerland has completed its migration. Germany has a mandated end date for DTAZV. In both cases, the direction and timeline are clear.

• France, Italy and Spain require bank-by-bank confirmation. The local authorities’ guidance exists, but adoption is inconsistent. Verify directly with each bank; do not assume.

• The UK's structured readiness framework provides additional confidence in banking counterparty preparation. Compliance obligations on the corporate side remain unchanged.

• The US completed its infrastructure migration ahead of November 2026. The legacy format EDI820 is still in use but might require some adaptations which need to be addressed as soon as possible.

• Japan operates at two speeds. Mega banks have migrated to pain.001 V9 but with divergent, bank-specific implementations. Regional banks may have not migrated at all. Verify requirements with each Japanese banking partner individually.

• Across all markets, November 2026 applies to cross-border payments regardless of local format. If your format cannot carry a structured address, migration is the path forward.

If you have questions about how these changes affect your specific payment corridors or formats, reach out to us. The time to find the gaps is now.