Unstructured / hybrid vs fully structured address
ISO 20022 can carry a postal address three ways — as free-text lines (unstructured), part-labelled (hybrid), or fully in labelled elements (structured). The migration is pushing all cross-border payments toward the structured end.
| DIMENSION | Unstructured / hybrid address | Fully structured address |
|---|---|---|
| How the data is held | Unstructured: the whole address sits in a few free-text lines with no labelled parts. Hybrid: town and country are labelled elements, but street and building stay as free text. | Every component — street name, building number, town name, post code, country — is carried in its own named element. |
| Machine readability | Unstructured data must be parsed or guessed at; a system cannot be sure which line is the country. Hybrid guarantees the town and country only. | A receiving system reads any component directly, with no parsing, because each is explicitly labelled. |
| Effect on sanctions screeningStructure helps only where originators actually populate the elements; an empty structured field is no better than a missing line. | A country or name buried mid-line can be missed or can trigger a false positive; truncation can cut exactly the part that would have matched. | Screening can target the country or name element precisely, which reduces false positives and makes matches more defensible. |
| Ease of capture at source | Easiest to collect — one free-text box — which is exactly why unstructured addresses persisted in customer channels. | Requires the channel to collect each part separately, so forms and host-to-host feeds often need rebuilding. |
| Permitted status from 15 November 2026The date aligns with that year's annual Standards Release. | Fully unstructured is no longer permitted for in-scope cross-border payments; hybrid remains allowed. | Structured is the target form and remains permitted; it is the direction the CBPR+ guidelines push toward. |
Sources for this comparison3
- Official requirement
Cross-Border Payments and Reporting Plus (CBPR+) usage guidelines ↗ — Swift (CBPR+ working group) · address structuring rules and the 15 November 2026 date
Full guidelines require MyStandards access; content here relies on public summaries. MT-to-CBPR+ translation rules are published on Swift's translation portal.
- Official requirement
ISO 20022 Catalogue of messages ↗ — ISO 20022 Registration Authority · PostalAddress element and its structured sub-elements
Each message set is described by a Message Definition Report; earlier versions remain available in the ISO 20022 messages archive.
- Simplified educational illustration
Payments Signal editorial teaching models — Payments Signal
What this simplifies: The three-way distinction is framed as two columns for comparison; exact element rules and permitted combinations are defined in the current CBPR+ guidelines and the ISO 20022 catalogue.
Used wherever diagrams, scenarios, figures, or example values are didactic constructions rather than sourced facts; every such use carries a simplifications disclosure. All people, companies, banks, and list entries in examples are fictional.