Find
01 Apr 2025

Eurex

MiFID II/MiFIR order flagging requirements: Short Code solution – Start of period for historical corrections phase

Eurex Circular 026/25 MiFID II/MiFIR order flagging requirements: Short Code solution – Start of period for historical corrections phase

1.   Introduction

With this circular, we are confirming the announced start of the historical corrections (HC) period on 1 April 2025. Trading Participants shall correct incurred final missing and registered Short Codes, which have an invalid Long Code, until 31 March 2026. A dedicated HC client manual and updated client documentation are available on the Eurex website.

HC phase start: 1 April 2025
HC phase end: 31 March 2026

2.   Required action

Trading Participants are required to download their individual correction scope, which is provided in the T7 XML Member Reports TR170 and TR171. The reports are available from 1 April 2025 until 15 April 2025 and shall be downloaded from the Common Report Engine (CRE) or in the Short Code and Algo ID upload GUI.

The start of the daily report processing of TR170 and TR171 is planned for 2 June 2025 in order to provide Trading Participants with their correction progress, i.e. successful corrections are excluded from these reports. Negative validation results are documented in the TR160 and successful corrections are documented in the TR169. The correction period is scheduled for one year. The final submission deadline is 31 March 2026.

3.  Details of the initiative.

There are two new T7 XML Member Reports TR170 and TR171 designed to facilitate the task of historical Short Code correction. The Report TR170 will provide Trading Participants with their individual correction scope of historical Short Code final missings. The Report TR171 will provide Trading Participants with their individual correction scope of historical Short Code registrations, which have an incorrect Long Code. The reports are also available in the simulation environment since 26 March 2025. The production reports will be provided with the date of 20250331 in the file name:

  • Example report name for TR170: RPTTR170GDBXX20250331XEURT7.XML_ZIP

For the upload of these corrections, the regular upload file will be used. There is a new Common Upload Engine (CUE) service “EXTREFDH” available, (also available in the Short Code and Algo ID upload GUI) for the upload of the Short Code registrations, which have an incorrect Long Code. Documentation of valid corrections will be provided in the TR169 Report and negative validation results will be provided in the TR160 Report. 

Please find the dedicated “Historical Corrections User Guide” and updated client documentation on the Eurex website www.eurex.com under the following path:

Rules & Regs > Regulations > MiFID II/MiFIR > Client & Member Reference Data


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: 

Eurex Circulars 063/24084/24129/24

Related Eurex Newsflash:

MiFID II/MiFIR order flagging requirements: Documentation about historical Short Code corrections and other updates

Contact:

mifid.reporting@deutsche-boerse.com

Web:

Rules & Regs > Regulations > MiFID II/MiFIR > Client & Member Reference Data

Authorized by:

Melanie Dannheimer


Market Status

XEUR

4 April 2025

5:29:16 AM


Production newsboard

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.