> For the complete documentation index, see [llms.txt](https://www.mica.wtf/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://www.mica.wtf/mica.wtf/mifid-ii/title-v-data-reporting-services-art.-59-66/66.md).

# Art. 66 — Organisational requirements

1. The home Member State shall require an ARM to have adequate policies and arrangements in place to report the information required under Article 26 of Regulation (EU) No 600/2014 as quickly as possible, and no later than the close of the working day following the day upon which the transaction took place. Such information shall be reported in accordance with the requirements laid down in Article 26 of Regulation (EU) No 600/2014.
2. The home Member State shall require the ARM to operate and maintain effective administrative arrangements designed to prevent conflicts of interest with its clients. In particular, an ARM that is also a market operator or [investment firm](https://headlesslaw.com/definitions/mifid-ii/investment-firm/) shall treat all information collected in a non-discriminatory fashion and shall operate and maintain appropriate arrangements to separate different business functions.
3. The home Member State shall require the ARM to have sound security mechanisms in place designed to guarantee the security and authentication of the means of transfer of information, minimise the risk of data corruption and unauthorised access and to prevent information leakage, maintaining the confidentiality of the data at all times. The home Member State shall require the ARM to maintain adequate resources and have back-up facilities in place in order to offer and maintain its services at all times.
4. The home Member State shall require the ARM to have systems in place that can effectively check transaction reports for completeness, identify omissions and obvious errors caused by the investment firm and where such error or omission occurs, to communicate details of the error or omission to the investment firm and request re-transmission of any such erroneous reports.

   The home Member State shall also require the ARM to have systems in place to enable the ARM to detect errors or omissions caused by the ARM itself and to enable the ARM to correct and transmit, or re-transmit as the case may be, correct and complete transaction reports to the competent authority.
5. ESMA shall develop draft regulatory technical standards specifying:

   1. the means by which the ARM may comply with the information obligation referred to in paragraph 1; and
   2. the concrete organisational requirements laid down in paragraphs 2, 3 and 4.

   ESMA shall submit those draft regulatory technical standards to the Commission by 3 July 2015.

   Power is delegated to the Commission to adopt the regulatory technical standards referred to in the first subparagraph in accordance with Articles 10 to 14 of Regulation (EU) No 1095/2010.


---

# 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.mica.wtf/mica.wtf/mifid-ii/title-v-data-reporting-services-art.-59-66/66.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.