Dora Operational Ict Compliance
DORA Article 28 & ITS (EU) 2024/2956: 15-Template xBRL-CSV Register of Information Guide
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.

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, EBA, France AMF, Netherlands AFM, and Estonia/Lithuania NCAs under EU DORA Regulation 2022/2554 and 2026 DORA Benchmark Controls—including EU entities of Coinbase, Anycoin Direct, CMC Markets, and Viverno Markets—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 inside the DORA operational compliance hub.
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! |
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:
- CheckRankChain(c,s) = prod(r = 2 .. MaxRank(c,s)) I( ExistsParentRowIn_B0502(c, s, Rank == r - 1) == 1 )
- CheckCIFRisk(c) = I( SupportsCIFInB0601(c) == 0 OR (HasB0701ExitPlan(c) == 1 AND LastAuditDatePopulated(c) == 1) )
- RoIPackageValid = ( prodp CheckVendorID(p) ) * ( prod(c,s) CheckRankChain(c,s) ) * ( prodc CheckCIF_Risk(c) )
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, RTS (EU) 2025/532 nth-party subcontracting controls, and Joint ESA Critical ICT Third-Party Provider (`CTPP`) designations.
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!
Publication record
- Published
- 13 November 2026
- Updated
- 14 November 2026
- Author
- Victoria Ashworth, LL.M, CAMS
- Review
- Review not recorded
- Automated fact check
- Passed in the stored pipeline record
- Source URLs
- 3 recorded
AI assistance recorded: anthropic/claude-opus-4.6. This field does not establish human review or source verification.
Academic & Institutional Attribution
Cite This Research & Embed Live Data Card
Standard academic & institutional research paper citation format.
Victoria Ashworth, LL.M, CAMS. (2026, November 14). 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-templatesRelated Dora Operational Ict Compliance & Institutional Briefings
Explore Dora Operational Ict Compliance Hub (20) →Dora Operational Ict Compliance
EU DORA Regulation (EU) 2022/2554 Master Guide: ICT Risk, 4h/72h Reporting, RoI & TLPT (2026)Dora Operational Ict Compliance
DORA Article 19 Major ICT Incident Reporting: RTS 2024/1772 Thresholds & 4h/72h/1m SLAsDora Operational Ict Compliance
DORA Article 26 Threat-Led Penetration Testing (TLPT): TIBER-EU Live Production & Purple TeamingDora Operational Ict Compliance
DORA Critical ICT Third-Party Providers (CTPPs): Designation Math, Lead Overseers & 1% Daily FinesDora Operational Ict Compliance
DORA Article 30 ICT Contractual Clauses: Two-Tier SaaS Repapering, Audit Rights & Exit PlansDora Operational Ict Compliance
UK Operational Resilience (FCA PS21/3 & PRA SS2/21) vs EU DORA: Cross-Mapping Dual ProgramsDora Operational Ict Compliance
US SEC Regulation S-P Amendments (2024–2026) & Form 8-K Item 1.05: 4-Day & 30-Day Cyber ClocksDora Operational Ict Compliance
DORA vs NIS2 Directive (Article 1(2) Lex Specialis): Dual-Scope Financial Groups & CSIRT SyncRegulatory Compliance
Deutsche Bank Fined €8M by German Regulator Over Postbank Migration - Global Banking & Finance ReviewRegulatory and Market Glossary
India's Financial Crimes Agency Searches CoinDCX, Delta Exchange Over Offshore TradesRegulatory and Market Glossary
Tron and Tether bring in Chainalysis after T3 crime unit foldsRegulatory Compliance
Thailand proposes $148K daily cap on stablecoin deposits and withdrawals
RegTech Codex Data, Benchmarks & Contributor Records
CC BY 4.0 Open Data
Open Institutional Datasets (CSV / JSON) →
Download desk-compiled quantitative series & schemas.
2026 Reference Matrix
2026 Institutional Benchmarks & Thresholds →
Statutory capital, clearing, margin & rate conventions.
Editorial Records
Authors & Review Records →
View named contributors where those records are available.
Complete Index
Master Research & Dossier Archive →
Browse all published briefings by topic pillar & date.
