Ariadnah
Platform
DORA Understand the responsibilities, common operating gaps, and the path from shared knowledge to evidence. AML & KYC Customer due diligence with the ownership look-through resolved as data. Risk & Control One control catalogue, read through every framework it answers to. Governance & Policies Policies drafted, mapped to requirements clause by clause, and approved in the platform.

Platform

  • Platform overview
  • AI assistant
  • Security & trust
  • Impact & access

Domains and services

  • Register of Information
  • Suppliers & Contracts
  • Asset Management
  • Risk & Control
  • AML & KYC
  • AIFMD Reporting
  • Fund Administration
  • Trust & Investor Portal
  • Governance & Policies
  • Incident Management
  • All solutions →

By sector

  • Banking
  • (Re)Insurance
  • Investment Firms
  • Investment Management
  • Payment Institutions
  • Pension Funds
  • Crypto Services
  • All sectors →
About Pricing Insights Resources Contact
Book a Discovery Call
Home About Platform Solutions Sectors Pricing Insights Resources DORA Guide NIS2 Guide Contact
Book a Discovery Call
Insights

LEI requirements in the DORA register of information: what you need to know

Ariadnah Solutions DORA 23 Jul 2025 2 min read

If you're preparing your DORA Register of Information submission, you need to understand the identifier requirements for ICT third-party providers in template B_05.01. The Implementing Technical Standards (ITS) on the DORA register of information requires valid identifiers for all ICT providers you report, including both direct providers and indirect suppliers in the service chain.

01

Which identifier should you use?

You can use different types of identifiers depending on your provider's location and legal status.

The Legal Entity Identifier (LEI) works for any provider worldwide – it's the universal option that works in every scenario. The European Unique Identifier (EUID) works only for companies registered in EU member state business registers. If you're reporting a natural person acting in business capacity, you can use alternative codes like Corporate Registration Numbers or VAT numbers.

Location determines your choice

EU-based companies: You can use either LEI or EUID Non-EU companies: You must use LEI Natural persons: You can use alternative codes regardless of location

When you fill in template B_05.01, field B_05.01.0010 captures the identifier itself, while field B_05.01.0020 captures which type of identifier you're using.

02

Where to find identifiers

LEI lookup

You can look up LEI codes on the Global Legal Entity Identifier Foundation website:

GLEIF LEI Search

The GLEIF database shows you whether each LEI is currently active and provides full entity details.

EUID lookup

For EUID codes, use the European Commission's business register search:

Business Register Interconnection System (BRIS)

Note that BRIS requires manual searches – there's no API available for automated lookups. When you report an EUID, make sure to include the dot separator in the code format (the dot between the country/register code and the company identifier is part of the official code).

03

Where to find detailed guidance

The identifier requirements are specified in Article 3 of the ITS on the DORA register of information.

Register of Information FAQ

For practical questions about identifier selection and formatting, consult the Register of Information FAQ (available on the EBA's DORA preparation page):

EBA DORA Preparations for Reporting

Key FAQ questions to review:

  • FAQ Question 39: Which identifiers can be used for which providers
  • FAQ Question 45: EUID formatting requirements

The template B_05.01 fill-in instructions in the ITS specify exactly what you need to report in each field.


04

Avoid common DORA reporting errors

Identifier requirements for template B_05.01 are just one of many pitfalls in DORA Register of Information reporting. Our comprehensive DORA compliance checklist helps you identify and prevent common errors before they impact your reporting.

Request your free DORA compliance checklist →

Originally published on DORA Solutions Insights.

Continue with DORA

Put this question in context.

The DORA guide connects this issue to governance, ICT risk, incidents, resilience testing, third-party risk and the Register of Information.

Recommended next Read the DORA compliance guide →
Explore the operating approach See the regulatory reporting approach Related analysis One Contract, How Many Countries? Related analysis How to report intra-group ICT service providers in your register of information
Manage Consent
We use cookies to keep this site reliable and to understand how it is used. You can accept, deny, or adjust your preferences at any time.
Functional Always active
The technical storage or access is strictly necessary for the legitimate purpose of enabling the use of a specific service explicitly requested by the subscriber or user, or for the sole purpose of carrying out the transmission of a communication over an electronic communications network.
Preferences
The technical storage or access is necessary for the legitimate purpose of storing preferences that are not requested by the subscriber or user.
Statistics
The technical storage or access that is used exclusively for statistical purposes. The technical storage or access that is used exclusively for anonymous statistical purposes. Without a subpoena, voluntary compliance on the part of your Internet Service Provider, or additional records from a third party, information stored or retrieved for this purpose alone cannot usually be used to identify you.
Marketing
The technical storage or access is required to create user profiles to send advertising, or to track the user on a website or across several websites for similar marketing purposes.
  • Manage options
  • Manage services
  • Manage {vendor_count} vendors
  • Read more about these purposes
View preferences
  • {title}
  • {title}
  • {title}
Ariadnah

Compliance advisory & technology

Regulatory specialists and technology that help organisations simplify compliance, strengthen operational resilience, and build lasting trust.

ISO/IEC 27001 certified (DNV)

Platform

  • Platform Overview
  • DORA Guide
  • NIS2 Guide
  • Regulatory Library
  • Register of Information
  • Risk & Control
  • Governance & Policies
  • Incident Management
  • Asset Management
  • Suppliers & Contracts
  • AML & KYC
  • AIFMD Reporting
  • Fund Administration
  • Trust & Investor Portal
  • AI
  • Security

Sectors

  • Banking
  • (Re)Insurance
  • Investment Firms
  • Investment Management
  • Payment Institutions
  • Pension Funds
  • Crypto Services

Company

  • About Ariadnah
  • Pricing
  • Our Experts
  • Impact
  • FAQ
  • Insights
  • Contact

Legal

  • General Terms
  • Data & Privacy
  • Cookie Policy
  • Accessibility

© 2026 Ariadnah Solutions B.V.