The November 2026 structured-address deadline: your checklist
From 14 November 2026, SWIFT CBPR+ stops accepting fully unstructured postal addresses. SEPA and other market infrastructures are aligned to the same window, and the rule captures any payment with a value date on or after cutover.
The Runway Is Shorter Than It Looks
October-November 2025
Hybrid addresses went live across SEPA, CBPR+, and HVPS+. The transition year is already running.
Now to November 2026
Institutions must move in-scope address data to structured or hybrid shape across backlog and in-flight payment flows.
14 November 2026
Fully unstructured postal addresses are retired. Payments carrying free-text-only addresses are rejected or delayed.
Beyond 2026
Real-time rails and market infrastructures continue tightening structured-data expectations, making the address engine reusable infrastructure.
Who And What Is In Scope
Debtor, creditor, ordering, beneficiary, and intermediary parties in CBPR+ payment messages need compliant addresses.
Corporate, securities, trade, FX, and funds flows are in scope, not only customer credit transfers.
If the value date falls on or after cutover, the rule applies even when the instruction is initiated earlier.
SEPA, CHAPS, and other infrastructures track the same window, so one policy must support multiple renderings.
Eight Steps To Examiner-Ready Compliance
Each step notes how a purpose-built engine compresses the journey into weeks rather than quarters.
Inventory Address Data And Flows
Map every place addresses enter payments: MT fields, pain/pacs messages, KYC/customer masters, and correspondent records.
Baseline Readiness
Measure what share of today's addresses resolves cleanly and what your STP and exception rates look like today.
Set A Format Policy Per Scheme
Decide where fully structured is the target and where hybrid is the pragmatic bridge by scheme, corridor, and counterparty.
Remediate The Backlog
Bulk-convert legacy address stores with financial identifiers preserved and every change traceable.
Deploy In-Line Resolution
Resolve and correct addresses in the live payment path before sanctions screening, at payment speed.
Stand Up Exceptions Handling
Low-confidence cases need maker-checker review, thresholds, and audit evidence rather than manual spreadsheets.
Parallel-Run And Measure
Run against production traffic, tune thresholds, and watch STP, exception ageing, and latency converge before cutover.
Document For The Regulator
Examiners ask why each address changed. Field-level reason codes and deterministic replay are the evidence pack.
Miss It, Muddle It, Or Make It
Deadline Questions
From 14 November 2026, CBPR+ stops accepting fully unstructured postal addresses. Structured and hybrid addresses remain valid.
Yes, if the value date falls on or after the cutover. Future-dated instructions need compliant address data before they reach the network.
Hybrid is accepted, but fully structured is the stronger target where you control the data because it improves STP, screening precision, and audit evidence.
Yes. ioNova ARS onboarding starts in days and typically reaches production in 2-4 weeks including parallel run.
The deadline is fixed. Your timeline does not have to be scary.
Start in days and go live in 2-4 weeks with deterministic resolution, the Exceptions Workbench, dashboards, and rule-cited evidence.