Skip to main content

LEI and EUID checks (VR_)

With the LEI and EUID checks, the EBA confirms that the identification codes in your register really exist. It checks an LEI against the GLEIF database and an EUID against BRIS, the European system that interconnects business registers (EBA (opens in a new tab)). It is the last step of the validation (EBA explainer (opens in a new tab)).

Which fields the EBA checks

Check Field Against
VR_2 B_01.01, field 0010: LEI of the entity maintaining the register GLEIF
VR_12 B_01.02, field 0010: LEI of the entity GLEIF
VR_16 B_01.02, field 0030: country of the entity GLEIF
VR_23 B_01.02, field 0060: LEI of the direct parent undertaking GLEIF
VR_71 and VR_72 B_05.01, field 0010: ICT third-party service provider code, when its type is LEI or EUID GLEIF or BRIS
VR_77 and VR_78 B_05.01, field 0030: additional identification code of the provider, when the type in field 0040 is LEI or EUID GLEIF or BRIS

If the field is empty, the EBA doesn't run the check (EBA (opens in a new tab)).

What a finding means

In the EBA's sample responses, LEI findings arrive as VALIDATION_RESULTS, not as a rejection (EBA (opens in a new tab)). The package has been received; the finding points to a data-quality issue.

  • LEI not found or lapsed: look the LEI up in GLEIF and use the correct one.
  • Provider without an LEI or EUID: enter another available identification number, not a dummy code and not an empty field. The AFM treats that as a data-quality issue but does not reject the register for it (AFM Q&A (opens in a new tab), AFM (opens in a new tab)).

The EBA's sample responses also cite VR_21, VR_85, VR_87 and VR_99. Those are not in the published catalogue, so we can't explain what they check.

Does DORA Convert catch these checks?

For LEIs largely; for EUIDs only the format.

Check What we do
LEI (VR_2, VR_12, VR_23, VR_71, VR_77) We always check the format. With the GLEIF check on, we look every LEI up at GLEIF.
Country (VR_16) With the GLEIF check on, we compare the country with GLEIF.
EUID (VR_72, VR_78) We check the format only. BRIS offers no public lookup service, so we can't confirm beforehand that an EUID exists.

Below is every LEI and EUID check with its official description.

Codes and official descriptions

  • VR_2

    LEI code validity against the GLEIF database.

    Checks: b_01_01.c0010 · Runs when: No prerequisite published.

  • VR_12

    LEI code validity against the GLEIF database.

    Checks: b_01_02.c0010 · Runs when: No prerequisite published.

  • VR_16

    Country-code validity according to the GLEIF database.

    Checks: b_01_02.c0030 · Runs when: No prerequisite published.

  • VR_23

    LEI code validity against the GLEIF database.

    Checks: b_01_02.c0060 · Runs when: No prerequisite published.

  • VR_71

    LEI code validity against the GLEIF database.

    Checks: b_05_01.c0010 · Runs when: Run only if b_05_01_c0020 = 'LEI'.

  • VR_72

    EUID code validity against BRIS.

    Checks: b_05_01.c0010 · Runs when: Run only if b_05_01_c0020 = 'EUID'.

  • VR_77

    LEI code validity against the GLEIF database.

    Checks: b_05_01.c0030 · Runs when: Published prerequisite: b_05_01_c0040 = 'LEI'.

  • VR_78

    EUID code validity against BRIS.

    Checks: b_05_01.c0030 · Runs when: Published prerequisite: b_05_01_c0040 = 'EUID'.

From the EBA's published catalogue, as recorded on 10 March 2026. The official text is in English.

Sources

  1. EBA: Overview of the RoI reporting technical checks and validation rules (28 April 2025) (opens in a new tab)
  2. EBA: RoI validation feedback explanation (10 February 2025, PDF) (opens in a new tab)
  3. EBA: DORA Sample Responses (reference date 2025-03-31) (opens in a new tab)
  4. AFM: Q&A DORA register of information (March 2026, PDF) (opens in a new tab)
  5. AFM: Register of Information (opens in a new tab)