Articles / Learning brief
Structured and hybrid addresses in ISO 20022
Your notes
In simple terms / 01
What this means in plain language
ISO 20022 payments are moving postal addresses out of free-text lines into labelled fields for street, town, and country. A hybrid address keeps a structured town and country while allowing some detail on address lines during the transition.
For decades a payment carried a party's address as a few lines of free text, and a computer could not reliably tell which line held the street and which held the country. ISO 20022 (International Organization for Standardization standard 20022) changes this by giving each part of an address its own labelled field: street name, building number, post code, town name, and a two-letter country code each sit in a separate element. A fully structured address places every part in its own field. A hybrid address is a halfway step that keeps the town name and country as structured fields while allowing the remaining detail to stay on free-text address lines. It exists to help institutions that cannot yet capture every element separately. Complete structured addresses are easier to validate, to screen against sanctions lists, and to process without manual repair, which is why the industry is steadily moving away from free text.
Complete lesson / 02
Understand the full idea, step by step
Think about how you write an address on a parcel: a few lines, and the postal worker's eye fills in which line is the street and which is the country. A person reads that in an instant. A computer sorting a payment cannot — and that gap is exactly what ISO 20022 is now closing.
The same address, three ways to carry it
- Unstructured
- Everything on free-text address lines, no labelled parts
- Hybrid
- Town name and country in their own fields; the rest may stay on address lines
- Structured
- Street, building, town, country subdivision, post code, country each in a labelled field
- Country code
- Two letters from the ISO 3166 list — a known place, every time
- Direction of travel
- Away from fully unstructured, toward structured
Why free-text lines are hard for a machine
A legacy address stored a location as a handful of free-text lines. A name, a street, a town, and a country could share those lines in any order, in any language. A person reads it easily; software cannot reliably tell which line holds the country without guessing. ISO 20022 (International Organization for Standardization standard 20022) takes the postal address apart and gives each component its own labelled element — street name, building number, post code, town name, a country subdivision such as a state or province, and a two-letter country code. Once each part sits in a known place, a receiving system finds the country every time without reading narrative text, and it can check that required parts are present before the payment moves on.
Structured postal address — an address split into labelled fields rather than free-text lines
A structured address places each element of a location in its own dedicated field: StrtNm for the street, TwnNm for the town, Ctry for the two-letter country code, and so on. A free-text address line still exists, but the intent is that it should not carry anything that already has a field of its own. The point is not neatness — it is that every reader, human or machine, finds the same fact in the same box.
ISO 20022 — ILLUSTRATIVE, NON-PRODUCTION
<PstlAdr>
<StrtNm>Handelsvei</StrtNm>
<BldgNb>17</BldgNb>
<PstCd>2000</PstCd>
<TwnNm>Nordhaven</TwnNm>
<Ctry>NO</Ctry>
</PstlAdr>SYNTHETIC — TRAINING ONLY. Each part of the supplier's address sits in its own element. A screening system reading this knows Ctry is the country without parsing a single line of prose.
Hybrid address
Moving every bank's customer records to fully structured addresses overnight is not realistic — much of that data still lives as free-text lines. The hybrid address is the bridge across that gap. It requires the town name and the two-letter country code to be present as their own structured fields, while remaining detail such as the street may stay on address lines. This guarantees that the two parts most useful for routing and screening are always in a known place, even before a bank can separate every element.
You may be wondering: why not just have the receiving system parse the free-text lines and pull the country out?
Because parsing means guessing, and guessing fails in exactly the cases that matter most. A line reading "San Marino" could be a town, a country, or part of a company name; "Georgia" is a country and a place in more than one country. When the country sits in its own two-letter field, there is nothing to guess. The cost of parsing is not the odd typo — it is the payment that gets held, or the sanctions check that compares against the wrong text.
What structure does for screening and straight-through processing
Two jobs improve when the address is structured. The first is sanctions screening: a control compares the parties and places on a payment against published lists of sanctioned people, entities, and jurisdictions. When the country and town sit in their own fields, the control compares them directly, rather than searching for a place name buried in a line of text — which means fewer genuine matches missed and fewer false alarms for an investigator like Kabir to clear. The second is STP (straight-through processing): a payment handled end to end by machine, with no person stopping to repair it. Complete, correctly-placed fields validate and book automatically; an ambiguous free-text block is more likely to be held. Both depend on the data being captured cleanly upstream, because detail never separated at onboarding cannot be reconstructed later.
STRICTLY SPEAKING
Strictly speaking, the rules for structured and hybrid addresses on cross-border payments are set by market-practice guidance — the CBPR+ (Cross-Border Payments and Reporting Plus) usage guidelines — and by each infrastructure's own timetable. Target dates for retiring the fully unstructured option have been set and then revised more than once as institutions prepared. So the safe statement is that the direction is settled while a specific cutover date should be confirmed for the service you are working on.
FOR NOW, REMEMBER
- ISO 20022 splits a postal address into labelled fields so any reader finds the same fact in the same place.
- Unstructured puts everything in free text; structured labels every part; hybrid is the bridge, guaranteeing town and country as fields.
- The industry is moving away from fully unstructured addresses, on a timetable that has shifted more than once.
- Structured fields make screening and straight-through processing more accurate — but only if the data is captured cleanly upstream.
TRY IT YOURSELF
Bank Alfa is preparing a cross-border payment for Asha Traders but its records only hold the supplier's address as free-text lines. It cannot fully structure the address today. What is the correct minimum it should aim for?
You have seen how the message says where a party is. The next question is why the payment is being made at all — and ISO 20022 has two dedicated codes that answer it.
KEEP GOINGKey takeaways / 03
Three things to remember
- 01
ISO 20022 replaces free-text address lines with labelled fields for street, post code, town name, and a two-letter country code.
- 02
A hybrid address keeps town and country structured while allowing remaining detail on free-text lines during the transition.
- 03
Complete structured addresses validate cleanly, screen more precisely, and process without manual repair.
Practical use cases / 04
Where you would use this
A bank's onboarding team captures customer addresses as separate street, town, and country fields so outgoing payments meet the structured-address requirement.
A payments engineering team maps legacy free-text addresses into hybrid form, populating a structured town and country while the remaining lines carry the rest.
A compliance team screens the dedicated country field against sanctions and high-risk-jurisdiction lists rather than parsing a free-text block.
Worked example / 05
Put the idea into a real situation
Illustrative example: a fictional bank, Meridian Trust, sends a customer credit transfer of EUR 34,500.00 on behalf of a fictional company, Alder Freight Ltd. In a fully structured address the message carries the street name 'Havenkade', building number '17', post code '3011', town name 'Rotterdam', and country 'NL' in 5 separate elements. A fictional counterparty, Kestrel Union Bank, that cannot yet store every element receives a hybrid version instead: 'Rotterdam' and 'NL' arrive as structured town and country fields, while 'Havenkade 17' and '3011' sit on 2 free-text address lines. Because the country code 'NL' is in its own field either way, Kestrel Union Bank screens it directly and books the EUR 34,500.00 without manual repair.
Evidence & review / 07
Evidence & review
ISO 20022 payments generally; structured/hybrid transition rules follow CBPR+ market practice for cross-border messages.
What this brief simplifies: Shows a representative subset of PostalAddress elements and a two-way screening/STP benefit; omits the full element set and per-infrastructure migration dates, which shift over time.
Sources for this brief4
- Official requirement
ISO 20022 Catalogue of messages ↗ — ISO 20022 Registration Authority · PostalAddress component
Each message set is described by a Message Definition Report; earlier versions remain available in the ISO 20022 messages archive.
- Market practice
Cross-Border Payments and Reporting Plus (CBPR+) usage guidelines ↗ — Swift (CBPR+ working group) · Structured and hybrid address rules
Full guidelines require MyStandards access; content here relies on public summaries. MT-to-CBPR+ translation rules are published on Swift's translation portal.
- Market practice
Wolfsberg Group Payment Transparency Standards ↗ — The Wolfsberg Group
The 2023 standards replace the 2017 version and are supplemented by separate Wolfsberg guidance on roles and responsibilities in payment chains.
- Simplified educational illustration
Payments Signal editorial teaching models — Payments Signal
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.