Checks whether EU payment messages use ISO 20022 structured address fields (TownName, PostCode, StreetName) in place of unstructured AdrLine free-text blocks. Correction: this page previously asserted a 9 November 2026 structured-address mandate under the EU Instant Payments Regulation. Regulation (EU) 2024/886 contains no structured postal address format mandate, on that date or any other; what it imposes is payee verification and daily sanctions screening of payment service users (Art. 5d, compliance by 9 January 2025), with instant-credit-transfer staging under Art. 5a(8). Structured addresses are driven by Swift CBPR+, whose own requirement Swift deferred on 27 August 2026. Treat this tool as a structural readiness check, not a countdown to an IPR deadline.
Paste a representative address block from your payment messages to check field usage. Use synthetic/anonymised data only. The tool will identify AdrLine vs structured field usage.
| Legacy field (AdrLine) | Structured replacement | ISO 20022 path | Required? | Notes |
|---|---|---|---|---|
| AdrLine[1]: street/number | StrtNm + BldgNb | PstlAdr/StrtNm | Mandatory | Split free-text into street name and building number |
| AdrLine[2]: city/postcode | TwnNm + PstCd | PstlAdr/TwnNm | Mandatory | Town/city name and postcode are separate structured fields |
| AdrLine[n]: country | Ctry (ISO 3166-1) | PstlAdr/Ctry | Mandatory | 2-letter ISO country code required: not full country name |
| AdrLine[n]: region | CtrySubDvsn | PstlAdr/CtrySubDvsn | Optional | State/province/region: optional but recommended for non-EU counterparties |
| AdrLine (unstructured) | NOT PERMITTED | PstlAdr/AdrLine | Not recommended | AdrLine free-text blocks are not prohibited by Regulation (EU) 2024/886, which sets no address-format mandate; they are rejected by Swift CBPR+ once its structured-address requirement takes effect |
Regulatory citations in this tool are subject to the reliance notice.