Mastering address management: what a global enterprise learned so you don't have to

In our first article on address management, we explained what is changing with the November 2026 deadline, why it matters, and how to approach your migration. Since then, we've been continuing working closely with customers already deep in the migration. One of them, a large global enterprise* managing tens of thousands of cross-border payments across multiple ERP systems and payment corridors, agreed to share their experience. What they shared was, frankly, more instructive than any technical guide we could write.

Here is what they learned, and what you should take away before you start.

The numbers are more alarming than you think

Before we get into their story, let's set the scene with the data.

Despite strong awareness of the November 2026 mandate across the payments industry, SWIFT reports that approximately 65% of payment messages still contain unstructured addresses. Some don't even include a town name.

Belgium's Isabel clearing reports that around 85% of payment files transiting through their network still fail to comply with the new address requirements.

At Kyriba, our own data tells a similar story: 79% of the ISO 20022 XML transactions we process contain at least one invalid address.

These figures are not projections. They reflect the state of the data right now, with less than six months to the deadline.

They started early. And it was still hard.

This customer did not wait until 2026. They began their structured address journey in 2025, making it a formal project with an internal deadline set ahead of the regulatory one. By any standard, they were early movers.

The difficulty wasn't primarily technical. It was organizational. Their address data originated from ERP systems, with dependencies on dozens of business partners across regions. Mandating new import file structures to include specific address fields immediately generated pushback. Getting those partners to consistently populate town name, country, and supporting fields required sustained internal communication and education.

The lesson: being early gives you time to absorb the friction. Starting late means absorbing that friction under deadline pressure.

The data problem is bigger than you might think

Before migration, this customer's beneficiary address data followed a pattern we see across many global enterprises: the debtor side had unstructured or structured addresses; the creditor side often had only the country field populated.

That single missing field, the city, is precisely what will become mandatory in November 2026.

When they ran their initial audit, the gaps were significant. Tens of thousands of one-time beneficiary payments, each dependent on ERP systems passing address information downstream. No single owner. No consistent data model. Multiple legacy formats co-existing across payment corridors.

This is the reality many treasury teams will face when they run their own audit. The data gaps are not edge cases. They are systemic, and they reflect years of accumulated shortcuts that structured payment standards are now forcing organizations to correct.

Hybrid addresses: the pragmatic middle ground

One of the most instructive decisions this customer made was their choice of address model. They had three options: fully structured, hybrid, and the legacy unstructured; and they quickly concluded that fully structured was not achievable at scale.

Therefore, they chose hybrid as their future state: a pragmatic model that satisfies the mandatory elements (town name and country) while preserving address line fields for supplementary information that doesn't fit neatly into structured tags. This mirrors what we at Kyriba have seen across our broader customer base: hybrid is emerging as the de facto standard for most global enterprises, precisely because it balances compliance with operational reality.

One important caveat: for some specific bank setups, hybrid addresses created unexpected issues during testing, requiring those configurations to remain in structured format. This is a reminder that no single address model works universally across all corridors and counterparties.

Banks are not ready either

One of the most frequently misunderstood aspects of the migration is the assumption that banks will proactively guide their corporate customers through the transition. But that may not be the case.

When this customer did initiate contact, they also found uneven bank readiness. Some banks had dedicated ISO teams; others had limited testing capacity restricted to specific countries. And the requirements were not uniform.

A particularly striking example: in several Asian countries, Town Name refers to a district, not a city. Country Subdivision is repurposed to capture the city. Both fields become mandatory alongside Country. This kind of regional variation is invisible until you test with the actual bank, and it can derail timelines if discovered late.

So our practical tip here is: do not assume your banking partners will flag these issues. Initiate the conversation now, test early, and expect to encounter country-specific deviations that are not documented in the global standard.

Payment rejections are already happening

This customer encountered their first payment rejections linked to address formatting not in November 2026, not even in 2025, but already in 2024.

The reason was that certain banks had already begun enforcing full beneficiary address requirements beyond the minimum of town name and country. These were bank-specific mandates, ahead of the global deadline, applied selectively by corridor.

This is a pattern we expect to accelerate in the second half of 2026 as banks begin pre-emptive enforcement. Waiting for the regulatory deadline to trigger action is no longer a safe strategy.

Managing changes simultaneously

Perhaps the most underappreciated complexity this and many of other customers navigated was the fact that the address migration did not happen in isolation. It coincided with:

• Migration to FIN+ for SWIFT messaging

• A new payment format structure for Kyriba import feeds

• New hybrid address format requirements across ERP systems

For treasury teams planning their roadmap, this is critical learning. The November 2026 address mandate does not exist in a vacuum. It sits alongside the broader ISO 20022 transition, FIN+ channel migration, and ongoing bank format updates. Planning for address compliance in isolation will likely result in underestimating the total project scope.

The governance challenge

Getting the technology right was the easier part. The harder part was governance.

This is the reality of large enterprise migrations: data quality governance cannot be enforced entirely through system controls. It requires cultural change, clear ownership, sustained communication, and ongoing monitoring.

Their approach to raising awareness was instructive. They prepared structured address samples, mapping examples comparing the three postal address types, and written guidelines explaining what was changing and why, distributing all of this proactively to business partners before the mandate took effect.

What does "done" actually look like?

We asked whether they viewed this as a one-time migration or the beginning of something longer.

The answer was immediate: "This is just the beginning."

This is a candid and important counterpoint to the optimistic narrative around ISO 20022 benefits. For organizations managing complex, multi-ERP, multi-corridor payment ecosystems, the compliance migration itself consumes enough energy that near-term operational gains may be modest. The structural benefits, including better data quality, improved fraud screening, richer payment analytics, are real, but they accrue over time and require the data foundation to be in place first.

What's next

In our next article, we will look at how the structured address transition affects other payment formats: EDI 820, MT101, AFB320, and local standards including DTAZV and CBI. We will also interview a banking partner to understand how they are approaching the mandate and what they most need from their corporate customers before November.

If you are working through this migration and want to share your experience or ask a question directly, reach out to us. The more we share across the community, the better prepared everyone will be.

_{*This article is based on an interview with a treasury professional at a large global enterprise who participated in the ISO 20022 address migration with Kyriba's support. The customer's identity has been kept anonymous at their request.}