Venvera DORA Register of Information with xBRL-CSV export
The DORA Register of Information - shown with sample data.

The Register of Information (RoI) is the cornerstone of DORA compliance. This article covers the regulatory background, the Venvera RoI dashboard, and every feature on the landing page - completeness scoring, CSV import, and pre-export validation.

1. Regulatory Context - Why the Register Exists

1.1 DORA Article 28(3) - The Legal Mandate

Article 28(3) of Regulation (EU) 2022/2554 (DORA) requires every in-scope financial entity to maintain and keep up-to-date a register of information on all contractual arrangements for ICT services provided by third-party service providers. This is a binding legal obligation from 17 January 2025. The register must include information at entity level and, where applicable, at sub-consolidated and consolidated levels.

1.2 Implementing Technical Standards - ITS 2024/2956

The European Supervisory Authorities (ESAs) - comprising the EBA, EIOPA, and ESMA - published Commission Implementing Regulation (EU) 2024/2956, which specifies the exact templates, data fields, and taxonomies that financial entities must use when populating and submitting their register. The ITS defines a set of standardised templates labelled B_01.01 through B_07.01, each covering a different aspect of the register. Venvera maps your business-language entries to these templates automatically during export, so you never need to memorise ESA alphanumeric codes.

The ITS defines 15 templates. Venvera generates all of them on export:

  • B_01.01 - Entity maintaining the register (your organisation)
  • B_01.02 - Entities within scope of the register
  • B_01.03 - Branches
  • B_02.01 - Contractual arrangements (general information)
  • B_02.02 - Contractual arrangements (specific ICT service information)
  • B_02.03 - Intra-group contractual arrangements
  • B_03.01 - Entities signing the contractual arrangement (receiver)
  • B_03.02 - ICT third-party service providers signing the arrangement
  • B_03.03 - Entities providing ICT services (intra-group)
  • B_04.01 - Entities making use of the ICT services
  • B_05.01 - ICT third-party service providers
  • B_05.02 - ICT service supply chains (sub-outsourcing)
  • B_06.01 - Functions supported by ICT services
  • B_07.01 - Assessment of ICT services (risk assessments)
  • B_99.01 - Internal reference definitions

1.3 Who Must Submit and to Whom

Every financial entity within the scope of DORA Article 2 must submit its register to its National Competent Authority (NCA). The NCA varies by Member State and by entity type - for example, BaFin in Germany, the Central Bank of Ireland (CBI), or ACPR/AMF in France. The submission is made in xBRL-CSV format, which is the structured data format specified by the ESAs. Venvera generates this export for you automatically.

NCAs may request the register at any time, not only on a fixed schedule. Financial entities should therefore ensure the register is kept continuously up to date, rather than treating it as a periodic reporting exercise.

1.4 Entities in Scope (Article 2)

DORA applies to a wide range of financial entities. Article 2 enumerates the following types:

  • Credit institutions
  • Payment institutions
  • Electronic money institutions
  • Investment firms
  • Insurance and reinsurance undertakings
  • UCITS management companies and alternative investment fund managers (AIFMs)
  • Central counterparties (CCPs) and central securities depositories (CSDs)
  • Trade repositories
  • Crypto-asset service providers (CASPs) and issuers of asset-referenced tokens
  • Institutions for occupational retirement provision (IORPs)
  • Credit rating agencies
  • Crowdfunding service providers
  • Securitisation repositories
  • Administrators of critical benchmarks

If your organisation falls under any of these categories, you are required to maintain a Register of Information.

1.5 Proportionality Principle

DORA includes a proportionality principle. Micro-enterprises and entities with limited ICT risk profiles may apply simplified requirements, but they are not exempt from maintaining the register itself. The depth and granularity of the information may be proportionate to the entity's size, nature, scale, and complexity, but the core obligation to record all ICT third-party arrangements remains in force.

1.6 Deadline Context

DORA became applicable on 17 January 2025. Financial entities were expected to have their registers populated by this date. NCAs have begun requesting registers as part of supervisory reviews. Entities that fail to maintain a complete register face potential enforcement actions, supervisory measures, and reputational risk.

2. RoI Structure - The Four Pillars

Venvera organises the Register of Information around four interconnected pillars. Understanding how these pillars relate to each other is essential for building a complete and accurate register.

2.1 ICT Providers

This pillar captures all ICT third-party service providers your organisation relies upon. Each provider record includes identifying information (name, LEI, country), classification (criticality level, provider type), and corporate structure details. Providers are the foundation of the register - you cannot create contracts or risk assessments without first registering the provider.

2.2 Contractual Arrangements

Contracts link your organisation to its providers. Each contractual arrangement record captures the contract reference, type, dates, cost, service details, data locations, and Article 30 clause compliance. A single provider may have multiple contracts (for example, separate agreements for cloud hosting and professional services).

2.3 Business Functions

Business functions represent the organisational capabilities that depend on ICT services. Each function is linked to one or more contracts, creating the chain that demonstrates which provider supports which business function. Functions carry criticality assessments, RTO (Recovery Time Objective), and RPO (Recovery Point Objective) values that feed into operational resilience planning.

2.4 Risk Assessments

Risk assessments evaluate the risk posed by each ICT provider arrangement. They consider factors such as concentration risk, substitutability, data sensitivity, and geographic location. Assessment records link back to providers and contracts, completing the full picture.

2.5 The Interconnection Chain

The data flows in a clear chain: Entity → Contract → Provider → Function. Your organisation (the entity) enters into contracts with ICT providers. Those contracts support specific business functions. Risk assessments overlay this chain to evaluate the resilience implications. Completeness is calculated based on how well this chain is populated.

3. Completeness Score

At the top of the RoI overview page, you will find the Register Completeness panel. This provides an at-a-glance measure of how ready your register is for NCA submission.

3.1 How Completeness Is Calculated

The overall completeness percentage is a weighted composite of four metrics:

  • Providers (30% of the score) - counts how many provider records have all required fields completed (display name, LEI, country, provider type). Criticality is not counted.
  • Contracts (30%) - counts how many contract records have all required fields completed (provider link, reference, type, start date, service type, annual cost). Article 30 clauses do not affect the score; unchecked clauses appear as a warning in Pre-Export Validation.
  • Functions (20%) - counts how many registered business functions are linked to at least one contract.
  • Assessments (20%) - compares the number of risk assessments with the number of providers, up to a maximum of 100%.

While the register holds no providers, the overall score is 0%.

A record is considered “complete” only when every mandatory field is filled and the record is linked to other relevant records in the chain. For example, a contract without a linked provider is incomplete, and a function without a linked contract is incomplete.

3.2 Progress Bar and Colour Thresholds

The completeness score is displayed as a progress bar beside the percentage value. The colour of both the bar and the percentage text changes based on thresholds:

Score RangeColourMeaning
70% and aboveGreenRegister is in good shape and approaching NCA-readiness. Continue filling remaining gaps.
40% to 69%AmberRegister has significant gaps. Prioritise missing provider details and unlinked contracts.
Below 40%RedRegister is substantially incomplete. Immediate action is required before any NCA request can be fulfilled.

3.3 Four Metric Cards

Below the progress bar, four metric cards display the total count of records in each pillar: ICT Providers, Contractual Arrangements, Business Functions, and Risk Assessments. Each card shows a large numeric count with a label and a coloured accent bar. When no data has been loaded yet, the count displays as a dash (-).

4. Pre-Export Validation

Before you export your register, Venvera runs an automated validation check against the ITS template requirements. The validation panel appears below the completeness score whenever issues are detected.

4.1 Error vs. Warning Severity

Validation issues are classified into two severity levels:

  • Errors (red badge with count) - these will cause your NCA to reject the submission. Errors typically represent missing mandatory fields, invalid identifiers, or broken linkages (e.g., a contract referencing a non-existent provider).
  • Warnings (amber badge with count) - these will not prevent submission but may trigger follow-up questions from your NCA. Warnings typically represent best-practice recommendations such as missing LEI codes or unpopulated optional fields.

4.2 Template Codes

Each validation issue displays a template code in monospace font (e.g., [B_05.01], [B_02.02]). This code tells you exactly which ITS template is affected, making it easy to identify where the problem lies. The validation uses four codes:

  • [B_05.01] - Provider issues (no providers registered, or a provider without an LEI, a country or a provider type)
  • [B_02.02] - Contract issues (no contracts registered, or a contract without a valid provider, a start date, a service type or an annual cost, or with unchecked Article 30(2) clauses)
  • [B_06.01] - Function issues (no functions registered, or a function not linked to any contractual arrangement)
  • [B_07.01] - Risk assessment issues (critical functions whose supporting provider has no risk assessment)

The panel lists the first 100 issues. If your register has more, the remaining ones appear as you resolve those shown.

4.3 How to Fix Issues

Click the validation panel header to expand the full list of issues. Each issue displays the template code and a human-readable message describing the problem. Navigate to the affected record (provider, contract, or function), fill in the missing information, and save. The validation will re-run automatically when you return to the overview page.

4.4 All Clear State

When all validation checks pass and you have at least one provider registered, a green confirmation banner appears: “All validation checks passed. Register is ready for export.” This confirms your register meets the minimum ITS requirements for NCA submission.

4.5 Export Warning Modal

If you click Export xBRL-CSV while validation errors exist, a warning modal appears instead of opening the xBRL-CSV Export page. The modal shows:

  • The number of unresolved validation errors.
  • A preview of the first 10 errors with their template codes.
  • Two action buttons: Fix Issues First (closes the modal so you can address problems) and Export Anyway (opens the xBRL-CSV Export page despite the errors, where you generate the package).
⚠️
Exporting with unresolved errors may result in your NCA rejecting the submission or requesting clarification. Always aim for zero errors before exporting.

5. CSV Import

The CSV Import feature allows you to bulk-load data into the register from CSV files (a spreadsheet saved as CSV), which is especially useful during initial setup or when migrating from another system.

It creates three kinds of record: ICT providers, contractual arrangements and business functions. It only adds records - it never changes one that is already in the register. Venvera's other imports are listed in the overview of every import.

⚠️
No preview and no undo. Rows are written to the register the moment you click Import, and an import cannot be reversed: unwanted records have to be deleted one by one from their lists. Check your file against the column tables in 5.3 first, and import each file only once.

5.1 Opening the Import Modal

Click the Import CSV button in the top-right corner of the overview page (DORA, Register of Information, Overview). A modal dialog titled Import CSV appears with a Data Type dropdown, a CSV File picker and an Import button. This is the only place an import can be started: the ICT Providers, Contracts and Functions lists have no import button of their own.

To import you need the Manage permission for Register of Information. Administrators always have it. The default Editor and Viewer roles do not, so an Editor can add a provider by hand but cannot import until an administrator grants Manage under Settings, Users & groups (see User Management). The Import CSV button is shown to everyone who can open the page; without the permission, clicking Import brings up an “Insufficient Permissions” message and nothing is imported. The Register of Information itself requires the DORA framework and the Professional or Enterprise plan. Demo accounts are read-only and cannot import.

5.2 Step-by-Step Import Workflow

Step 1 - Select Data Type

Choose what type of data you are importing from the Data Type dropdown. Options are: ICT Providers, Contractual Arrangements, or Business Functions. The expected column format changes based on your selection: the line under the file picker lists the columns for the chosen type. ICT Providers is preselected. Each file holds one data type. Import providers first and contracts second, because every contract row must match a provider that is already in the register.

Step 2 - Prepare Your CSV File

Structure your CSV file with the column headers shown below. The first row must contain column names, and there must be at least one row of data beneath it. Accepted file extensions are .csv and .txt. Excel workbooks (.xlsx, .xls) are not read, so save the sheet as CSV first. There is no template to download: the tables in 5.3 are the specification, and the file rules there say how the file must be saved.

Step 3 - Upload the File

Under CSV File, click the file picker and select your prepared CSV file from your computer. One file is uploaded per run.

Step 4 - Click Import

Press the Import button, which becomes available once a file is chosen. There is no confirmation step: the rows are saved straight away. The button text changes to “Importing...” while the operation runs. Do not close the modal during processing.

Step 5 - Review Results

A results panel appears showing the count of imported records, skipped records, and any row-level errors (see 5.4). When at least one row was imported, the message “Import created.” also appears. The completeness score and Pre-Export Validation refresh automatically after a successful import. To import another data type, choose it under Data Type, select the next file and click Import again. Close the dialog with the X when you have finished.

5.3 Column Formats by Data Type

File Rules

  • Format - a text file saved as CSV in UTF-8 encoding, so that accented characters in names arrive intact. Columns may be separated by commas or by semicolons; Venvera reads which from the header row. Tab-separated files and Excel workbooks are not read.
  • Header row - the first row holds the column names. Capitals do not matter and a space counts as an underscore (a hyphen does not), so “Provider Name” is read as provider_name. The columns may be in any order, and columns Venvera does not recognise are ignored. Where a table below says “also accepted”, a column with that name is treated as the same column.
  • Values - wrap a value in double quotes if it contains the separator, and write a double quote inside such a value twice. Every value must stay on one line, so remove line breaks inside cells before saving. Blank lines are skipped.
  • Size - one file per run, up to 25 MB, with no limit on the number of rows. The results list only the first 50 row messages, so a large register is easier to check when it is imported in several smaller files.

Providers

ColumnTypeRequiredDescription
provider_nameTextRequiredDisplay name of the provider. It is saved as the legal name too. Also accepted: name, display_name, legal_name, provider
leiText (20 chars)OptionalLegal Entity Identifier. It is saved as typed and its format is not checked. A row whose LEI is already in the register is skipped. Also accepted: legal_entity_identifier
countryISO 3166 alpha-2RequiredHeadquarters country code (e.g., DE, FR, US), saved in capitals. A row without it is skipped. The code is not checked against a list, so make sure it is the two-letter code. Also accepted: country_code, headquarters_country
provider_typeTextOptionalType of provider as free text (e.g., Cloud Service Provider); blank is saved as “other”. After the import, open each provider and choose Provider Type from the list (see 5.5). Also accepted: type
criticalityTextOptionalcritical, important, or supporting. Blank is saved as supporting; a row with any other value is skipped. Also accepted: criticality_level
is_intragroupBooleanOptionaltrue, 1, yes or y - the provider is in your corporate group. Any other value, or a blank, means it is not. Also accepted: intragroup
contact_nameTextOptionalName of the provider contact person. Also accepted: contact_person
contact_emailTextOptionalEmail address of the contact. Also accepted: email

Each imported provider counts towards the vendor limit of your plan; once the limit is reached, that row and every later provider row is skipped. The Register of Information and Third-Party Risk, ICT Providers show the same provider list, so imported providers appear in both.

Contracts

ColumnTypeRequiredDescription
contract_referenceTextRequiredYour reference for the contract. The import does not check whether the reference is already in the register, so import each file only once. Also accepted: reference, contract_ref, contract_id
provider_lei or provider_nameTextRequiredLinks the contract to a provider that is already in the register. The LEI is tried first; if the row has no LEI or it is not found, the name is compared with each provider's display name and legal name. The whole name must be the same (capitals do not matter) - part of a name does not match. Where two providers share a name, give the LEI. Also accepted: lei for the LEI and provider for the name
contract_typeTextOptionalType of contractual arrangement as free text; blank is saved as “other”. After the import, open each contract and choose Contract Type from the list (see 5.5). Also accepted: type
service_typeTextOptionalICT service type, saved as typed. After the import, choose ICT Service Type from the list on the contract as well, so that the export carries the matching ESA code. Also accepted: service
start_dateDate (YYYY-MM-DD)RequiredContract start date, for example 2025-01-31. A row without it, or with a date written any other way, is skipped. Also accepted: effective_date
end_dateDate (YYYY-MM-DD)OptionalContract end date, written the same way. Also accepted: expiry_date, termination_date
annual_costNumberOptionalAnnual cost of the arrangement as a plain number with a dot for decimals, such as 12500.50. A row with a thousands separator, a decimal comma, a space or a currency symbol in this column is skipped. Also accepted: cost, annual_value
currencyText (3 chars)OptionalThree-letter currency code; blank is saved as EUR. Keep to EUR, USD, GBP, CHF or BGN, the currencies the contract form offers. The code is saved in capitals and is not checked, so a mistyped code is imported as it stands
data_locationsTextOptionalData location countries, as two-letter codes. Separate several with a vertical bar or a semicolon, for example DE|IE; in a semicolon-separated file use the vertical bar. The export uses them as the country of provision when Country of Provision is not set on the contract. Also accepted: data_location

Functions

ColumnTypeRequiredDescription
function_nameTextRequiredName of the business function. Also accepted: name, function, business_function
is_criticalBooleanOptionaltrue, 1, yes or y - the function is critical, and its Criticality Level is set to Critical. Any other value, or a blank, sets it to Not Critical. Also accepted: critical
rto_hoursTextOptionalRecovery Time Objective. It is saved as text exactly as typed, with no unit added (“4” is shown as “RTO: 4”), so write it the way you would enter it in the function form. Also accepted: rto
rpo_hoursTextOptionalRecovery Point Objective, saved in the same way. Also accepted: rpo

5.4 Results Display

After the import completes, the results panel appears with a coloured border:

  • Green border - all rows imported successfully. Shows “Imported N records.”
  • Amber border - some rows had issues, or the whole upload was refused. Shows the imported count, the skipped count (“N skipped.”), and a scrollable list of messages.

Each row is saved on its own, so a file can be partly imported: the rows that went in stay in the register even when others are skipped. Row numbers count the header as row 1, so the first row of data is Row 2; blank lines are not counted. The list shows the first 50 messages, while the skipped count covers every skipped row. When the whole upload is refused, the panel reads “Imported 0 records.” with the reason beneath it.

MessageMeaning
CSV is empty or has no data rowsThe upload was refused: the file is empty or holds only the header row.
Insufficient permissionsThe upload was refused: you do not have the Manage permission for Register of Information (see 5.1).
Upload failedThe upload did not complete, for example because the file is larger than 25 MB or the connection dropped. Check the lists before trying again, in case some rows were already saved.
Failed to importThe import stopped on an unexpected error. Rows read before that point may already be saved, so check the lists before trying again.
Row N: Missing provider nameThe provider row has no name. If every row shows this, the file has no header row or its columns are separated by something other than commas or semicolons.
Row N: Missing countryThe provider row has no country.
Row N: criticality must be critical, important or supporting (got "X")The criticality column holds another value. Correct it or leave it blank.
Row N: Skipped, a provider with LEI X is already in the registerThe provider is already there and has been left as it was. Edit it by hand if its details have changed.
Row N: Your plan includes N vendors. Upgrade your plan to add more.The vendor limit of your plan has been reached. This row and every later provider row is skipped.
Row N: Missing contract referenceThe contract row has no reference.
Row N: Could not match provider "X"No provider in the register has that LEI or exactly that name. Import or add the provider first, or correct the spelling. Empty quotes mean the row has neither an LEI nor a name.
Row N: Missing start dateThe contract row has no start date.
Row N: Dates must be written as YYYY-MM-DDThe start or end date is written another way, such as 31/01/2025.
Row N: annual_cost must be a plain number such as 12500.50 (got "X")The cost holds a thousands separator, a decimal comma, a space or a currency symbol.
Row N: Missing function nameThe function row has no name.
Row N: followed by any other textThe row could not be saved, for example because its date does not exist (2025-02-30). Correct the row and import it again.

To retry skipped rows, correct them and import a file that holds only those rows beneath the header row. Do not import the whole file again: contracts and functions that went in the first time would be added a second time, as would providers without an LEI.

5.5 After the Import

An import fills in the basics only. Before you export, work through the imported records:

  • Pre-Export Validation - the panel refreshes after the import and normally shows new warnings: providers without an LEI, unchecked Article 30(2) clauses on each imported contract, and functions not linked to any contractual arrangement.
  • Providers - under DORA, Register of Information, ICT Providers, open each imported provider for editing, choose its Provider Type from the list and save.
  • Contracts - under DORA, Register of Information, Contracts, open each imported contract for editing, choose its Contract Type and ICT Service Type from the lists, tick the functions it supports under Business Functions, and assess the Article 30 clauses.
  • Functions - under DORA, Register of Information, Functions, check each function's Criticality Level. The import sets Critical or Not Critical only, so set Important by hand where it applies, and add the business line, description and discontinuation impact.
  • Audit trail - each imported record is logged on its own as “Created” under ICT Providers, Contracts or Functions in Settings, Audit trail, in the name of the user who ran the import. There is no single entry for the import as a whole.

5.6 What the Import Does Not Do

  • It does not update existing records. A provider, contract or function that is already in the register is never changed by an import; edit it by hand.
  • It checks for duplicates by provider LEI only. A provider row is skipped when its LEI is already in the register. Providers without an LEI, contracts and functions are not compared with what is there, so importing the same file twice adds them twice.
  • It cannot be undone. There is no import history and no way to reverse an import. Unwanted records have to be deleted one by one from their lists, which needs the Manage permission for Register of Information. Deleting a provider also deletes its contracts.
  • It does not import everything. Risk assessments, branches, sub-outsourcing chains, the links between functions and contracts, Article 30 clause answers, documents and custom fields are not imported. Nor are a provider's Alternative ID, Person Type and Ultimate Parent ID, a contract's notice periods, governing law, data sensitivity, storage and processing locations and audit details, or a function's business line, description, discontinuation impact and last assessment date. Enter these by hand. A licensed_activity column in a functions file is ignored.
  • It does not read export files. The files produced by the xBRL-CSV export (b_01.01.csv to b_99.01.csv) are made for your NCA and cannot be imported back.

6. Section Cards

The lower portion of the overview page displays a 2×2 grid of section cards, one for each pillar of the register:

CardIconDescriptionActions
ICT ProvidersBuilding icon (teal accent)Third-party ICT service providers in your registerView all - opens the providers list page. Add provider - opens the new provider form.
Contractual ArrangementsDocument icon (indigo accent)Contracts and agreements with ICT providersView all - opens the contracts list page. Add contract - opens the new contract form.
Business FunctionsLayers icon (amber accent)Functions supported by ICT arrangementsView all - opens the functions list page. Add function - opens the functions page for adding a new entry.
Risk AssessmentsShield icon (rose accent)Risk evaluations per ICT providerView all - opens the risk assessments list page. Add assessment - opens the new assessment form.

Each card is styled as a glass-effect panel that highlights on hover. The two action buttons are at the bottom of each card: a secondary button for “View all” and a primary button for adding a new record.

7. Exporting for NCA Submission

The Export xBRL-CSV button in the top-right corner opens the xBRL-CSV Export page, where Generate xBRL-CSV Export produces the complete register in the format required by your NCA. During export, Venvera automatically:

  • Converts business-language values to the codes the ESA templates use (e.g., the country “DE” becomes eba_GA:DE). The provider type is kept in Venvera only and is not part of the export.
  • Structures data into the correct ITS template sheets (B_01.01 through B_99.01).
  • Applies the xBRL-CSV taxonomy header rows and metadata.
  • Packages everything into a downloadable archive.

You do not need to understand ESA codes or xBRL-CSV formatting - Venvera handles the translation layer entirely.

💡
NCA Submission Readiness. A completeness score of 100% with zero validation errors means your register meets all minimum ITS requirements. However, review the exported data for accuracy before submitting - automated validation checks structure, not substance. Ensure that provider names, LEIs, contract references, and cost figures are factually correct.
ℹ️
Ongoing Obligation. The Register of Information is not a one-time filing. Article 28(3) requires you to keep it “up to date.” Every time you onboard a new ICT provider, sign a new contract, terminate an arrangement, or identify a change in criticality, update the register accordingly. NCAs may request the register at any point during the year.