- 0] opencorporates @ OpenCorporates |ID to LE| mapping table Factsheet
opencorporates OQ 1. Introduction
OpenCorporates is the world’s foundational source for legal entity data and is on a mission to bring about genuine corporate transparency, and has been instrumental in opening access to corporate registries across Europe and North America, as well as being the largest open database of companies in the world, containing over 220 million companies and 300 million officers from 145 jurisdictions (as at early 2023). Its data is fully provenanced to official sources, unified according to a global schema, up-to- date and available at scale.
The Global Legal Entity Identifier Foundation (GLEIF) is a not-for-profit organization created to support the implementation and use of the Legal Entity Identifier (LEI). GLEIF manages a network of partners, the LEI Issuing Organizations, to provide trusted services and open, reliable data for unique legal entity identification worldwide.
The Legal Entity Identifier (LEI) is a 20-digit, alpha-numeric code based on the ISO 17442 standard developed by ISO. It connects to key reference information that enables clear and unique identification of legal entities participating in financial transactions.
Both datasets enable smarter, less costly and more reliable decisions about who to do business with. By providing a link between these two datasets, users gain access to a richer pool of information with which to make decisions and, in turn, cut costs, simplify and accelerate operations. In taking this step forward by publishing a publicly available OpenCorporates ID-to-LEI mapping reference file - individuals and organizations will be able to map LEIs to information compiled by OpenCorporates from local corporate registrations globally.
The mapping file is built upon a mapping process established in cooperation between GLEIF and OpenCorporates leveraging on OpenCorporates API. This file will be updated initially on a bi-weekly basis. The purpose of this factsheet is to describe the reference data involved, the analysis applied to map LEls to OpenCorporates IDs, and the ongoing update process.
- Reference Data
The OpenCorporates dataset is the source for the OpenCorporates ID and associated company data sourced from official company registers. Additional information on this data source including field definitions can be found here.
The GLEIF Concatenated File is the source for the LEIs and the legal entity reference data. Additional information on the GLEIF Concatenated Files and the Common
Data File formats can be found here. The OpenCorporates ID-to-LEI mapping table does not include historical OpenCorporates ID/LEI pairs, stand-alone unmapped OpenCorporates IDs and LEls, nor the listing of daily or monthly changes.
The following table describes the critical fields considered for mapping. Some additional pre-processing steps are in place considering specific local differences. Should you require further information please reach out to info@gleif.org.
Public Use
Author: GLEIF and OpenCorporates | Version: 1.1 | 2023-06-29 Page 2 of 6
-] opencorporates OQ Table 1 - Critical Fields Considered for Mapping i =< | S el Comments Registration Status LEls with Registration Status of ANNULLED or DUPLICATE are excluded EntityCategory LEls with EntityCategory FUND are excluded RegistrationAuthorityld LEls which use reserved Registration Authority codes RA888888 and RA999999 (GLEIF Registration Authorit code list) I o =l identifier alidationAuthorityEntitylD Company Identifier given by the | |RegistrationAuthorityEntityID |All available entity IDs of an Number Company register to LEI Record are used to he entity. Together alidationAuthorityEntitylD |establish a mapping pair. All with the Jurisdiction white spaces are removed Code OtherValidationAuthorityEnti jand jurisdiction-specific his forms a composite | tylD pre-processing of entity IDs primary key for a legal is applied where necessary entity urisdiction Code for the Legallurisidiction he Legallurisdiction Code jurisdiction (lowercase, element is transformed to underscore match the lowercase, ersion of ISO 3166-2 underscore code). List of version of the ISO 3166-2 jurisdiction code codes are available at https://api.opencorpor ates.com/jurisdictions 3. Analysis In April 2023, there were around 220 million companies in the OpenCorporates dataset with over 2.3 million LEIs having been issued. Of these 2.3 million, about 1.2 million have been automatically reconciled with a strict criterion applied with respect to registered jurisdiction, local company number. There are two main reasons why an LEI will not have an applicable OpenCorporates ID: Public Use Author: GLEIF and OpenCorporates | Version: 1.1 | 2023-06-29 Page 3 of 6
opencorporates @) 1. The LElis associated with legal form other than a company legal entity (e.g. mutual fund or government bond) 2. OpenCorporates does not yet include the register in the jurisdiction where the entity is registered. The technical approach to the mapping process will be subject to continuous review to improve the quality of the matching process. 4. On-going update process This section describes what changes (events) to the underlying datasets trigger update to the mapping discussed in the section above. Generally, an existing mapping pair is only updated if one of the following LEI data elements is changed: ® RegistrationAuthorityEntityld (RAEID) e ValidationAuthorityEntityld (VAEID), e OtherValidationAuthorityEntityld (OVAIED) Unmapped records will also be revisited on an adhoc basis based on updates to OpenCorporates coverage or on renewal if an OpenCorporates ID has not previously been mapped. Public Use Author: GLEIF and OpenCorporates | Version: 1.1 | 2023-06-29 Page 4 of 6
-] opencorporates @) Table 2: The change to an LEI (event) and the consequent update to the OpenCorporates/LEIl pair on the mapping file. [Evet |update In an OpenCorporates ID/LEI pair the LEI The mapping is removed from the mapping ANNULLED or DUPLICATE, the RAID or VAID file. changes to RA999999/RA888888, or EntityCategory changes to FUND. In an OpenCorporates ID/LEI pair the LEI became | The mapping is not removed from the In an OpenCorporates ID/LEI pair any of the If RAEID, VAEID or OVAEID of an LEI Record OpenCorporates ID or LEI data fields considered changes, the LEl is sent to through the as equivalent mapping (see Table 1) change. mapping process irrespective whether previously a mapping existed. If the updated set of entity IDs for an existing mapping cannot be matched with OpernCorporates anymore, the mapping pair is removed. If any of the OpenCorporates data fields is updated, the existing mappings are not updated. The only trigger to update existing mappings is currently by updating one of the entity ID elements in the LEl data If an LEI that was not mapped in the past is The LEl is sent through the mapping process renewed. again. Users of the OpenCorporates ID-to-LEI mapping reference file may ask general questions or challenge individual OpenCorporates ID/LEI pairs by emailing info@gleif.org. Public Use Author: GLEIF and OpenCorporates | Version: 1.1 | 2023-06-29 Page 5 of 6
opencorporates @) 5. File Specifications The file is published in comma-separated format (csv) contained in a zip file. It contains all identified OpenCorporates ID-LEI pairs, i.e. is a “full” file. No “delta” file is made available. The file does not contain OpenCorporates IDs that do not have corresponding LEIs nor LEIs without corresponding OpenCorporates IDs. The file contains the following data: OpenCorporates ID 136 alphanumberic IAlways present he OpenCorporates ID of the entity. jurisdiction_code “/” company number
- Resources The OpenCorporates ID-to-LEI mapping full file can be downloaded via https://www.gleif.org/en/lei- data/lei-mapping/download-oc-to-lei-relationship-files The GLEIF API can be accessed via https://api.gleif.org/ For every OpenCorporates ID-LEI pair, on the website, the LEI can be seen under the section titled “Additional Identifiers” using the following URL where YY is the jurisdiction code (YY_YY in case of subdivisions e.g. US_DE for Delaware), and XXXXXXX represents an arbitrary company number: www.opencorporates.com/companies/YY/XXXXXXX For users of the OpenCorporates API, the relevant call structure (before appending your API token) is: http://api.opencorporates.com/v0.4/companies/YY/XXXXXXX The API call will return the LEI within the “identifiers” section. If you receive OpenCorporates bulk data, please refer to your technical documents with respect to “Additional Identifiers”. Using GLEIF as an example the relevant URLs would be:
e https://opencorporates.com/companies/ch/1190521
e https://api.opencorporates.com/v0.4/companies/ch/1190521 For details on how to access the OpenCorporates data at-scale through API or Bulk data, please refer to: https://opencorporates.com/info/our-data/. Public Use Author: GLEIF and OpenCorporates | Version: 1.1 | 2023-06-29 Page 6 of 6