It has been suggested that ACR could have some level of integration with LEI data. The following could be considered:
-
Finding an LEI. There are already web-based tools out there to look up an LEI based on a name. We could either simply provide a URL to (say) the GLEIF LEI site (https://www.gleif.org/en/lei/search) from ACR, or design our own search page that would access the GLEIF API.
-
Pulling LEI data records. For entities that already have an LEI in ACR, we could put in place a ‘pull’ mechanism that would query the LEI database (via their Rest API), fetching any relevant data (Name, Country, Direct parent, Ultimate Parent, etc.) for such entities and storing this in a ‘shadow record’ in ACR (like what we recently implemented in a dedicated ‘LEI’ section of the Customer Property Sheet).
-
Data Reconciliation. Once we have this ‘shadow record’, we could present ACR users with a reconciliation view of ACR data vs LEI data. The design is still open for discussion, but we could imagine a side-by-side view of the data, highlighting any material differences between the records.
-
Update ACR data. If the reconciliation process above identifies genuine errors in the ACR data, the user could then prompt the system to (selectively) update itself with the LEI data.
