November 2026 structured-address deadline

From 14 November 2026, fully unstructured postal addresses are rejected in SWIFT CBPR+ payment messages and by the Bank of England's CHAPS validation library. Town Name and Country must be carried in their own structured elements. A compliant hybrid address remains acceptable — this is not a structured-only mandate.

What is changing

The requirement is a minimum, not a maximum. From 14 November 2026 an in-scope party must carry Town Name in and Country in as a two-letter ISO 3166 code. Everything else — street, building number, post code — may remain in address lines. That combination is a hybrid address and it is explicitly accepted. What is removed is the fully unstructured address, where the entire address sits in free-text lines with no structured town or country. Agents identified by BIC alone are unaffected and need no postal address.

Why it matters

• Unstructured addresses increase manual repair rates and delay straight-through processing.
• Structured addresses improve sanctions screening accuracy by separating party name from location data.
• Regulatory and scheme requirements increasingly mandate structured data for compliance and reporting.
• Cross-border payment rejection rates rise when address quality does not meet counterparty expectations.

Which messages are affected

• pacs.008 — debtor and creditor postal addresses in customer credit transfers.
• pacs.009 — institution addresses in financial institution credit transfers and cover payments.
• pacs.004 — party addresses in payment returns.
• pacs.003 — creditor and debtor addresses in customer direct debits.

How pacs008 helps

• Validates structured and hybrid postal address fields before XML generation.
• Flags unstructured address data that would fail after the deadline.
• Supports both pre-deadline hybrid formats and post-deadline structured-only formats.
• Integrates address quality checks into CI pipelines and batch validation workflows.

Normative rules

Generated from the pacs008 rule registry (ruleset 2026.11.0). Each rule has a stable identifier, an effective date, an authoritative source and both a passing and a failing test fixture.

Address formats compared

Format	TwnNm	Ctry	AdrLine	Before 14 Nov 2026	On or after
Fully structured	Present	Present	Absent	Accepted	Accepted
Hybrid	Present	Present	Present	Accepted	Accepted
Fully unstructured	Absent	Absent	Present	Accepted	Rejected

Exceptions

The requirement does not apply to these message types: admi.024, camt.025, camt.052, camt.053, camt.054, camt.060.

Agents identified by BIC alone remain valid without a postal address (CBPR-ADDR-005). Do not add a partial address solely to satisfy the rule.

Test fixtures

Download and run these through the workbench, the CLI or the API. Each maps to the rule it exercises.

• structured-valid.csv — passes CBPR-ADDR-001
• hybrid-valid.csv — passes CBPR-ADDR-001
• unstructured-invalid.csv — fails CBPR-ADDR-001
• hybrid-valid.csv — passes CBPR-ADDR-002
• missing-town-invalid.csv — fails CBPR-ADDR-002
• hybrid-valid.csv — passes CBPR-ADDR-003
• missing-country-invalid.csv — fails CBPR-ADDR-003
• hybrid-valid.csv — passes CBPR-ADDR-004
• agent-bic-only-valid.csv — passes CBPR-ADDR-005
• hybrid-valid.csv — passes CHAPS-ADDR-001
• unstructured-invalid.csv — fails CHAPS-ADDR-001

Timeline

Date	Scheme	Change	Rule
2025-11-22	CBPR+	Hybrid postal address option available	CBPR-ADDR-004
2025-11-22	CBPR+	MT/MX coexistence for payment instructions ends	—
2026-11-14	CBPR+	Fully unstructured postal address rejected	CBPR-ADDR-001
2026-11-14	CHAPS	CHAPS validation library rejects unstructured addresses	CHAPS-ADDR-001
2026-11-14	CBPR+	MT101 interbank coexistence ends; contingency relays to pain.001	—
2026-11-14	Swift	camt.110 investigation requests must be receivable	—
2026-11-14	Swift	Annual Standards Release cycle begins	—
2027-11	CHAPS	Purpose codes mandatory on all payments (announced)	CHAPS-PURP-001
2027-11	CHAPS	Structured remittance information mandatory (announced)	CHAPS-RMT-001
2027-11	Swift	camt.110 and camt.111 both mandatory (announced)	—

What to do now

• Audit current address data quality across debtor, creditor, and agent records.
• Map existing unstructured address fields to the structured format (street, building, post code, town, country).
• Add address validation to the pre-generation pipeline using pacs008.
• Test with representative payment data before the deadline.

References

• SWIFT CBPR+ roadmap and standards programme
• SWIFT CBPR+ ISO 20022 usage-guidelines announcement
• SWIFT CBPR+ migration roadmap PDF