T2S Release 3.1 – Introduction on 21 September 2019 – Final update of scope


Note: This announcement originally published on 14 May 2019 was updated on 16 July 2019 to reflect changes in the scope of the T2S Release. This final update provides the list of Problem Tickets that will be implemented in September 2019. Changes have been highlighted.

Clearstream Banking AG, Frankfurt1 informs customers about the latest scope elements of TARGET2-Securities (T2S) Release 3.1. According to the T2S Release Concept, the resolution for various T2S Problem Tickets (PBIs) will be deployed on

Saturday, 21 September 2019
for the business day Monday, 23 September 2019

T2S Release 3.1 – Scope

Based on the T2S status reporting on 27 August 2019, with the T2S Release 3.1 the resolution of 21 Problem Tickets is envisaged for a delivery in production. 

CBF’s final assessment related to these Problem Tickets shows that the fixes do not require software changes in CBF. More details are available in the attached file that provides the latest information about the related PBIs that might have impact on CBF’s customers acting in ICP and / or DCP mode. Customers are recommended to validate these scope elements and check whether operational and / or functional modifications in their procedures are required. Therefore, the file shows from the entire scope elements ten PBIs that will be deployed according to the T2S Service Transition Plan.

The changes to the last published list are highlighted in colour. The comparison shows that: 

  • PBI 204404 "CDLR status not visible” has been rescheduled for implementation. The resolution is planned to be delivered with T2S Release 3.3 in February 2020. This PBI is related to the T2S GUI and therefore of interest for customers acting in DCP mode.
  • Implementation of fixes has been confirmed for:
    • PBI 204475 “Missing feedback for "Hold / Release" via "Securities Settlement Conditions Modification Request" (sese.030)”; and
    • PBI 204715 “Issue with the restart of RTS procedure”.

T2S Release 3.1 – Transition plan

The Market Infrastructure Board (MIB) will decide on the deployment of T2S Release 3.1 in production once the expected results have been shown during testing. On Tuesday, 10 September 2019, the final decision, known as “Go/No-Go Decision”, is to be made.

The deployment of T2S Release 3.1 into production is foreseen for the business day Monday, 23 September 2019. The implementation of the software will take place during the weekend within the T2S maintenance window. Meaning that currently no changes in the T2S Operational Day are expected; neither for the end of day (“EoD”) procedure on Friday, 20 September 2019, nor for the start of the business day, Monday, 23 September 2019.

The below table provides an overview of the important T2S milestones:

T2S Release 3.1 Timeline

T2S Service Transition Plan – Activity for T2S Release 3.1Date
Go / No-Go deployment to UTEST by OMGThursday, 30 July 2019
Deployment to UTESTFriday, 9 August 2019
End of testing of scope elements in UTESTWednesday, 4 September 2019
Final approval of deployment to Production by MIBTuesday, 10 September 2019
Deployment to Production environmentSaturday, 21 September 2019

Customer simulation

The simulation activities can be conducted in a “free simulation mode”. The already established static data for CBF accounts and the related connectivity settings in the CBF customer simulation environment (IMS23) remain unchanged.

CBF still maintains its technical link to UTEST so that customers can test on their demand. The ECB initially installed the software update in UTEST on Friday, 9 August 2019.


Please contact our Client Services teams for questions regarding the functionality. Questions related to the technical connection can be addressed to our Connectivity Support teams. Particular questions related to the T2S Release 3.1 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.