DORA Report Data Validation Reference

Important:

The DORA Report Generation feature is available for customers with solution packaging only.

The table below provides context on data validations to add to DORA system attributes. This helps ensure correct data formatting for the Register of Information report when exported from the OneTrust application.

You can update attribute values within the inventory details view of a record if any of these attributes have corresponding attribute questions configured within assessment templates and as part of bulk create or bulk update imports.


Object	Attribute	Validation	Notes
Entity	LEI of Entity	20-character, alpha-numeric code based on the ISO 17442 standard. Values must be unique unless the records are connected through a supported Parent/child link. When inheritance is enabled, the child may share the parent’s value when that value is inherited from the parent.	Use the Is Financial Entity attribute to ensure users input the correct value format: If Yes, only LEI is allowed. If No, either LEI or EUID is allowed.
Entity	LEI of Entity (when using EUID)	Should contain correct EU country code format
Entity	Function Identifier	Values must be unique unless the records are connected through a supported Parent/child link. When inheritance is enabled, the child may share the parent’s value when that value is inherited from the parent. Function Identifier value should be in the format: F + an integer (e.g.: F1, F2, F3)
Vendor	Identification code of the ICT third-party service provider	If LEI, then 20-character, alpha-numeric code based on the ISO 17442 standard If EUID, should contain correct EU country code format Values must be unique unless the records are connected through a supported Parent/child link. When inheritance is enabled, the child may share the parent’s value when that value is inherited from the parent.
Vendor	Identification code of the ICT third-party service provider’s ultimate parent undertaking
Nth Party	Identification code of the ICT third-party service provider’s ultimate parent undertaking	Values must be unique across records.
Nth party	Identification code of the ICT third-party service provider, Identification code of the ICT third-party service provider’s ultimate parent undertaking, Identification code of the recipient of sub-contracted ICT services	If LEI, then 20-character, alpha-numeric code based on the ISO 17442 standard If EUID, Should contain correct EU country code format Values must be unique across records for Identification code of the ICT third-party service provider
Entity	LEI of Entity	Values must be unique unless the records are connected through a supported Parent/child link. When inheritance is enabled, the child may share the parent’s value when that value is inherited from the parent.
Entity	Identification code of the Branch	Values must be unique unless the records are connected through a supported Parent/child link. When inheritance is enabled, the child may share the parent’s value when that value is inherited from the parent.
Entity	Value of total assets of the financial entity	Number only, no decimals.
Contract	Contractual Arrange Reference Number	Values must be unique unless the records are connected through a supported Parent/child link. When inheritance is enabled, the child may share the parent’s value when that value is inherited from the parent.
Contract	End Date of Contractual Arrangement	The end date cannot be before the start date.
Contract	Annual expense or estimated cost of the contractual arrangement for the past year	Number only, no decimals.
Engagement	Notice period for the financial entity making use of the ICT service(s)	Number only, no decimals.
Engagement	Notice period for the ICT third-party service provider	Number only, no decimals.
Vendor	Total annual expense or estimated cost of the ICT third-party service provider	Number only, no decimals.
Entity	Recovery time objective of the function	Number only, no decimals.
Entity	Recovery point objective of the function	Number only, no decimals.

Note:

Users can employ Parent/child linking to allow a child record to share the parent’s value for the following four attributes when inheritance is enabled: Identification Code of the ICT Third Party Service Provider, Function Identifier (Function), LEI of Entity, and Identification code of the Branch.

This is a targeted capability for linked parent/child records, not a general relaxation of duplicate validation. Values on records that are not connected through a supported Parent/child link remain subject to the uniqueness validation. Existing child records are not automatically backfilled unless the product workflow performs the inheritance or synchronization.