The model standardizes how business partner information is described and linked. It includes core concepts, their attributes, and the relationships required for validation logic, data observability and interoperability with external reference sources. Each of the 422 concepts is defined with clear semantics to support use cases such as legal form recognition, address normalization, identifier validation, entity matching and structured data sharing.
| Active data sources | Records |
|---|
| BR.RF (data source) | 68,448,240 | | CDQ.INTEL (data source) | 53,424,978 | | VIES (data source) | 50,000,000 | | FR.RC (data source) | 42,668,104 | | GB-EAW.CR (data source) | 9,224,308 | | US-CA.BER (data source) | 8,923,189 | | US-FL.BER (data source) | 6,616,885 | | JP.CR (data source) | 5,708,772 |
|
The Data sharing platform integrates 246 data sources. 147 of these are external data sources with 4,198 concepts and 24,858 terms mapped to 422 concepts and 17,376 terms of the CDQ data model.
|
Documentation of 2,940 data quality rules, grouped into 11 rule features and 60 rule categories.
| Rule features
|
Categories
|
Rules
|
| Address checks
|
Address consistency, Address inactive, Address incomplete, Administrative area invalid, Administrative area missing, Country invalid, Dummy postal code, Missing locality, PO Box misplaced, Phone number format, Phone number misplaced, Postal code format, Postal code invalid, Postal code missing, Postal code outdated, Postal code schema, Street address incomplete, Thoroughfare missing
|
1,247
|
| Bank account checks
|
Domestic bank account number format, Domestic bank identifier format, IBAN checkdigit, IBAN format
|
140
|
| Bank account data checks
|
Domestic bank account number format, Domestic bank identifier format, IBAN checkdigit, IBAN format
|
25
|
| Business and tax identifier qualifications
|
EU TAX Qualification, EU VAT Qualification (AT), EU VAT Qualification (Fuzzy), EU VAT Qualification (Standard), EU VAT Qualification by AT.FON, EU VAT Qualification by BZSt, EU VAT Qualification by VIES, Fuzzy EU VAT Qualification by VIES, Identifier qualification, Qualification, Worldwide TAX Qualification
|
78
|
| Business partner checks
|
Business partner inactive, Care of misplaced, Contact misplaced, Name missing
|
338
|
| Business partner profile checks
|
Business partner inactive, Care of misplaced, Contact misplaced, Name missing, Name pattern
|
7
|
| Compliance and risk checks
|
Unflagged natural person
|
2
|
| Identifier checks
|
Identifier checkdigit, Identifier consistency, Identifier deprecated, Identifier deprecation, Identifier existence, Identifier format, Identifier missing, Identifier qualification, Identifier schema
|
782
|
| Identifier qualifications
|
EU TAX Qualification, EU VAT Qualification (AT), EU VAT Qualification (Fuzzy), EU VAT Qualification (Standard), EU VAT Qualification by AT.FON, EU VAT Qualification by BZSt, EU VAT Qualification by VIES, Fuzzy EU VAT Qualification by VIES, Qualification, Worldwide TAX Qualification
|
292
|
| Legal form checks
|
Legal form invalid, Missing legal form
|
0
|
| Name checks
|
Name missing, Name pattern
|
1
|
CDQ provides documented data quality rules to validate business partner records in a consistent, service-ready way. Instead of translating changing business requirements into repeated, manual IT implementation, CDQ maintains rule logic and the required reference knowledge (for example country specific formats, legal forms, and Business identifier metadata specifics) so customers can apply checks reliably across systems and processes.
Rules can use different types of inputs depending on the validation need. Some checks are purely structural and can be executed on the record itself, others require managed reference data, and some depend on external validation services (for example for tax related checks that go beyond format). The same rule set can be applied both in real time workflows and in batch based data quality assurance, exposed through a single execution interface and integrable via APIs.
Where a rule relies on external or community defined requirements, CDQ maintains supporting sources to ensure content correctness and traceability. Depending on the case, this can include an authority reference, another trustworthy publication, or a community-provided standard, along with the relevant metadata to document why the rule exists and what it is based on.
|
Metadata defines how data is structured, interpreted, and validated across systems. It is the foundation that enables organizations to exchange and compare information consistently, regardless of jurisdiction or language. For CDQ, metadata is essential to make data sharing possible at scale and across borders.
Because regulatory and business requirements change over time, metadata must evolve dynamically. CDQ maintains a continuously updated metadata repository that captures national and sector-specific data rules, such as address formats, identifier structures, and legal form codes. This ensures that shared and validated data remains semantically correct and compliant across all contexts. By sharing standardized metadata, CDQ enables customers to align their data models and validation rules, making collaboration efficient and legally sound.
| Metadata | Description |
|---|
| Bank account metadata | Managed reference data for bank accounts worldwide with banking metadata for 170 countries incl. 251 bank identifiers. | | Business identifier metadata | Managed reference data for 569 business identifiers used to uniquely identify legal entities, establishments, and other organization types across jurisdictions. | | CDQ data model | Conceptual structure of business partner data across the CDQ platform with 422 concepts. It provides a consistent semantic framework for representing legal entities, addresses, identifiers, classifications and related attributes that are used in CDQ Cloud Services such as validation, monitoring and data sharing. | | Compliance list metadata | Managed reference data for 913 compliance lists such as sanctions lists, watchlists, and politically exposed persons (PEP). | | Country metadata | Managed reference data for 316 countries based on ISO 3166-2 standards, used for harmonization, validation, and international data interoperability. | | County (administrative area) metadata | Managed reference data for 5,854 counties, including their ISO 3166-2 codes and hierarchical relationships. | | Data quality rules | Documentation of 2,940 data quality rules, grouped into 11 rule features and 60 rule categories. | | Legal form metadata | Managed reference data for 3,731 legal forms with official and commonly used abbreviations and corresponding country. Legal forms with a similar purpose, beside country-specific aspects, are grouped by 86 legal form categories. | | Locality metadata | Managed reference data for localities (such as cities or towns) used for harmonization and standardization, including exonym terms in multiple languages. | | Post code metadata | Managed reference data for post codes used for validation, harmonization, and standardization of postal addressing. | | Postal delivery point metadata | Managed reference data for postal delivery points, such as Post Office Boxes, used for identification, extraction, harmonization and standardization. | | Region (administrative area) metadata | Managed reference data for 3,741 regions, including their ISO 3166-2 codes and hierarchical relationships. | | Registration authority metadata | Managed reference data for 1,277 registration authorities responsible for issuing and maintaining official business identifiers. | | Thoroughfare metadata | Managed reference data for thoroughfares of type STREET used for harmonization and standardization. |
|