Demo #22 · SWIFT CBPR+ · MT-to-MX cutover · Processors Hub

6 message families scored Structured-address gate · CBPR+ @ainumbers.co/iso20022-readiness-v1

MT→MX is done. The structured-address deadline is what's left.

SWIFT's CBPR+ coexistence period ended 22 November 2025 — MT103 / MT202 / MT900 / MT910 are retired for cross-border FIN traffic and ISO 20022 is now mandatory. The remaining open deadline is the 14 November 2026 structured-address mandate: after that date, CBPR+ payment instructions carrying unstructured postal addresses face rejection. This lab scores readiness across six message families, the gateway capability tier, and CBPR+ structured-address state — then exports an AP2 mandate the programme team can audit against.

Zero PII · Client-side Pair with #2 Truncation Auditor for the field-level depth Last Reviewed · 2026-05-13

SWIFT CBPR+ · structured-address mandate DEADLINE 14 NOV 2026

SWIFT's Cross-Border Payments and Reporting Plus (CBPR+) framework migrated payments-and-reporting messages to ISO 20022 in March 2023. The coexistence period ended 22 November 2025 — MT103, MT202 / MT202COV, and the MT9xx cash-reporting series are retired for cross-border FIN traffic; ISO 20022 is now mandatory. The remaining open milestone is the structured-address mandate: from 14 November 2026, CBPR+ payment instructions carrying unstructured postal addresses will be rejected. Hybrid address (town + country minimum) is the compliance floor; fully structured is preferred. The 2024 Eurosystem T2 migration completed the EU TARGET2 → T2 transition on ISO 20022.

Sources: SWIFT CBPR+ Market Practice Guidelines · ISO 20022 Programme · Eurosystem T2 launch (Mar 2023) · Fed FedWire ISO 20022 migration (Mar 2025)

Value at risk · cutover non-readiness

Per-month rejection cost ~$35K + correspondent-relationship termination + reconciliation backlog measured in days

Since the 22 November 2025 MT retirement, inbound MT-format cross-border traffic on the FIN service is rejected. From 14 November 2026, messages with unstructured addresses face rejection on the CBPR+ path too. Each rejected payment carries a per-message investigation cost (~$35–$60 industry estimate), a customer-experience hit, and a multi-day reconciliation tail. Repeated rejections trigger correspondent-bank investigations and, in the worst case, correspondent-relationship termination — a far higher cost than the operational rejection itself. The mandate codifies the chosen message-family coverage so the programme team can prove status at every steering committee.

SWIFT CBPR+ market practice · Fed FedWire ISO 20022 (Mar 2025) · Eurosystem T2 (Mar 2023) · industry estimates from Celent / Aite-Novarica 2024 surveys

§1 · Message-Family Coverage — / 6 full-native

Per-message support tier

For each message family, declare your gateway's current support tier. Full native = MX-native send and receive; Translation = MX received, internal MT translation; Partial = some flows still MT; None = no MX support.

Code	Family	Priority	Current tier

§2 · Gateway Capability SWIFT Alliance / Volante / in-house

Gateway maturity tier

The gateway is the chokepoint. A gateway that round-trips MX losslessly is the floor.

§3 · CBPR+ Structured Address PstlAdr block

Structured-address readiness

The structured postal address (PstlAdr) is the highest-impact CBPR+ change. From 22 November 2025 unstructured address fields are deprecated for new market practice; from 14 November 2026 they're rejected.

§4 · Exception & Hybrid Plan Coexistence countdown

Exception handling & coexistence

Exception-handling maturity

Hybrid-period inbound MT acceptance

§5 · Readiness Scorecard — / 100

Composite + per-family

Composite

—

Cutover risk

—

@ 14 Nov 2026

T-minus to cutover

—

Target: 14 Nov 2026
—

Per-message-family readiness

AP2 v1.0 · valid · @ainumbers.co/iso20022-readiness-v1

Compose with

Pair with #2 — ISO 20022 / CBPR+ Truncation Auditor for field-level depth on the structured-address risk. The mandate this demo emits feeds #27 — Agentic Mandate Sandbox via custom-schema paste. Position: Tool Chain Composer, T101 / T81 / T98 in the Payment Standards cluster.