SEPA payment addresses: the November deadline has been deferred
Alpha Insights | Operational insight updated on 17 November 2026.
Position verified on 17 November 2026
The retirement of fully unstructured addresses under the EPC payment schemes did not take place on 15 November 2026. After the September deferral, the Payment Scheme Management Board decided on 29 October to postpone setting a replacement date and to revisit that decision by February 2027. February is a decision milestone, rather than a newly announced migration deadline.
Version 2.2 of the EPC address guidance removed the previous deadline. The SCT scheme page identifies version 1.2 of the 2025 rulebook as currently effective. These statements concern EPC schemes and should be distinguished from the schedules of other infrastructures and individual providers.
Why this matters to a payments project
A date copied into a project plan can remain in circulation after the underlying source changes. When a project involves a bank, a PSP, accounting software and an operations team, the useful exercise is to align the dependencies: which message is being produced, which documentation governs that flow, and which checks does its recipient apply?
Alpha’s operational perspective: the deferral creates room to improve reference data and complete testing. It does not confirm that every counterparty will accept any existing file. Ask the provider for the expected format, documentation version and dates applicable to the specific service being used. Keep the answer with the project requirements so that later decisions have an identifiable basis.
Three checks to complete now
Documentation and ownership. Update the deadline register with the source, version, verification date and person responsible for the next review. Revisit customer messages that still describe 15 November as an active requirement. Record which external communications need a correction.
Data quality. Identify where addresses originate and which fields are missing. Separate records that are already structured from those needing correction or additional information. Review the results of any automated conversion against a representative sample before relying on it.
Partner testing. Agree sample messages, error scenarios and acceptance criteria. Follow the path from the source system to the provider, including how rejected records reach the team able to correct them. Assign an owner to unresolved cases and define the evidence needed to close each one.
How to use the available time
Alpha’s proposed approach is to work in small, verifiable batches: select one flow, examine a sample of records, document exceptions and repeat the test after corrections. A shared business and technical review should distinguish completed work from assumptions awaiting validation. The test result should refer to an agreed file or message version rather than a general statement that a system is ready.
The practical objective is clear ownership of address data throughout the chain. A change introduced only in the final system can leave the original issue unresolved. Addressing it at source makes it possible to compare the information entered, transformed and ultimately accepted by the recipient.
This article reviews previously announced EPC decisions and was verified on 17 November 2026. Project recommendations are Alpha Payments’ own methodological assessment. Before a release, confirm the applicable timeline against the current sources and with the parties involved; retain that confirmation with the acceptance evidence.
Sources and references
The sources describe the referenced frameworks and services; the design recommendations reflect Alpha's operational perspective.

Comments