> 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/eu-level/q-and-a/eba-qa-2024-7277-template-specific-instructions-field-b-01-02-0050-hierarchy.md). # Template specific instructions – field B\_01.02.0050 (Hier... | | | | --------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------- | | **Authority** | EBA | | **Q\&A ID** | EBA\_QA\_2024\_7277 | | **Topic** | Register of information (DORA) | | **Legal basis** | [Article 28(9)](https://www.mica.wtf/dora/digital-operational-resilience-act/chapter-v-managing-ict-third-party-risk/article-28-general-principles) DORA | | **Status** | Final Q\&A | | **Published** | 28/03/2025 | | **Submitted** | 13/12/2024 | | **Source** | [EBA Q\&A](https://www.eba.europa.eu/single-rule-book-qa/qna/view/publicId/2024_7277) | ## Question What does ‘where applicable’ mean in the title of data field B\_02.01.0050? What should be reported in this field in case the entity that is being reported in this template is not a financial entity (i.e., option 22, 23, or 24 was selected in field B\_01.02.0040 for the entity type)? ## Background Field B\_01.02.0050 is described as mandatory with no conditionality with the fill-in option provided in the ITS referring only to ‘financial entities’, but the name of the data field is “Hierarchy of the financial entity within the group (where applicable)”, which suggests optionality. The closed set of options refers only to financial entities, but there may be other entities reported in this template. However, since the field name includes “where applicable” it is unclear how non-financial entities should fill it in. ## Final answer Field B\_01.02.0050 is mandatory and should be filled in also when the entity being reported in this template is not a financial entity, following the fill in instructions and choosing one options from the drop-down menu. Therefore, the reference to ‘where applicable’ in the name of the data field should be disregarded, and the drop-down values provided should be applied to all types of entities. Where an entity fulfils more than one options from the closed list, the higher- level option applicable to the entity should be selected. --- # 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/eu-level/q-and-a/eba-qa-2024-7277-template-specific-instructions-field-b-01-02-0050-hierarchy.md?ask=&goal= ``` `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.