v8878_m - Function name required when the row contains any other data (B_06.01)
If any other data column in a B_06.01 function row is filled, the function name (c0030) must be filled too.
- Layer
- W2
- Severity
- warning
- Templates
- B_06.01
- Columns
- c0030
- Taxonomy version
- eba-4.0-errata5
- Status as of
- 2026-06-23
Last reviewed
Content last changed
Official expression (EBA, verbatim)
with {tB_06.01, default: null, interval: false}: if ( not ( isnull ({c0020}) ) ) or not (( isnull ({c0050}) )) or not (( isnull ({c0060}) )) or not (( isnull ({c0070}) )) or not (( isnull ({c0080}) )) or not (( isnull ({c0090}) )) or not (( isnull ({c0100}) )) then ( ( not ( isnull ({c0030}) ) )) endif
Precondition (verbatim): {v_B_06.01} - the rule is evaluated only when template B_06.01 is part of the filing (its filing indicator is true).
Description in the EBA artifact: empty (NULL).
What this rule checks
Template B_06.01 (Functions identification) has one row per function of a financial entity. The row key has two parts: c0010 (Function Identifier) and c0040 (LEI of the financial entity).
The rule looks at each row: if at least one of the other data columns is filled - Licenced activity (c0020), Criticality or importance assessment (c0050), Reasons for criticality or importance (c0060), Date of the last assessment (c0070), Recovery time objective (c0080), Recovery point objective (c0090), Impact of discontinuing the function (c0100) - then c0030 (Function name) must be filled as well. A row that contains only the key columns does not trigger the rule.
c0030 is a free-text column (the name of the function); the rule checks only that it is filled.
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 licenced activity or the assessment columns and the name cell (c0030) was left empty.
- The row was created with the key columns only, other columns were filled in later and the name was never added.
- A column shift in a CSV or Excel export left c0030 empty and moved values into neighbouring columns.
How to fix it, step by step
- Open template B_06.01 and find the flagged row. The finding gives the row number and the two-part key: c0010 (Function Identifier) and c0040 (LEI of the financial entity).
- Enter the function's name in column c0030 (Function name).
- If the whole row is there by mistake, delete the entire row instead. A row with only the key columns does not trigger this rule.
- Run the validation again and confirm the v8878_m warning for that row is gone.
Example: fails vs passes
Fails - the licenced activity is filled, the function name is empty; the finding points at column c0030 of this row:
| c0010 (Function Identifier) | c0040 (LEI of the financial entity) | c0020 (Licenced activity) | c0030 (Function name) |
|---|---|---|---|
| F-001 | 549300Q5EH2NP82EPE32 | eba_TA:x162 | (empty) |
Passes - the function name is filled:
| c0010 (Function Identifier) | c0040 (LEI of the financial entity) | c0020 (Licenced activity) | c0030 (Function name) |
|---|---|---|---|
| F-001 | 549300Q5EH2NP82EPE32 | eba_TA:x162 | Przyjmowanie depozytow |
Also passes (edge case) - a key-only row: only c0010 and c0040 are filled, no data column has a value, so the condition never activates.
Related rules
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.