v8871_m - End date required when the row contains any other data (B_02.02)

Official expression (EBA, verbatim)

with {tB_02.02, default: null, interval: false}: if ( not ( isnull ({c0070}) ) ) or not (( isnull ({c0040}) )) or not (( isnull ({c0090}) )) or not (( isnull ({c0100}) )) or not (( isnull ({c0110}) )) or not (( isnull ({c0120}) )) or not (( isnull ({c0140}) )) or not (( isnull ({c0170}) )) or not (( isnull ({c0180}) )) then ( ( not ( isnull ({c0080}) ) )) endif

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

Description in the EBA artifact: empty (NULL).

What this rule checks

Template B_02.02 (Contractual arrangements - Specific information) details each contractual arrangement per entity, provider and ICT service. The row key is composite - eight columns: c0010 (Contractual arrangement reference number), c0020 (LEI of the entity making use of the ICT service(s)), c0030 (Identification code of the ICT third-party service provider), c0050 (Function identifier), c0060 (Type of ICT services), c0130 (Country of provision of the ICT services), c0150 (Location of the data at rest (storage)), c0160 (Location of management of the data (processing)). A finding on this template carries all eight key values.

The rule looks at each row: if at least one of the data columns is filled - Start date of the contractual arrangement (c0070), Type of code to identify the provider (c0040), Reason of the termination or ending (c0090), Notice period for the financial entity (c0100), Notice period for the ICT third-party service provider (c0110), Country of the governing law (c0120), Storage of data (c0140), Sensitiveness of the data stored (c0170), Level of reliance on the ICT service (c0180) - then c0080 (End date of the contractual arrangement) must be filled as well. A row that carries only the eight key columns does not trigger the rule.

The requirement can be surprising: the published expression requires c0080 in every row that contains any other data - also for open-ended arrangements with no agreed end date; the check runs exactly as published. With c0080 empty, the warning simply remains in the validation feedback. This rule checks only that the cell is filled; the date format itself (yyyy-mm-dd) is a separate, format-level check, and no active W2 rule compares c0080 with c0070 (that relation was guarded by v8816_m, inactive on the current EBA list).

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 arrangement is open-ended, so there is no end date to enter - the published expression still requires a value in every otherwise-filled row.
• The row was filled in starting from other columns (for example the storage-of-data flag) and the end-date cell was left 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_02.02 and find the flagged row. The finding gives the row number and all eight key values (c0010, c0020, c0030, c0050, c0060, c0130, c0150, c0160).
2. Enter the end date of the contractual arrangement in column c0080 in the yyyy-mm-dd format, for example 2023-03-26.
3. If the arrangement has no agreed end date, note that the published expression requires a value in c0080 anyway - with the cell empty, this warning remains in the validation feedback.
4. If the whole row is there by mistake, delete the entire row instead. A row that carries only the eight key columns does not trigger this rule.
5. Run the validation again and confirm the v8871_m warning for that row is gone.

Example: fails vs passes

Key of the row in both tables (all eight key columns filled): c0010 CTR-0001, c0020 549300Q5EH2NP82EPE32, c0030 DUMMYLEI123456789012, c0050 F-001, c0060 eba_TA:S19, c0130 eba_GA:PL, c0150 eba_GA:PL, c0160 eba_GA:IE.

Fails - the storage-of-data flag is filled, the end date is empty; the finding points at column c0080 of this row:

c0080 (End date of the contractual arrangement)	c0140 (Storage of data)
(empty)	eba_BT:x28

Passes - both dates are filled (the end date after the start date):

c0070 (Start date of the contractual arrangement)	c0080 (End date of the contractual arrangement)
2023-02-13	2023-03-26

Also passes (edge case) - a key-only row: all eight key columns are filled and none of the data columns has a value, so the condition never activates. With several rows, only the incomplete row is flagged - the finding carries its row number and all eight key values.

Related rules

• v8870_m - the twin date rule on B_02.02: it requires c0070 (Start date of the contractual arrangement) under the same trigger.
• v8869_m - the same row-completeness family on B_02.02: it requires c0040 (Type of code to identify the ICT third-party service provider).
• v8816_m - date relation on the same pair: c0080 must be later than c0070 (inactive on the current EBA list).
• e23680_e - existence rule on the columns c0040-c0080 of B_02.02, including c0080 (inactive on the current EBA list).