SEPA Structured Address Deadline: Why 15 November 2026 Still Stands

On 28 August 2026 the European Payments Council (EPC) confirmed that its 15 November 2026 end-date for the fully unstructured address format in SEPA scheme messages still stands. The confirmation landed one day after Swift said, on 27 August 2026, that it would extend the migration period for structured addresses in cross-border ISO 20022 payment messages. For payment service providers, the SEPA structured address deadline and the Swift cross-border timeline are now two separate calendars, and only one of them has moved.

The EPC’s language is firm. Its notice states that the timelines remain unchanged and 15 November 2026 stands until further notice, and it asks participants to continue their preparations as planned. The EPC’s Payment Scheme Management Board (PSMB) will decide the scheme’s position at its meeting on 9 September 2026, after consulting its stakeholder groups, and will issue a further update once that discussion has taken place.

That gap matters because the address change reaches into live processing. For SCT, SCT Inst and SDD instructions or transactions to be executed or settled as of 15 November 2026 and containing address data, the address must be structured or hybrid; where it is unstructured, the relevant PSPs must reject or return the instruction per the applicable EPC scheme rulebook. For SCT Inst, the cutover time set by the EPC for SCT Inst on 15 November 2026 applies. A firm that quietly paused its address-cleansing work on the strength of Swift’s announcement would be preparing to the wrong date.

Related reading: SEPA Instant Payments Regulation

The SEPA structured address calendar at a glance

  • 20 August 2026: the ECB’s Advisory Group on Market Infrastructures for Payments (AMI-Pay) held an ad-hoc meeting on removing the fully unstructured postal address across major infrastructures.
  • 27 August 2026: Swift announced it would extend the structured-address migration for cross-border ISO 20022 payment messages.
  • 28 August 2026: the EPC confirmed its 15 November 2026 timeline stands until further notice.
  • 9 September 2026: the EPC’s PSMB decides the SEPA scheme position, after stakeholder consultation.
  • 15 November 2026: current EPC end-date for using the unstructured address format in the relevant initial SEPA payment instructions and transactions; for SCT Inst, the EPC scheme rules set a specific cutover time. EPC153-22 preserves limited R-transaction exceptions; consult the current EPC153-22 guidance document for the precise conditions.

Two calendars, one go-live weekend

The single most consequential misread this week is treating Swift’s extension as an EPC extension. Swift’s migration governs cross-border ISO 20022 messages exchanged over its network. The EPC’s date governs the relevant EPC SEPA payment schemes across the SEPA schemes’ geographical scope, which extends beyond the euro area and includes non-euro and non-EEA SEPA countries and territories. They were deliberately aligned to the same November 2026 window, which is why they are easy to conflate, but they are owned by different bodies and can now diverge.

The ECB’s AMI-Pay outcome from 20 August 2026 is explicit that any Eurosystem response to the market request is conditional on Swift and other major infrastructures actually postponing, and the EPC’s own decision on the SEPA schemes remains open. Firms managing both cross-border and domestic euro flows should track the two timelines on separate lines of their programme plan, the same way they already separate their cross-border payments roadmap from euro retail work.

Structured, hybrid and unstructured: the distinction that decides your mapping

Three address formats sit behind this deadline. Under EPC153-22, the unstructured address format uses up to two Address Line elements and may also include the structured Country element; Country alone does not turn an unstructured address into a hybrid or structured address. A structured address carries the address in dedicated ISO 20022 elements with no free-text lines. A hybrid address mixes the two: the structured elements plus a limited number of free-text address lines.

From 15 November 2026, the EPC unstructured address format is no longer permitted for the relevant initial payment instructions and transactions. Structured and hybrid addresses require Town Name and Country. A structured address cannot contain Address Line. A hybrid address uses one or two Address Line occurrences of up to 70 characters each; any address component available in structured form must be mapped to its corresponding structured element and must not be duplicated in Address Line. The AMI-Pay contingency under discussion would make Town Name and Country optional and increase Address Line to up to three occurrences for the proposed T2 option.

A hybrid address remains permitted after 15 November 2026. It must carry Town Name and Country as structured elements, use one or two Address Line occurrences of up to 70 characters each, map address components available in structured form into their corresponding structured elements, and avoid duplicating those elements in Address Line. The retired EPC unstructured format may itself contain the structured Country element, so the dividing line is the EPC-defined address format rather than whether the address contains any structured content.

The deadline sits in the scheme rulebooks, not in EU law

The 15 November 2026 date lives in the 2025 SEPA scheme rulebooks for credit transfer and direct debit, aligned to the November 2026 Swift standards release. It is a scheme-adherence obligation, enforced through participation in the EPC schemes, and it is not a statutory deadline written into an EU regulation. That distinction changes where a reporting or payments team looks for the rule. The Instant Payments Regulation, Regulation (EU) 2024/886, mandates instant credit transfer reachability, charge parity and verification of payee, and it drives a large parallel workstream, but it does not set the address-format date. Within the scope of Regulation (EU) No 260/2012, Article 5 and the Annex require the message formats referred to in Article 5(1)(b) and (d) to use the ISO 20022 XML standard. The EPC SEPA schemes have a wider geographical scope than the Regulation, including non-EEA jurisdictions. The granular address rules sit one layer below that, in the EPC rulebooks and their implementation guidelines. A team that searches the Instant Payments Regulation for a structured-address clause will not find one, and can lose time doing it. The cleaner reference points for the address-format change are EPC153-22 and the applicable EPC payment scheme rulebook and implementation guidelines. Verification of Payee is governed by a separate EPC VOP Scheme Rulebook.

The contingency the Eurosystem has already sketched, and why it stays conditional

The AMI-Pay meeting followed a specific industry request. On 4 August 2026, European industry participants of the Payments Market Practice Group (PMPG) asked the AMI-Pay Chair for the Eurosystem to consider aligning the removal of the fully unstructured postal address across major infrastructures, citing readiness concerns in parts of the global payments ecosystem and the risk of an uncoordinated approach for cross-border flows.

AMI-Pay discussed two options for the TARGET Services, both conditional on Swift and other infrastructures postponing. The first is a fix-forward through change request CR T2-0188, which would allow the fully unstructured postal address format in RTGS messages. The second is to proceed with CR T2-0156 as originally planned. Most participants supported the first as a pragmatic way to protect cross-border interoperability, and the group’s conditional advice to the Market Infrastructure Board is to implement it if Swift and major infrastructures postpone. The AMI-Pay advice was explicitly premised on Swift’s decision applying exclusively to payments. Swift’s 27 August announcement also moved securities, trade and other Standards Release 2026 changes to Q1 2027; the AMI-Pay outcome says that, if Swift’s decision is not payments-only, further steps must be determined. For SCT Inst, the ECB noted that TIPS, as a compliant clearing and settlement mechanism, plans to remove the fully unstructured address by the deadline in line with the EPC approach, unless the EPC decides otherwise. Anyone modelling how their instant-payment rails behave under these options can cross-read the ECB T2 roadmap for the underlying release mechanics. None of this is settled: every branch depends on decisions that had not been taken when the group met.

Preparation between 9 September and go-live

The operative instruction from the EPC has not changed: continue preparing for 15 November 2026. In practical terms, where an address is required or provided, outbound instructions to be executed or settled from that date must use a structured or hybrid address. Town Name and Country are mandatory in those formats, and hybrid mapping must place available structured address components in their corresponding elements while limiting residual Address Line content to one or two occurrences of up to 70 characters each. Systems should also accept and process valid structured and hybrid inbound addresses.

My working assumption is that the PSMB is more likely to confirm the date than to reopen it, given the EPC’s public wording and the TIPS plan already on record. That is a read, not a certainty. The right control is to hold the 15 November milestone in the plan, and to move it only after the EPC’s own update following 9 September, rather than on the back of a Swift headline.

Frequently Asked Questions

If we already send hybrid addresses, are we compliant on 15 November?

The EPC unstructured format is the format being removed from the relevant initial instructions and transactions. A hybrid address remains permitted when it contains Town Name and Country as structured elements, uses one or two Address Line occurrences of up to 70 characters each, maps address components available in structured form to their corresponding elements, and does not duplicate those structured components in Address Line. An EPC-unstructured address may itself contain Country, so ‘no structured content’ is not the correct test.

What happens to a cross-border payment that still carries an unstructured address after go-live?

That is the scenario the AMI-Pay contingency addresses. If Swift and other infrastructures postpone, the Eurosystem’s conditional advice is a T2 fix-forward that would keep accepting the fully unstructured format in RTGS messages. The SEPA schemes are decided separately by the PSMB, and a T2 RTGS contingency would not itself amend the EPC scheme rules. The ECB’s CR T2-0188 description applies to RTGS messages and does not limit the option to cross-border traffic.

Does the 15 November date apply to SCT Inst as well as credit transfer and direct debit?

The EPC end-date covers SEPA scheme messages generally. For instant payments specifically, the ECB has said TIPS, as a compliant clearing and settlement mechanism for SCT Inst, plans to remove the fully unstructured address by that deadline in line with the EPC approach, unless the EPC decides otherwise.

What should we tell corporate customers who supply addresses as free text?

Where an address is required or provided, Town Name and Country must be structured. For a hybrid address, any other address components available in structured form must also be mapped to their corresponding structured elements; one or two Address Line occurrences of up to 70 characters each may carry the residual unstructured content without duplicating structured fields.

Key Takeaways

  • 15 November 2026 remains the current EPC end-date for the unstructured address format in the relevant initial SEPA payment instructions and transactions, subject to the limited R-transaction copy exceptions in EPC153-22.
  • The PSMB decides the SEPA scheme position on 9 September 2026, with a follow-up EPC update to come.
  • Swift’s 27 August 2026 extension applies to cross-border ISO 20022 messages, not to the EPC’s SEPA date.
  • From 15 November 2026, structured and hybrid addresses require Town Name and Country; a hybrid address uses one or two Address Line occurrences of up to 70 characters each, with available structured components mapped to their corresponding elements and not duplicated in Address Line.
  • The date lives in the 2025 SEPA scheme rulebooks, not in the Instant Payments Regulation; within the scope of Regulation (EU) No 260/2012, Article 5 and the Annex require the ISO 20022 XML standard.
  • The Eurosystem’s proposed T2 fix-forward (CR T2-0188) would allow fully unstructured postal addresses in RTGS messages if the stated conditions are met; it would not itself amend the EPC SEPA scheme rules. The ECB source does not restrict CR T2-0188 to cross-border RTGS traffic.

Sources and References

  • European Payments Council, “November 2026 end-date of the unstructured address format for EPC payment scheme transactions” (28 August 2026): europeanpaymentscouncil.eu
  • European Central Bank, AMI-Pay ad-hoc meeting outcome, 20 August 2026: ecb.europa.eu (PDF)
  • Swift, “Swift accepts community request to extend structured address migration for ISO 20022 payment messages” (27 August 2026): swift.com
  • European Payments Council, EPC153-22 guidance document, “Provision of Addresses under the EPC Payment Schemes”: europeanpaymentscouncil.eu
  • European Payments Council, SEPA Credit Transfer rulebook and implementation guidelines: europeanpaymentscouncil.eu
  • Regulation (EU) No 260/2012 (SEPA Regulation), Article 5 and Annex, technical requirements: EUR-Lex
  • Regulation (EU) 2024/886 (Instant Payments Regulation): EUR-Lex

The date to watch is 9 September

The next hard signal is the PSMB meeting on 9 September 2026 and the EPC update that follows it. Until that update lands, the operative date for SEPA address preparation is 15 November 2026. Any decision to slow an address-cleansing programme should wait for the EPC’s own confirmation, not for a headline about Swift.

Disclaimer: The information on RegReportingDesk.com is for educational and informational purposes only. It does not constitute legal, regulatory, tax, or compliance advice. Always consult your compliance officer, legal counsel, or the relevant supervisory authority for guidance specific to your institution.

Similar Posts

  • EBA Reporting Framework 4.3: TCB and AMLA Reporting From 2027

    Updated July 2026In this guideThe 4.3 calendar reporting teams are now building toWhat the EBA reporting framework 4.3 package delivers, and what it is notThird-country branch reporting under CRD VIThe head-undertaking templates and the waiver most teams missAMLA’s risk-assessment data collectionWhy TCB and AMLA reporting should not share a project planTurning final artefacts into a…

  • EMIR Reporting Requirements – What You File, When, and How to Get It Right

    Updated August 2026In this guideEMIR Transaction Reporting: Who Reports, Which Trades, and What You FileEMIR Reporting to Trade Repositories: Submission, Reconciliation, and Error HandlingEMIR Regulatory and Supervisory Reporting: How NCAs and ESMA Use the DataFrequently Asked QuestionsRelated ArticlesKey TakeawaysSources and ReferencesGetting EMIR Reporting Right Across All Three DisciplinesA single lapsed LEI can cascade into hundreds…

  • ECB Streamlines Its Supervisory Guidance: What the Discontinued Publications Mean for EU Banks’ Reporting and Controls

    Updated July 2026In this guideWhat the ECB changed in its supervisory guidance on 26 June 2026Why a discontinued guide does not loosen a binding obligationThe guides being revised, not retiredContent pulled to track the moving regulationWhere this sits in the wider simplification agendaWhat reporting and control teams should do nowFrequently Asked QuestionsRelated ArticlesKey TakeawaysSources and…

  • CESOP: What Payment Service Providers Need to Report

    Updated July 2026In this guideIntroductionLegal Basis and Regulatory ScopeWhat is CESOP? System ArchitectureWho Must Report? Payment Service Provider ScopeThe 25-Payment Threshold: How It WorksWhat Gets Reported in CESOP?Cross-Border Element and Scope DeterminationReporting Across Multiple Member StatesFiling Format: XML Schema and Technical RequirementsCESOP Reporting in Practice: Step-by-Step ProcessCommon Challenges and SolutionsCESOP as Part of the VAT…

  • Uncleared Margin Requirements: What the 2025 BCBS-IOSCO Review Found

    On 12 December 2025 the Basel Committee on Banking Supervision and the International Organization of Securities Commissions published a joint review of how the uncleared margin requirements framework has been implemented, and the headline for reporting and collateral teams is that nothing in the rulebook moves. The review found no material issues with the framework…