Skip to content
RegisterBench

STRUCT-COUNTRY-VALUE - Country columns take codes from the EBA country lists (B_01.01, B_01.02, B_01.03, B_02.02, B_05.01)

A country cell holds a value outside the column's EBA country list; canonical codes look like eba_GA:PL.

Layer
STRUCT
Severity
blocking
Templates
B_01.01, B_01.02, B_01.03, B_02.02, B_05.01
Columns
c0030, c0040, c0080, c0120, c0130, c0150, c0160
Taxonomy version
eba-4.0-errata5
Status
founder-approved

Reviewed at gate 1 (founder) on

Content last changed

Official control text (EBA, verbatim)

Extensible main property and explicit key dimension must only be reported with one of the restricted value of a hierarchy

Source: EBA technical check 503 (sheet "DPM Technical Checks", category "DPM Technical Checks" in the official overview of the RoI technical checks). The RoI Builder runs it as structural check STRUCT-COUNTRY-VALUE.

What this rule checks

The check covers the country-typed columns. Measured in eba-4.0-errata5, these are 8 columns: c0030 (Country of the entity) in B_01.01 and B_01.02; c0040 (Country of the branch) in B_01.03; c0120 (Country of the governing law of the contractual arrangement), c0130 (Country of provision of the ICT services), c0150 (Location of the data at rest (storage)) and c0160 (Location of management of the data (processing)) in B_02.02; c0080 (Country of the ICT third-party service provider’s headquarters) in B_05.01.

Every non-empty cell must be one of the column's OWN allowed country codes - all codes live in the eba_GA namespace, encoding the ISO 3166 alpha-2 domain (e.g. eba_GA:PL for Poland). Measured: the fact columns use 251-code lists (dictionaries ei1355, ei1555, ei1556), while the three B_02.02 key columns (c0130, c0150, c0160) use 252-code lists that additionally carry eba_GA:qx2007 ("Not applicable") - so qx2007 is valid ONLY in those three key columns.

An empty cell is skipped here; emptiness of the three B_02.02 key columns is STRUCT-MANDATORY. The comparison is exact against the verbatim codes: a plain ISO code (PL) or a country name does not match.

This is a structural check (STRUCT layer, severity: blocking). If it fails, the package is technically rejected on receipt (feedbackMain = REJECTED). The structural layer is the only layer that blocks a filing.

Most common causes

  • A plain ISO code without the prefix: PL instead of eba_GA:PL.
  • A country name typed as text: Poland instead of eba_GA:PL.
  • eba_GA:qx2007 ("Not applicable") used in a fact column (e.g. c0030 of B_01.02), where it is not in the list.

How to fix it, step by step

  1. Open the flagged template and find the row - the finding gives the row number, the key values and the offending value.
  2. Enter the country as the prefixed code from the column's own list, e.g. eba_GA:PL; the finding shows sample allowed codes.
  3. For the three B_02.02 key columns only (c0130, c0150, c0160): if the dimension genuinely does not apply, the list carries eba_GA:qx2007 ("Not applicable").
  4. Run the validation again and confirm the finding is gone.

Example: fails vs passes

Fails - a plain ISO code; the finding points at column c0030 of this B_01.02 row:

c0010 (LEI of the entity) c0030 (Country of the entity)
549300Q5EH2NP82EPE32 PL

Passes - the prefixed EBA code:

c0010 (LEI of the entity) c0030 (Country of the entity)
549300Q5EH2NP82EPE32 eba_GA:PL

Edge case - eba_GA:qx2007 ("Not applicable") passes in the three B_02.02 key columns (c0130, c0150, c0160 - their 252-code lists carry it) and fails in c0030 of B_01.02 (its 251-code list does not).

  • STRUCT-ENUM-VALUE - the same EBA check 503 on the 30 general closed-list columns.
  • STRUCT-CURRENCY-VALUE - the same EBA check 503 on the currency columns.
  • STRUCT-MANDATORY - emptiness of the B_02.02 key columns c0130/c0150/c0160 is reported there.
  • VR_16 - a W3 data-quality check that compares c0030 of B_01.02 against a GLEIF country reference (never blocking).

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.