What changes in November 2026

Banks are dropping fully unstructured postal addresses from ISO 20022 payment messages. SWIFT's cross-border payments (CBPR+) stop accepting them with the November 2026 standards release, and the European Payments Council's SEPA schemes follow on 22 November 2026. From then on, the address of every payer, payee and bank in a payment has to be structured or hybrid, and a payment with an unstructured address can be rejected. Files that accounting, payroll and ERP software create for the bank (pain.001 credit transfers, pain.008 direct debits) are affected as much as the messages banks send each other.

Three kinds of address

A structured address puts every part in its own element: street (StrtNm), building number (BldgNb), postcode (PstCd), town (TwnNm) and country (Ctry), with no address lines.

<PstlAdr>
  <StrtNm>Market Street</StrtNm>
  <BldgNb>12</BldgNb>
  <PstCd>10115</PstCd>
  <TwnNm>Berlin</TwnNm>
  <Ctry>DE</Ctry>
</PstlAdr>
XML

A hybrid address has the town and the country in their own elements and the rest in at most two address lines (AdrLine) of up to 70 characters. The lines shouldn't repeat the town or the country.

<PstlAdr>
  <TwnNm>Lisbon</TwnNm>
  <Ctry>PT</Ctry>
  <AdrLine>Rua das Flores 25, 2nd floor</AdrLine>
</PstlAdr>
XML

An unstructured address is written in address lines only, without a separate town. This is the kind that goes away.

<PstlAdr>
  <Ctry>FR</Ctry>
  <AdrLine>8 Rue du Vent</AdrLine>
  <AdrLine>69002 Lyon</AdrLine>
</PstlAdr>
XML

How to check a file

Paste the XML or upload the file. The checker finds every postal address (PstlAdr) in it, whatever the message type and version: pain.001, pain.008, pacs.008, pacs.009, pacs.004, camt.053 and others. It shows:

  • The message name from the file's namespace, and how many addresses of each kind the file has.
  • A checklist for the whole file.
  • A table of all addresses with the party each one belongs to (debtor, creditor, ultimate creditor, a bank and so on), where it sits in the file (payment and transaction number), its fields and its problems. In a large file, tick "Only addresses with problems". The buttons under the table download it as CSV or JSON.

What the problems mean

  • Unstructured address: add the town (TwnNm) and the country (Ctry) as elements of their own. The address lines can stay, which makes it a hybrid address, or the street, building number and postcode can move into their own elements as well.
  • Town missing or country missing: every structured and hybrid address needs both.
  • Unknown country code: the country is a two-letter ISO 3166 code in capital letters, such as DE, FR or PT.
  • Too many address lines, or a line that's too long: a hybrid address takes two lines of up to 70 characters.
  • A field that's too long: each element has a maximum length in the ISO 20022 schemas, such as 35 characters for the town and 16 for the postcode.
  • An address line that repeats the town or the country is shown as a warning: those belong in their own elements only.

Good to know

  • The checker looks at addresses only. It doesn't validate the whole file against the message's XML schema, and your bank may have rules of its own, so check its guidelines too.
  • Everything happens in your browser. The file isn't uploaded anywhere, which matters because payment files contain names and account details.

Features

  • Finds every postal address in any ISO 20022 message
  • Tells structured, hybrid and unstructured addresses apart
  • Checks town, country, address lines, field lengths and country codes
  • Shows each address with its party and its place in the file
  • Filters to the addresses with problems and exports them as CSV or JSON