T2S Release R2024.SEP – Introduction on 28 September 2024 – Final update
Note: This Announcement, originally published on 7 May 2024 and updated on 20 August 2024, has been further updated to indicate the reduced scope of this T2S release. Changes have been highlighted.
Clearstream Banking AG, Frankfurt,1 informs on the TARGET2-Securities (T2S) Problem Release in September 2024 (R2024.SEP). According to the T2S Release Concept, the resolution for various T2S Problem Tickets (PBIs) will be deployed on
Saturday, 28 September 2024
for business day Monday, 30 September 20242
T2S Release R2024.SEP – Scope
Based on the T2S status reporting of mid-September 2024, the T2S Problem Release R2024.SEP is planned to solve ten Problem Tickets in production. Two of them are relevant for CBF clients operating in ICP or DCP mode (see attachment). PBI 233306 has not achieved the intended test results and has been descoped.
T2S Release R2024.SEP – Transition plan
On 17 September 2024, the Market Infrastructure Board (MIB) has decided the deployment of T2S Release R2024.SEP to production based on the outcome of the testing campaign.
The implementation of the software will take place during the weekend’s T2S maintenance window – meaning that currently no changes to the T2S Operational Day are expected for the End of Day (EOD) procedure on Friday, 27 September 2024, or for the start of business day, Monday, 30 September 2024.
Contact
For further information, clients may contact Clearstream Banking Client Services or their Relationship Officer. Questions related to the technical connection can be addressed to Connectivity Support. Particular questions related to the production launch in September 2024 will be routed to the experts of the T2S Settlement Functionality team.
------------------------------------------
1. This Announcement is published by Clearstream Banking AG (CBF), registered office at Mergenthalerallee 61, 65760 Eschborn, Germany, registered with the Commercial Register of the District Court in Frankfurt am Main, Germany, under number HRB 7500.
2. Due to scheduling constraints, the implementation was exceptionally postponed from the third to the fourth weekend in September.