2023 releases

The 52 release notes published during 2023, newest first.

2023-12-22

To be sure the data in curation or validation monitors are always up-to-date CDQ provided a new feature in the data monitor settings – Validity Span. Thanks to this solution if there was no trigger for some selected period, the Business Partner will be reevaluated. It's very helpful for business partners for which the update monitoring is not enabled.

Available range: quarter, half year, year.

2023-12-18

The list of rules classified as MAJOR was extended with the following cases:

• Business partner name contains special keywords such as “in liquidation”, “in bankruptcy”, etc., - rules 99 and 100
• Business partner status – update proposals (add/modify) for statuses DISSOLVED, IN_LIQUIDATION, INSOLVENCY – rules 14 and 15

Additionally, rules 78, 79, and 88 are applied also for the Business Partner name of type VAT_REGISTERED.

Check all Update Classification rules.

2023-11-24

We are pleased to announce the integration of Orbis ID numbers within our Business Partner Lookup service.

Orbis ID, a unique 9-digit entity identifier assigned to companies in the Orbis database by Bureau van Dijk (BvD), is now fully supported by CDQ.

2023-11-23

We are pleased to announce a significant enhancement to our lookup service – the inclusion of CDQ/Business Partner/Identifier/FR RNA (National Register of Associations Identifier) numbers in records sourced from the France Register of Companies (FR.RC). This expansion enables users to access a comprehensive set of identifiers, including SIREN and SIRET, for French associations.

Key Features:

• RNA Integration: In addition to standard identifiers like SIREN and SIRET, our lookup service now incorporates RNA numbers, providing a more exhaustive view of associations registered in France.
• Enhanced Data Accuracy: The inclusion of RNA numbers enhances the accuracy and completeness of information available through our service, empowering users with a broader understanding of French entities.
• Seamless Integration: Users can seamlessly integrate RNA numbers into their workflows, making it easier to identify and verify information related to associations registered with the France Register of Companies.

How It Works:

Upon accessing records from the France Register of Companies, users will now find the RNA number alongside existing identifiers, offering a comprehensive profile of registered associations.

Why It Matters:

This update responds to the evolving needs of our users, providing a more thorough and nuanced dataset for those involved in research, compliance, and business intelligence.

We are committed to continuously enhancing our services to meet the diverse requirements of our users. The addition of RNA numbers reflects our dedication to delivering accurate, up-to-date, and comprehensive information.

2023-11-22

CDQ would like to present a new Augmentation configuration. The configuration contains 3 main parts:

• Data source settings - It’s possible to select which data sources (external or internal) should be used for lookup or updates. Thanks to this solution curation will use the same data sources as selected for lookup (in the past curation used all data sources turned on for the organization).
• Lookup – almost all settings from the BP lookup configuration were moved to this section. Data source selection was moved to the Data source settings. From features “source activation”
• Curation – all settings from the curation configuration were moved here.

Business Partner Fetch Configuration is not included in the augmentation configuration

The creation of new curation and lookup configurations will be blocked soon, but existing configurations can be edited and used as before. Augmentation configuration ID can be applied to curation or lookup API requests exactly the same way as lookup or curation configuration.

Curation monitors migration to augmentation monitor

All curation monitors will be migrated into augmentation. For each data source of the mirror, there is a new monitor with an assigned new augmentation configuration. A list of reference data sources available for curation and lookup was created based on the list of data sources enabled for the organization in the global settings.

Update Monitoring section of the Data Clinic APP was removed

All update monitors will be migrated into augmentation monitors for selected data sources of the mirror. In case the data source has a curation monitor and an update monitor we migrate them into one augmentation monitor. The update monitoring section on the configuration page of the Data Clinic was removed. To turn on update monitoring for business partners follow the steps:

• Create/change the augmentation configuration and choose on the data sources page which reference data sources should be monitors
• In the case of internal data source monitoring it’s required to provide an External Context Identifier type
• Create/edit augmentation monitor, assign the configuration and list of data sources for which would you like to receive updates

Curation/Lookup app settings

For curation and lookup single or batch app, we extended the settings option – to the list of lookup/curation configurations it’s possible to select augmentation as well.

First Time Right

Lookup, Address curation, and BP curation settings will be merged into one augmentation setting.

Subscription Management was moved to the Collaboration Configuration

From now Subscription settings are part of the Collaboration and Subscription Configuration. All settings inside stay without any change.

Action to do

• Check the new configuration
• Check migrated monitors
• Create new configuration if needed
• Change your integration – instead of lookup/curation configuration ID please use augmentation configuration if

Future changes

Once all customers change the integration and use augmentation configuration instead of lookup/curation the old types of configurations (lookup and curation) will be removed

Benefits from the new configuration

• Data source management for curation
• The same Golden Record for the Lookup and Curation
• Update and curation monitors can provide the same results
• Simplified configuration
• Easier to extend augmentation configuration with new features (prioritization of sources, country-dependent settings, etc.)

2023-11-02

We are pleased to announce that our services now offer comprehensive support for CDQ/Business Partner/Identifier/NZ GST (Goods and Services Tax) identifiers for business partners located in New Zealand.

This enhancement enables you to seamlessly incorporate GST data into your workflow, making it readily available for both lookup and curation services.

2023-10-30

We are excited to announce significant improvements to our Data Quality as a Service (DQaaS) products! In this release, we have introduced new data quality rules that focus on post code formats for various countries around the world. These enhancements will help you ensure the accuracy and consistency of postal code data for improved data management and analytics.

Enhancements by World Regions

• Latin America:

• Colombia: Added support for verifying Colombian postal code formats.

• Asia:

• Afghanistan: Enhanced capabilities to validate Afghan postal code formats.

• Cuba: Now supports checking Cuban postal code formats.

• Gibraltar: Added support for validating postal codes in Gibraltar.

• Africa:

• Ghana: Improved validation for Ghanaian postal code formats.

• Malawi: Now supports checking postal codes in Malawi.

• Mozambique: Enhanced capabilities for validating Mozambican postal code formats.

• Oceania:

• Kiribati: Added support for verifying postal code formats in Kiribati.

• Caribbean:

• Cayman Islands: Enhanced capabilities to validate postal code formats in the Cayman Islands.

• Montserrat: Now supports checking postal codes in Montserrat.

• Saint Martin: Added support for validating postal codes in Saint Martin.

• Southeast Asia:

• Laos: Enhanced capabilities for validating postal code formats in Laos.

• Myanmar: Now supports checking postal codes in Myanmar.

• Vietnam: Added support for verifying Vietnamese postal code formats.

• Central America:

• El Salvador: Enhanced validation for Salvadoran postal code formats.

• Trinidad and Tobago: Now supports checking postal codes in Trinidad and Tobago.

• South America:

• Peru: Improved validation for Peruvian postal code formats.

• North America:

• Saint Vincent and the Grenadines: Added support for verifying postal codes in Saint Vincent and the Grenadines.

• British Virgin Islands: Enhanced capabilities to validate postal code formats in the British Virgin Islands.

• Europe:

• Kosovo: Now supports checking postal codes in Kosovo.

These updates to our DQaaS products demonstrate our commitment to providing you with accurate and reliable data quality tools tailored to specific regions. By ensuring postal code accuracy, you can enhance your data analytics, customer experiences, and business operations.

For more information and to take advantage of these enhancements, please visit our platform or contact our support team. We look forward to helping you maintain data accuracy and integrity for your global operations.

2023-10-18

To the existing two types of quota control (CDQ and Client) we provided a new one – credential dependent. The max quota limit can be increased only if credentials are provided by the customer. In the case of using CDQ credentials, the max quota can’t be changed.

Currently, this type of quota control is applied to GOOGLE.PLACES and PL.NOBR

2023-10-17

We are excited to introduce significant improvements to our Data Quality as a Service (DQaaS) products, focused on enhancing the validation of business partner data in specific countries and corresponding business and tax identifiers. These enhancements are designed to elevate your data quality and compliance efforts for these targeted regions.

Key Updates

New Validation Rules for Targeted Countries and Identifiers

In this release, we have introduced specialized validation rules for business partner data in Kenya, Lithuania, and Algeria, along with specific identifiers:

• Personal Identification Numbers (PINs) in Kenya: You can now validate the format of both individual and business PINs in Kenya, ensuring adherence to precise standards.
• Business Registration Numbers in Lithuania: We have implemented comprehensive validation rules for Lithuanian Business Registration Numbers, covering various entity types and associated codes.
• Tax Registration Numbers (NIF) in Algeria: Our enhanced validation now includes the Numéro d'Identification Fiscale (NIF) in Algeria

Missing Data Identification

Our DQaaS products now feature rules to help you identify missing business partner data specifically in these countries. This proactive identification of data gaps empowers you to take corrective actions promptly.

Updated Documentation

Our documentation has been updated to provide detailed information about these new validation rules and targeted enhancements, enabling users to leverage these improvements effectively.

Reliability and Scalability

Our DQaaS platform continues to offer high reliability and scalability to support your data quality needs effectively, whether you are managing data locally or globally. These enhancements demonstrate our commitment to providing tailored solutions for specific regions and identifiers, allowing you to achieve data accuracy, compliance, and consistency where it matters most. We understand the importance of reliable business partner data in your operations and decision-making processes.

We hope that these updates empower you to streamline your data quality efforts, reduce errors, and enhance your overall data management capabilities for business partner data in Kenya, Lithuania, and Algeria. If you have any questions, require assistance, or wish to explore these new features further, please do not hesitate to reach out.

2023-10-17

We are happy to announce that we have released a completely new UI for the Single Sanction & Watchlist App.

We have introduced 2-pane experience (results on the left side of the screen and the details on the right side of the screen) that you may know from apps like First Time Right or BP Single Lookup.

With this new UI you can:

• Browse and compare results faster
• Search for entries without country (in the previous app we required also the country input)
• Assign a specific Sanction and watchlist configuration (that you can create in the Sanction and Watchlist Configurator App)

Please let us know if you have any questions or comments about the new look of this app.

2023-10-09

CDQ provides the possibility of testing our services with demo organizations. An account can be quickly created without any support from CDQ employees thanks to the integration with LinkedIn.

On the special landing page, there is a LinkedIn button. To create an account click on the button and then confirm your registration wish. The process required acceptance of terms and conditions. As a result of the registration, there is provided an API key, which can be applied to the SAP MDG service. This allows to use of “lookup“ and “lookup and enrich” features integrated into the SAP.

Demo account users can also use our APPs and search business partners stored in the CDQ.TEST data source by Single Lookup APP. Demo users have access to 3 applications:

• Business Partner Lookup
• API Key Management
• Content Pack Manager

2023-09-06

Few weeks ago we informed you about improvement of Data Quality Rules for Chinese legal forms. Now we are pleased to announce that the same improvement has been implemented for Japanese and South Korean legal forms as well.

What Changed?

Previously, when encountering Japanese and Korean characters, our data quality rule failed to recognize the legal form even when it was provided in the data. The issue was prettny much the same as for China - very often the business name and legal form is written together without any whitespace or separators, what caused the system incorrectly interpreted the entire string as the business name, leading to an INFO error (legal form missing).

The Solution

To resolve this, we have implemented a specific handling mechanism for Japanese and Korean characters within our data quality rule. The updated system now accounts for the common practice of combining the business name and legal form in Japan and South Korea, allowing it to accurately identify and differentiate between the two.

How it Works

With the new changes, our data quality rule will parse Japanese character strings in a more sophisticated manner. For example, consider the following Japanese business name and legal form written together:

• Business name and legal form: 株式会社星光商事 With the latest update, the system will now correctly identify the business name and legal form as follows:

• Business name: 星光商事

• Legal form: 株式会社

In case of Korean characters:

• Business name and legal form: 엘에스글로벌인코퍼레이티드주식회사 Which now will be correctly identified as:

• Business name: 엘에스글로벌인코퍼레이티드

• Legal form: 주식회사

Why It Matters

By accurately identifying the legal form, our data quality rule enables users to gain valuable insights and maintain the highest level of data accuracy and compliance. It ensures that the legal form is correctly recorded and processed, avoiding potential issues related to data interpretation and analysis.

2023-09-01

Bureau van Dijk (BvD) data source offers a wide range of information including f.e. financial risk and company ownership details. CDQ customers who have BvD products subscription, are now able to obtain these information via our Reference Data API Fetch Business Partner endpoint.

BvD data are grouped into, so called, "data packages":

• Master Data Basic
• Master Data Extended
• Financial Risk Data
• Ownership Data and each such a package consists of dozens of attributes.

To get these data in the fetch response, you just need to turn one of the following feature toggles in the fetch request on:

• ACTIVATE_MASTER_DATA_BASIC_BVD
• ACTIVATE_MASTER_DATA_EXTENDED_BVD
• ACTIVATE_FINANCIAL_RISK_DATA_BVD
• ACTIVATE_OWNERSHIP_DATA_BVD

Feature toggles can be used individually, but can also be combined.

The example fetch request payload might look like:

{ "cdqId": "BVD:DE7130197492", "featuresOn": [ "ACTIVATE_MASTER_DATA_BASIC_BVD", "ACTIVATE_OWNERSHIP_DATA_BVD" ] }

The data are then available in "rawRecordJson" object in the fetch response.

2023-08-29

Unique Taxpayer Reference Number (United Kingdom)

• Rule Description: This rule checks the format of the unique taxpayer reference number (UTR) in the United Kingdom. A company UTR is a unique 10-digit number issued by HM Revenue and Customs (HMRC) to all new limited companies for tax-related identification.
• Use Case: These numbers are essential for identifying companies for tax-related activities and compliance.
• Learn More: For further details, visit Identifier format invalid (Unique taxpayer reference number (United Kingdom)).

National Insurance Number (United Kingdom)

• Rule Description: This rule validates the format of the National Insurance number in the United Kingdom. The National Insurance number, often referred to as NI No or NINO, is crucial for the administration of the National Insurance or social security system and certain tax-related activities.
• Format: The National Insurance number format consists of two prefix letters, followed by six digits, and ending with one suffix letter which can be 'A', 'B', 'C', or 'D'. For example: AA123456C.
• Learn More: For more information, visit Identifier format invalid (NI number (United Kingdom)).

Bugfix

• UK VAT Number: e.g. GB345886022 was wrongly identified as "Invalid Format"
• Issue: The regular expression for validating the UK VAT number allowed only digits from 1-9 and not 0-9.
• Resolution: The regex has been updated to include '0' in the acceptable digit range, thereby fixing the issue of incorrectly identifying some valid VAT numbers like GB345886022 as invalid.
• Impact: This bugfix ensures accurate validation of UK VAT numbers, enhancing the integrity of tax-related data processing.
• Learn More: For more information, visit Identifier format invalid (VAT_registration_number_(United_Kingdom))

For any issues or further information, please consult the documentation or contact support.

2023-08-28

We have just deployed some improvements in the User Management App:

• Added a functionality to activate disabled users

• Added advanced filtering options: by user status (ACTICE, INACTIVE) and filtering by assigned role

• Added visual representation of assigned roles in the first view

The app itself should work faster as well.

2023-08-28

Sharing is one of the best ways to increase the quality of your data. Currently CDQ.POOL contains almost 2 million records from over 50 countries, which pass the quality gate. Thanks to Update Monitoring once any change appears for a shared business partner our service sends information about the update with special classifications.

During the sharing process sometimes business partner differs from candidates from the POOL and the decision about the linkage is needed to be provided in the Collaboration Self-Review APP. During this review, there are 3 possible decisions to make:

• no match – no similar candidates – shared BP is inserted into the POOL as a new record
• link record and send update – there is already the same BP in the POOL and will be updated with the data from the customer
• link record – the same BP found, the link is created but the BP in the POOL is not updated with the data from the customer (the quality of the BP in the POOL is better than from the customer Data Mirror)

In the last case - link record, thanks to this release we not only provide a linkage between BP in the POOL and in the customer mirror but also generate the update proposal for the customer (with the data from the POOL) to increase the quality of the data in the mirror.

2023-08-19

Today we announce an update to our data quality ruleset, designed to provide an even more accurate and reliable data quality profiling. This update introduces a new category for identifier checks that allows you to perform checks between tax/business identifiers and legal forms of companies, helping you ensure consistency and accuracy in your business partner data.

Feature Overview

In certain countries, tax or business identifiers contain valuable information about the legal form of the represented entity. This information can be encoded in the format of the identifier itself, often through the use of specific characters or patterns. Our enhanced data quality rule leverages this insight to detect any inconsistencies between the stated legal form of a company and the characteristics of its tax or business identifier.

Advanced Legal Form Identification

Identifying the legal form of a company based solely on its name can be challenging. However, we've overcome this challenge by curating an extensive database of over 1500 legal forms. This database is enriched with abbreviations, alternative names, and categorizations, allowing us to leverage machine learning techniques to accurately identify the legal form associated with a company's name. This innovative approach empowers our data quality rules to perform the newly introduced consistency checks.

Example: Spain

For instance, let's consider the case of Spain. In Spain, the first letter of the NIF (Número de Identificación Fiscal) number signifies the legal structure of the entity. With our new data quality rule, you can now easily cross-check the legal form provided in the business partner name against the first letter of the associated NIF number. If there's a discrepancy, the data quality rule engine will promptly identify it, allowing you to address the potential inaccuracies in your data.

How It Works

1. Input Data: Provide the legal form of the company (as available in the business partner name) and the associated tax or business identifier (e.g., NIF number) for analysis.
2. Automated Check: Our system automatically extracts the relevant information from the provided identifier, such as the first letter or specific characters.
3. Comparison: The system then compares the extracted identifier information with the legal form provided. If there's a mismatch or inconsistency, the rule triggers an alert.
4. Data Integrity: By catching potential mismatches between the stated legal form and the identifier, you can maintain data accuracy, reduce errors, and enhance the quality of your records.

Benefits

• Enhanced Data Accuracy: Avoid discrepancies between legal forms and identifiers that could lead to data quality issues.
• Time Savings: Automated checks reduce the need for manual validation and intervention.
• Regulatory Compliance: Ensure that your data adheres to country-specific regulations and conventions.
• Confidence in Decision-Making: Make informed decisions based on trustworthy and consistent data.

2023-08-08

With this release we provide an adapted response structure for the business partner validation. In detail we introduced the following changes:

• we report data defects from all rules that were successfully executed

• we provide the list of all data quality rules that were not successfully executed (rulesInError structure)

• we improved the calculation of a validation level by introducing the hierarchy (importance) of statuses: OK < INFO < WARNING < UNKNOWN < ERROR

• we introduced a data quality record status on the record level which is calculated according to the validation level. Data quality record status can have the following values: (i) NO_ISSUES_FOUND - means that we did not find any data defects; (ii) ISSUES_FOUND- means that we found at least one data defect; and (iii) UNKNOWN - means that we did not find ERROR issue but at least one data quality rule could not be executed

• we revised the error handling from VIES responses, respectively the messages provided by CDQ's reference data API

2023-08-07

We have released a completely new app - Sanction and Watchlist Configurator. In this app you will be able to create a custom Sanction and Watchlist configuration.

This configuration will enable you to define the bundle of Sanction lists, Watchlists and PEP lists relevant to you.

You can use the newly created configuration by assigning it to your API Key in the API Key Management app. It will be the base for the screening via the chosen API-key via our APIs.

Why is this beneficial?

Using a dedicated configuration of selected Sanction lists, Watchlists and PEP lists enables the user to devide into several approaches. From practical experience, it is known that it is necessary to generate different risk approaches, which can now be implemented by the configuration. A high Risk, Mid Risk and Low Risk Screening can now be realized with generating 3 different types of configurations. Furthermore, limiting the lists to be screened results in fewer hits that are not relevant because they are listed on other lists.

Implications

• Faster analyzation of less screening results due to specified lists.

• There are only hits from lists, included in the configuration.

• Quicker screening process due to less lists to be screened

Need for Action

• Build up your configurations in the WebApps

• Configuration is then available via your API Key and for all solutions, using the CDQ Compliance API.

Coming soon:

Use of this configuration inside the upcoming new Screening app in our Apps.

2023-08-02

For business partners from Great Britain is possible now to get updates from the UK.VAT. This reference data source is monitored against changes for business partners every day at 3 a.m.

2023-08-01

With this update on the data quality rules comprehensive format checks for all Brazilian State Tax Numbers were introduced. This enhancement ensures that all state-specific tax numbers are accurate, valid, and compliant with the specific format requirements mandated by the respective Brazilian state tax authorities.

Key Features:

• Complete Coverage: Our data validation capability now supports format checks for all state-specific tax numbers, covering each Brazilian state and ensuring adherence to the unique rules and regulations of each jurisdiction.
• Validation of Tax Number Structure: With this update, the rules engine will automatically validate the structure of state tax numbers, ensuring they meet the required length and format.
• Verification of Check Digits: The rule engine verifies the validity of the check digits within each tax number, confirming that they meet the required algorithm for authenticity.
• Improved Data Accuracy: By implementing format checks, we significantly reduce the likelihood of erroneous or outdated tax numbers being processed, leading to more accurate and reliable data.
• Compliance with State Tax Laws: Our format checks are designed in accordance with the latest guidelines set by the respective Brazilian state tax authorities, ensuring that businesses and individuals stay compliant with the regulatory requirements.

2023-07-25

We are pleased to introduce a set of new data quality rules aimed at enhancing the accuracy and completeness of your address data. These rules have been thoughtfully implemented to ensure data integrity and consistency, providing significant benefits to our users.

What Changed?

In response to our commitment to data quality and compliance, we have introduced new data quality rules. This release comes also as a response to the implementation of the Import Control System (ICS2), a customs pre-arrival security and safety program by the European Union, effective March 1. The ICS2 program mandates comprehensive pre-arrival security filings for all air cargo destined to or transiting through the European Union, Switzerland, or Norway. To comply with the program's requirements and avoid delays, precise and reliable address information, including correct post codes, has become essential for all shippers and supply chain actors.

The Solution

Under the newly introduced data quality rules, we now require the inclusion of post codes for street addresses in select countries. This ensures that address details are more robust and reliable. Additionally, we have implemented a postal code format validation rule for Ireland, specifically tailored to the Eircode system, guaranteeing accurate and reliable address data for the country. Furthermore, we have introduced a validation rule for South Korean postal codes to ensure precise and consistent address data for locations in South Korea.

How it works

Mandatory Post Code for Street Addresses: To bolster the comprehensiveness of address information, we now require the inclusion of post codes for street addresses in select countries. This ensures that address details are more robust and reliable for the following countries:

• Afghanistan (AF)
• Saint Barthélemy (BL)
• Bermuda (BM)
• Colombia (CO)
• Micronesia (FM)
• Guernsey (GG)
• Ghana (GH)
• Gibraltar (GI)
• Greenland (GL)
• Guadeloupe (GP)
• South Georgia and the South Sandwich Islands (GS)
• Guam (GU)
• British Indian Ocean Territory (IO)
• Jersey (JE)
• Kiribati (KI)
• Cayman Islands (KY)
• Saint Martin (MF)
• Northern Mariana Islands (MP)
• Martinique (MQ)
• Malawi (MW)
• Mozambique (MZ)
• Namibia (NA)
• New Caledonia (NC)
• Saint Pierre and Miquelon (PM)
• Réunion (RE)
• Sudan (SD)
• Svalbard and Jan Mayen (SJ)
• Eswatini (SZ)
• Trinidad and Tobago (TT)
• Virgin Islands (VG)
• Vietnam (VN)
• Wallis and Futuna (WF)

Postal Code Format Validation (Eircode - Ireland): For Ireland, we have introduced a postal code format validation rule specifically tailored to the Eircode system. The validation ensures that all Eircode postal codes adhere to the correct format, including a three-character "routing key" starting with an uppercase letter followed by two numeric digits. The second part consists of a space followed by four characters, which can be either uppercase letters or numeric digits. This validation guarantees accurate and reliable address data for Ireland, supporting compliance with various regulatory programs.

Validation Rule for South Korean Postal Codes: We have implemented a validation rule for South Korean postal codes, ensuring that all postal codes used for South Korean addresses adhere to the correct format. This validation promotes precise and consistent address data for locations in South Korea.

Identifying Non-Existing Routing Key in Irish Post Codes: In Ireland, users can now identify non-existing routing keys within a given Irish post code. This essential rule assists users in detecting potentially incorrect or invalid routing keys, ultimately improving the accuracy of address data in Ireland.

Why It Matters?

Ensuring correct post codes and precise address data offers significant business benefits. Accurate address information facilitates efficient deliveries, optimized logistics, and enhanced customer satisfaction. Compliance with various regulations, including the Import Control System (ICS2) program by the European Union, is just one example of how these rules provide value. By adhering to these data quality rules, our users can ensure that their cargo shipments meet regulatory requirements and smoothly proceed through customs without delays. Additionally, accurate address data enables businesses to gain valuable insights into customer demographics and regional trends, enhancing data analytics capabilities.

2023-07-22

What Changed?

In this latest release, we have expanded our data quality and validation platform to support a wide range of new business identifiers in multiple countries. We have introduced unique identifiers from Pakistan, Japan, Malaysia, India, and Panama, empowering businesses with enhanced data accuracy and validation capabilities.

The Solution

Our platform now includes support for the following newly added business identifiers:

Pakistan

• Computerized National Identity Card (CNIC): The unique national identity card used in Pakistan for identification purposes.
• National Tax Number (NTN): The tax identification number assigned to businesses in Pakistan.

Japan

• Japanese Consumption Tax (JCT) VAT Registration Number: The value-added tax registration number used for businesses in Japan.

Malaysia

• Service Tax Registration Number: The registration number for businesses required to collect and remit service tax in Malaysia.

India

• UDYAM: The registration number provided to small and medium-sized enterprises (SMEs) in India under the UDYAM registration process.

Panama

• Tax Registration Number (Registro Único de Contribuyente): The unique tax registration number assigned to businesses in Panama.

How It Works

Our platform now seamlessly integrates with these new business identifiers', allowing real-time validation and verification of business information. Users can easily access and validate the accuracy of these identifiers to improve data quality and streamline business processes.

Why It Matters

With this expanded support for global business identifiers, our users can:

• Ensure accurate and error-free data entry: Our platform validates business identifiers in real-time, reducing data entry errors and improving overall data accuracy.
• Facilitate compliance and reporting: Businesses can ensure compliance with local tax regulations by validating and verifying tax identification numbers promptly.
• Enhance customer address validation: With precise identification numbers, businesses can optimize customer address verification, leading to improved delivery and customer satisfaction.
• Streamline business operations: Validating business identifiers streamlines various processes, including tax reporting, invoicing, and financial transactions, saving time and resources.

The addition of these new business identifiers marks a significant step forward in our commitment to providing the most comprehensive and accurate data quality and validation solutions. We believe this update will empower businesses to make better-informed decisions and unlock valuable global business insights.

2023-07-21

We are pleased to announce an update to our data quality rule, aimed at enhancing the identification of legal forms in Chinese characters. In previous versions, the data quality rule did not properly identify the legal form, despite being provided. With this release, we have implemented changes to address this issue, ensuring more accurate and reliable results.

What Changed?

Previously, when encountering Chinese characters, our data quality rule failed to recognize the legal form even when it was provided in the data. This was due to the common practice in Chinese of writing the business name and legal form together without any whitespace or separators. As a result, the system would incorrectly interpret the entire string as the business name, leading to an INFO error.

The Solution

To resolve this, we have implemented a specific handling mechanism for Chinese characters within our data quality rule. The updated system now accounts for the common practice of combining the business name and legal form in Chinese, allowing it to accurately identify and differentiate between the two.

How it Works

With the new changes, our data quality rule will parse Chinese character strings in a more sophisticated manner. For example, consider the following Chinese business name and legal form written together:

• Business name and legal form: 斯凯孚（上海）汽车技术有限公司

• With the latest update, the system will now correctly identify the business name and legal form as follows:

• Business name: 斯凯孚（上海）汽车技术有限公司

• Legal form: 有限公司 This improvement will lead to more accurate and informative data validation results for Chinese character inputs.

Why It Matters

By accurately identifying the legal form, our data quality rule enables users to gain valuable insights and maintain the highest level of data accuracy and compliance. It ensures that the legal form is correctly recorded and processed, avoiding potential issues related to data interpretation and analysis.

2023-07-20

To keep the high level of data quality for the same business partners in different sources we provided the possibility of monitoring data sources of the same data mirror by other data sources.

External context identifiers

Providing updates for the same business partners is based on the special linkage, enabled thanks to the extension of our data model with External Context identifiers. These special identifiers can be defined by customers in the format KEY: VALUE. Business partners need to have the same key and value to create a linkage.

Updates are provided immediately once we detect any differences between business partners (seed updates) or when the business partner was changed by the customer. In the case of many BP with the same key: value, all business partners with this combination will be subscribed. Changing the key or the value cause a reevaluation of the linkage.

How to turn on the monitoring?

• Update your mapping with an external concept identifier type and value or provide additional data for it
• Go to the Data Clinic – Update Monitoring section (or use API)
• Choose the data source for which you would like to get updates
• Choose data sources from your mirror you would like to subscribe
• Provide External Concept identifier type which will use for a linkage
• Check the BP Update Browser APP to see updates from your data sources

2023-07-12

We have extended a list of jobs that can be canceled with the API and APPs. The current list contains the following jobs:

• Curation jobs
• Batch lookup job
• Import job
• Decision jobs
• Validation jobs
• Transformation jobs
• Risk and compliance jobs
• Batch whitelist job
• Batch Bank Trust Score Check
• Import job for bank accounts
• Statistics jobs
• Sanction fetch job
• Screening job
• Report jobs
• Duplicate job
• linkage jobs

Jobs can be deleted

All failed or canceled jobs can be from now also deleted.

2023-07-11

Referencedata Fetch Business Partner endpoint allows to use different feature toggles or setting the Screening Matching Threshold. They can be switch on/off directly in the request, but since now these settings can be managed also by fetch configurations.

There is a dedicated set of configuration endpoints available, which allow to:

• create
• read
• update
• delete business partner fetch configurations. For more details visit Developer Portal page.

To make configuration management more comfortable, we have also implemented a dedicated application Business Partner Fetch Configurator

2023-06-12

To enable filtering business partners by important changes we extended Business Partner Augmented endpoint with Metadata and summary Results.

Summary results

Informs what was changed for selected concepts of the business partner. There are separated parameters for creation (added) and modification of the concepts. When something was added or modified and the response for the parameter is true – we can check for which concept something was detected.

For example, parameter registeredAddressCreated = True – informs the augmented business partner of contains the proposition of adding some address concepts (locality, thoroughfare, post code) for the address of type registered. To check what exactly was added we can use the second parameter – registeredAddressConceptsUpdated, which provides a list of all added or modified concepts for registered addresses.

For identifiers, we provided two separated lists of identifier types – one for modified (identifierTypeTechnicalKeysUpdated) and the second for added (identifierTypeTechnicalKeysCreated)

A list of all concepts with filtering options is provided in the Query Parameters of the Read a Page of Augmented Business Partner endpoint.

Metadata

Filtering is possible by such basic information as external id, country, business partner type, but also by :

• executedAt (when the generation of the augmented record was performed),
• overall classification of BP (REJECTED -> MAJOR -> MINOR -> TRIVIAL),
• trigger type (created, updated, REFERENCE_DATA_CHANGED..)
• trigger provenance (data sources that triggered the generation of a new version of the business partner).

Thanks to this improvement we can easier create a list of business partners, for which real important data was updated.

2023-06-12

Business Partner Lookup configurations CRUD endpoints are now available to use. For more details please check our Developer Portal

As an API user, you can now:

• create
• read
• update
• delete business partner lookup configurations.

2023-06-02

New change types

Two new change types (confirmed, not changed) have been added to the existing ones (added, modified, deleted). If an update receives the change type “confirmed” it means that the original value was confirmed by the reference data source. “Not changed” means that the given value was not changed because no data from a reference data source could be found.

New classification types

A new version of update classification brings new rules which can classify updates as trivial, rejected (both already mentioned in the previous release note about update classification), or unmodified.

• Trivial – very low-level change with no implication for your business partner – f.e. difference in legal form due to permutation
• Rejected – update breaks some quality rules so it should not be consumed
• Unmodified – this classification is used for not changed or confirmed updates

Classification type hierarchy

Sometimes multiple rules can touch the same concept of the business partner. To avoid misunderstanding there are two main rules:

• If an update is classified by more than one rule, the highest classification level is returned: REJECTED > MAJOR > MINOR > TRIVIAL
• Rules of type GENERAL are only used for classification if no specific rule is applied

All rules are available here: Update classification

Business value

Automatic updates reduce data maintenance costs and mitigate the risk of process failures due to outdated data.

Implications

Change types allow for quick analysis of the provided updates. Also, the information that nothing has changed but the current data has been confirmed is valuable.

Need for action

Make use of the update classifications to filter only for relevant updates and use the change types to determine the necessary actions according to your data governance rules.

2023-05-30

In order to make consuming business partner lookup results list more readable and user friendly, we did an improvement in sorting the results.

It happens that the lookup service responses with a bunch of records with the same matching score and a part of business partners have status inactive. Till now the status of business partners had no influence on the order of results list.

Our last improvement changes that and now - in case of exactly the same matching score - active business parters are listed first, then the business partners without explicitly status provided (however we assume, that the status is "active" in such cases) and finally - business partners with status "inactive".

2023-05-25

We have added a possibility of assigning workspace types (either Production or Sandbox) to your workspaces. These new labels should help you to make a clear distinction between the production and sandbox workspaces.

Additional information:

• You can assign type while you create a new workspace (Global Settings App -> Create workspace).
• You can assign type while editing existing workspace (Global Settings App -> Edit workspace).
• You can have multiple “production” workspaces.
• You can have multiple “sandbox” workspaces.

2023-05-08

Currently it’s possible to create Sanction and Watchlist configurations via the API.

Therefore we have added a possibility of assigning previously created Sanction and Watchlist configuration to API keys via the API Key Management App.

You can find this feature in the “Edit” modal in the API Key Management App.

2023-05-05

Until now, curation configurations could only be managed from Data Curation Configurator app level.

Today we share with our users a dedicated set of endpoints, which allow to manage configurations also via the API.

As an API user, you can now:

• create
• read
• update
• delete curation configurations using endpoints documented on our Developer Portal.

2023-04-24

Augmented Business Partners endpoints were enriched with two new featuresOn:

• SHOW_ORIGINAL_BUSINESS_PARTNER  – retrieves original business partner record used for generation of augmented record. It’s important to understand the BPs provided in this endpoint may temporarily differ from the current BPs in the mirror. The reason is the time between the modification of BP by the customer and finishing the curation monitor triggered by this update.  This feature returns BPs used as an input value for the last triggered curation monitor, so if we change the original BPs in our mirror, it will cause the generation of new BPs. For big storages, where the generation of new augmented records may last longer than usual this difference can appear.
• FETCH_RAW_UPDATES – provides updates from reference data sources. In the previous version, this feature was turned on by default, now it’s optional.

Implications

In the past the original Business Partner as well as the raw updates have been returned by default. In many cases this led to very large response sizes without additional value.

Need for action

If you currently use the original Business Partner or raw updates from the response, you need to activate these features in your request to receive the same response as until now.

2023-04-20

We are happy to inform you, that from now on update monitoring for 7 new data sources can be activated. List of new data sources:

• DK.CR - linkage possible with: CDQ/Business Partner/Identifier/CVR DK
• NZ.CR - linkage possible with: CDQ/Business Partner/Identifier/NZ BN
• AT.CR - linkage possible with: CDQ/Business Partner/Identifier/BR ID AT
• CZ.REE - linkage possible with: CDQ/Business Partner/Identifier/CZ ICO
• NO.RBE - linkage possible with: CDQ/Business Partner/Identifier/NO ORGID
• EE.CR - linkage possible with: CDQ/Business Partner/Identifier/EE BRN
• IL.CR - linkage possible with: CDQ/Business Partner/Identifier/IL VAT

Additionally, due to the newly introduced automation, new data sources will be available for update monitoring much faster in the future.

Business value

Avoid process errors: Receive updates before they affect you (e.g. wrong deliveries, rejected invoices, transferred money to insolvent business partners).

Implications

Make sure to provide the required identifier (and map it correctly) in order for the update monitoring to work.

Need for action

Activate the monitoring for the new data sources in the Data Clinic.

2023-04-06

Another new app available for you.

This time we have completely redesigned the First Time Right App. The new, fresh look brings also new functionalities to the app:

• New, 2-pane look (lookup results on the left, details of the business partner on the right). makes it easier to browse Business Partner Lookup results.

• The same 2-pane approach was applied to Screening results.

• “Transfer values to search mask” button now also transfers the “Issuing body” field for the Business Registration Number (DE) - DE_BNUM identifier.

• We have added a “Clear search mask” button - you can clear the whole form with one click.

• Another new thing is the “Generate GR” button that can generate the Golden Record for any Business Partner.

• Last but not least, we have reworked the “Request settings” modal. Now you can easily navigate between Lookup/Validation/Curation settings and we have added respective links for the API documentation.

2023-04-05

We are happy to announce that we have just released a new app called Content Pack Manager.

This app allows you to download CDQ metadata for tax categories, and identifications in template formats that you can directly import into your SAP applications, such as S/4HANA or SAP MDG, cloud edition.

You can find the app in the Utility Apps section.

2023-03-31

The business partner data returned by the Lookup service contains information about the address type of the given business partner.

From now on, this information is displayed in the Single BP Lookup application. Thanks to this, you will know at a glance whether a given address is of the "Registered", "VAT Registered", "Headquarter" or other type.

2023-03-31

"Family Roles Played" information are now displayed in D&B records, right under "Hierarchy information".

2023-03-14

Sharing Scope further extended (two additional countries)!

TN: A new country from Africa was added to the sharing scope – Tunisia. To create a linkage and share data to the POOL business partners need to have CDQ/Business Partner/Identifier/TN TVA.

BO: Bolivia was to the sharing scope as well. To create a linkage and share data to the POOL business partners need to have CDQ/Business Partner/Identifier/BO NIT

Linkage with multiple identifiers enabled for new countries!

Possible of linkage with more than one identifier was added to following countries:

• Sweden – linkage possible with: CDQ/Business Partner/Identifier/SE ORG ID and CDQ/Business Partner/Identifier/EU VAT ID SE
• Estonia  - linkage possible with: CDQ/Business Partner/Identifier/EE BRN and CDQ/Business Partner/Identifier/EU VAT ID EE
• Finland - linkage possible with: CDQ/Business Partner/Identifier/BIC FI and CDQ/Business Partner/Identifier/EU VAT ID FI
• Russia - linkage possible with: CDQ/Business Partner/Identifier/RU KPP and CDQ/Business Partner/Identifier/RU INN

Business Value

DQ Improvement: For countries with no other available external data source the CDQ Sharing Pool can provide a source of data quality improvements.

Time-efficient: by getting all updates for the records set under monitoring for a specified time period and for given attributes.

2023-03-06

There is a new feature toggle in Data Curation API - CAPITALIZE_ADDRESS - which can be used once address values in curation result are needed to be converted to upper case.

This feature can be used of course both in API request and in the Single Business Partner / Address Curation Apps.

2023-03-06

We have added 30 active identifier DQ rules and 30 rules in the IDEA status.

The identifiers have been added for the following countries:

• Tunisia
• Morocco
• Egypt
• Turkey
• Bolivia

The corresponding identifier DQ rules were created and activated for identifiers in these countries. The rules cover:

• Identifier format
• Identifier schema
• Identifier missing
• Identifier unknown (currently DQ rules are in IDEA status)

For Venezuela the RIF identifier was enhanced with the corresponding DQ rules:

• Identifier format inaccurate (RIF number (Venezuela))
• Identifier format invalid (RIF number (Venezuela))
• Identifier missing (RIF number (Venezuela))
• Identifier unknown (RIF number (Venezuela)) (in IDEA status)

2023-03-03

Qualification report helps the user to check the consistency between the identifier and business partner (BP) details and is frequently used for compliance/audit purposes. To support the main objective of the report, we have recently introduced two new features:

1. Request id: during the process of qualifying the BP, qualification service uses external reference data (e.g. VIES). Such external reference data issue a request id proving the execution of request. In compliance/audit processes this information might be used to have an evidence on the way of checking the BP details.
2. Violation message: Before the qualification process starts, it conducts several data quality checks on the submitted identifier to reduce unnecessary calls on external reference data. If an identifier fails in any of the rule category, the user can newly track down the reason for failure and take adequate actions, if required.

The feature (1) is available for both qualification profiles (profile: QUALIFICATION and profile:EU_VAT_QUALIFICATION), while the feature (2) is available for profile:EU_VAT_QUALIFICATION only.

2023-03-03

Not every update from a reference data source is relevant. Therefore CDQ classifies updates into the following categories based on certain event types:

• MAJOR --> you should follow up on this, e.g. status changed from “active” to “inactive”
• MINOR --> you could follow up on this, e.g. house number has changed
• TRIVIAL --> no need for action, e.g. casing of name has changed
• REJECT --> no need for action, e.g. an update violates a validation rule

Previously the classification was based on simple string comparison – if the similarity score between old and new data was higher than 0.9 then an update was classified as MINOR; in other cases, the update was classified as MAJOR.

The same improvement was applied for curation, where all changes by default were classified as MAJOR. Currently, curation uses the same mechanism as for updates.

For details about the classification rules, see Update Classification

Business value

Time-saving: By only creating change workflows for relevant updates you can save resources required to validate and approve those change requests.

Avoid process errors:  Curate data defects before they affect you (e.g. wrong deliveries, rejected invoices, transferred money to insolvent business partners)

Implications

When loading updates you should distinguish between different update classifications in order to maximize the ratio between effort and positive impact.

Need for action

Use the classifications in update reports and integrations.

2023-03-02

From now on you can assign a type to each business partner. The business partner type specifies if the business partner is a legal entity, an organizational unit, an address, etc. (please see Business Partners types for more details). It determines the business context a business partner is involved in. Such categorization will help you manage your business partner data in general and CDQ data sharing specifically, as matching between records can now include business partner type.

;Business Value :Accuracy: by assigning types to each business partner the matching process between sharing members improves in its accuracy. Legal entities can be matches with legal entities, subsidiaries can be matched with subsidiaries. Cross matches can be avoided.

;Implications :When sharing data, please provide the business partner type.

;Need for action :Please reach out to your customer success manager and align how the business partner type information can be added to the sharing process and/or how it can be mapped automatically.

2023-02-03

The EORI system is established in order to facilitate the registration of economic operators and people wishing to trade.

An EORI number means an identification number, unique in the customs territory of the European Union and Great Britain, assigned by a customs authority to an economic operator or to another person in order to register that person for customs purposes.

Since now the EORI is supported by our Reference Data API and Business Partner Lookup services and app.

EORI has been integrated to our services as two external data sources:

• EU.EORI covering European Union countries
• UK.EORI dedicated to business partners from Great Britain and Northern Ireland

2023-01-25

We are happy to announce that we have just released a completely redesigned Single Lookup App (aka “Business Partner Lookup V2). This app allows browsing details about a particular business partner and enables searching for matches in the CDQ Data Pool for a single business partner record.

**Highlights of the new app: **

--> New view (2-pane view) makes it easier (you need less clicks) to jump between particular Business Partner records.

--> "Reset filters" button - clears all of the fields from the top form.

--> "Generate GR" button - it appears when you hover the mouse over a search result on the left side. You can generate a Golden Record from a selected Business Partner.

Let us know what you think about the new app - any feedback appreciated!

2023-01-25

Florida Business Entity Register data source has been unavailable for some time due to integration issues.

Those has been fixed latelty and thanks to that additional over 450k records are available on the data pool.

2023-01-20

We have added a search field for the quota management window in the Data Source Management table (“Global Settings” app). It should be easier now to find a particular workspace for organizations with many workspaces.

2023-01-20

The new button allows you to add all displayed users to the selected notification with one click. You no longer need to manually add each and every user.

2023-01-11

Configurations for a distinct workspace for business partner validation (Data Quality Checks) can be read, created and updated, and deleted via dedicated API. Data Validation API provides now CRUD endpoints for configurations on the workspace level.

Users now can:

• create, read, update and delete a configuration within a particular workspace,

• read all configurations for a particular workspace.

Everything now can be executed using a dedicated set of endpoints that can be browsed here.

Usage Examples:

• Transfer Configuration through Workspaces: You can adapt your validation rules in a test environment and try them out there. Through the endpoint, you can easily and quickly transfer your configuration details into a productive configuration.
• Get all available Validation Configurations with considering the Workspace information
• Open a specific configuration to read out the respective details from the configuration and make adjustments. this procedure makes sense if the validation rules are managed centrally in the company.

Further possible Extensions are documented here: https://ideas.cdq.ch/ideas/IPOC-I-340