Initiatives & Releases

Readiness for projects

CCS RRS Release 2.0

Key updates to the Regulatory Reporting Solution (RRS) are on the horizon with the introduction of Client Convenient Solution (CCS). These changes, set to be implemented, will affect both MiFIR and non-MiFIR members and are designed to enhance efficiency and flexibility in transaction reporting.

Mandatory updates for all Trading Members: 

  • New XML Schema Definitions (XSDs) for reports TR160 and TR161 
  • New Short Code upload files

Optional enhancements for non-MiFIR members: 

  • The creation of one-off registrations for SCLC combinations, including personal identification data (First Name, Surname, Date of Birth)
  • New enrichment options via SCLC upload/GUI


Simulation start: 01 December 2025
Production start: 16 March 20256

Timeline Eurex (1)









Participants Requirements

Feature/Enhancement

Details

Action Item

 

The new XML Schema Definitions (XSDs) for reports TR160 and TR161

As part of the T7 Release 14.0, new XML Schema Definitions (XSDs) have been introduced to support updated report formats.


Report TR160 will include the following new error codes:


  • Error Code 50 – Invalid Value in DateOfBirth
  • Error Code 51 – Invalid Value in FirstName
  • Error Code 52 – Invalid Value in SurName
  • Error Code 53 – Incomplete Personal Data


Report TR161 will be enhanced with new fields:


  • FirstName
  • Surname
  • DateOfBirth

To leverage these improvements and ensure the reporting remains fully compliant, all Trading Participants are required to adopt to the new XSDs. This essential update is the next step toward more streamlined and accurate reporting.

The new Short Code upload Files


To streamline your reporting process, we have launched a new service tailored for Trading Participants:


  • New Dedicated Service: Use the new EXTREFNM channel for all non-MiFIR SCLC business.
  • Simplified Data Upload: Directly upload buyer/seller personal data, including First Name, Surname, and Date of Birth.
  • Improved Accuracy: The system now validates uploads by participant type, ensuring correct processing and preventing errors.
  • No Change for MiFIR Members: MiFIR participants continue to use the existing EXTREFDA service.

To take advantage of the latest system improvements and maintain full reporting compliance, we ask that all non-MiFIR Trading Participants to review the new requirements for Short Code upload files.

New enrichment options via SCLC upload/GUI

We are introducing a new optional enhancement for non-MiFIR Trading Participants, that gives more flexibility. Members can now enrich transaction data with personal identification details using two different timelines:


  • Same-Day Enrichment: Add data via the SCLC upload or GUI until 23:30 CET/CEST on the day of the trade (T).
  • Next-Day Enrichment: Add data via SCLC/RRS until 18:00 CET/CEST on the business day after the trade (T+1).

To ensure your data remains accurate and consistent, you must choose only one of these methods per transaction. Using both the SCLC upload/GUI and the RRS method for the same trade can cause data conflicts and reporting errors.


Eurex Initiatives Lifecycle

From the announcement till the rollout, all phases of the Eurex initiatives outlined on one page! Get an overview here and find other useful resources.

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
Key Account Management

Service times from 09:00 - 18:00 CET

client.services@eurex.com

 


   

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.