A member of
Eurex
1. Introduction
With this circular, Eurex Deutschland informs about the RRS Release 1.7, affecting all Trading Participants outside the scope of MiFIR regulation ("Non-MiFIR Trading Participants"). With the introduction of RRS Release 1.7 effective 30 June 2025, changes to the handling of the Backup Enrichment File (BKU) and an automated derivation of the Commodity Derivative Indicator (Field 64) from T7 will be implemented.
Simulation start: 12 May 2025
Production start: 30 June 2025
Further information about the RRS Release 1.7 can be found on the Eurex website www.eurex.com under the following link: Support > Initiatives & Releases > Readiness for projects > Regulatory Reporting Solution 1.7 for non-MiFIR firms.
2. Required action
Non-MiFIR Trading Participants are requested to initiate the preparatory steps to ensure readiness for the RRS Release 1.7 on 30 June 2025, if necessary. Recommended testing scenarios will be provided in the “Simulation Participation guide” which will be available before Simulation start on the website mentioned above.
3. Details of the initiative
A. Availability of simulation environment
A dedicated release simulation environment will be provided to give non-MiFiR Trading Participants the opportunity to perform comprehensive testing of their trading applications, independent of the RRS production environment. The simulation environment will be available for testing from 12 May 2025 until further notice.
B. Overview of functional enhancements
With RRS Release 1.7, incomplete mandatory fields (buyer, seller, execution responsible, or investment decision) will be flagged with a "final missing" status in the BKU file. This status will apply to transactions where a Non-MiFIR Trading Participant fails to provide the required information via a valid Upload File (TVUPL) during the daily enrichment and correction process by the T+1, 18:00 CE(S)T deadline.
Furthermore, as of RRS Release 1.7, Eurex Trading Participants will see automated mapping of the Commodity Derivative Indicator (Field 64) using executed trade order data. TVUPL uploads for this field will no longer be accepted by RRS.
Effective 30 June 2025, all Non-MiFIR Trading Participants are required to utilize the OrderAttributeRiskReduction field (ETI 23003) in T7 to indicate the hedging status for all commodity derivative orders.
The known limitations list for RRS Release 1.7 is available on the Eurex website under the following path:
Support > Initiatives & Releases > Readiness for projects > Regulatory Reporting Solution 1.7 for non-MiFIR firms.
If you have any further questions, please do not hesitate to contact the Regulatory Reporting & Monitoring Team at mifid.reporting@deutsche-boerse.com.
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 005/24 (RRS Release 1.2), 068/24 (RRS Release 1.3), 105/24 (RRS Release 1.4) | |
Contact: | Regulatory Reporting & Monitoring, mifid.reporting@deutsche-boerse.com | |
Web: | Support > Initiatives & Releases > Readiness for projects > Regulatory Reporting Solution 1.7 for non-MiFIR firms | |
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.