Eurex
With this Newsflash, Eurex wants to inform you about the introduction of a new Client Convenient Solution (CCS) to ease the transaction reporting for non-MiFIR Trading Participants.
The new functionality introduces optional enhancements to the existing Regulatory Reporting Solution (RRS) and Short Code-Long Code (SCLC) Application.
The Client Convenient Solution (CCS) simplifies transaction reporting for non-MiFIR Trading Participants by enabling one-off registrations of Short Code-Long Code combinations including personal data (first name, last name, date of birth). These can be reused for reporting as long as the combination remains valid, reducing manual effort and improving data accuracy. CCS helps prevent incomplete reports and supports overall data quality.
Please note: MiFIR Trading Participants, although unaffected by the new SCLC upload and related report changes, are still required to adopt the new XSD that will be introduced with T7 Release 14.0.
The first preparations for the upcoming CCS offer will be part of the broader technical readiness for T7 Release 14.0. This release will introduce new XML Schema Definitions (XSDs) which are required for compatibility with the updated report formats. All Trading Participants are expected to adopt these new XSDs to ensure seamless integration with the revised reporting infrastructure. The complete CCS rollout will follow in a subsequent phase and will be announced in due time.
As part of T7 Release 14.0, the reports TR160 and TR161 will be updated to reflect the new technical solution. These updates will be accompanied by the new XSDs, which all Trading Participants must adopt to ensure compatibility with the revised reporting formats.
Report TR160 will include new error codes:
Report TR161 will be enhanced with new fields:
The addition of this data via the SCLC upload file is optional. Non-MiFIR Participants can continue to add the buyer/seller details via the RRS upload file solution. However, non-MiFIR Trading Participants should opt for one method of data provision to ensure data accuracy.
Further details on the release timeline and preparatory steps will be communicated in due course in a subsequent circular, allowing all Trading Participants time to prepare for the upcoming changes.
Furthermore, the Common Upload Engine (CUE) will be enhanced to distinguish between MiFIR and non-MiFIR Trading Participants during upload, allowing for separate processing of their data. Validation will be enforced bidirectionally: any attempt by MiFIR entities to access non-MiFIR services, or by non-MiFIR entities to access MiFIR services, will result in rejection accompanied by a dedicated error code.
If you have questions or require further information, kindly send an e-mail to: mifid.reporting@deutsche-boerse.com.
Kind regards,
Your Client Services Team
Visit now Eurex Support Trading to access a wide array of support content!
Further Information
Recipients: | All Trading Participants of Eurex Deutschland and Vendors | |
Target groups: | Front Office/Trading, Middle + Backoffice, IT/System Administration, Auditing/Security Coordination | |
Contact: | mifid.reporting@deutsche-boerse.com | |
Web: | www.eurex.com > Rules & Regs > Regulations > MiFID II/MiFIR > Reporting |
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.