CDL software development roadmap
|Display business rules changelog||Display business rules changelog||Any changes on business rules should be visibile in some kind of changelog report. It should consider: Bugfixes, new rules, changes on existing rules, updates on the documentation, updates on the criticality level.||Data validation||Delayed||2018-04-10||2018-03-04|
|Display managed administrative areas in the metadata repository||Administrative area documentation||We manage administrative areas per country (e.g. Rhineland-Palatinate in Germany) together with alternative names and different language variants. This data is used for providing a standardized translation. Currently this data is not visibile to CDL members. We will provide all adminsitrative area information in the CDL metadata repository.||Reference data||Delayed||2018-05-15||2018-03-05|
|Revise the management of multiple addresses||Revise the management of multiple addresses||According to the CDL Steering Committee decision (February 2018) only the legal address will be reviewed in future. Additionally address context information is to be managed using a distinct address tag. Below the most relevant requirements resulting from the decision are documented:
|Provide unified identifier validation interface||Enable validation of identifier data via a standard interface||Validation of identifiers should be enabled via a unified interface. The interface enables to select which depth of validation should be applied (qualification, standard, quick). Regarding qualification different data sources should be selectable. For more information about the service see:identifier validation service||Data validation||On track||2018-05-15||2018-05-15|
|Roadmap item CDL-5154||Cloud data quality dashboard||Within the CDL data validation app there should be a data quality dashboard that can be customized according to the requirements of an user. It enables filtering validation results by countries, attributes and/or specific rules. Different visualization options are provided.||Data validation||On track||2018-05-15||2018-05-15|
|Enable user authentication on app level||Revise user authentication||Organizational administrators should be enabled to define which user is allowed to use which app. Authorization shall be defined via the existing User Management App. The user management app is only accessible for defined admins per CDL member company. As of today user authorization is only available for the complete CDL web application including review management.||Collaboration||On track||2018-05-31||2018-05-31|
|Provide batch identifier data validation||Enable batch validation of identifier data||Identifier data validation should be enabled in a batch mode. This means that more than 1 business partners with identifiers can be validated via the standard identifier validation service||Data validation||On track||2018-05-31||2018-05-31|
|Roadmap item CDL-4305||Provide EIN validation||An Employer Identification Number (EIN) is used to identify a business entity in the US. The CDL API shall provide a service to validate such IDs. A REST service to validate EINs is provided by HIPAASpace.||Reference data||On track||2018-06-17||2018-06-17|
|Manage business partner classification based on NACE||Business partner classification||The Statistical Classification of Economic Activities in the European Community, commonly referred to as NACE (for the French term "nomenclature statistique des activités économiques dans la Communauté européenne"), is the industry standard classification system used in the European Union. The current version is revision 2 and was established by Regulation (EC) No 1893/2006.
We will include the possibility to classify business partners and organizational units in the CDL with respect to NACE and possible related classification taxonomies (e.g. NAF code in France). Wherever possible this information is gathered from external data sources such as the SIRENE database in France or the Belgium company register.
The data model will be extended to store at least the following Classification Codes:
|Roadmap item CDL-5180||Implement the Russian SME register as a CDL robot member||There is a register of Russian company data. The whole database is available as open data (https://www.nalog.ru/opendata/7707329152-rsmp/) This register should be treated as a CDL robot member like the Legal Entity Identifier and Numero SIREN data. This means the data is created in the CDL database and existing records are subject to updates by the Robot. Similarly to other robot integrations, there is a need for an initial matching against the database in order to enrich existing records and create the new records that are not yet available in the CDL.||Reference data||On track||2018-06-25||2018-06-25|
|Enable qualification of German VAT numbers against an official source||Enable qualification of German VAT numbers against an official source||Validation of German VAT numbers should be enabled via an official trusted source such as the Austrian tax authorities. The identifier validation service should enable the selection of this qualification data source explicitly.||Data validation||On track||2018-06-30||2018-06-30|
|Roadmap item CDL-4384||Use USPS services to curate US addresses||US Postal Services (USPS) provides a web service to validate US addresses . This service shall be used as primary source for enriching and standardizing US addresses.||Address curation||On track||2018-06-30||2018-06-30|
Download as Excel
Released features and improvements
|Enable data quality tasks for identifiers||Ensure correctness of identifier data||We need to assure the correctness of identifiers (i.e. VAT numbers and other kind of national (tax) identifiers: see the CDL identifier type list) in the CDL database. When there is no update for a certain period of time for a record it likely happens that the identifier is outdated.
|Roadmap item CDLD-237||Implement Washingtom company register (United States) as robot member||Washingtom company register data is integrated in the CDL database. See here||Reference data||2018-03-15|
|Improve the measurement of address curation accuracy||Adress curation accuracy indicator||The currently available curation level is dependent on the differences and similarities found in an input address compared to the resulting address. It should consider an additional score to indicate in a more informed way how "sure" the CDL app is that a provided address is correct (really existing, representing the requested address, belonging to a given business partner, etc.).
We will implement an accuracy logic based on
|Roadmap item CDL-4678||Enable fraud case attachments||Users shall be able to add documents (e.g. a fraudulent invoice, a fake email, etc.) to a fraud case in order to better explain the case. In addition, consent forms with the approval of a supplier to disclose certain information can be attached to a fraud case in this way. Multiple attachments shall be enabled per use case, and the user shall be able to decide about disclosure of particular attachments, i.e. disclose one attachment and hide another one.||Fraud protection||2018-02-26|
|Roadmap item CDL-5015||Extend taxnumber checksum validation||Extend the CDL checksum function library by providing checksum validation functions for tax numbers in Columbia, Russia, Mexico, and Chile.||Data validation||2018-02-26|
|Roadmap item CDL-5561||Provide real validation and fix proposals for legal names||Data validation||2018-02-26|
|Add additional cleaners for names in the matching app||Cleaning country or locality information in names||A standard cleaner for our Matching App should be provided. It removes country names from a field (i.e. the name fields such as name local, name international). The country name should be considered in different language variants.
Exemplary company names with country names included are:
Similarly a cleaner for locality information in the name is required. It should search for the given locality from the address in the name field.Both cleaners will be standard for the overlap matching in case of lookups and imports against the CDL database. Additionally they can be used and configured in the matching app.
|Roadmap item CDL-4875||Enable check digit calculation for Chinese Business Registration Number||Enable checking the Chinese Business Registration Number in Business Rules via simply calculating and comparing the given vs. the calculated check digit.||Data validation||2018-02-05|
|Roadmap item CDL-5690||Enable check digit calculation for Spanish NIF||Implement the check digit calculation of the Spanish NIF number according to this documentation: https://www.ordenacionjuego.es/en/calculo-digito-control||Data validation||2018-02-05|
|Roadmap item CDL-5177||Return lookup results from UK Companies House when not available in CDL database||When a UK record is not found in the CDL database, then a lookup via the UK Companies House API is performed. The data is transformed into the CDL data model so that a user could directly subscribe to this record. The data is then stored in the CDL database. For any newly created UK record, a lookup should be performed to assign the UK Company number. This number is necessary to provide regular updates from this data source.||Reference data||2018-02-04|
|Roadmap item CDLD-757||Inform organizations about blacklist cases for investigation||CDL regularly consolidates sanction list information from different sources and matches the list against the business partner repository. If a match is found, the affected CDL members are notified about those cases for investigation.||Reference data||2018-01-29|
|Roadmap item CDLD-160||Implement Swiss Zefix services as robot member||We are currently using the Swiss Zefix service for validating the existence of a Swiss UID. The Zefix services should be implemented as a robot member similarly to UK companies house and ABN (Australian Business Register). This means:
|Roadmap item CDL-5560||Provide real validation for identifier data||Based on the data managed in the CDL, the data validation app could provide fix proposals for data defects. This should be implemented for tax numbers in a first step and should then possibly extended afterwards regarding address data etc.||Data validation||2018-01-14|
|Roadmap item CDL-5435||Implement the Numero SIREN database as a CDL robot member||The SIREN number is assigned to companies in France in order to make them uniquely identifiable. The whole database is available as open data (https://www.data.gouv.fr/fr/datasets/base-sirene-des-entreprises-et-de-leurs-etablissements-siren-siret/). The SIREN database should be treated as a CDL robot member like the Legal Entity Identifier. This means the data is created in the CDL database and existing records are subject to updates by the Robot. Similarly to LEI, there is a need for an initial matching against the database in order to enrich existing records with the SIREN number and create the new records that are not yet available in the CDL.||Reference data||2018-01-09|
|Roadmap item CDL-5175||Enrich records in CDL database with UK Company number||UK Companies House provides a webservice API to retrieve information about companies registered in UK. All records in the CDL database should be enriched with the UK company number via a lookup of this API.||Reference data||2018-01-06|
|Roadmap item CDL-5156||Provide fix proposals for tax number data defects||Based on the data managed in the CDL, the data validation app could provide fix proposals for data defects. This should be implemented for tax numbers in a first step and should then possibly extended afterwards regarding address data etc.||Data validation||2017-12-22|
|Roadmap item CDL-5196||Provide fraud protection statistics.||For fraud protection, statistics shall provide an overview about the current overall and the current "own" status. The following KPIs and charts shall be provided:
|Roadmap item CDL-4675||Use name reference data to categorize individuals||The Corporate Data League has decided to exclude data about individuals (e.g. an individual doctor, lawyer, or craftsman) from cross-corporate data sharing. To enable CDL members to exclude those records from sharing and also to enable the CDL Team to identify those records in the CDL database, we need a services to categorize individuals records due to name attributes. For example, if a business partner name does not comprise a legal name, but a typical forename and surname for the given country, there is a high probability that this record represents not an organization but an individual. The categorization shall be integrated via data validation, i.e. if a record is validated (single record or batch), the category ||Data validation||2017-12-13|
|Roadmap item CDL-5176||Create regular updates from UK Companies House||The records in the CDL database that have a UK company number are regularly checked against the information the UK Companies House API provides. If there are changes available, then an update of the record is triggered.||Reference data||2017-11-01|
|Roadmap item CDL-6023||Handle default mappings for identifiers||SAP identifiers are mapped to CDL identifiers according to mapping rules which consider the SAP column and the associated country. For example, identifier value of ||Data model||2017-10-24|
|Roadmap item CDL-5181||Provide the Belgium company register in the data lake||The Belgium company register data is available as open data (https://kbopub.economie.fgov.be/kbo-open-data/kbo-open-data) The data needs to be downloaded, transformed and exposed via the API.||Reference data||2017-10-17|
|Roadmap item CDL-4642||Enrich existing CDL records with new reference data||Existing business partner records in the CDL database are enriched with data available from LEI, e.g. the LEI identifier, business register information (i.e. UID for CH, Handelsregister ID for DE, also including registered name), and trading names. Moreover, the additionally available addresses are imported and the legal address is specified based on the registered address type in LEI. If it is the first update by LEI and a review task is triggered for a CDL Member, the Reviewer needs to be made aware that this is a "Match Review" (i.e. Label in the App). A "Match Review" can only be accepted or rejected. Edit is not allowed.||Data validation||2017-09-29|
|Roadmap item CDL-4969||Conflate business partners||Business partners that are currently in the CDL database having the exact same name AND the exact same country AND no disagreement in identifiers should be conflated into one single business partner. Disagreement in identifieres means: * Business partners may have different identifiers which should be merged * But if they have the same, the value must be exactly the same All addresses are assigned to this business partner. These records are not real duplicates as they are the input from CDL members that have maintained differing legal addresses. After conflation, the lookup shall find only one record, also if the record has multiple matching addresses. This Epic also comprises not only development work, but also running the conflation. *Open:* switch subscription from conflated business partners to remaining business partner *Open:* Priorizite last updated business partners (clarify with Kai), start matching with bp's orders by last update des Open: Ensure that updates which come for a conflated business partner are "redirected" to the remaining (not deactivated) business partner (done by Michal) Open: Ensure "redirect" for BP/Addr read service (conflated record to remaining record (not needed from my perspective) Before we close this Epic, create follow-ups: Eigener Epic: Provide a report to read conflation-ID-mappings (conflated records to remaining record) Eigener Epic: Revise TaskCurator and process conflated tasks (wish: close tasks)||Collaborative processes||2017-09-29|
|Roadmap item CDL-5059||Identify blacklist matches and notify organizations||Periodically check CDL database against up-to-date blacklists and notify origanizations about matches.||Blacklist matching||2017-09-24|
|Roadmap item CDL-4676||Provide additional information by whitelist validation||At the moment, whitelist information provides an aggregated trust score and the five highest trust scores. Please add for each detail score the date of the last whitelist update by the particular organization. And please add the complete bank account data which is available (e.g. the national IDs might be interesting if the request was only performed via IBAN). And please inform about scores which are coming from the organization which requests the scores, to highlight them in the app.||Fraud protection||2017-07-17|
|Roadmap item CDL-5163||Provide filter for self reviews||Self-Reviews are generated when large data set updates are imported by CDL members. Self-Reviews ensure that each CDL member checks his date before review tasks are generated for other CDL members. Currently, in the Review App can not be distinguished between Self-Reviews and real Collaborative-Reviews. A filter is added to allow the user distingusih between those two review types.||Collaborative processes||2017-07-06|
|Roadmap item CDL-3164||Revise edit forms in Review App||Revise edit forms in Review App to better support editing Premises, Identifiers, Postal Delivery Points and Administrative Areas.||CDL Apps||2017-06-19|
|Roadmap item CDL-4532||Provide app for address curation||Addresses can only be curated via CDL API. This capability shall be also provided by CDL Apps, e.g. to curate a single address or an entire database.||Address curation||2017-06-19|
|Roadmap item CDL-4641||Provide LEI reference data by lookup||Legal Entitiy Identifier (LEI) reference data is a reliable and up-to-date information source for company names, legal addresses and some hierarchy information. This data shall be accessible via lookup services, i.e. a user shall be able to find LEI records (beside regular CDL records) when he/she uses the CDL lookup service.||Reference data||2017-06-19|
|Roadmap item CDL-4761||Enable Google Maps view of curated addresses in the address curation app||Show all curated records with pins on a Google Map or a Open Street Map view popup or separate tab. This should be triggered by clicking a button in the curation app, or in a separate tab.||CDL Apps||2017-06-19|
|Roadmap item CDL-4900||Enable checksum validation of tax numbers||For almost every VAT number there is a specific checksum algorithm. The algorithms need to be called from business rules in order to verify VAT numbers regarding formal correctness.||Data validation||2017-06-19|
|Roadmap item CDL-5002||Show links to business rule descriptions in the validation report||Each CDL business rule is described in the CDL metadata repository. The Excel-based validation report shows all violated rules. For each rule that is referenced there, a link to the corresponding rule description in the CDL metadata repository should be shown.||Data validation||2017-06-19|
|Roadmap item CDL-3808||Provide changelog report with provenance information||The changelog report provides an overview of all records (i.e. business partner and address data) which have been updated since a given point in time. For each updated record, provenance information is provided to inform about the changes (e.g. address curation or manual review by CDL Member). Such provenance information can also be used for filtering.||Collaborative processes||2017-06-05|
|Roadmap item CDL-4638||Enable unsubscribe in Review App||A user may receive a review task for a business partner, wich is no longer in scope of her/his organization due to e.g. a carve out or just discontinuation of a business relation. In such a case, the reviewer must be able to unsubscribe from the related business partner or to trigger re-assignment of the task to a reviewer from another organization.||CDL Apps||2017-06-05|
|Roadmap item CDL-4639||Enable lookup by country name in Browosing App||To lookup a business partner, it is required to know the ISO country code for the related country. This is inconvenient, the form shall provide auto-completion for country names as well. Only country names would be sufficient in select box.||CDL Apps||2017-06-05|
|Roadmap item CDL-4533||Enable whitelist validation in Fraud Protection App||The Fraud Protection App shall provide a form to validate a bank account against the CDL Whitelist.||Bank account whitelist||2017-05-08|
External managed business partner data
The timeline below displays external managed business partner data sources that are planned to be integrated.