# DORA ITS 2024/2956 Register of Information 15 Templates

> Build a validation-clean EU DORA Article 28(3) Register of Information across all 15 ITS (EU) 2024/2956 xBRL-CSV tables, LEI/EUID rules, and rank chains.

Canonical: https://regtechcodex.org/briefings/dora-article-28-its-2024-2956-register-of-information-templates
Last updated: 2026-11-14T19:38:19.604Z

**Publication:** RegTech Codex
**Category:** Dora Operational Ict Compliance
**Published:** 2026-11-13T09:25:25.915Z
**Author:** Victoria Ashworth, LL.M, CAMS (LL.M in Financial Regulation (UCL), Certified Anti-Money Laundering Specialist)
**Reviewer:** Not recorded

## Answer-first summary

Under DORA Article 28(3) and Commission Implementing Regulation (EU) 2024/2956, financial entities must submit a relational 15-table Register of Information in xBRL-CSV format—feeding the Joint ESAs’ quantitative engine that designates Critical ICT Third-Party Providers.

## Key takeaways

- Implementing Regulation (EU) 2024/2956 standardizes the DORA Article 28(3) Register of Information (RoI) into 15 relational tables (B_01.01 through B_99.01) submitted in EBA Data Point Model xBRL-CSV format!
- Every non-EU ICT third-party service provider (and critical nth-party subcontractor) MUST be identified by an active 20-character GLEIF LEI, while EU-domiciled providers may use either an LEI or official EUID!
- Table B_05.02 (ICT service supply chain) requires explicitly numbering Rank 1 (direct ICT vendor), Rank 2 (subcontractor), through Rank N for every ICT service supporting a Critical or Important Function (CIF)!
- National Competent Authorities validate uploaded RoI .zip packages against 120+ EBA syntax and cross-table referential-integrity assertions before forwarding clean datasets to EBA, ESMA, and EIOPA!

## Related financial entities

- **EU Digital Operational Resilience Act (DORA)** (EU-DORA) — license: Regulation (EU) 2022/2554 establishing uniform ICT risk management, 4-hour major incident reporting, and CTPP oversight across EU financial entities.
- **EU Digital Operational Resilience Act (DORA) ICT Risk & 4-Hour Incident SLA — 2026 Standard** (EU-DORA-2022-2554-STD) — license: EU-DORA-2022-2554 2026 Institutional Benchmark Framework is defined as the standardized quantitative and compliance methodology published by ESMA / EBA / EIOPA Joint RTS governing EU Digital Operational Resilience Act (DORA) ICT Risk & 4-Hour Incident SLA across EU capital markets (4 Hours Major ICT Incident Alert, October 2026).

## Analysis

Procurement spreadsheets built in Microsoft Excel cannot survive the EBA Data Point Model (`DPM`) validation gateway! Under **DORA Article 28(3)** and **Commission Implementing Regulation (EU) 2024/2956**, financial entities supervised by [ECB Banking Supervision](/regulators/european-central-bank-160), [EBA](/regulators/eba-65), [France AMF](/regulators/amf), [Netherlands AFM](/regulators/afm), and [Estonia/Lithuania NCAs](/regulators/financial-crime-investigation-service-of-lithuania-138) under [EU DORA Regulation 2022/2554](/definitions/eu-dora-regulation-2022-2554) and [2026 DORA Benchmark Controls](/definitions/eu-dora-2022-2554-2026-benchmark-standard)—including EU entities of [Coinbase](/licence-holders/coinbase), [Anycoin Direct](/licence-holders/anycoin-direct), [CMC Markets](/licence-holders/cmcmarkets), and [Viverno Markets](/licence-holders/viverno-markets-ltd-2714)—must maintain a normalized relational database capable of exporting **15 linked `xBRL-CSV` tables** at both individual-entity and EU-consolidated levels. Review our [EU DORA Compliance Master Guide 2026](/briefings/eu-dora-regulation-2022-2554-ict-risk-tlpt-compliance-hub-2026) inside the [DORA operational compliance hub](/topics/dora-operational-ict-compliance).

## Relational Architecture of the 15 `ITS (EU) 2024/2956` RoI Tables (`B_01` – `B_99`)

Think of the DORA Register of Information as a strictly typed SQL join graph linking **Regulated Entities -> Critical Functions -> Master/Sub Contracts -> Vendors -> Subcontractor Ranks -> Risk Assessments**:

| Template Group | Table Codes | Primary Key (`PK`) & Foreign Keys (`FK`) | Mandatory Granular Fields | #1 EBA xBRL-CSV Rejection Error |
| :--- | :--- | :--- | :--- | :--- |
| **1. Entity & Group Scope** | `B_01.01`, `B_01.02`, `B_01.03` | `Entity_LEI` + `Branch_Code` | Regulated license type (`eba_BT`), country, total assets/annual ICT spend (`EUR`) | Reporting parent non-EU holding LEI instead of EU licensed entity |
| **2. Contractual Arrangements** | `B_02.01`, `B_02.02`, `B_02.03` | `Contract_Ref_No` -> Overarching vs Specific (`B_02.03`) | Governing law, notice periods, annual cost, data storage & processing `ISO 3166` countries! | Orphan child schedules (`B_02.02`) missing overarching MSA link |
| **3. Signatories & Intra-Group** | `B_03.01`, `B_03.02`, `B_03.03`, `B_04.01` | `Contract_Ref_No` x `Entity_LEI` x `Provider_ID` | Links which group entity signed vs which regulated branches/entities consume the service | Same entity listed simultaneously as customer & external provider |
| **4. Vendors, Chains & CIFs** | `B_05.01`, `B_05.02`, `B_06.01` | `Provider_ID (LEI/EUID)`, `Function_ID`, `Rank (1..N)` | `ICT Service Type (S01..S19)`, **Supply Chain Rank `1, 2, 3..`**, Function `RTO`/`RPO` & criticality! | Gap in `Rank` sequence (`Rank 1 -> Rank 3` missing `Rank 2`!) |
| **5. Substitutability & Risk** | `B_07.01` + `B_99.01` (Enum defs) | `Contract_Ref_No` x `Provider_ID` x `ICT_Service` | **Substitutability (`Easy/Difficult/Impossible`)**, reintegration feasibility, **Last Audit & Exit Plan flags**! | Claiming `CIF = True` in `B_06.01` while leaving `B_07.01` blank! |

![Automated SQL-to-xBRL-CSV pipeline generating, validating, and packaging the 15 EU DORA ITS 2024/2956 Register of Information tables](/api/figure?type=flow&title=Automated%20PostgreSQL-to-xBRL-CSV%20DORA%20RoI%20Build%20Pipeline&subtitle=Joining%20Procurement%20ERP%2C%20CMDB%20Critical%20Functions%2C%20and%20GLEIF%2FBRIS%20APIs%20to%20pass%20100%25%20of%20EBA%20DPM%20v3.5%2B%20checks&steps=1.%20Vendor%20ID%20Enricher%3A%3AValidate%20non-EU%20vendor%2020-char%20LEIs%20via%20GLEIF%20API%20%26%20EU%20vendor%20EUIDs%20via%20BRIS%20registry%7C2.%20CIF%20Rank-N%20Builder%3A%3ATraverse%20cloud%2FSaaS%20dependency%20graph%20%28SaaS%20-%3E%20AWS%20Frankfurt%20-%3E%20Equinix%29%20into%20B_05.02%20Ranks%201..N%7C3.%20Referential%20SQL%20Check%3A%3ARun%20125%20EBA%20DPM%20foreign-key%2C%20closed-list%20enum%20%28eba_ZZ%29%2C%20and%20date%2Fcurrency%20assertions%7C4.%20xBRL-CSV%20Zip%20Export%3A%3AEmit%20META-INF%2FreportPackage.json%20%2B%20FilingIndicators.csv%20%2B%20b_01..b_99%20UTF-8%20CSVs%20via%20Arelle&metrics=EBA%20DPM%20TAXONOMY%3A%3ADPM%203.5%20%2F%204.0%3A%3AStrict%20Closed-List%20URI%20Enumerations%7CCURRENCY%20NORMALIZATION%3A%3ASingle%20Ccy%3A%3AConvert%20USD%2FGBP%20SaaS%20Spend%20at%20ECB%20Ref%20Rate%7CRANK%20CONTIGUITY%3A%3A1%20-%3E%202%20-%3E%203%3A%3AZero%20Skipped%20Tiers%20in%20B_05.02%20Supply%20Chain!%7CADHOC%20NCA%20PULL%20SLA%3A%3AOn-Demand%3A%3AKeep%20RoI%20Live%20Year-Round%E2%80%94Not%20Annual%20Scramble!)

## Mastering `B_05.02` ICT Supply-Chain Ranking (`Rank 1` -> `Rank 2` -> `Rank 3`)

Suppose your EU brokerage licenses a cloud-hosted **Trade Surveillance SaaS (`Vendor Alpha`, US Corp)** (`Rank 1`), which hosts its multi-tenant Kubernetes cluster on **Amazon Web Services EMEA SARL (`AWS`, Luxembourg)** (`Rank 2`), which relies on a specialized **Managed HSM Security Sub-Processor (`Vendor Gamma`)** (`Rank 3`)—and Trade Surveillance supports a **Critical or Important Function (`CIF`: `MAR Art. 16 Market Abuse Surveillance`)**! Inside table **`B_05.02`**, you must log **all three contiguous links** (`Rank 1 = Alpha`, `Rank 2 = AWS linked to Alpha`, `Rank 3 = Gamma linked to AWS`), including exact **Country of Data at Rest** and **Country of Data Processing (`ISO 3166-1 alpha-2`)** for every tier!

## Relational Integrity & `xBRL-CSV` Pre-Submission Gate Equations

Compliance engineering pipelines run deterministic SQL constraints across the 15 `B_*` staging tables so `Arelle` / NCA portal validation passes with zero errors:

```formula
Check_Vendor_ID(p) = I( (Country(p) in EU_EEA AND (Valid_GLEIF_LEI(p) OR Valid_BRIS_EUID(p))) OR (Country(p) not in EU_EEA AND Valid_GLEIF_LEI(p)) )
Check_Rank_Chain(c,s) = prod_(r = 2 .. MaxRank(c,s)) I( Exists_Parent_Row_In_B0502(c, s, Rank == r - 1) == 1 )
Check_CIF_Risk(c) = I( Supports_CIF_In_B0601(c) == 0 OR (Has_B0701_ExitPlan(c) == 1 AND Last_Audit_Date_Populated(c) == 1) )

RoI_Package_Valid = ( prod_p Check_Vendor_ID(p) ) * ( prod_(c,s) Check_Rank_Chain(c,s) ) * ( prod_c Check_CIF_Risk(c) )
```

![Distribution of EBA xBRL-CSV technical validation errors encountered by financial entities during DORA RoI submissions](/api/figure?type=bars&title=Most%20Frequent%20EBA%20xBRL-CSV%20Validation%20Errors%20in%20DORA%20RoI&subtitle=Breakdown%20of%20blocking%20syntax%20and%20business-rule%20failures%20across%20tables%20B_01%20through%20B_07&steps=Foreign-Key%20Orphan%20Rows%3A%3A34.8%25%20referenced%20Contract_Ref%20or%20Function_IDs%20missing%20in%20parent%20tables%7CInvalid%20Closed-List%20Enums%3A%3A26.5%25%20wrote%20free-text%20%22Cloud%22%20instead%20of%20exact%20eba_TA%3AS06%20taxonomy%20code%7CNon-EU%20Missing%20GLEIF%20LEI%3A%3A22.4%25%20submitted%20US%2FUK%2FSG%20vendor%20tax%20IDs%20where%20only%2020-char%20LEI%20is%20legal%7CBroken%20B_05.02%20Rank%20Graph%3A%3A16.3%25%20omitted%20intermediate%20Rank%202%20cloud%20IaaS%20parent%20behind%20SaaS%20tools&metrics=ICT%20SERVICE%20CODES%3A%3AS01%20to%20S19%3A%3AMandatory%20Annex%20III%20ICT%20Service%20Taxonomy%7CFUNCTION%20TAXONOMY%3A%3ALicensed%20Map%3A%3AMap%20CIFs%20to%20Annex%20II%20Regulated%20Activities%7COPEN-SOURCE%20EXCLUSION%3A%3ANo%20Contract%3DOut%3A%3APure%20Uncontracted%20OSS%20Excluded%20From%20RoI%3B%20Paid%20Support%3DIn!%7CCTPP%20FEED%3A%3ADirect%20Input%3A%3AESAs%20Aggregate%20All%20EU%20RoIs%20to%20Name%20CTPPs!)

## How to Handle Refusing US/APAC Vendors Who Lack a `GLEIF LEI`

What happens when a boutique Delaware or Singapore SaaS vendor refuses to spend `$65` registering a `GLEIF LEI`? **Add a mandatory `LEI Registration & Renewal Covenant` into your standard procurement onboarding gate**—or utilize GLEIF's **Registration Agent / Assisted Registration** workflow during contract signature! Remember: for any non-EU ICT vendor, leaving the `LEI` column blank or typing a `DUNS`/`EIN` number triggers a **hard blocking error (`v-rule failure`)** at your NCA's `xBRL-CSV` gateway!

## Connecting DORA RoI Templates to Art. 30 Contracts, Nth-Party RTS & CTPPs

Link your live `ITS 2024/2956` database directly to [DORA Article 30 contractual audit & exit clauses](/briefings/dora-article-30-ict-contractual-clauses-audit-exit-strategies), [RTS (EU) 2025/532 nth-party subcontracting controls](/briefings/nth-party-ict-subcontracting-rts-critical-function-chain-risk), and [Joint ESA Critical ICT Third-Party Provider (`CTPP`) designations](/briefings/critical-ict-third-party-providers-ctpp-lead-overseer-powers).

## Frequently asked questions

### Why did the European Commission reject draft RoI rules in late 2024 before adopting ITS (EU) 2024/2956?

The original Joint ESA draft mandated EXCLUSIVELY GLEIF LEIs for every ICT supplier worldwide, sparking pushback that small EU software vendors lacked LEIs; final ITS (EU) 2024/2956 allows EU-established ICT legal entities to use either an LEI or their free national business-registry European Unique Identifier (EUID), while keeping LEIs mandatory for third-country (non-EU) vendors!

### Must intra-group IT shared-service subsidiaries be recorded inside the DORA Register of Information?

Yes! DORA Article 2(21) and Article 28 define "ICT third-party service provider" to INCLUDE intra-group ICT service entities (such as a UK, US, or Polish group technology hub providing trading, cloud, or SOC services to an EU regulated subsidiary)—explicitly differentiated via intra-group flags in B_02.02!

### Do we have to map Rank 2, Rank 3, and Rank 4 subcontractors for non-critical office software?

No! Under ITS (EU) 2024/2956 Annex I–III instructions, while ALL direct (Rank 1) ICT service contracts must appear in the Register (B_02.01/B_05.01), deep multi-tier supply-chain mapping (Rank >= 2 in B_05.02) is strictly required ONLY for ICT services supporting Critical or Important Functions (CIFs) or material parts thereof!

### What exact file packaging format do NCAs require for annual DORA RoI submissions?

Entities must package plain UTF-8 CSV files conforming to the EBA Filing Rules v5.4+ xBRL-CSV specification inside a structured .zip archive (META-INF/reportPackage.json + reports/parameters.csv, FilingIndicators.csv, and b_01.01.csv .. b_07.01.csv), not Excel .xlsx workbooks!


## Source URLs

- https://eur-lex.europa.eu/eli/reg_impl/2024/2956/oj
- https://www.eba.europa.eu/activities/single-rulebook/regulatory-activities/operational-resilience/dora-register-information
- https://www.esma.europa.eu/esmas-activities/digital-finance-and-innovation/digital-operational-resilience-act-dora

## Citation

- APA: Victoria Ashworth, LL.M, CAMS. (2026). DORA Article 28 & ITS (EU) 2024/2956: 15-Template xBRL-CSV Register of Information Guide. RegTech Codex. https://regtechcodex.org/briefings/dora-article-28-its-2024-2956-register-of-information-templates
- Canonical article: [DORA Article 28 & ITS (EU) 2024/2956: 15-Template xBRL-CSV Register of Information Guide](https://regtechcodex.org/briefings/dora-article-28-its-2024-2956-register-of-information-templates)
- Site research index: [RegTech Codex](https://regtechcodex.org/llms-full.txt)
