> 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-7282-template-specific-instructions-field-b-04-01-0040-identifica.md).

# Template specific instructions – field B\_04.01.0040 (Iden...

|                 |                                                                                                                                                          |
| --------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Authority**   | EBA                                                                                                                                                      |
| **Q\&A ID**     | EBA\_QA\_2024\_7282                                                                                                                                      |
| **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_7282)                                                                    |

## Question

How to report data field B\_04.01.0040 if the financial entity is not a branch?

## Background

According to the ITS, the fields B\_04.01.0040 is mandatory only if the financial entity making use of the ICT service(s) is a branch of a financial entity (B\_04.01.0030). According to the data model, however,  this field is marked as a primary key and therefore cannot be missing or reported empty. It is unclear how to fill in the data field without triggering a data quality error when the financial entity reporting is not a branch

## Final answer

According to the data model for the Register of Information , data field B\_04.01.0040 is marked as a primary key value. As result it should not be missing or reported empty. The field should be filled in with ‘Not Applicable’ if the financial entity is not a branch (i.e., option 2 is selected in B\_04.01.0030)


---

# 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-7282-template-specific-instructions-field-b-04-01-0040-identifica.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.