---
sourceDocument: Australia Governance, Risk, and Compliance
sourceDocumentLink: https://servicenow-prod.fluidtopics.net/r/governance-risk-compliance

 Release :

    - australia

ft:locale :

    - en-US

ft:publication_title :

    - Australia Governance, Risk, and Compliance

ft:clusterId :

    - grc

bundleId :

    - grc

workflow :

    - Technology


---

# Validation framework for Register of Information in Operational Resilience

# Validation framework for Register of Information in Operational Resilience {#ariaid-title1}

* Release version: Australia
* 
* Updated March 12, 2026
* 
* ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 4 minutes to read

Summarize  
![AI sparkle icon](https://servicenow.com/docs/portal-asset/ai-sparkle-icon) 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 Validation framework for Register of Information in Operational Resilience

The validation framework in the Digital Resilience Third-party Information Register (RoI) application ensures that RoI packages comply with the regulatory requirements set by the Digital Operational Resilience Act (DORA).
It provides a real-time, automated, three-level validation during the upload of RoI CSV files to verify technical accuracy, regulatory compliance, and business rules adherence.
This system helps ServiceNow Operational Resilience administrators and managers efficiently validate and maintain data integrity for operational resilience reporting.
Show full answer Show less  

## Key Features

* **Three-level validation system:**
  * **Level 1 (Technical checks):** Validates file encoding, structure, and naming against 29 rules.
  * **Level 2 (Template and schema alignment):** Applies 12 rules to ensure correct templates and schema usage.
  * **Level 3 (Business rules):** Enforces 70 rules verifying regulatory logic and dependencies.
* **Automatic validation upon upload:** When a ZIP package is uploaded, validation runs immediately without extra user actions.
* **Validation results reporting:** Outputs downloadable reports with detailed error mappings, rule descriptions, and row-level summaries to assist in troubleshooting.
* **Email notifications:** Users who initiate uploads or downloads receive automated emails with validation results and attachments as applicable.
* **Templates for error resolution:** Excel templates reflecting the CSV structure are available for download to help identify and correct errors in source data.
* **Accessible configuration:** Operational Resilience administrators can view and adjust validation rules and settings via the Digital Operational Resilience Management interface.

## Practical Guidance for ServiceNow Customers

* Ensure RoI CSV packages conform to the required file encoding (UTF-8), naming conventions, and size limits (under 5 MB) to avoid upload errors.
* Use provided Excel templates to prepare data and to interpret validation reports effectively by cross-referencing row numbers and field labels.
* Review validation reports carefully for missing fields, invalid LEI codes, incorrect currency values, or improper use of "Not applicable" entries, then correct data accordingly.
* Re-upload corrected packages to trigger validation again and confirm compliance before final submission.
* Operational Resilience administrators and managers have the permissions needed to perform validation tasks within ServiceNow.

## Expected Outcomes

By leveraging this validation framework, ServiceNow customers can confidently submit RoI packages that meet DORA regulatory standards, reducing manual errors and streamlining compliance workflows. The automatic validation and detailed reporting facilitate quick identification and correction of data issues, improving data quality and operational resilience reporting accuracy.  
The validation framework helps to verify that RoI packages meet regulatory requirements defined by the DORA.

## Validation overview {#opres-dora-validate-roi__section_fg1_zq4_dhc}

The validation framework for the Digital Resilience Third-party Information Register application ensures that downloaded RoI packages comply with the structural, formatting, and data integrity requirements defined by the DORA. It supports a real-time, three-level validation system that automatically checks for technical accuracy, regulatory alignment, and business rule compliance during the upload
process.

* Level 1 (Technical checks): 29 rules validating file encoding, structure, and naming.
* Level 2 (Data package mode technical checks): 12 rules ensuring template and schema alignment.
* Level 3 (Data package model business rules): 70 rules verifying regulatory logic and field dependencies.

{#opres-dora-validate-roi__ul_o5g_g5w_3hc}  
Note:  
The Data Package Model is used to structure and validate RoI packages.

Operational Resilience administrators can view and maintain validation logic and configuration settings using the DPM business validation rules and the report.json, reportPackage.json, and FrameworkCodeModuleVersion properties. These settings support CSV reporting and automated validation. Operational Resilience administrators can access these properties by navigating to AllDigital Operational Resilience Management and then selecting Properties or DPM Business Validation Rules.

## Validation process {#opres-dora-validate-roi__section_rkn_1r4_dhc}

Validation is now performed automatically during the upload of RoI CSV files. As soon as the ZIP package is uploaded via an Excel download/upload request, the system initiates real-time validation without requiring a separate request
type. The system performs checks across multiple dimensions:

* File-level validation: Ensures correct encoding, naming conventions, and file structure.
* Template-level validation: Verifies that required templates are present and formatted correctly.
* Field-level validation: Applies rule expressions to check for missing values, incorrect formats, and invalid references.

{#opres-dora-validate-roi__ul_i2c_cr4_dhc}

Validation results are returned in a downloadable report that includes:

* Mappings to regulator fields such as Template Code, Row Code, and Column Code.
* Rule expressions and descriptions.
* Real-world field labels and record identifiers.
* Row-level error summaries.

{#opres-dora-validate-roi__ul_j2c_cr4_dhc}

Operational Resilience managers (sn_oper_res.manager) can validate downloaded RoI packages using the same Plain-CSV Report Package option. After a validation report is generated for a Register of Information (RoI)
package, the system automatically sends an email notification to whoever initiated the download or upload request. This email alerts the user that the process has completed and provides access to the results. If validation warnings are
detected, both the validation report and the CSV package are attached to the request record. If no issues are found, only the CSV package is included. This automated notification ensures timely awareness and facilitates efficient
follow-up actions for compliance and data correction workflows.

To assist with error resolution, users can cross-reference the validation report with downloadable templates that mirror the CSV structure. These templates help identify the location and context of each issue, making it easier to
correct data in the ServiceNow instance or source system. Validation reports are only generated when errors or warnings are detected. If no issues are found, only the CSV package is returned.

To improve troubleshooting, the system maps rule expressions to real-world field labels and record identifiers. Even when malformed data is uploaded, the validation API returns meaningful error messages to help users identify and
resolve issues efficiently.

Excel templates are available for download from the Download/Upload Request page. These templates mirror the expected CSV structure and provide field definitions, formats, and sample values to assist with
validation and error resolution.  
Important:  
The Operational Resilience administrators (sn_oper_res.admin) and managers (sn_oper_res.managers) can perform the validation tasks.

## Common validation issues {#opres-dora-validate-roi__section_azd_xq4_dhc}

Refer to the following guidance to troubleshoot common validation issues when submitting RoI packages.

* Validation report is missing: The uploaded package contains no errors or warnings. Check the Result section of the request. If no issues are found, only the CSV package is returned and no validation report is generated.
* Missing required fields: One or more required fields are empty or incorrectly formatted. Open the validation report and locate the affected row and column. Use the template to identify the correct field name and expected format. Update the record in the ServiceNow instance or source system and revalidate.
* Rule expression failures: The data violates one or more business rules defined in the validation framework. Review the rule expression and description in the validation report. Use the record identifier to locate the affected
  record and correct the data. Common issues include invalid LEI formats, empty currency fields, or missing contract references.

  The following example shows an LEI validation error returned in the validation report: Row 4.0, errorCode=INVALID_VALUE, errorMessage=LEI not found in GLEIF database: column: Identification code of the branch, value: BR1234567890ABCDEF40

  The error indicates that the uploaded LEI value does not exist in the GLEIF database. Correct the LEI value in the source record or Microsoft Excel file and re-upload. Only LEI values that pass real-time GLEIF validation are accepted.
* Invalid use of "Not applicable" values: These values are used in fields that don't support them. Check the field definition in the template. Replace "Not applicable" with a valid value or remove it if the field is required. Revalidate the updated package.
* Validation report is difficult to interpret: The report lacks context or field labels are unclear. Download the template and use it to cross-reference the row number, sheet name, and record identifier. This helps locate the affected record and understand the validation error in context.
* File size or encoding issues: The uploaded ZIP file exceeds the 5 MB limit or uses unsupported encoding. Compress the file to meet the size requirement and ensure all CSV files use UTF-8 encoding. Re-upload the corrected package.

{#opres-dora-validate-roi__ul_p5g_g5w_3hc}

For more information, see [Validate the Register of Information packages](https://servicenow-prod.fluidtopics.net/8~8TzP4z24wfOH9ZAGOr9w "Run real-time validation on Register of Information (RoI) packages to help ensure compliance with DORA requirements.").

*[\>]: and then