Data Sharing Community Portal

Welcome to the Portal of the CDQ Data Sharing Community

The CDQ Data Sharing Community is a trusted network of user companies to manage business partner data collaboratively.

  CDQ data model       Support

Metadata and standards ·  Data quality rules ·  Data sources ·  Procedures

What's new? (RSS) Introducing the Activity Log App (13 May 2025) We’re excited to announce the launch of Activity Log, a powerful new application that delivers full visibility into every change made across your organization’s resources. Key Features: Comprehensive Change Tracking: Monitor all modifications to resources such as configurations, users, API keys, source management settings, storage, and more. Audit Details: See exactly when a change was made, who performed it, and what was altered—down to the specific fields and values. Advanced Filtering: Quickly pinpoint relevant entries by filtering on: Exact date or date range User identifier Workspace Specific resource (e.g., API key, storage bucket) Activity type (create, update, delete, etc.) Role-Based Access: The Activity Log app is visible and accessible only to users with the Bureaucrat role, ensuring sensitive audit data remains secure. Benefits: Enhanced Transparency: Instantly understand who’s doing what—and when—across your environment. Faster Troubleshooting: Isolate configuration mistakes or unauthorized changes in seconds. Improved Compliance & Security: Maintain a complete, tamper-evident record for audits and investigations. Activity Log is now available—log in to explore your organization’s change history! Data model A key prerequisite for collaborative data management is a shared understanding of the data being exchanged. Within the CDQ Data Sharing Community, this shared understanding is formalized through the CDQ Data Model. Its 303 concepts and the 3,925 mapped external concepts with 37,298 mapped terms are documented in this wiki, serving as a standardized business vocabulary. Data maintenance procedures A procedure is a common standard or "how-to" for a specific data management task. Within the CDQ Data Sharing Community, companies agree on such procedures to ensure similar rules and guidelines for similar tasks. For several countries, the CDQ Wiki provides such information, e.g. data quality rules, trusted information sources, legal forms, or tax numbers. Try CH (Switzerland), DE (Germany), PL (Poland), US (United States of America), or select another country from the list.

Data sources Active data sources Records BR.RF (data source) 65,565,621 CDQ.INTEL (data source) 53,424,836 FR.RC (data source) 41,615,326 US-CA.BER (data source) 8,790,794 GB-EAW.CR (data source) 8,727,512 US-FL.BER (data source) 6,276,945 JP.CR (data source) 5,629,300 AU.BR (data source) 4,816,780 ... further results The CDQ data sharing platform integrates 238 data sources with 3,925 concepts and 37,298 terms. All concepts and terms are mapped to the CDQ data model, e.g., 3,274 legal forms from LEI (data source) are mapped to 1,002 legal forms managed by CDQ. Metadata and standards: Metadata-driven data quality Data quality plays a pivotal role in ensuring compliance with legal, regulatory, and industry standards. One of the core challenges in achieving high data quality is adhering to dynamic data requirements that evolve due to changes in national regulations. These requirements vary by country, making it essential for businesses to track and update compliance criteria continuously. Metadata Description Administrative area metadata Managed reference data for administrative areas with language-specific terms and short names according to ISO 3166-2. Bank account metadata Managed reference data for bank accounts worldwide. Business identifier metadata Managed reference data for types of identifiers per country. CDQ data model Basic data concepts of CDQ Cloud Services. Compliance lists metadata Managed reference data about compliance lists considered in the sanction and watchlist screening services. Country metadata Managed reference data for countries with language-specific names and short names according to ISO 3166-2. Data quality rules Documentation of data quality rules with explanation and technical constraints to validate business partner data records. Legal form metadata Managed reference data for legal forms with official and commonly used abbreviations and corresponding country. Locality metadata Managed reference data for localities, such as exonyms. Post code metadata Managed reference data for post codes. Postal delivery point metadata Managed reference data for postal delivery points, such as Post Office Boxes used for identification, extraction, harmonization and standardization. Registration authority metadata Managed reference data for registration authorities of identifiers. Thoroughfare metadata Managed reference data for thoroughfares of type STREET used for harmonization and standardization. Data quality rules Transformation of human-documented data requirements into executable data quality rules is mostly a manual IT effort. Changing requirements cause IT efforts again and again. Some checks, e.g. tax number validity (not just format!), require external services. Other checks, e.g. validity of legal forms, require managed reference data (e.g. legal forms by country, plus abbreviations). Continuous data quality assurance (i.e. batch analyses) and real-time checks in workflows often use different rule sets. Data requirements and related reference data are collected and updated collaboratively by the Data Sharing Community. Data quality rules are derived from these requirements automatically. All data quality rules are executed behind 1 interface, in real-time. Batch jobs and single-record checks use the same rule set and can be integrated by APIs. For proving that a data quality rule is content-wise correct we maintain supporting document(s) per data quality rule which share the rule's source. This could be: a public authority source any other trustful webpage a data standard of a specific community member We manage the URL (if any), a screenshot of the relevant parts (if any) and the source's name (e.g. Community member data standard, European Commission, National ....) See Identifier format invalid (SIREN (France)) as an exemplary rule that was specified and implemented based on information provided by the OECD.