On 22 November 2025, the payments industry reached an important milestone. The coexistence period between MT and ISO 20022 for CBPR+ cross-border payments came to an end, making ISO 20022 the required message format for in-scope Swift activity.

But the transition is not over. A second, firm deadline is approaching fast.

From 14 November 2026, fully unstructured postal addresses will no longer be accepted in CBPR+ payment messages. Where address information is provided, it must be in a fully structured or hybrid format, and non-compliant messages will be rejected outright on the network.

With industry readiness still low and the deadline now imminent, this article explores what institutions need to have in place, and what the November 2026 requirement means in practice.

CBPR+ stands for Cross-Border Payments and Reporting Plus. It is Swift’s framework for enforcing the adoption of ISO 20022 for cross-border payments by bringing an end to the coexistence of legacy MT messages alongside ISO 20022-compliant MX messages.

Through common usage guidelines and validation rules applied across the Swift network, CBPR+ ensures that financial institutions construct, interpret and exchange ISO 20022 XML messages in a consistent and predictable way.

Without this shared framework, institutions could adopt ISO 20022 inconsistently, introducing variation into processes that depend on standardisation.

CBPR+ reduces this risk by defining how specific message types should be structured, which data elements are required and how messages are validated in production.

This marks a fundamental change in how payment data is handled. Unlike MT messages, which rely on condensed free-text fields, ISO 20022-compliant XML messages carry explicitly structured information for parties, addresses, references and remittance data.

ISO 20022 is a global standard for exchanging financial information. It describes business processes and defines how data should be organised within messages.

What sets ISO 20022 apart is its use of structured XML-based (Extensible Markup Language) messaging, where data elements are explicitly defined rather than inferred. Instead of compressing information into a few lines of text, ISO 20022 messages use clearly defined fields for names, postal addresses, remittance information, account details and supporting references. This richer structure delivers practical benefits across the payments chain, including more consistent screening and compliance outcomes, fewer manual workarounds, improved traceability and greater potential for automation, reconciliation and straight-through processing.

As a result, ISO 20022 enhances interoperability across domestic and cross-border payment systems. ISO 20022 is becoming the norm for payment across the globe, albeit implemented slightly differently across schemes, clearing houses, and clearing houses. As of now, major payment schemes and systems like SEPA (EU), T2 (EU), FedNow (US), PIX (Brazil), NPP (Australia), and FAST (Singapore) are based on ISO 20022, with others planning to migrate.

With the standard now live for CBPR+ cross-border payments, the focus is turning toward operating confidently with richer, more granular payment data in everyday production.

Swift published the first CBPR+ usage guidelines in March 2023, initially covering core cross-border payment and cash management messages.

Subsequent releases expanded the scope to include additional use cases such as cheques, direct debits, cancellations and margin collections.

Over the following two years, financial institutions have aligned their systems and processes to meet the CBPR+ migration timeline.

On 22 November 2025, the coexistence period formally ended. MT message families traditionally used for cross-border payments (MT 1xx, MT 2xx and MT 9xx) no longer meet CBPR+ requirements and have been replaced by their ISO 20022 equivalents. In practical terms, this includes:

Not all MT messages have been retired. Categories outside the CBPR+ scope, including MT 3xx, 4xx, 5xx and 6xx series, remain active for now.

This has created a hybrid environment where some payment flows run on ISO 20022 MX messages while others continue to rely on MT. As a result, internal systems, routing logic and operational processes must continue to recognise and support both formats, often within the same payments landscape.

The next major milestone is 14 November 2026. From that date, CBPR+ payment messages will no longer accept fully unstructured postal addresses. Where address information is provided, it must be in a fully structured or hybrid format across all in-scope messages, including pain.001, MT101, all agents and parties, and all payment types.

Critically, there is no Swift contingency measure: non-compliant messages will be NAK'd on the network. During this period, financial institutions must complete their transition towards fully structured data across onboarding, corporate channels and internal systems.

With ISO 20022 now the live format for CBPR+ cross-border payments, attention is shifting from migration mechanics to how payments behave in production. Several themes are already shaping this next phase, and for many institutions, the pressure is building.

ISO 20022 allows for richer information, but it also applies clearer validation rules.

Fields that were loosely populated in MT formats are now subject to defined structures and usage guidelines. As a result, data quality issues in party information, addresses and remittance details are surfacing more consistently in production.

This places greater emphasis on upstream controls, particularly in corporate channels, onboarding and KYC processes, where message quality is effectively set. Institutions that have not yet tightened these controls are increasingly feeling the impact.

Postal addresses play a direct role in screening, routing and investigations, and the requirements around them are now firm.

This applies across all in-scope messages and payment types, including corporate, securities, trade, FX and funds. Critically, address data must be sourced at origin. Institutions relying on free-text address fields in onboarding, corporate channels or internal systems will need to adjust how that data is captured, validated and submitted before a payment is initiated.

Where payments move between ISO 20022 and MT formats mid-chain, some structured information may be lost or truncated. This can affect compliance checks, investigations and downstream processing.

As more correspondents operate natively with ISO 20022, reducing conversion points and treating MX messages as the authoritative format is becoming less of a best practice and more of an operational necessity.

Richer messages introduce new patterns in rejects, investigations and reconciliation. ISO 20022 messages carry more granular error information and larger payloads, requiring adjustments to operational dashboards, case handling and reporting processes.

Institutions that have not yet adapted these workflows are finding the gaps harder to ignore as live volumes grow.

The November 2026 deadline is firm, but readiness across the industry is not.

Swift has confirmed that approximately 65% of payment messages still contain unstructured addresses, and has called on the community to accelerate efforts to avoid last-minute disruption. As address information must be sourced at origin, Swift has also been explicit: there is no contingency solution available for institutions that experience delays in readiness.

The question of whether Swift might postpone the deadline has been raised. Given the current level of adoption, a delay is not inconceivable. But institutions that plan around a postponement are taking a significant risk. Non-compliant messages will be NAK'd on the network, with no fallback and no repair mechanism available at the Swift level.

The more prudent position is to treat November 2026 as immovable and act accordingly.

Several areas are now clear priorities for institutions operating ISO 20022 at scale, and the window to address them is narrowing.

Validation rules are tightening as usage guidelines mature and correspondents align more closely on interpretation. This is increasing consistency across the network while placing greater emphasis on clean, well-structured data at the point of initiation. Institutions still relying on loosely structured data in production are increasingly exposed.

End-to-end ISO 20022 processing is becoming more common. As more institutions and market infrastructures operate natively with MX messages, reliance on MT and conversion layers is decreasing. Institutions that have not yet reduced their dependence on conversion points should treat this as a priority.

Institutions that take a deliberate approach to validation, data models and internal routing now will be better positioned to operate with confidence as requirements continue to tighten beyond 2026.

With ISO 20022 now established as the operating standard for CBPR+ cross-border payments, many institutions are looking beyond initial compliance and focusing on how to operate reliably with more structured payment data.

Mambu Payments operates as a certified Swift Business Connect Enabler, offering ISO 20022-native, CBPR+ compliant connectivity through a cloud-based gateway. By supporting core Swift communication channels, including FIN, FileAct, and InterAct/FINplus, Mambu connects Swift activity to a broader Payments hub for orchestration, tracking, and operational management.

On the November 2026 address requirements, Mambu handles structured and hybrid address fields correctly end-to-end, both in outbound payment flows and when capturing inbound payment data, in line with CBPR+ requirements.

As CBPR+ adoption continues to mature, Mambu Payments is investing in capabilities designed to support operational stability and data quality, including payment validation and audit trails, along with tooling that helps institutions manage message flows and lifecycle events more effectively as volumes increase and requirements evolve.

For institutions reviewing their post-coexistence setup or preparing for the next phase of ISO 20022 adoption, Mambu Payments acts as a partner focused on reducing complexity and supporting long-term operational confidence.

The CBPR+ coexistence period is behind us, but the harder work is not. With a significant proportion of payment messages still containing unstructured addresses and the 14 November 2026 deadline firm and non-negotiable, the industry is in a critical window.

Institutions that have not yet reviewed how address data is captured, validated and submitted across their payment flows are running out of time. The consequences of non-compliance are not administrative: messages will be rejected outright on the Swift network, with no fallback available.

The institutions best positioned for what comes next are those treating November 2026 not as a standards release to manage, but as an operational deadline to meet. Data quality, validation and structured address handling are no longer preparation tasks. They are live requirements.