> 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-7283-template-specific-instructions-field-b-05-01-0020-type-of-co.md).

# Template specific instructions – field B\_05.01.0020 (Type...

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

## Question

How to report type of identification code in data field B\_05.01.0020 when using codes other than LEI or EUID?

## Background

The fill-in instructions for field B\_05.01.0020 in the ITS include 'Country Code’+Underscore+Type of Code’ as an option for non-LEI and non EUID code. The instructions for this data filed are not consistent with the instruction for other similar data filed, e.g. B\_05.01.0040).

## Final answer

When reporting data field B\_05.01.0020 financial entities should choose only the values from the closed set of options, without including the country code. One of the following values can be chosen:

* ‘LEI’ for LEI
* ‘EUID’ for EUID
* CRN for Corporate registration number
* VAT for VAT number
* PNR for Passport Number
* NIN for National Identity Number

This is valid for all fields that make reference to B\_05.01.0020.

Only LEI or EUID can be used for legal persons, as identified in B\_05.01.0070, whereas alternative code may be used only for an individual acting in a business capacity. Only LEI can be used for legal persons that are not established in the Union.


---

# 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-7283-template-specific-instructions-field-b-05-01-0020-type-of-co.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.