SWIFT CBPR+ SR 2026 Postal Address Deadline: Structured & Hybrid PostalAddress24 Requirements

The Deadline

Starting November 2026, SWIFT will enforce structured postal address requirements for all CBPR+ messages. Messages containing only free-text elements without proper structured fields (, , ) will be rejected at the SWIFT network level.

This isn't a soft recommendation — it's a hard cutoff. Messages that don't comply simply won't go through.

What Changes

The ISO 20022 PostalAddress24 type supports three formats:

• Structured: Every component in its own XML element — StrtNm, PstCd, TwnNm, Ctry. This is the target format for CBPR+.
• Hybrid: A mix of AdrLine elements with some structured fields like TwnNm and Ctry.
• Unstructured: Only AdrLine elements with free-text content. This is what gets rejected after November 2026.

The PMPG (Payments Market Practice Group) recommends using the "CUTOVER2026" placeholder in TwnNm when the real town name cannot be determined, combined with the original text in AdrLine. This buys time while the address is reviewed by an operator.

The Scale of the Problem

Industry estimates suggest that 60-80% of postal addresses in banking systems are still in unstructured format. These exist in core banking databases, customer master files, and correspondent banking directories that haven't been updated in years — sometimes decades.

What Banks Need to Do

1. Audit your address data: How many of your CBPR+ messages currently have unstructured addresses?

2. Assess your core banking timeline: Can your vendor deliver structured address fields before November 2026?

3. Consider middleware solutions: An address transformation engine between your backoffice and SWIFT can bridge the gap without touching your core banking system.

4. Test early: SWIFT provides testing environments. Start processing your real message volumes now to identify edge cases.

The PostalIQ Approach

PostalIQ sits between your backoffice and SWIFT as a Docker container. It parses unstructured addresses, resolves country and city using multiple data sources (IBAN, BIC, clearing codes, text analysis), and outputs CBPR+ compliant structured addresses. High-confidence transformations happen automatically; low-confidence ones go to a human review queue with a self-learning cache that improves over time.

No changes to your core banking system. Deploy in hours, not months.