CDQ Data Quality as Service

Kuehne+Nagel requires support for handling and validating the European Unique Identifier (EUID) as a separate identifier for legal entities.

From the KN CIP data model perspective, EUID must be stored and validated independently from existing Romanian identifiers such as:

• CUI, currently handled as VAT / EU VAT ID

• CNP, currently handled as BRN / RO Tax ID

EUID is a separate European business-register identifier and should not be treated as either a VAT identifier or a national business registration identifier.

Requested Capability from CDQ

KN would like CDQ to support EUID as a dedicated identifier type and validation object, for example:

• EUID

• EU_ID

• or another dedicated technical key defined by CDQ

The identifier should be available for maintenance, validation, and qualification independently from VAT and BRN identifiers.

Background

For Romania, KN already maintains identifier mappings for:

• CUI as VAT / EU VAT ID

• CNP as BRN / RO Tax ID

However, EUID (European Unique Identifier) is a separate European business-register identifier and should not be treated as either a VAT identifier or a national business registration identifier.

According to the Romanian National Trade Register Office / Ministry of Justice Order No. 5307/C/2022, the Romanian EUID format is:

<country code><register ID><order number in the Trade Register>

EUID is therefore a separate business-register identifier and not the same as EU VAT/CUI or CNP/BRN.

Source:
https://www.onrc.ro/documente/Ordinul%20ministrului%20justi%C8%9Biei%20nr.%205307.pdf

Currently, KN could not identify a dedicated EUID identifier type within CDQ and therefore requires support for maintaining and validating this identifier independently from existing VAT and BRN identifiers.

Request:

KN requests CDQ to evaluate and provide:

• Support for a dedicated EUID identifier and technical key.

• Availability of EUID support for Romanian legal entities.

• Validation support within Data Quality and Qualification processes.

• Format validation based on applicable EUID rules.

• Clarification whether validation is implemented as a generic EU-wide rule or as a country-specific rule.

• If not currently available, onboarding of EUID as a separate identifier including format validation.

Business Impact:

KN needs to maintain and validate European business-register identifiers accurately and independently from VAT and BRN identifiers.

The absence of dedicated EUID support creates risks related to:

• Incorrect identifier mapping.

• Mixing business-register identifiers with tax identifiers.

• Reduced master data quality.

• Inconsistent identification of legal entities across European jurisdictions.

A dedicated EUID identifier and validation capability would ensure accurate master data maintenance, improve data quality, and enable clear separation between tax identifiers and European business-register identifiers.