{"release":{"id":"7a41a2cc5aaf78412593b2d310cf279f6d209fcbf373aa170d236de8b21d8f21","published":"2026-11-17T06:41:06Z","pinned":false},"limits":{"coverage":{"history":"current_only","held_since":"2026-11-16","gaps":[],"covered":["2017/574 — RTS — Level of accuracy of business clocks [no longer in force] L2"],"not_covered":["national guidance","court decisions"]},"freshness":{"release_id":"7a41a2cc5aaf78412593b2d310cf279f6d209fcbf373aa170d236de8b21d8f21","release_published":"2026-11-17T06:41:06Z","checked_at":"2026-11-16","checked_against":"EUR-Lex"},"truncation":null,"failures":[],"incomplete":[]},"page":{"path":"/mifid-ii/level-2/rts/2017-574-the-level-of-accuracy-of-business-clocks","url":"https://www.headlesslaw.com/mifid-ii/level-2/rts/2017-574-the-level-of-accuracy-of-business-clocks","title":"2017/574 — RTS — Level of accuracy of business clocks [no longer in force]","family":"l2","work_id":"spaces/mifid-ii/level-2/rts/2017-574-the-level-of-accuracy-of-business-clocks","status":"repealed","force_status":"no_longer_in_force","date_state":"no_longer_in_force","requested_date":null,"as_of":"2026-11-18","applies_from":null,"application":null,"version_label":"Commission Delegated Regulation (EU) 2017/574, OJ L 87, 31.3.2017","check":{"against":"EUR-Lex","on":"2026-11-16"},"check_result":"matched","official_url":"https://eur-lex.europa.eu/eli/reg_del/2017/574/oj/eng","valid_from":null,"valid_until":"2026-03-02","revision":1,"content_id":"f8525c664df245d3","change_date":null,"nearest_versions":["2026-11-16"],"first_text_date":"2016-06-07","correction_applies":false,"versions":["2026-11-16"],"version_url":"https://www.headlesslaw.com/mifid-ii/level-2/rts/2017-574-the-level-of-accuracy-of-business-clocks/versions/2026-11-16","revision_url":"https://www.headlesslaw.com/mifid-ii/level-2/rts/2017-574-the-level-of-accuracy-of-business-clocks/versions/2026-11-16/rev/f8525c664df245d3","versions_url":"https://www.headlesslaw.com/mifid-ii/level-2/rts/2017-574-the-level-of-accuracy-of-business-clocks/versions","relations_url":"https://www.headlesslaw.com/mifid-ii/level-2/rts/2017-574-the-level-of-accuracy-of-business-clocks/relations","source_line":"Commission Delegated Regulation (EU) 2017/574 · superseded — not in force · OJ L 87, 31.3.2017 · dated 7 Jun 2016 [no longer in force]","attribution":{"prepared_by":"European Commission","published_by":"Publications Office of the EU","published_in":"Official Journal of the European Union","document_type":"delegated_regulation","legal_nature":"binding_adopted","addressees":"not stated in the document","dates":{"document_date":"2016-06-07","entry_into_force":"2017-04-20","locators":{"document_date":"CELLAR 32017R0574 work_date_document","entry_into_force":"CELLAR 32017R0574 resource_legal_date_entry-into-force (earliest on or after the document date)"}},"adoption":null}},"provenance":{"official_url":"https://eur-lex.europa.eu/eli/reg_del/2017/574/oj/eng","check":{"result":"matched","checked_at":"2026-11-16","against":"EUR-Lex"},"repo_path":null,"body_sha256":"daa86d2306b90f1548c05cf2ae2f3f8c37159b841133c0f317112bb538ad0c80","markdown_sha256":"ed6562e114101a67edf1afa5da34e192a44fa47ef45609615a860b05536574da"},"units":[],"markdown":"**Commission Delegated Regulation (EU) 2017/574 · superseded — not in force · OJ L 87, 31.3.2017 · dated 7 Jun 2016 [no longer in force]**\n\n*No longer in force · Commission Delegated Regulation (EU) 2017/574, OJ L 87, 31.3.2017 · Verified 16 Nov 2026 · [Official source](https://eur-lex.europa.eu/eli/reg_del/2017/574/oj/eng)*\n\n| | |\n|---|---|\n| **Instrument** | Commission Delegated Regulation (EU) 2017/574 (RTS) |\n| **CELEX** | [32017R0574](https://eur-lex.europa.eu/legal-content/EN/TXT/?uri=CELEX:32017R0574) |\n| **OJ reference** | OJ L 87, 31.3.2017 |\n| **Drafted by** | ESMA |\n| **Legal nature** | Superseded — not in force |\n| **Legal basis** | the third subparagraph of Article 50(2) MiFID II |\n| **Adopted** | 7 June 2016 |\n| **In force** | 20 April 2017; end of validity 1 March 2026 (CELLAR) |\n| **Corrigenda** | None in English (CELLAR) |\n| **Related instruments** | Repealed by Commission Delegated Regulation (EU) 2025/1155 ([EUR-Lex](https://eur-lex.europa.eu/eli/reg_del/2025/1155/oj/eng); [page](https://www.headlesslaw.com/mifir/level-2/rts/2025-1155-commission-delegated-regulation-eu-2025-1155-of-12-june)) |\n| **Text on this page** | Word for word — title, recitals, articles and annexes as in the OJ act; not reproduced: citations, enacting formula, closing formula, signature and OJ footnotes |\n\n**COMMISSION DELEGATED REGULATION (EU) 2017/574 of 7 June 2016 supplementing Directive 2014/65/EU of the European Parliament and of the Council with regard to regulatory technical standards for the level of accuracy of business clocks (Text with EEA relevance)**\n\n## Recitals\n\n1. Clock synchronisation has a direct impact in many areas. In particular it contributes to ensuring that post-trade transparency data can readily be part of a reliable consolidated tape. It is also essential for conducting cross-venue monitoring of orders and detecting instances of market abuse and allows for a clearer comparison between the transaction and the market conditions prevailing at the time of their execution.\n2. The number of orders received every second by a trading venue can be very high, much higher than that of executed transactions. This may extend to several thousands of orders per second depending on the trading venue, the type of members or participants or clients of a given trading venue, and the financial instruments' volatility and liquidity. As a result, a time granularity of one second would not be sufficient for the purposes of effective market manipulation surveillance of certain types of trading activities. Therefore, it is necessary to establish minimum granularity requirements for recording the date and time of reportable events by operators of trading venues and their members or participants.\n3. Competent authorities need to be able to reconstruct all events relating to an order throughout the lifetime of each order in an accurate time sequence. Competent authorities need to be able to reconstruct these events over multiple trading venues on a consolidated level to be able to conduct effective cross-venue monitoring on market abuse. It is therefore necessary to establish a common reference time and rules on maximum divergence from the common reference time to ensure that all operators of trading venues and their members or participants are recording the date and time based on the same time source and in accordance with consistent standards. It is also necessary to provide for accurate time stamping to allow competent authorities to distinguish between different reportable events which may otherwise appear to have taken place at the same time.\n4. There are however, trading models for which increased accuracy might not be relevant or feasible. Voice trading systems or request for quote systems where the response requires human intervention or does not allow algorithmic trading, or systems which are used for concluding negotiated transactions should be subject to different accuracy standards. Trading venues operating those trading systems are not typically susceptible to the high volume of events that can happen within the same second, meaning that it is not necessary to impose a finer granularity to time stamping of those events since it is less likely that there would be multiple events occurring at the same time. In addition, trades on those trading venues may be agreed using manual methods which can take time to agree. In those trading venues there is also an inherent delay between the moment when the trade is executed and the moment when the trade is recorded in the trading system, meaning that applying more stringent accuracy requirements would not necessarily lead to more meaningful and accurate record keeping by the operator of the trading venue, its members or participants.\n5. Competent authorities need to understand how trading venues and their members or participants are ensuring their traceability to Coordinated Universal Time (UTC). This is because of the complexity of the different systems and the number of alternative methods that can be used to synchronise to UTC. Given that clock drift can be affected by many different elements, it is also appropriate to determine an acceptance level for the maximum divergence from UTC.\n6. For reasons of consistency and in order to ensure the smooth functioning of the financial markets, it is necessary that the provisions laid down in this Regulation and the related national provisions transposing Directive 2014/65/EU apply from the same date.\n7. This Regulation is based on the draft regulatory technical standards submitted by the European Securities and Markets Authority (ESMA) to the Commission.\n8. ESMA has conducted open public consultations on the draft regulatory technical standards on which this Regulation is based, analysed the potential related costs and benefits and requested the opinion of the Securities and Markets Stakeholder Group established by Article 37 of Regulation (EU) No 1095/2010 of the European Parliament and of the Council,\n\n## <a id=\"art-1\"></a>Article 1 — Reference time\n\nOperators of trading venues and their members or participants shall synchronise the business clocks they use to record the date and time of any reportable event with the Coordinated Universal Time (UTC) issued and maintained by the timing centres listed in the latest Bureau international des poids et mesures Annual Report on Time Activities. Operators of trading venues and their members or participants may also synchronise the business clocks they use to record the date and time of any reportable event with UTC disseminated by a satellite system, provided that any offset from UTC is accounted for and removed from the timestamp.\n\n## <a id=\"art-2\"></a>Article 2 — Level of accuracy for operators of trading venues\n\n1. <a id=\"art-2-p-1\"></a>Operators of trading venues shall ensure that their business clocks adhere to the levels of accuracy specified in Table 1 of the Annex according to the gateway to gateway latency of each of their trading systems.\nGateway to gateway latency shall be the time measured from the moment a message is received by an outer gateway of the trading venue's system, sent through the order submission protocol, processed by the matching engine, and then sent back until an acknowledgement is sent from the gateway.\n1. <a id=\"art-2-p-2\"></a>By derogation from paragraph 1, operators of trading venues that operate a voice trading system, request for quote system where the response requires human intervention or does not allow algorithmic trading, or a system that formalises negotiated transactions in accordance with Article 4(1)(b) of Regulation (EU) No 600/2014 of the European Parliament and of the Council shall ensure that their business clocks do not diverge by more than one second from UTC referred to in Article 1 of this Regulation. The operator of the trading venue shall ensure that times are recorded to at least a one second granularity.\n1. <a id=\"art-2-p-3\"></a>Operators of trading venues that operate multiple types of trading systems shall ensure that each system adheres to the level of accuracy applicable to that system in accordance with paragraphs 1 and 2.\n\n## <a id=\"art-3\"></a>Article 3 — Level of accuracy for members or participants of a trading venue\n\n1. <a id=\"art-3-p-1\"></a>Members or participants of trading venues shall ensure that their business clocks used to record the time of reportable events adhere to the level of accuracy specified in Table 2 of the Annex.\n1. <a id=\"art-3-p-2\"></a>Members or participants of trading venues that engage in multiple types of trading activities shall ensure that the systems that they use to record reportable events adhere to the level of accuracy applicable to each of these trading activities in accordance with the requirements set out in Table 2 of the Annex.\n\n## <a id=\"art-4\"></a>Article 4 — Compliance with the maximum divergence requirements\n\nOperators of trading venues and their members or participants shall establish a system of traceability to UTC. They shall be able to demonstrate traceability to UTC by documenting the system design, functioning and specifications. They shall be able to identify the exact point at which a timestamp is applied and demonstrate that the point within the system where the timestamp is applied remains consistent. They shall conduct a review of the compliance of the traceability system with this Regulation at least once a year.\n\n## <a id=\"art-5\"></a>Article 5 — Entry into force and application\n\nThis Regulation shall enter into force on the twentieth day following that of its publication in the Official Journal of the European Union.\nIt shall apply from 3 January 2018.\n\n## ANNEX\n\nANNEX\nTable 1\nLevel of accuracy for operators of trading venues\n\n<!-- lint: table-cell-ok — verbatim annex reporting-template grid from the source regulation -->\n| Gateway-to-gateway latency time of the trading system | Maximum divergence from UTC | Granularity of the timestamp |\n|---|---|---|\n| > 1 millisecond | 1 millisecond | 1 millisecond or better |\n| ≤ 1 millisecond | 100 microseconds | 1 microsecond or better |\n\nTable 2\nLevel of accuracy for members or participants of a trading venue\n\n<!-- lint: table-cell-ok — verbatim annex reporting-template grid from the source regulation -->\n| Type of trading activity | Description | Maximum divergence from UTC | Granularity of the timestamp |\n|---|---|---|---|\n| Activity using high frequency algorithmic trading technique | High frequency algorithmic trading technique. | 100 microseconds | 1 microsecond or better |\n| Activity on voice trading systems | Voice trading systems as defined in Article 5(5) of Commission Delegated Regulation (EU) 2017/583 | 1 second | 1 second or better |\n| Activity on request for quote systems where the response requires human intervention or where the system does not allow algorithmic trading | Request for quotes systems as defined in Article 5(4) of Delegated Regulation (EU) 2017/583 | 1 second | 1 second or better |\n| Activity of concluding negotiated transactions | Negotiated transaction as set out in Article 4(1)(b) of Regulation (EU) No 600/2014. | 1 second | 1 second or better |\n| Any other trading activity | All other trading activity not covered by this table. | 1 millisecond | 1 millisecond or better |\n\n## Related Level 1 articles\n\n- [Article 50 — Synchronisation of business clocks](https://www.headlesslaw.com/mifid-ii/articles/50)\n"}