v8826_m - LEI format of the direct parent LEI (B_01.02)

Official expression (EBA, verbatim)

match({tB_01.02, c0060}, "^[A-Z0-9]{18}[0-9]{2}$")

Precondition (verbatim): {v_B_01.02} - the rule is evaluated only when template B_01.02 is part of the filing (its filing indicator is true).

Description in the EBA artifact (verbatim): "Checks LEI format"

What this rule checks

Template B_01.02 (List of entities within the scope of the register of information) has one row per entity within the scope of the Register of Information (RoI). The row key is c0010 (LEI of the entity).

The rule looks at c0060 (LEI of the direct parent undertaking of the entity): when the cell is filled, its value must match the pattern ^[A-Z0-9]{18}[0-9]{2}$ - exactly 20 characters, the first 18 being uppercase letters A-Z or digits, the last 2 being digits. When c0060 is empty, this rule does not fire; whether c0060 should be filled is guarded separately by v8862_m.

The rule checks only the character pattern. An LEI that matches the pattern but has an incorrect ISO 17442 check-digit sum still passes this rule, and the rule does not check whether the LEI exists in the GLEIF database - that is the separate W3 identifier check VR_23.

This is a warning-level check (layer W2, severity: warning). It does not technically block or reject a filing at the ESAs - a technical rejection can only be caused by the structural file checks (STRUCT layer). A violation shows up as a warning in the validation feedback. The rule is active on the current EBA validation rules list (status as of 2026-06-23).

Most common causes

• An extra character was pasted into c0060 (for example 21 characters instead of 20).
• Lowercase letters in the code - the pattern accepts only uppercase A-Z and digits.
• A space or another separator inside the code, or a truncated code shorter than 20 characters.

How to fix it, step by step

1. Open template B_01.02 and find the flagged row. The finding gives the row number, the key value (c0010) and the offending value from c0060.
2. Re-copy the LEI of the direct parent undertaking into c0060 as exactly 20 characters: 18 uppercase letters or digits, then 2 digits. Remove spaces and fix lowercase letters.
3. If no parent LEI is meant to be reported in this row, clear c0060 - an empty cell does not trigger this rule (v8862_m guards separately whether c0060 is required in a filled row).
4. Run the validation again and confirm the v8826_m warning for that row is gone.

Example: fails vs passes

Fails - 21 characters with a lowercase letter at the end (a value measured in the ESAs feedback sample); the finding points at column c0060 and carries the offending value:

c0010 (LEI of the entity)	c0020 (Name of the entity)	c0060 (LEI of the direct parent undertaking of the entity)
549300Q5EH2NP82EPE32	Bank Testowy A	549300Q5EH2NP82EPE34a

Passes - a 20-character code in the valid format:

c0010 (LEI of the entity)	c0020 (Name of the entity)	c0060 (LEI of the direct parent undertaking of the entity)
549300Q5EH2NP82EPE32	Bank Testowy A	DUMMYLEI123456789012

Also passes (edge case) - c0060 empty: the pattern is not evaluated on an empty cell.

Related rules

• v8862_m - row-completeness guard of the same column: c0060 is required when the B_01.02 row contains any other data.
• v8891_m - the LEI format of the B_01.02 row key itself (c0010).
• VR_23 - W3 identifier check on B_01.02: whether the LEI exists in the GLEIF database.