v8881_m - Recovery time objective (RTO) required when the row contains any other data (B_06.01)

Official expression (EBA, verbatim)

with {tB_06.01, default: null, interval: false}: if ( not ( isnull ({c0030}) ) ) or not (( isnull ({c0050}) )) or not (( isnull ({c0060}) )) or not (( isnull ({c0070}) )) or not (( isnull ({c0020}) )) or not (( isnull ({c0090}) )) or not (( isnull ({c0100}) )) then ( ( not ( isnull ({c0080}) ) )) 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), Function name (c0030), Criticality or importance assessment (c0050), Reasons for criticality or importance (c0060), Date of the last assessment (c0070), Recovery point objective (c0090), Impact of discontinuing the function (c0100) - then c0080 (Recovery time objective of the function) must be filled as well. A row that contains only the key columns does not trigger the rule.

c0080 is a numeric column (the recovery time objective of the function); this rule checks only that it is filled, not the numeric type. c0090 (Recovery point objective of the function) is part of this rule's antecedent: a row with only the key and c0090 filled does require c0080.

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 recovery point objective (c0090) was entered but the recovery time objective (c0080) was not.
• The RTO value was left to be confirmed later and the cell stayed empty.
• A column shift in a CSV or Excel export left c0080 empty and moved values into neighbouring columns.

How to fix it, step by step

1. 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).
2. Enter the function's recovery time objective as a number in column c0080 (for example 845).
3. 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.
4. Run the validation again and confirm the v8881_m warning for that row is gone.

Example: fails vs passes

Fails - the recovery point objective is filled, the recovery time objective is empty; the finding points at column c0080 of this row:

c0010 (Function Identifier)	c0040 (LEI of the financial entity)	c0090 (Recovery point objective of the function)	c0080 (Recovery time objective of the function)
F-001	549300Q5EH2NP82EPE32	806	(empty)

Passes - the RTO is filled:

c0010 (Function Identifier)	c0040 (LEI of the financial entity)	c0090 (Recovery point objective of the function)	c0080 (Recovery time objective of the function)
F-001	549300Q5EH2NP82EPE32	806	845

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

• v8877_m to v8880_m and v8882_m - the same row-completeness family on B_06.01: each rule requires a different column of the same row.
• v8883_m - the sister rule guarding c0100: its published antecedent omits c0090 (Recovery point objective of the function), while v8881_m does include c0090 - a row with only the key and c0090 filled triggers v8881_m but not v8883_m.
• e23682_e - existence rule on B_06.01 (inactive on the current EBA list).