With the introduction of Regulatory Reporting Solution (RRS) Release 1.4, RRS will be compatible with the changes resulting from the initiatives introduced with the T7 Release 13.0:
Simulation start: 28 October 2024
Production start: 18 November 2024
Circulars
Participants Requirements
Feature/Enhancement | Details | Action Item |
| Enhanced registration and maintenance process for Short Codes and Algo IDs | With T7 Release 13.0, an enhanced registration and maintenance process for Short Codes and Algo IDs will be introduced. The introduction of RRS Release 1.4 will ensure that valid registered Short Codes and Algo IDs are submitted to the RRS as part of the transaction report creation process for non-MiFIR Trading Participants. | For details on enhanced registration and maintenance process for Short Codes and Algo IDs, please refer to the RRS 1.4 Simulation Guide (to be published soon on this webpage) for understanding test cases, and GUI – Short Code ID and Algo ID upload User Guide and Reporting handbook for audit trail and other regulatory reporting under the MiFID II / MiFIR regime.
|
Are you looking for information on a previous initiative? We have stored information about our previous initiatives in our Archive for you!
Contacts
Eurex Frankfurt AG
Customer Technical Support / Technical Helpdesk
Service times from Monday 01:00 – Friday 22:00 CET
(no service on Saturday and Sunday)
T +49-69-211-VIP / +49-69-211-1 08 88 (all)
Eurex Frankfurt AG
Key Account Management
Service times from 09:00 - 18:00 CET
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.