TARGET Services June 2027 Release: Swift ISO 20022 and the T+1 Squeeze

On 15 September 2026 the ECB published a letter, dated the previous day, in which the Advisory Group on Market Infrastructures for Securities and Collateral (AMI-SeCo) formally asked Swift to move its 2026 securities message upgrade onto the TARGET Services June 2027 release. AMI-SeCo’s purpose is practical: the group is trying to protect the testing runway for the euro area’s central securities depositories before the European Union switches to a T+1 settlement cycle on 11 October 2027.

The chain of events is short. On 27 August 2026 Swift announced it would extend the timeline for its annual Standards Release (SR) 2026. Swift then indicated that the securities-related changes in that release would be deployed separately in the first quarter of 2027. AMI-SeCo, drawing on analysis from the T2S governance groups, concluded that a stand-alone first-quarter deployment would compress the window in which depositories can test the June 2027 TARGET Services release, and that this release carries the T+1 changes for TARGET2-Securities (T2S). The ask, in one line, is to align the two events on the June 2027 production date of 12 June 2027.

For a reporting or operations team connected to T2S through a depository, this is a scheduling decision that reaches into your own test plan. It ties three fixed points together: the shifted November 2026 TARGET release, the June 2027 TARGET release, and the October 2027 T+1 go-live. Getting the sequence wrong is how a market-wide migration loses its testing buffer.

Related reading: EU T+1 Settlement Transition: 2027 Deadlines

The release calendar that now runs from November 2026 to October 2027

Deadline pressure is the reason this item matters, so start with the calendar. Every date below is drawn from the ECB, ESMA, or the primary regulation, and each one is either fixed or, where flagged, still provisional.

• 27 August 2026: Swift announces an extension to the SR 2026 timeline.
• 4 September 2026: the Eurosystem’s Market Infrastructure Board decides to proceed with the November 2026 TARGET Services releases, following advice from AMI-Pay and AMI-SeCo.
• 28 November 2026: the new deployment date for the November 2026 TARGET Services releases, put back from 14 November 2026.
• 7 December 2026: the Commission-adopted amendments to the RTS on Settlement Discipline are scheduled to start applying. As of 16 September 2026, Commission Delegated Regulation C(2026) 4640 has been adopted by the Commission but remains under European Parliament and Council scrutiny, with the European Parliament and Council non-objection period still running; Official Journal publication and entry into force are still pending.
• First quarter of 2027: Swift’s currently envisaged window for the SR 2026 securities changes. Swift said it would confirm the final implementation date by mid-September 2026.
• 1 to 12 February 2027: the first harmonised EU, UK and Switzerland T+1 testing window is planned under BAU testing conditions; 19 to 30 April 2027 is a subsequent testing window.
• 5 April to 1 October 2027: the joint T+1 testing plan sets a dedicated EU period for testing the new Operational Day; T2S-specific UTEST and EAC availability follows the separate T2S testing and release schedule.
• 12 June 2027: production deployment of the TARGET Services June 2027 release, which includes the T+1 changes for T2S.
• 1 July 2027: the amended rules on the reporting and publication of settlement fails data by depositories are expected to apply.
• 11 October 2027: the EU moves to a T+1 settlement cycle under Regulation (EU) 2025/2075.

Two of these dates sit before you have even shortened a settlement cycle. The 7 December 2026 allocation and confirmation change and the 28 November 2026 TARGET deployment both land more than ten months ahead of go-live, which is the point most planning conversations underweight.

What AMI-SeCo put in front of Swift

AMI-SeCo is an advisory group of market participants and central banks that the ECB convenes on securities settlement and collateral. It advises; it does not legislate, and it does not run Swift’s release schedule. So the 14 September 2026 letter is a formal request, not an instruction, and Swift retains the decision on when its deferred securities changes go live. The letter itself says a much broader set of considerations will feed Swift’s choice.

The substance of the request is narrow and specific. AMI-SeCo asked Swift to align the deployment date for its SR 2026 securities roll-out in 2027 with the TARGET Services June 2027 release on 12 June 2027, as a measure to support the transition to T+1. That is the entire ask. It does not change the June 2027 TARGET release, which was already scheduled; it asks Swift to bring its securities message deployment to the same date rather than run it earlier and alone in the first quarter.

It is worth being precise about who is moving what, because the easy misreading is that the ECB is delaying one of its own releases. The Eurosystem confirmed the November 2026 releases and set the June 2027 release; the moving part in this letter belongs to Swift. AMI-SeCo also flagged that further analysis is needed on two knock-on questions before anyone treats alignment as settled: the effect on corporate actions processing, and the effect on the date of the following year’s Standards Release, SR 2027.

Why a first-quarter Swift deployment eats the CSD testing window

The mechanism is a testing-calendar collision, and it is worth walking through because it explains the urgency. The June 2027 TARGET release for T2S has to be tested by depositories on the T2S interoperability test environment, known as EAC, before the community moves into the joint EU, UK and Switzerland T+1 testing windows. The harmonised EU, UK and Switzerland testing plan contains multiple 2027 windows, beginning with 1 to 12 February; 19 to 30 April is a subsequent window. T2S-specific EAC and UTEST scheduling is governed separately through the T2S testing and release process.

AMI-SeCo worked the arithmetic in its letter. On the assumption that a Swift SR 2026 securities deployment were aligned with a TARGET release on 20 February 2027, the depository testing phase on EAC would shrink from eight weeks, running 5 February to 2 April 2027, to four weeks, running 5 March to 2 April 2027, and would overlap the Easter period. That February date is AMI-SeCo’s illustrative scenario, not a planned date. The real concern is worse than the example: Swift is understood to be considering later dates in the first quarter to align with global markets, and later dates would compress the depository testing window further or eliminate it before the joint T+1 testing even begins.

AMI-SeCo’s requested alignment would put the Swift securities deployment on the same 12 June 2027 production date as the TARGET Services June release. The rationale stated by the ECB is to preserve the overall T+1 testing and migration timeline. The analysis behind this came from the CSD Steering Group inside the T2S governance structure.

The June 2027 T2S release and what a T+1 change actually touches

T2S is the Eurosystem platform on which euro area depositories settle securities against central bank money, and it is one of four TARGET Services alongside the T2 large-value payment system, the TIPS instant payment service, and the Eurosystem Collateral Management System. T2S settlement volumes rose 16.1% in 2025, so this is not a marginal pipe. The June 2027 T2S release includes changes linked to T+1. ECB T2S governance materials specifically place T2S-0858-URD, on adjustment of night-time settlement, and T2S-0865-URD, on a dedicated gating event, in R2027.JUN; hold and release, auto-partial settlement and auto-collateralisation are separately identified in the Commission-adopted settlement-discipline amendments for application from 11 October 2027 and should not be presented as the June T2S release scope without a release-specific source.

T2S uses ISO 20022 messaging. Swift continues to maintain MT and MX/ISO 20022 standards for securities messaging, and its Standards Release process updates those standards. The AMI-SeCo issue is the timing of Swift’s deferred securities-message changes against the TARGET Services June 2027 release, a co-ordination question between two existing ISO 20022 deployments.

AMI-SeCo’s position is that aligning the two deployments would help preserve the overall T+1 testing and migration timeline; the letter is a request to Swift, not a binding testing requirement.

How the ask sits inside the 11 October 2027 mandate

None of this floats free of hard law. The EU move to T+1 is set by Regulation (EU) 2025/2075 of 8 October 2025, published in the Official Journal on 14 October 2025, which amends the Central Securities Depositories Regulation (Regulation (EU) No 909/2014). It replaces Article 5(2) of CSDR so that, from 11 October 2027, the intended settlement date for in-scope transactions is no later than the first business day after trading. The in-scope perimeter is transactions in transferable securities executed on trading venues, with defined carve-outs, so it bites on trading-venue settlement and many other transfers fall outside it.

The settlement-discipline detail is being phased, and this is where “T+1” turns out to bite well before October 2027. The Commission adopted the amending delegated regulation C(2026) 4640 on 6 July 2026. As of 16 September 2026 it remains under European Parliament and Council scrutiny and is not yet in force; if the process is completed without objection and the act is published, it is scheduled to apply from 7 December 2026, with specified settlement-fails reporting changes from 1 July 2027 and specified settlement-instruction, hold-and-release, auto-partial-settlement and auto-collateralisation changes from 11 October 2027. For in-scope professional-client transactions, the adopted text sets a deadline of 23:00 CET on trade date for written allocations and confirmations and requires standardised electronic, machine-readable communications, subject to the specific Article 2 non-sending and same-firm exclusions and the temporary technical-unavailability exception. ESMA’s July 2026 statement says the first two industry readiness surveys showed uneven implementation levels. Our note on ESMA’s allocation and confirmation rules works through that first deadline in detail.

The AMI-SeCo request is the infrastructure counterpart to those obligations. The regulation fixes when firms must settle in one day; the TARGET release schedule and the Swift deployment date decide whether the machinery to do so has been tested together first.

The November 2026 release is a different animal

It is easy to fold the two 2026 developments into one story, and they are not the same. The November 2026 TARGET Services release covers T2, T2S, TIPS and ECMS. The timeline reassessment was triggered by Swift’s SR 2026 deferral and the unstructured-postal-address issue in payments, but the confirmed release scope is not payments-only. When Swift extended the SR 2026 timeline, the Eurosystem first said it would reassess the November releases, then decided to proceed while shifting the deployment from 14 November to 28 November 2026 and postponing the discontinuation of unstructured postal addresses. Our coverage of the November 2026 TARGET Services reassessment sets out that payments-side decision.

The securities upgrade in the AMI-SeCo letter is the separate, later track: the securities part of SR 2026 that Swift deferred into 2027 and that AMI-SeCo now wants aligned to the June 2027 T2S release. Different message domain, different platform release, different deadline. The reason to keep them apart in your own project plan is that the payments-address change and the securities messaging change belong to different teams, different test environments and different risk owners.

The coordination reaches beyond the euro area. The Bank of England deferred its own November 2026 RTGS standards release in its entirety, expressly to stay aligned with Swift and other infrastructures, and the joint T+1 testing windows that AMI-SeCo is trying to protect are a shared EU, UK and Switzerland exercise. Anyone tracking the UK leg can follow it through our note on UK T+1 settlement and FCA readiness.

What connected depositories and their participants can do before the dates harden

The letter does not create an obligation on banks, but it changes how a sensible readiness plan should be sequenced. Three practical moves follow from it.

First, treat the SR 2026 securities build and the June 2027 T2S release as one test event in your internal plan, not two, even before Swift confirms its date. If AMI-SeCo’s alignment request succeeds, that is exactly how they will arrive. If it does not, you will still want the two changes tested together instead of a first-quarter Swift deployment landing in the middle of your T2S migration testing.

Second, watch for Swift’s confirmation of the SR 2026 securities deployment date. Swift indicated a mid-September 2026 confirmation, and the AMI-SeCo letter is a direct attempt to steer that decision toward 12 June 2027. Until Swift confirms, the first-quarter 2027 date remains the working assumption in the letter, and your contingency planning has to cover the version where Swift keeps an earlier date and the depository testing window is compressed.

Third, do not let the infrastructure timeline distract from the regulatory one. The Commission-adopted amendments are scheduled to apply from 7 December 2026, subject to completion of the EU scrutiny and publication process. For in-scope professional-client transactions, they set a deadline of 23:00 CET on trade date and require standardised electronic, machine-readable communications, subject to the specific non-sending and same-firm exclusions in Article 2 and the temporary technical-unavailability exception. That change is independent of the TARGET and Swift release timing.

AMI-SeCo also flagged that further analysis is needed on two knock-on questions before anyone treats alignment as settled: the effect on corporate actions processing, and the effect on the date of the following year’s Standards Release, SR 2027. Neither is resolved in the letter, and both are worth a line in any migration risk log.

Frequently Asked Questions

Does the AMI-SeCo letter change any legal deadline for my institution?

No. The 11 October 2027 T+1 date is fixed by Regulation (EU) 2025/2075. The Commission adopted the settlement-discipline amending delegated regulation C(2026) 4640 on 6 July 2026, but as of 16 September 2026 it remains under European Parliament and Council scrutiny and is not yet in force. The AMI-SeCo letter is a request to Swift about message-upgrade timing and does not itself alter a statutory or regulatory deadline.

If Swift keeps its first-quarter 2027 date, what actually goes wrong?

According to the ECB, Swift’s envisaged first-quarter 2027 securities deployment could severely affect the testing timeline for the TARGET Services June 2027 release, which includes T+1 changes. The harmonised EU, UK and Switzerland testing plan contains several 2027 testing windows, while the 11 October 2027 EU T+1 application date is unchanged.

Is T2S being migrated from ISO 15022 to ISO 20022 as part of this?

No. T2S already operates on ISO 20022. Swift maintains MT standards and MX/ISO 20022 standards for securities messaging. The alignment question is about coordinating Swift’s deferred securities-message changes with the June 2027 T2S release; it is not a T2S conversion from ISO 15022 to ISO 20022.

What is the difference between the November 2026 release and the June 2027 release?

The November 2026 TARGET Services release covers T2, T2S, TIPS and ECMS, and its deployment moved to 28 November 2026. The unstructured-postal-address issue is a payments-specific part of the reassessment, not the scope of the whole TARGET Services release. The June 2027 release carries the T+1 changes for T2S securities settlement. They involve different message domains and different platforms, and should be planned separately.

Which transactions are actually in scope for EU T+1?

Regulation (EU) 2025/2075 amends Article 5(2) of CSDR to require settlement no later than the first business day after trading for transactions in transferable securities that are executed on trading venues, subject to the exemptions set out in that provision. It is a trading-venue settlement rule, so not every securities transfer is caught in the same way.

What should be finished before 7 December 2026?

The Commission-adopted amendments are scheduled to apply from 7 December 2026, subject to completion of the EU scrutiny and publication process. For in-scope professional-client transactions, written allocations and confirmations must reach the investment firm as soon as possible and no later than 23:00 CET on trade date and use standardised electronic, machine-readable communications. Article 2 also provides specific non-sending and same-firm exclusions, and permits non-structured communication only for documented temporary technical unavailability or service disruption.

Related Articles

• EU T+1 Settlement Transition: 2027 Deadlines: How Regulation (EU) 2025/2075 shortens the EU settlement cycle and the milestones on the way to 11 October 2027.
• ESMA T+1 Settlement Allocations and Confirmations: The allocation and confirmation obligations and the 7 December 2026 application date under the RTS on Settlement Discipline.
• TARGET Services November 2026 Reassessment: The payments-side release, the shift to 28 November 2026 and the unstructured postal address question.
• UK T+1 Settlement 2027 and FCA Readiness: The UK leg of the coordinated EU, UK and Switzerland move to T+1.
• ECB TARGET Services Annual Report 2025: Volume growth across T2, T2S, TIPS and the launch of the Eurosystem Collateral Management System.

Key Takeaways

• On 15 September 2026 the ECB published a 14 September AMI-SeCo letter asking Swift to align its SR 2026 securities upgrade with the TARGET Services June 2027 release on 12 June 2027.
• The driver is testing capacity: the ECB says a first-quarter 2027 Swift securities deployment could severely affect testing for the TARGET Services June 2027 release, while the harmonised EU, UK and Switzerland testing plan begins with a 1 to 12 February 2027 window.
• The letter asks Swift to act and places no new obligation on banks; Swift still decides its deferred securities deployment date, which it said it would confirm by mid-September 2026.
• EU T+1 is fixed at 11 October 2027 by Regulation (EU) 2025/2075, amending Article 5(2) of CSDR for transferable securities executed on trading venues.
• The settlement-discipline changes phase in earlier: allocations and confirmations expected from 7 December 2026, fails reporting from 1 July 2027, settlement-instruction mechanics from 11 October 2027.
• The November 2026 TARGET Services release is scheduled for deployment on 28 November 2026 and covers T2, T2S, TIPS and ECMS; it should be tracked separately from the June 2027 T2S release and Swift’s deferred 2027 securities changes.
• Plan the SR 2026 securities build and the June 2027 T2S release as one test event, and keep a contingency for Swift holding an earlier first-quarter date.
• AMI-SeCo says further analysis is required on the wider implications of alignment, including corporate actions processing and the SR 2027 release date.

Sources and References

• ECB, MIP News, “AMI-SeCo asks Swift to synchronise securities messages upgrade with TARGET Services June 2027 release”, 15 September 2026: ecb.europa.eu
• AMI-SeCo, letter to Swift, “AMI-SeCo request to SWIFT to align SR 2026 securities message upgrade with TARGET Services June 2027 release”, 14 September 2026 (PDF): ecb.europa.eu
• ECB, MIP News, “Reassessment of timeline for November 2026 TARGET Services releases”, 28 August 2026: ecb.europa.eu
• Regulation (EU) 2025/2075 of 8 October 2025 amending Regulation (EU) No 909/2014 as regards a shorter settlement cycle in the Union: EUR-Lex
• Regulation (EU) No 909/2014 (Central Securities Depositories Regulation, CSDR): EUR-Lex
• Commission Delegated Regulation C(2026) 4640 (amending Delegated Regulation (EU) 2018/1229 on settlement discipline), adopted 6 July 2026: EUR-Lex
• ESMA, Final Report on amendments to the RTS on Settlement Discipline and tools to improve settlement efficiency (ESMA74-2119945926-3430), 13 October 2025: esma.europa.eu
• ESMA, Consultation Paper on Guidelines on standardised procedures and messaging protocols under Article 6(2) of CSDR (ESMA74-2119945926-3513): esma.europa.eu
• ESMA, “ESMA calls on firms to finalise preparations ahead of T+1 settlement deadlines”: esma.europa.eu
• EU T+1 Industry Committee, UK Accelerated Settlement Taskforce, SwissSPTC, Joint T+1 Testing and Readiness Plan, March 2026: finextra.com (coverage)
• Swift, Standards Releases: swift.com
• Bank of England, “Delay to the November 2026 RTGS standards release”, 27 August 2026: bankofengland.co.uk
• ECB, TARGET Services (T2, T2S, TIPS, ECMS): ecb.europa.eu
• ECB, T2S Change Request T2S-0858-URD, “Adjustment of Night-Time Settlement for T+1 transition” (7 October 2025): ecb.europa.eu
• ECB, T2S Change Request T2S-0865-URD, “Dedicated T2S gating event for T+1 transition” (6 January 2026): ecb.europa.eu

The date that decides whether T+1 arrives tested

If Swift aligns its SR 2026 securities deployment with 12 June 2027, the Swift deployment and the TARGET Services June release would share a production date, which AMI-SeCo says would help preserve the overall T+1 testing and migration timeline. If Swift keeps a first-quarter 2027 date, the ECB says the TARGET Services June 2027 testing timeline could be severely affected. The next thing to watch is Swift’s confirmation of its securities deployment date. Separately, firms in scope of the Commission-adopted settlement-discipline amendments should prepare their allocation and confirmation processes for the adopted-text 23:00 CET trade-date deadline ahead of 7 December 2026, subject to the delegated regulation completing scrutiny, publication and entry into force.

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.