Skip to content
RegisterBench

v8876_m - Reporting date required when the row contains any other data (B_01.01)

If any other data column in a B_01.01 row is filled, the date of the reporting (c0060) must be filled too.

Layer
W2
Severity
warning
Templates
B_01.01
Columns
c0060
Taxonomy version
eba-4.0-errata5
Status as of
2026-06-23

Last reviewed

Content last changed

Official expression (EBA, verbatim)

with {tB_01.01, default: null, interval: false}: if ( not ( isnull ({c0030}) ) ) or not (( isnull ({c0040}) )) or not (( isnull ({c0050}) )) or not (( isnull ({c0020}) )) then ( ( not ( isnull ({c0060}) ) )) endif

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

Description in the EBA artifact: empty (NULL).

What this rule checks

Template B_01.01 (Entity maintaining the register of information) describes the entity (or entities) maintaining and updating the Register of Information (RoI). The row key is c0010 (LEI of the entity maintaining the register of information).

The rule looks at each row: if at least one of the data columns c0020-c0050 is filled - Name of the entity (c0020), Country of the entity (c0030), Type of entity (c0040), Competent Authority (c0050) - then c0060 (Date of the reporting) must be filled as well. A row that contains only the key c0010 does not trigger the rule.

This rule checks only that the cell is filled. The date format itself (yyyy-mm-dd) is a separate, format-level check, and the rule does not compare the date with anything.

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

  • The row was filled in starting from the name or the authority and the reporting date cell was left empty.
  • A column shift in a CSV or Excel export left c0060 empty and moved values into neighbouring columns.
  • The row was created with the LEI key only, other columns were filled in later and the date was never entered.

How to fix it, step by step

  1. Open template B_01.01 and find the flagged row. The finding gives the row number and the key value: c0010 (LEI of the entity maintaining the register of information).
  2. Enter the reporting date in column c0060 (Date of the reporting) in the yyyy-mm-dd format, for example 2026-12-31.
  3. If the whole row is there by mistake, delete the entire row instead. A row with only the key (c0010) does not trigger this rule.
  4. Run the validation again and confirm the v8876_m warning for that row is gone.

Example: fails vs passes

Fails - the competent authority is filled, the reporting date is empty; the finding points at column c0060 of this row:

c0010 (LEI of the entity maintaining the register of information) c0050 (Competent Authority) c0060 (Date of the reporting)
549300Q5EH2NP82EPE32 Komisja Nadzoru Finansowego (empty)

Passes - the reporting date is filled:

c0010 (LEI of the entity maintaining the register of information) c0050 (Competent Authority) c0060 (Date of the reporting)
549300Q5EH2NP82EPE32 Komisja Nadzoru Finansowego 2026-12-31

Also passes (edge case) - a key-only row: only c0010 is filled, none of c0020-c0050 has a value, so the condition never activates. With several rows, only the incomplete row is flagged - the finding carries its row number and key value.

  • v8872_m, v8873_m, v8874_m, v8875_m - the same row-completeness family on B_01.01: each rule requires a different column of the same row (c0020 Name of the entity, c0030 Country of the entity, c0040 Type of entity, c0050 Competent Authority).
  • v8858_m to v8865_m - the sister row-completeness family on template B_01.02: the same pattern applied to the rows of the entity list.

Fix it in the RoI Builder - it points at the exact row and cell and re-checks as you type.

This page describes what the software does. It is neither legal advice nor an interpretation of any regulation, and using the product does not by itself make any submission complete, correct or acceptable to any authority. The responsibility for what is filed stays with the entity that files it.