> For the complete documentation index, see [llms.txt](https://www.headlesslaw.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://www.headlesslaw.com/mifir/articles/27ha.md).

# Article 27ha — Reporting obligations for CTPs

*In force · Consolidated version of 23 November 2025 · Checked against EUR-Lex on 30 Sep 2026 ·* [*Official source*](https://eur-lex.europa.eu/legal-content/EN/TXT/?uri=CELEX:02014R0600-20251123)

1. A CTP shall, every year, publish on its website performance statistics and incident reports relating to data quality and data systems. Those performance statistics and incident reports shall be publicly accessible free of charge.
2. ESMA shall develop draft regulatory technical standards to specify the content, timing, format and terminology of the reporting obligation laid down in paragraph 1.

   ESMA shall submit those draft regulatory technical standards to the Commission by 29 September 2025.

   Power is delegated to the Commission to supplement this Regulation by adopting the regulatory technical standards referred to in the first subparagraph in accordance with Articles 10 to 14 of Regulation (EU) No 1095/2010.
3. A CTP shall keep records relating to its business at the disposal of the relevant competent authority or ESMA for at least five years.

***

[Title IVa — Data reporting services](/mifir/titles/iva.md) · [← Article 27h](/mifir/articles/27h.md) · [Article 27i →](/mifir/articles/27i.md)


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://www.headlesslaw.com/mifir/articles/27ha.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.