---
sourceDocument: Zurich Governance, Risk, and Compliance
sourceDocumentLink: https://www.servicenow.com/docs/r/zurich/governance-risk-compliance
Release :
- zurich
ft:locale :
- en-US
ft:publication_title :
- Zurich Governance, Risk, and Compliance
ft:clusterId :
- grc
bundleId :
- grc
workflow :
- Technology
---
# Register of information regulatory packages
# Register of information regulatory packages {#ariaid-title1}
Release version: Zurich
Updated September 10, 2026
 3 minutes to read
Summarize
 Summarized using AI
This content was generated using new OpenAI-powered functionality. Results are provided on an as is basis and are not guaranteed to be accurate or complete.
## Summary of Register of information regulatory packages
The Register of Information (RoI) is a mandatory regulatory reporting package under the Digital Operational Resilience Act (DORA), designed for financial entities to demonstrate compliance.
Supported by the Digital Resilience Third-party Information Register application within the Vendor Management Workspace, RoI captures structured data on legal entities, third-party service providers, contracts, and functions aligned with DORA requirements.
Show full answer Show less
Starting with version 21.1.x, third-party assessors can generate regulator-ready RoI packages in a Plain-CSV format that complies with European Banking Authority standards. These packages include metadata, reports, and filenames containing key identifiers such as LEI and entity ID, facilitating automated validation and regulator submission.
## Key Features
* **Data Capture and Reporting:** Supports detailed data entry for entities, contracts, functions, and third parties with CSV report generation aligned to regulator specifications.
* **Validation and Compliance:** Includes technical, schema, and business rule validations with automated workflows and email notifications for errors or warnings.
* **Role-Based Access:** Enables third-party risk administrators and assessors to manage and maintain reporting configurations, validation rules, and terminology definitions within the Vendor Management Workspace.
* **Currency Conversion and Aggregation:** Optional features during report generation standardize and aggregate third-party expenses without altering source data.
* **Scheduled Quarterly Reporting:** A scheduled job can automatically generate quarterly RoI CSV reports based on prior configurations to ensure timely compliance submissions.
* **LEI Validation:** Performs Level 4 Legal Entity Identifier validation against the GLEIF database, including detailed validation reports for enhanced data quality assurance.
* **Terminology Definitions Module:** Allows customization of closed-set indicator options used in RoI templates to reflect organizational terminology in exports.
## Practical Use for ServiceNow Customers
ServiceNow customers leveraging the Digital Resilience Third-party Information Register can efficiently prepare and submit RoI packages compliant with DORA. The application streamlines the collection, validation, and packaging of critical third-party risk and operational resilience data, reducing manual effort. Role-based controls ensure proper governance, while automated validation and scheduled reporting enhance accuracy and timeliness.
Customers can choose between Excel master templates for internal data preparation and Plain-CSV packages for regulator submissions. Access to configurable validation rules and decimal precision settings allows customization to organizational needs without impacting system data integrity.
By using this framework, customers ensure consistency across regulatory submissions, satisfy EU DORA compliance, and facilitate automated regulator validation workflows, ultimately supporting stronger operational resilience and third-party risk management.
The Register of Information (RoI) is a regulatory reporting requirement under the Digital Operational Resilience Act (DORA) and is supported by the Digital Resilience Third-party Information Register application in the Vendor Management Workspace.
## RoI overview
The RoI is a structured data package that financial entities must submit to regulators to demonstrate compliance with DORA. It includes information about legal entities, third-party service
providers, contracts, and functions.
Starting with version 21.1.x, third-party assessors (sn_vdr_risk_asmt.vendor_assessor) can generate regulator-ready RoI packages using the Plain-CSV Report Package option on the download
page. The ZIP file includes metadata and report folders structured to regulator specifications, with file names containing LEI, entity ID, and release version. This enhancement supports EU
DORA compliance and automated validation workflows. You can follow the guide provided in the Instructions section on the Download/Upload request page for step-by-step instructions
and required permissions.
Note:
You can use the Excel master template option to download a document to use for data preparation and internal review and the Plain-CSV reporting package option to download a document to use for regulator submission and compliance validation. For more information, see [Create a Microsoft Excel download request](https://www.servicenow.com/docs/gbMfEB7xcsyNrgoBrgIAPw "Create a Microsoft Excel download request to download the records from the Digital resilience third-party registers using Third-party Risk Management for auditing purposes.").
The RoI framework aligns with DORA's five
pillars, particularly ICT third-party risk management and incident reporting. TPRM contributes third-party risk data that is included in RoI packages generated by Digital Operational Resilience capabilities. These RoI packages follow the European Banking Authority's
structure and validation requirements.
The RoI framework includes DPM business validation rules, properties, and additional configuration files such as report.json, reportPackage.json, decimalsMonetary, and FrameworkCodeModuleVersion. These components enable third-party risk administrators (sn_vdr_risk_asmt.vendor_risk_admin) to view and maintain validation logic and configuration settings for CSV reporting and automated validation workflows, helping maintain consistency across regulatory submissions. TPR admins can access these properties by navigating to AllDigital Operational Resilience ManagementProperties and can access DPM business validation rules by navigating to AllDigital Operational Resilience ManagementDPM business validation rules.
Note:
The decimalsMonetary property controls decimal precision for monetary values in Master Template and CSV downloads only. You can set decimal precision to -6,
-3, 0, or 2 for monetary value fields. It doesn't affect UI display, upload and validation, individual table downloads, or database storage.
After validation completes, the system automatically notifies the request initiator by email and attaches the validation report when errors or warnings are detected.
## Digital Resilience Third-party Information Register support for RoI
The Digital Resilience Third-party Information Register provides the following capabilities to support RoI compliance:
* Data capture for entities, contracts, functions, and third parties
* CSV report generation aligned with regulator specifications
* ZIP packaging with metadata and report folders
* Validation workflows for technical, schema, and business rule checks
* Level 4 LEI validation against the GLEIF database, with a downloadable `Level4_LEI_Validation_Report.csv` included in `Consolidated_Reports.zip`. For more information, see [Validate Legal Entity Identifier codes for DORA reporting](https://www.servicenow.com/docs/gxEkcBc0Mbt~Y0VUDiXsVA "Review and resolve Legal Entity Identifier (LEI) validation results for DORA Register of Information reporting. LEI validation runs automatically during Plain-CSV Reporting Package generation and Microsoft Excel upload to verify that LEI codes in the digital resilience registers exist in the GLEIF database and have an active and issued status.").
* A Terminology Definitions module for providing your organization's internal definitions of the closed-set indicator options used across RoI templates, so the B_99.01 export includes your terminology. For more information, see [Define terminology for the Register of Information export](https://www.servicenow.com/docs/98sGPqZQ2dcauPcogIEw6Q "Define your organization's internal definitions for the closed-set indicator options used across the Register of Information, so the B_99.01 export includes your terminology rather than empty values.").
* Role-based access for managing RoI requests
Note:
All RoI-related actions are performed in the Digital resilience third-party registers section of the Vendor Management Workspace. This workspace provides access to download/upload requests, validation tools, and master
templates.
For more information, see [Generate a register of information package](https://www.servicenow.com/docs/5LW15PFA4Sb22JAsihNLzA "Use the CSV report option in the download page to generate regulator-ready Register of Information (RoI) packages.")
## Currency conversion and aggregation {#tprm-dora-roi__section_z3w_jmz_13c}
During report generation, you can enable optional currency conversion and third‑party total expense aggregation. These options standardize or combine annual expense values in the reporting package. These options affect only the
generated reporting package and don't modify source records in the digital resilience registers.
For more information, see [Currency conversion and third-party expense aggregation](https://www.servicenow.com/docs/Og~5dpBeSdZTG4MRXHHc~Q "During report generation, the Register of Information (RoI) converts contract annual expenses to a base currency. It then aggregates totals per eligible third-party provider or engagement. The RoI is a regulatory reporting requirement under the Digital Operational Resilience Act (DORA) and is supported by the Digital Resilience Third-party Information Register application in the Vendor Management Workspace application.").
## RoI validation checks {#tprm-dora-roi__section_dora_roi_validation_checks}
Business-rule checks for RoI validation generate data quality warnings for contracts and third-party service providers without blocking Plain-CSV reporting package generation. For the complete list of these checks, see [Validation framework for Register of Information](https://www.servicenow.com/docs/QQY190ndqMkH3BX7pnkygw "The validation framework helps ensure that RoI packages meet regulatory requirements defined by the DORA.").
## Quarterly RoI CSV generation {#tprm-dora-roi__section_dora_roi_scheduled_csv}
A quarterly scheduled job (DORA: Quarterly CSV download) generates the CSV Register of Information report for the previous quarter automatically, so you don't have to trigger the download manually each quarter. The job is inactive by
default; a TPR admin \[sn_vdr_risk_asmt.vendor_risk_admin\] can navigate to AllSystem DefinitionScheduled Jobs and activate it before it runs.
When the job runs, it uses the most recently created CSV download request record as its configuration template, regardless of that record's state. It copies the entity, competent authority, base currency, currency
conversion, and third-party total expense aggregation settings to the new request. No email notification is sent for the generated report, because the job runs under the system account rather than a specific user.
**Related concepts**
* [Validation framework for Register of Information](https://www.servicenow.com/docs/QQY190ndqMkH3BX7pnkygw "The validation framework helps ensure that RoI packages meet regulatory requirements defined by the DORA.")
**Related tasks**
* [Generate a register of information package](https://www.servicenow.com/docs/5LW15PFA4Sb22JAsihNLzA "Use the CSV report option in the download page to generate regulator-ready Register of Information (RoI) packages.")
* [Define terminology for the Register of Information export](https://www.servicenow.com/docs/98sGPqZQ2dcauPcogIEw6Q "Define your organization's internal definitions for the closed-set indicator options used across the Register of Information, so the B_99.01 export includes your terminology rather than empty values.")
**Related reference**
* [Terminology and definitions fields](https://www.servicenow.com/docs/DwMNeTqW_lCWSLc3EKYZ4w "Field descriptions and the full set of closed-set options for the Terminology and definitions list, used to populate the DORA B_99.01 Register of Information export.")
*[\>]: and then