# Register of Information

DORAedge enables regulated financial entities to easily generate the Register of Information (RoI) report from ICT Network data. The report can be extracted ad-hoc as needed and to comply with annual regulatory reporting requirements. 

### Specifications of the Register of Information

* **Format:** xBRL-CSV reporting package, zip file with all required sheets and metadata. 
* **Data:** Includes all ICT Network and contractual relationship data required for reporting in alignment with the European Banking Authority (EBA) Data Model (DPM) 4.0.

### Generating the Register of Information

Prior to generating the Register of Information, ensure that all ICT Network data (Entities, Branches, Functions, Providers, and Contracts) is accurate. 

{% hint style="warning" %}
Any Archived records or Draft Contracts will **not** be included in the Register of Information. Expired Contracts will be included, unless those records are Archived.
{% endhint %}

To create a Register of Information report: 

1. In the sidebar, go to the Export section, then click **Register of Information**.
2. Select the **Subject Entity**.
3. Select the **Reporting level**.
   1. **Individual consolidation:** All non-draft and non-archived Contacts with the Subject Entity identified as the Consumer Entity will be included.
   2. **Sub-consolidated:** All non-draft and non-archived Contacts with the Subject Entity and child Entities identified as the Consumer Entity will be included.
   3. **Consolidated:** All non-draft and non-archived Contacts for all Entities identified as the Consumer Entity will be included.
   4. **Custom:** Select specific Entities from the Group to be included.
4. Choose the **Reference Date**. 
   1. For annual reporting requirements, select the date instructed by regulators.
5. Choose the **Reporting Standard.**
   1. As of April 2026, DORAedge offers four (4) Reporting Standards can be selected when generating the Register of Information, where each standard has its own custom fields and file package requirements in relation to the corresponding Competent Authority.
      1. **EBA Standard**
         1. This is the EBA's Reporting Standard and is the base Standard for all Register of Information reports. Enabling **Use Custom Report File Settings** allows you to modify the Reporting ID and Reporting Package File Name when generating the reporting package.
         2. **NBB-, AFM-, and CAA-specific Standards**
            1. These Standards specific to each corresponding Competent Authority with unique custom fields and file package requirements. Select one of these Standards if in need to generate a Register of Information for the applicable Competent Authority.
6. Enable or **Skip validations.**
   1. If this box **is not selected**, data validations will run prior to the Register of Information being created to ensure that all data fits reporting requirements. 
      1. If the Invalid Register of Information error message pops up, click **View** on the individual records that have errors. Click **Edit \[Record]** to correct invalid data on the record. 
      2. Once all data errors are corrected, click **Create** to generate the Register of Information.
   2. If this box **is selected**, the Register of Information will be generated, regardless of any data errors.
7. Click on **Create Report** to export the Register of Information out of DORAedge. 

{% hint style="warning" %}
Once the Register of Information is exported, **do not make any changes to the file**, including the name of the folder, sheets or any data. Doing so can cause invalid report submissions to regulators.
{% endhint %}


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.doraedge.com/user-guide/register-of-information.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.