Navigating the New MiFID II and MiFIR Clock Synchronisation Requirements

What's actually changed since 2018

MiFID II and the supporting MiFIR regulation went into force across the EU on 3 January 2018. The clock synchronisation expectations under Regulatory Technical Standard 25 (RTS 25) were already tight at that point — 100 microseconds traceable to UTC for high-frequency trading, 1 millisecond for other algorithmic trading, with timestamp granularity at least matching the divergence ceiling. What's changed in the years since is not the headline numbers but the supporting interpretation: ESMA Q&A guidance, national competent authority enforcement positions, and the operational expectations of how firms demonstrate compliance.

The result is that the regulatory baseline has tightened in practice without the headline numbers changing. Firms that built their MiFID II compliance posture in 2018 and haven't revisited it should reconfirm that their current architecture, documentation and audit trail meet 2026 expectations rather than 2018 expectations.

What "extended scope" actually means

The phrase "extended scope" in the context of MiFID II clock synchronisation usually refers to two things. First, the operational definition of high-frequency trading has been refined by ESMA and national authorities to capture activity that wasn't always identified as HFT in 2018 — sub-millisecond trading systems, algorithmic market making with co-located infrastructure, certain quote-generating activities. Firms that previously thought they fell under the 1 ms algorithmic-trading budget may now fall under the 100 µs HFT budget.

Second, the audit trail expectations have been extended in practice. Firms are now expected to demonstrate not only that their clocks are accurate at the moment of an examination, but that they were accurate at any historical point in time within the regulatory retention period (5+ years). This requires continuous timing telemetry capture, tamper-evident long-term storage, and the operational ability to produce historical audit reports on demand. None of this is new in the rule text — it's been there since 2018 — but enforcement expectations have firmed up around it.

What firms should be doing now

Three actions, in priority order. First, audit current architecture against current ESMA guidance rather than 2018 interpretation. The headline numbers in RTS 25 haven't changed, but the supporting guidance has, and the practical compliance bar is higher than it was. Second, confirm activity classification: HFT, algorithmic trading, market making, systematic internaliser. Misclassification produces a precision budget mismatch that surfaces during the next examination. Third, audit the continuous-monitoring and audit-trail layer. If you can't currently produce a historical phase-offset report for any specific minute in the past three years on demand, you have a gap to close before the next examination notice arrives.

Where TimeBeat fits

TimeBeat builds the open-standard PTP grandmasters and audit-defensible Sync Insight observability platform that regulated investment firms use to meet MiFID II / MiFIR clock synchronisation requirements. Our customers include market makers, trading venues, prime brokers and clearing houses across European markets. We focus on the audit-defence layer because it's the part of compliance that most firms underestimate — the precision itself is straightforward; the operational layer that proves the precision is what's expensive.