As with the previous release of Sprint 48 at the end of 2022, Sprint 49 & 50 sees the majority of new development work happening under the hood in readiness for changes we plan to release throughout 2023. For example we’ve integrated some enhanced address handling APIs which will help us achieve a better percentage of automation (i.e. where address parsing was not previously available to correct edge cases). Unfortunately during the analysis stage, we spotted an error in our current address logic. We’d highlighted both Region Code and Post Code as ‘Optional’ in our front end GUI/internal workflow logic whereas they should have been moved to mandatory. Optional is correct for the schema which needs to cater for countries which do not support postal codes, but incorrect for those that do. You can see this in the GLEIF State Transition Rules (Page 32) GLEIF State Transition Rules (Version 2.6)
“All addresses reported SHALL be complete and include the following mandatory elements:
• FirstAddressLine SHALL include the first line describing the address. Up to three additional lines MAY be included.
• City SHALL be the name of the city in local language and alphabet.
• PostalCode SHALL be the postal code in the format specified by the local postal service. For countries that do not use postal codes in addresses, this optional element SHALL NOT be provided.
• Region SHALL be the ISO 3166-2 region code of the address. For countries that do not have region codes, this optional element SHALL NOT be provided.
• Country SHALL be the ISO 3166-1 country code of the address”
We’ll modify the GUI interface and backend system logic in Sprint 51. In the mean time, please ensure Region Codes and Post Codes are added to all new orders and renewals, and your own workflows take this information from Legal Entities in your application process. This issue affects roughly 1% of all LEIs managed by RapidLEI, and our Data Quality team are now busy working hard to backfill those missing data points for you. This is acceptable, as both Region Code and Postal Code may be added by the Managing LOU without affecting the Corroboration Level of the Legal Entity Reference Data.
Enhanced support for the NON_PUBLIC reason in XLS based bulk requests.
We’ve also aligned our XLS bulk update template to cater for NON_PUBLIC. i.e. where a parent exists but the legal entity is prevented from reporting the details. NON_PUBLIC as a reporting exception alternative was introduced with the update of the GLEIF schema in early 2022, and RapidLEI have supported from that time in our API and GUI ordering systems. Some of our key partners wanted the same option for our XLS bulk request format.
Please note that whist XLS has advantages in some circumstances, it cannot specifically identify an incorrect company name or company number. Using the GUI/API pre-submission search takes advantage of our automation engine to correct potential mistakes saving time and avoiding potential duplicates. You’ll find the new XLS sheets downloadable
Warning – Blacklisted company numbers will soon be updated!
In Sprint 45 (April 2022) we highlighted a range of blacklisted number formats such as
‘NOT AVAILABLE’, ‘N.A.’, ‘N.A’, ‘N/A’, ‘N A’, ‘N.V’, ‘N.V.’, ‘N V’, ‘EXENTO’, ‘EXENTA’, ‘NO SUJETO’, ‘0’,
all of which were not allowed as part of the Legal Entity Reference Data.
The exiting list will continue to be backlisted, however, others are soon to be added which include
‘TRUST’ ,’OBCHODNý REGISTER’ ,’REGISTRAR OF COMPANIES’ ,’HANDELSREGISTER’ ,’COMPANIES REGISTER’ ,’TRADE AND COMPANY REGISTER’ ,’FUND REGISTER’ ,’TRADE REGISTER’ ,’TRUST REGISTER’ ,’BUSINESS REGISTER’ ,’DOCUMENT’ ,’DOCUMENTS’ ,’REGISTER’ ,’0THER’ ,’OTHER’ ,’OTHERS’ ,’REGISTO COMERCIAL’ ,’COMMERCIAL_REGISTER’ ,’INTERMEDIARY REGISTER’ ,’COMPANY REGISTER’ ,’REGISTRY OF TRUST’ ,’REGISTER OF COMPANIES’ ,’REGISTRO COMERCIAL (TRADE REGISTER)’ ,’DIğER’ ,’NULLVALUE’ ,’UNDEFINED’ ,’OTHERLEGALFORM’ ,’OTHER COMPANY TYPE’ ,’S/N’ ,’UNKNOWN’ ,’000’
