SEPA Structured Addresses: the 15 November 2026 Deadline Explained
From 15 November 2026, a postal address in a SEPA payment must be structured or hybrid, or your bank will reject the file. What changes, why the trigger is the execution date inside the file, and how to check a pain.001 or pain.008 today.
What changes for SEPA addresses on 15 November 2026?
From 15 November 2026, if a SEPA credit transfer (pain.001) or direct debit (pain.008) carries a postal address for the debtor or creditor, that address must be structured or hybrid — it can no longer be a free-text address made only of AdrLine elements. A structured address supplies each component in its own tag (town, country, street, building number, postal code) with no AdrLine; a hybrid address keeps at most two AdrLine of 70 characters but must still add the town name (TwnNm) and country (Ctry). The country alone is not enough: the town name is the discriminator. If the address is unstructured, the bank must reject the instruction. The trigger is the requested execution or collection date inside the file, not today's date — a file produced now for a November execution is already non-compliant.
Validate your file right now
Free, instant and 100% in your browser - no file is ever uploaded.
What is actually changing on 15 November 2026
The European Payments Council rulebooks that govern SEPA Credit Transfer, SEPA Direct Debit and OCT Inst are moving postal addresses from free text to structured data. The change is set out in EPC153-22 ("Provision of Addresses under the EPC Payment Schemes", version 2.1) and takes effect on 15 November 2026 — a date the EPC aligned with the November 2026 Swift Standards MX Release, scheduled for the second full weekend of that month.
Until now you could describe a party's address as one or two lines of free text — the AdrLine element — and the bank accepted it. From the cut-off date, an address supplied for the debtor or the creditor must be machine-readable: either fully structured, or hybrid. If it is neither, the payment service provider must reject the instruction. Nothing forces you to supply an address at all; the rule only bites when one is present.
This is not a cosmetic tidy-up. The EPC notes that only the structured Town and Country fields are needed for regulatory screening, and that structured addresses reduce errors in payment processing, screening and reconciliation — increasing straight-through processing. SEPA is bringing its own messages into line with where the rest of the payment world is already heading.
Structured vs hybrid vs unstructured
The rulebook recognises three shapes of postal address. Knowing which one your file uses is the whole game — two of them pass after the cut-off, one does not.
Structured — passes
Every component sits in its own element: StrtNm (street), BldgNb (building number), PstCd (postal code), TwnNm (town), Ctry (country). There is no AdrLine at all. TwnNm and Ctry are required.
Hybrid — passes
You keep up to two AdrLine of at most 70 characters for the street part, but you must also add TwnNm and Ctry as their own elements. This is the pragmatic migration path for systems that cannot fully split an address.
Unstructured — rejected
Only AdrLine elements (optionally with Ctry), and no TwnNm. This is the classic free-text address. From 15 November 2026 it is no longer accepted and the bank must reject the file.
TwnNm is the discriminator
Adding Ctry alone does not make an address structured. The presence of a real town name in TwnNm is what tells the bank the address is machine-readable. Miss it and the address counts as unstructured.
Unstructured: rejected from 15 November 2026
<PstlAdr> <Ctry>BE</Ctry> <AdrLine>Rue de la Loi 1</AdrLine> <AdrLine>1000 Bruxelles</AdrLine> </PstlAdr>
Hybrid: accepted (TwnNm + Ctry + at most 2 AdrLine)
<PstlAdr> <TwnNm>Bruxelles</TwnNm> <Ctry>BE</Ctry> <AdrLine>Rue de la Loi 1</AdrLine> </PstlAdr>
Structured: accepted, and recommended by the EPC
<PstlAdr> <StrtNm>Rue de la Loi</StrtNm> <BldgNb>1</BldgNb> <PstCd>1000</PstCd> <TwnNm>Bruxelles</TwnNm> <Ctry>BE</Ctry> </PstlAdr>
The first example is the one that catches people out: the country is there, and the town appears in the text, but it is buried inside an AdrLine. With no TwnNm element, the bank reads an unstructured address and rejects the instruction.
The trigger is the date inside the file — and the scope is narrow
The most misunderstood part of this rule is the timing. The cut-off is not evaluated against today's date; it is evaluated against the requested execution date (ReqdExctnDt) of a credit transfer, or the requested collection date (ReqdColltnDt) of a direct debit, carried inside the file. A batch you build today whose execution date falls on or after 15 November 2026 is already non-compliant today — standing orders and direct-debit collections sent days or weeks ahead are in scope well before the calendar reaches November.
The scope is narrower than people assume. The requirement concerns the address of the payer and of the payee — the debtor (Dbtr) and the creditor (Cdtr) in a pain.001 or pain.008. EPC153-22 addresses only those parties: it says nothing about ultimate parties (UltmtDbtr, UltmtCdtr), the initiating party (InitgPty) or the agents, so a blocking error on an ultimate party's free-text address goes beyond what the guidance requires.
Watch one more source of confusion: 15 November 2026 is the SEPA date, driven by the EPC rulebooks for pain.001 and pain.008. It is not the SWIFT CBPR+ migration, which governs the interbank pacs messages banks exchange between themselves on a different rail and whose MT/ISO 20022 coexistence already ended in November 2025. If you only send SEPA files through your bank, the SEPA date is the one that governs you.
How to make your SEPA file compliant
Bringing a pain.001 or pain.008 into line is mechanical once you know the rule. These four steps move an address from unstructured to compliant, and you can confirm the result locally before you send.
- 1
Find every Dbtr and Cdtr postal address
Look inside the PstlAdr element of each debtor and creditor block. Ignore ultimate parties, the initiating party and agents — they are out of scope for this rule.
- 2
Add TwnNm and Ctry as their own elements
The town name in TwnNm and the ISO country code in Ctry are the mandatory pair. Adding Ctry without TwnNm still leaves the address unstructured.
- 3
Choose structured or hybrid for the rest
Either split the street into StrtNm, BldgNb and PstCd with no AdrLine (fully structured), or keep at most two AdrLine of 70 characters alongside TwnNm and Ctry (hybrid). Never mix more than two AdrLine or exceed 70 characters.
- 4
Validate against the execution date, not today
Check the file with the ReqdExctnDt or ReqdColltnDt it actually carries. If that date is on or after 15 November 2026, an unstructured address is a blocking error; before it, a warning. ValidateFin applies exactly this logic in your browser.
- 5
Check future-dated instructions with your bank
If your software submits future-dated instructions — standing orders in particular — ask your bank how it will treat those already sent with an execution date on or after 15 November 2026. Ordinary direct debits are usually only submitted a couple of weeks before the due date, so for those you still have time.
Check your address format before the deadline
Do not wait for a rejected batch to discover an unstructured address. ValidateFin reads the execution date inside your pain.001 or pain.008, checks each debtor and creditor address against EPC153-22, and tells you whether it will pass on 15 November 2026 — all locally, with nothing leaving your machine.
Open the SEPA validatorOfficial source
The rule comes from the European Payments Council guidance "Provision of Addresses under the EPC Payment Schemes" (EPC153-22 v2.1): section 6.3 for the 15 November 2026 date, and section 7.4 for the execution-date rule. Cite it if you need to convince someone internally.
EPC153-22 v2.1 — Provision of Addresses under the EPC Payment Schemes (PDF)Frequently Asked Questions
What exactly happens on 15 November 2026?
From that date, if a SEPA credit transfer (pain.001) or direct debit (pain.008) carries a postal address for the debtor or creditor, the address must be structured or hybrid. A purely free-text address (only AdrLine, no TwnNm) is rejected by the bank. If no address is supplied at all, nothing changes.
What is the difference between a structured and a hybrid address?
A structured address puts every component in its own element (StrtNm, BldgNb, PstCd, TwnNm, Ctry) with no AdrLine. A hybrid address keeps up to two AdrLine of at most 70 characters for the street part, but must still add TwnNm and Ctry. Both are accepted after the cut-off.
Is providing a postal address mandatory?
No. The rule does not force you to add an address. It only says that if you do supply one for the debtor or creditor, it must be structured or hybrid. An address that is simply absent raises no error.
Why does adding the country not fix the problem?
Because the town name (TwnNm) is the discriminator, not the country. A free-text address with only AdrLine and Ctry is still unstructured. You must add a real TwnNm — and Ctry — for the address to count as structured or hybrid.
Does the deadline depend on today's date or the payment date?
The payment date inside the file. The trigger is the requested execution date (ReqdExctnDt) for credit transfers or the requested collection date (ReqdColltnDt) for direct debits. A file built today for a November execution is already non-compliant, which matters for standing orders and pre-sent direct debits.
Which parties are affected?
The address of the payer and of the payee — that is, the debtor (Dbtr) and the creditor (Cdtr). EPC153-22 covers only those parties and is silent on ultimate parties (UltmtDbtr, UltmtCdtr), the initiating party (InitgPty) and the agents, so treating an ultimate party's free-text address as a blocking error goes beyond the guidance.
Is this the same as the SWIFT ISO 20022 migration?
No. 15 November 2026 is the SEPA date, from the EPC rulebooks for pain.001 and pain.008. SWIFT CBPR+ is a different rail — the interbank pacs messages banks exchange between themselves — and its MT/ISO 20022 coexistence period already ended in November 2025. For SEPA files sent through your bank, the SEPA date is the one that applies.
How can I check my file now?
Paste your pain.001 or pain.008 into the ValidateFin SEPA validator. It reads the execution or collection date in the file, inspects each debtor and creditor address against EPC153-22, and reports a blocking error if the date is on or after 15 November 2026 or a warning if it is earlier — all in your browser, with no upload.
What about standing orders already submitted with a November 2026 date?
That is the one case to act on now. A future-dated instruction — a standing order in particular — already sitting at your bank with an execution date on or after 15 November 2026 carries its address under the new rule. Check with your bank how it will handle instructions already submitted. Ordinary direct debits are typically sent only a couple of weeks before the due date, so they come into scope closer to the deadline.