Guides · Updated 2026-10-20
Structured, hybrid and unstructured addresses in SEPA pain.001
In a SEPA pain.001.001.09 the debtor and creditor postal address (PstlAdr) can be structured (separate elements, no AdrLine), hybrid (separate elements plus address lines) or unstructured (only AdrLine and Ctry). Structured and hybrid addresses always need TwnNm and Ctry, and SEPA allows at most two address lines. The planned end of unstructured addresses was postponed in September 2026.
The three address forms
The EPC implementation guidelines define the forms for the debtor address (EPC132-08 2025 v1.0, item 2.23) and the creditor address (item 2.118). The structured address is the recommended one.
| Form | Mandatory | Allowed | Not allowed |
|---|---|---|---|
| Structured | TwnNm and Ctry | All structured elements; the guidelines recommend giving as many as possible | AdrLine |
| Hybrid | TwnNm, Ctry and at least one AdrLine | Structured elements plus up to two AdrLine | More than two AdrLine |
| Unstructured | At least one AdrLine | Up to two AdrLine and Ctry | Every other PstlAdr element |
For an unstructured debtor address, Ctry is mandatory when the debtor agent or the creditor agent is located in a non-EEA SEPA country or territory (item 2.23). The ISO 20022 schema itself allows up to seven address lines; the limit of two is a SEPA rule (items 2.39 and 2.134).
Examples
<PstlAdr>
<StrtNm>Beispielweg</StrtNm>
<BldgNb>1</BldgNb>
<PstCd>12345</PstCd>
<TwnNm>Musterstadt</TwnNm>
<Ctry>DE</Ctry>
</PstlAdr><PstlAdr>
<PstCd>12345</PstCd>
<TwnNm>Musterstadt</TwnNm>
<Ctry>DE</Ctry>
<AdrLine>Beispielweg 1</AdrLine>
</PstlAdr><PstlAdr>
<Ctry>DE</Ctry>
<AdrLine>Beispielweg 1</AdrLine>
<AdrLine>12345 Musterstadt</AdrLine>
</PstlAdr><PstlAdr>
<StrtNm>Beispielweg</StrtNm>
<Ctry>DE</Ctry>
<AdrLine>Beispielweg 1</AdrLine>
<AdrLine>Building B</AdrLine>
<AdrLine>12345 Musterstadt</AdrLine>
</PstlAdr>PstlAdr elements in pain.001.001.09
The schema type is PostalAddress24. Elements must appear in this order; the lengths are the same in ISO 20022 and SEPA, except the number of address lines.
| Element | Tag | Length |
|---|---|---|
| Address type | AdrTp | Code (Cd) or proprietary (Prtry) |
| Department | Dept | 1 to 70 |
| Sub-department | SubDept | 1 to 70 |
| Street name | StrtNm | 1 to 70 |
| Building number | BldgNb | 1 to 16 |
| Building name | BldgNm | 1 to 35 |
| Floor | Flr | 1 to 70 |
| Post box | PstBx | 1 to 16 |
| Room | Room | 1 to 70 |
| Post code | PstCd | 1 to 16 |
| Town name | TwnNm | 1 to 35 |
| Town location name | TwnLctnNm | 1 to 35 |
| District name | DstrctNm | 1 to 35 |
| Country sub-division | CtrySubDvsn | 1 to 35 |
| Country | Ctry | Two capital letters (ISO 3166 code, pattern [A-Z]{2,2}) |
| Address line | AdrLine | 1 to 70, up to 2 in SEPA (7 in ISO 20022) |
BldgNm, Flr, PstBx, Room, TwnLctnNm and DstrctNm do not exist in pain.001.001.03; see pain.001.001.03 vs pain.001.001.09.
Deadline status for unstructured addresses
Status as of 2026-10-20. The 2025 implementation guidelines (EPC132-08 2025 v1.0, section 1.7) planned that only structured and hybrid addresses would be allowed from 22 November 2026; the SCT Rulebook dated it 15 November 2026. In September 2026 the EPC postponed this end date for unstructured addresses, and a new date had not been published as of 20 October 2026. Swift’s CBPR+ timeline for cross-border messages is separate and is not covered here.
Sources: The Paypers and Finextra. According to The Paypers, the EPC still recommends moving from unstructured directly to fully structured addresses where possible, rather than using the hybrid form as an intermediate step.
What BankLint checks
BankLint checks debtor and creditor addresses against the address rules of the 2025 guidelines: at most two AdrLine elements, and TwnNm plus Ctry whenever the address is structured or hybrid. An address that has only Ctry, or a street without a town, is therefore reported. BankLint does not reject unstructured addresses by date, because no new end date has been published.
In a Flow, the address form is also a regression signal: the debtor and creditor address modes are compared with the bank-accepted baseline, so a switch from structured to address lines after a configuration change is reported for review. Try the changed-configuration sample and read payment-file regression testing.
- SEPA-SCT-ADDR-001BLOCKERAt most two Address Line occurrences. SEPA allows at most two Address Line occurrences in the debtor and creditor postal addresses (ISO 20022 allows seven). The first failing address in each payment information block is reported.
- SEPA-SCT-ADDR-002BLOCKERStructured or hybrid address needs Town Name and Country. A structured address (structured fields only) or hybrid address (structured fields plus Address Line) must contain Town Name and Country. Only a purely unstructured address (Address Line, optionally Country, nothing else) may omit them. The first failing address in each payment information block is reported.
Questions
Is a hybrid address allowed in SEPA?
Yes. A hybrid address gives town and country as separate elements (TwnNm and Ctry, both mandatory) plus one or two address lines.
How many address lines are allowed in a SEPA pain.001?
Two. The ISO 20022 schema allows up to seven AdrLine elements, but the SEPA guidelines allow at most two.
When do banks stop accepting unstructured addresses in SEPA?
The 2025 guidelines planned 22 November 2026, but the EPC postponed the end date in September 2026. As of 20 October 2026 no new date had been published.
Is the country mandatory in the postal address?
In structured and hybrid addresses, yes. In an unstructured debtor address it is mandatory when the debtor agent or the creditor agent is in a non-EEA SEPA country or territory.
Validate a pain.001 fileFree, no account needed, files are not stored.
More guides
- How to validate a pain.001 payment file
- pain.001.001.09 XML example for a SEPA credit transfer
- pain.001 XSD validation errors and how to fix them
- pain.001.001.03 vs pain.001.001.09: what changed and how to migrate
- IBAN and BIC in a SEPA pain.001
- Remittance information in a SEPA pain.001 (Ustrd, Strd, RF)
- SEPA Credit Transfer rules for pain.001.001.09
- Why banks reject pain.001 files
- Payment-file regression testing after SAP or TMS changes
- Charge bearer SLEV in SEPA credit transfers
- Control sum (CtrlSum) and number of transactions (NbOfTxs) in pain.001
- SEPA character set, names and identifiers