A member of
Eurex
1. Introduction
Trading Participants are required to provide corrections of historical final missing Short Codes and of historical Short Code registrations with invalid Long Codes. The start of the envisaged time-limited correction period for historical Short Code registrations will be postponed from 3 February 2025 to 1 April 2025. The T7 XML TR170 report structure was amended and an updated XSD is provided.
2. Required action
The trading venue will provide the T7 XML Member Reports TR170 and TR171 with the individual Trading Participant’s correction scope of historical final missing Short Codes and corrections of historical Short Code registrations with incorrect Long Codes. These reports will be available on 1 April 2025 via the Common Report Engine (CRE) and in the Short Code and Algo ID upload GUI. Trading Participants are required to retrieve the reports within ten business days. The start of the daily report processing of TR170 and TR171 is planned for the 2 June 2025 in order to provide Trading Participants with their correction progress. The correction period is scheduled for one year. The final submission deadline is 31 March 2026.
T7 XML report TR170 was updated and published as part of the T7 Release 13.0 documentation (details below). Trading Participants shall make themselves familiar with the changes and retrieve the new XSD, if required.
3. Details of the initiative.
The T7 XML Member Reports TR170 and TR171 will be introduced in order to enable Trading Participants to perform the task of historical Short Code correction. The correction period will start on 1 April 2025. Trading Participants are required to deliver final missing Short Codes and to correct Short Code registrations, i.e. which have an invalid Long Code. The historical correction scope encompasses the period from 1 April 2020 until 15 November 2024. Since the launch of the new Short Code solution including a correction facility with T7 Release 13.0, Trading Participants are required to submit any data of final missing Short Codes since the 18 November 2024 in due course. The T7 XML Report TR169 was introduced for this purpose.
Relevant T7 XML reports:
For the upload of these corrections, the regular upload file will be used. There will be a new Common Upload Engine (CUE) service “EXTREFDH” (also available in the Short Code and Algo ID upload GUI) for the upload of the Short Code registrations with an invalid Long Code. Successful corrections are covered in the new TR169 Report and negative validation results will be covered in the TR160 Report.
Related documentation is provided in the updated “Reporting handbook for audit trail and other regulatory reporting under the MiFID II/MiFIR regime” available on the Eurex website www.eurex.com under the following path:
Rules & Regs > Regulations > MiFID II/MiFIR > Client & Member Reference Data
T7 XML report structure of the TR170 was adapted and a new XSD provided. More information can be found on the Eurex website under the following path:
Support > Initiatives & Releases > T7 Release 13.0 > Reports
More detailed information on the correction period and a dedicated user manual will be published in due course.
Further information
Recipients: | All Trading Participants of Eurex Deutschland and Vendors | |
Target groups: | Front Office/Trading, Middle + Backoffice, IT/System Administration, Auditing/Security Coordination | |
Related circulars: | ||
Related newsflashes: | Eurex Readiness Newsflashes from 14 October 2024, 16 October 2024, 15 November 2024 | |
Contact: | client.services@eurex.com | |
Web: | Rules & Regs > Regulations > MiFID II/MiFIR > Client & Member Reference Data; | |
Authorized by: | Melanie Dannheimer |
Market Status ⓘ
XEUR
The market status window is an indication regarding the current technical availability of the trading system. It indicates whether news board messages regarding current technical issues of the trading system have been published or will be published shortly.
Please find further information about incident handling in the Emergency Playbook published on the Eurex webpage under Support --> Emergencies and safeguards. Detailed information about incident communication, market re-opening procedures and best practices for order and trade reconciliation can be found in the chapters 4.2, 4.3 and 4.5, respectively. Concrete information for the respective incident will be published during the incident via newsboard message.
We strongly recommend not to take any decisions based on the indications in the market status window but to always check the production news board for comprehensive information on an incident.
An instant update of the Market Status requires an enabled up-to date Java™ version within the browser.