Registering an Entity for an LEI on the GMEI Utility Portal

+ What is a Legal Entity Identifier?
  • An LEI is a unique code associated with a single legal entity in accordance with the ISO 17442 standard. The LEI is a reference data tool to standardize how a counterparty is identified on financial transactions. Its goal is to help improve the measuring and monitoring of systemic risk and support more cost-effective compliance with regulatory reporting requirements.
+ What entities require an LEI?
  • The GMEI utility does not mandate which global entities require LEIs. These requirements are driven by international regulations applied to financial services firms, however in accordance with the LEI standard, we do not issue LEIs to natural persons.
  • The GMEI utility will neither accept nor reject submissions based on entity size, jurisdiction, asset class or role in a financial transaction.
  • The validation checks performed against registered LEI records are to confirm that the requested entity exists, that it is eligible to receive an LEI, and that the submitted data is accurate. These are not Know Your Customer (KYC) checks and do not represent a judgment on suitability or the capability of the entity being registered for taking part in financial transactions.
+ What entities can receive an LEI?
  • An LEI can be requested for all parties in a financial transaction including but not limited to:
  • An LEI should not be requested for individuals, branch offices, or operating divisions. These entities should utilize the LEI of their parent organization.
  • Additional assistance can be provided by emailing CustomerService@GMEIutility.org.
+ Who can register an entity for an LEI?
  • An LEI can be registered through a process known as Self-Registration. You must meet the following conditions to register an entity as the primary party:
    • You are currently an employee of the firm for which you are registering, or are currently an employee of the firm which has controlling interest over the entity you are registering.
    • You are authorized by your firm to register for an LEI.
  • An LEI can also be registered via Assisted Registration by a third party that is not associated with the entity being assigned an LEI, provided that the entity being assigned an LEI has given explicit permission for the third party to do so.
+Who registered my LEI?
  • The GMEI utility meets the industry and regulatory requirement that we allow for assisted registration. Thus one firm can register another firm they are affiliated with at any time, provided that the affiliated firm has provided permission to do so. For example a swaps dealer may register a hedge fund it occasionally enters into bilateral swaps contracts with and the dealer enters the reference data and pays the registration fee. The GMEI utility validation team will attempt to compare the data against public sources. Best practice calls for the entity to review the record on the site and complete the maintenance process to indicate that they have reviewed the data and have advised the GMEI utility of any inaccuracies. The GMEI utility validation team will then update the Record State and Maintenance State attributes accordingly.
+How long does it take to receive an LEI?
  • The LEI assignment process begins after payment is processed and validation against public sources has occurred. Once record validation is completed by the GMEI utility validation team, the record will have an LEI assigned and will be transferred from the Staging Database to the GMEI utility Issued Database. It takes approximately three business days from the time the request for LEI assignment is received to the time that the record is listed in the GMEI utility Issued Database.
+How will I be notified of my registered LEI?
  • You will receive an email upon completion of the registration process confirming that your request has been received. After validation review has completed, you will receive an email from the GMEI utility providing you a link to the record with the assigned LEI. The record will be publicly available via the GMEI utility portal at this time.
+What information is needed for an entity to receive an LEI?
  • At this time, basic information in compliance with the ISO 17442 standard as well as the information needed to uniquely identify the entity is required. This includes legal name, registered address, headquarters address, entity status, and the entity's legal form.
  • The registered address of the entity should be provided and listed according to the documentation of incorporation. It is common for registered addresses to be care of an agent of service, and therefore should not be regarded as a mailing contact or a headquarters address for the entity.
+How is information regarding unique entities, such as funds, entered onto the GMEI utility portal?
  • Please refer to the Fund Guidance document, which defines various data submission use cases for these unique legal forms.
+What is the cost for the registration of a new LEI?
  • Please refer to the FAQ Payment information below.
+What validation will be done against my submission?
  • To ensure a high degree of data quality and that core principles are maintained, all LEI registration requests will be independently validated against public sources prior to assignment of an LEI. These sources will vary depending on entity type and jurisdiction but will include national company registries, filings held by regulators and central banks, stock exchange listings and the fund prospectus.
+What actions will the GMEI utility validation team take to review my registration request?
  • The GMEI utility validation team will go perform a two-stage validation check for all requests made via the GMEI utility portal. Checks will be made for duplication, data accuracy and data formatting. The record may be accepted, corrected or set to duplicate status.
  • A record will be flagged as a duplicate when it is identified as pertaining to the same legal entity that already has another LEI. If a record is found to be a duplicate during the validation of a registration request, the request will be rejected and the submitter will be notified via email regarding the correct globally accepted LEI to use. No refunds will be issued. This may be necessary even if core data is not identical across the two records. Examples include:
    • Where the same entity has been listed twice at multiple addresses, e.g. a branch has been registered as well as the entity itself.
    • Where the same entity has been listed twice under both former and current names.
    • Where the same entity has been listed twice under both local language and Anglicized names.
    • Where one entity has merged into another entity and legal succession has been confirmed.
  • The GMEI utility validation team will also monitor ongoing corporate actions and processing to identify data changes that are needed but have not been raised as a challenge.
+How long will it take for the GMEI utility validation team to review my registration request?
  • It is difficult to estimate how long a registration request will be pending as this will depend on the volume of items requiring validation. Most outstanding actions have been cleared within 3-5 business days.
  • LEIs being registered are placed in the staging file immediately after the registration request is received. These registrations will remain in the staging file until the GMEI utility validation team has reviewed the record. Once the review is complete, the record will be assigned an LEI code, and will be moved to the GMEI utility Issued Database. Records in this Database are mutually accepted for reporting to global regulators.
  • Requests against existing records, including Maintenance and Challenge requests, will undergo review by the GMEI utility validation team prior to the record being updated on the GMEI utility portal. To prevent vandalism of a record, changes will not be made to the record until the GMEI utility validation team has reviewed the request.

Maintaining an Entity on the GMEI Utility Portal

+What is the maintenance process?
  • The maintenance process is a procedure implemented on the GMEI utility portal to allow parties with explicit permission to provide information related to an entity record on an ongoing basis. Bulk processing is also available.
  • A record will not be updated on the GMEI utility portal until the GMEI utility validation team has reviewed the record. After successful validation, the record will have its Maintenance State set to "CURRENT" and the Next Maintenance Date will be extended one calendar year from the time of maintenance.
+What occurs if a record is not maintained?
  • A record that is not maintained by the date noted in its Next Maintenance Date will have its Maintenance State value set to "NOT_CURRENT". Having a record marked as "NOT_CURRENT" is an indication that the LEI may not be compliant with practices recommended by the FSB and ROC, and in some instances may indicate non-compliance with regulatory requirements. However, records marked as "NOT_CURRENT" are still valid for use in regulatory reporting and should continue to be used for such purposes.
+Why should I maintain my entity record?
  • Although entity data at the time of registration may be accurate, the reference data associated with an entity record will change over time. As a result, users should return to the GMEI utility portal on an annual basis to maintain their record via the maintenance process.
  • Not maintaining a record on an annual basis may render the LEI non-compliant with practices recommended by the FSB and ROC, and in some instances may indicate non-compliance with regulatory requirements. However, records marked as "NOT_CURRENT" are still valid for use in regulatory reporting and should continue to be used for such purposes.
+What actions will the GMEI utility validation team take to review my maintenance request?
  • The GMEI utility validation team will perform a two-stage validation check for all requests made via the GMEI utility portal. Checks will be made for duplication, data accuracy, and data formatting. The maintenance request may be accepted or rejected.
  • Maintenance requests may be rejected if they change the entity that the record information refers to. If you have any questions concerning a pending maintenance request, please contact the GMEI utility customer service team at CustomerService@GMEIutility.org.
+How long will it take for the GMEI utility validation team to review my maintenance request?
  • It is difficult to estimate how long a maintenance request will remain pending as this will depend on the volume of requests that require validation. Most outstanding actions have been completed with updated results on the GMEI utility portal within 3-5 business days.
+What is the cost for maintaining an existing LEI record?
  • Please refer to the FAQ Payment information below.

Performing the Bulk Action Process

+What templates are used for the bulk action process?
+What are the required fields for the bulk action process?
  • The following fields will be required when creating your bulk service file for the bulk action process:
    • Registered Entity Name
      • Legal Name
      • Anglicized Legal Name will be required when the Legal Name contains non-ASCII characters
    • Registered Entity Address
      • Address Line One
      • Country
      • City
    • Headquarters Entity Address
      • Address Line One
      • Country
      • City
    • Entity Information
      • Business Registry
      • Entity Status
      • Legal Form
      • Managing LOU
+What are the standardized field values for the bulk action process?
  • The standardized fields for the bulk processes are:
    • Country
    • State (United States and Canada only)
    • Business Registry (Dependent on selected Registered Entity Address Country)
    • Entity Status
    • Legal Form (Dependent on selected Registered Entity Address Country)
    • Managing LOU (Dependent on selected Registered Entity Address Country)
  • You can find all standardized values within the Registration Template and Maintenance Template documentation.
+What errors indicate my entire Bulk Action submission file was rejected?
  • You will see one of the following message on the Bulk Action Dashboard and Bulk Action Process pages. In each case, you will need to fix your Bulk Action submission file to resolve the rejection prior to resubmitting your file.
    • No Data (0 bytes) Found in File
      • This message indicates the file was detected to contain no header and no records, and has failed to process. Please select a file that contains bulk service data.
    • No Records Found in File
      • This message indicates the file was detected to contain no records and has failed to process. Please select a file that contains data.
    • Maximum Records Allowed for a Bulk Service File Exceeded
      • This message indicates the maximum number of records for a bulk service file is 500 records. Please select a file that contains 500 records or fewer.
    • Incorrect Template Version Used
      • This message indicates the file was detected to be using an incorrect or invalid bulk service template. Please download the most up-to-date template and resubmit your data using the current template.
    • File Format not XML or Excel (.XLS or .XLSX)
      • This message indicates the file was detected to be in a format other than Excel (.XLS or .XLSX) or XML. Please resubmit your data using an Excel (.XLS or .XLSX) or XML file type.
+What indicates my record processed successfully through Bulk Action?
  • Each record must pass a variety of data quality checks before it can be processed. A record that was successfully processed will receive the code listed below.
    • 000 - Record has Processed Successfully
      • This code indicates the record was processed successfully and has been submitted for payment. There are no additional actions other than payment that are required at this time for the record.
+What errors indicate my record(s) was rejected by Bulk Action and not processed?
  • Each record must pass a variety of data quality checks before it can be processed. A record that encountered an error(s) will receive one or more of the following rejection codes. The information that appears below the rejection code provides information on the action you need to take in order to successfully process the rejected record(s).
    • 200 - Unknown Failure
    • 202 - Anglicized Legal Name Not Provided
      • The Legal Name has been identified to contain non-ASCII characters, and has failed to process because no Anglicized Legal Name was provided. The Anglicized Legal Name becomes a required field when the Legal Name contains non-ASCII characters.
    • 203 - Incorrect Ultimate Parent Listed
      • An Ultimate Parent(s) LEI for this record was not located within the GMEI utility. Ensure the provided Ultimate Parent(s) LEI is correct by searching the GMEI utility for the Ultimate Parent(s) LEI.
    • 204 - Duplicate LEIs Within File
      • The record was not processed because another record within the file for this LEI has already been processed.
    • 205 - Exact Duplicate Match
      • The record has been identified as an exact match to a record currently in the GMEI utility. Review the record to ensure the correct data and LEI have been submitted. If the record is a duplicate of the existing record on the GMEI utility, do not resubmit the record. If the record is a duplicate but data needs to be updated on the GMEI utility, update the data that needs to be changed.
    • 207 - LEI Provided Does Not Exist
      • The LEI code you provided for the record does not exist within the GMEI utility. Review the record to ensure the correct LEI has been provided. You may use the GMEI utility search feature to identify the proper LEI.
    • 208 - Pending Operational Review
      • The record is currently pending operational review for a separate action and cannot be maintained until the current review is completed.
    • 209 - Record Cannot List Self as Ultimate Parent
      • The Ultimate Parent LEI associated to the record is its own LEI. The Ultimate Parent LEI must be something other than the LEI of the record itself.
    • 210 - Related Ultimate Parent LEI Pending Operational Review
      • The Ultimate Parent LEI is currently pending operational review for a separate action. The Ultimate Parent LEI cannot be associated to the record being registered or maintained until the current review is completed.
    • 212 - Entity Status Not Provided
      • The Entity Status is a required field and was not provided.
    • 213 - Record State Does Not Allow Maintenance
      • The record is marked with a Record State that does not allow the record to be maintained. The record states that cannot be maintained are DUPLICATE, REMOVED, PENDING_REMOVAL, TRANSFERRED, or PENDING_TRANSFER. Please omit all records that currently have these Record States from your file.
    • 214 - Invalid State/Province Code Format
      • The record has been identified as containing an invalid State or Province code. An example of this is when a user supplies Florida for the state field, the correct format for this field is FL. Update the state or province to reflect the two character abbreviation.
    • 215 - Business Registry Not Provided or Invalid
      • The Business Registry for the record is not a valid value for the Registered Entity Address Country, or was left blank. Review the Registered Country and Business Registry to ensure they are valid.
    • 216 - Business Registry Number Without Business Registry
      • The record was identified as having a Business Registry Number, but does not contain a Business Registry. Update the record to include the Business Registry issuing the Business Registry Number.
    • 217 - Business Registry Number Supplied For Not Available Business Registry
      • The record was identified as having a Business Registry Number and the Business Registry indicates "Not Available". Update the record to include the Business Registry issuing the Business Registry Number.
    • 218 - State/Province Not Supported by Country
      • A State/Province value within this record was found to use data that is not allowed for the Registered Entity Address Country or Headquarters Entity Address Country selected. Update the record to reflect the standardized values supplied within the bulk action templates.
    • 219 - Legal Name Not Provided
      • Legal Name is a required field and was not provided for the record.
    • 221 - Registered Entity Address Line One Not Provided
      • Registered Entity Address Line One is a required field and was not provided for the record.
    • 222 - Registered Entity Address Country Not Provided
      • Registered Entity Address Country is a required field and was not provided for the record, or was found to be invalid.
    • 223 - Registered Entity Address City Not Provided
      • Registered Entity Address City is a required field and was not provided for the record.
    • 224 - Headquarters Entity Address Line One Not Provided
      • Headquarters Entity Address Line One is a required field and was not provided for the record.
    • 225 - Headquarters Entity Address Country Not Provided
      • Headquarters Entity Address Country is a required field and was not provided for the record, or was found to be invalid.
    • 226 - Headquarters Entity Address City Not Provided
      • Headquarters Entity Address City is a required field and was not provided for the record.
    • 227 - Legal Form Not Provided or Invalid
      • Legal Form is a required field and was not provided for the record, or was found to be invalid for the Registered Entity Address Country.
    • 228 - Managing LOU Not Provided or Invalid
      • Managing LOU field is a required field and was not provided for this record, or was found to be invalid for the Registered Entity Address Country.
    • 229 - EOR Indicator Not in Expected Cell
      • The End of Row indicator ("EOR") was not in the correct cell of the original bulk submission file. The value "EOR" is automatically provided in the correct cell in the rejection file for ease of resubmitting.
    • 230 - EOR Indicator Not in Expected Cell
      • The End of Row indicator ("EOR") was not in the correct cell of the original bulk submission file. The value "EOR" is automatically provided in the correct cell in the rejection file for ease of resubmitting.
    • 231 - Assisted Registration Cannot Add Ultimate Parents
      • The record was not processed because an Ultimate Parent LEI was present on the record. Assisted Registrations are not allowed to provide Ultimate Parent LEIs.
    • 232 - Exact Duplicate Records Within File
      • The record was identified as being an exact duplicate to another record within the file, and was not processed.
    • 234 - LEI Not Provided
      • LEI is a required field and was not provided for this record.
    • 235 - Registration Status Not Provided or Invalid
      • Registration Status is a required field and was not provided for this record, or is not a valid Registration Status.
    • 236 - Customer Reference ID Max Length Exceeded
      • The Customer Reference ID for this record has exceeded the maximum 50 characters.
    • 237 - Anglicized Legal Name Contains Non-ASCII
      • The Anglicized Legal Name cannot contain non-ASCII characters.
    • 238 - Invalid Characters Found
      • Invalid characters were found in this record and have been replaced with the string "{bad data}" for ease of identification and correction.

Challenging the Data Associated with an Existing Entity

+What is the challenge process?
  • Challenging a record will trigger a review of the record by the GMEI utility validation team to determine the validity of the updated information being submitted. This will allow users to indicate updates to records at no cost to the user.
  • Challenging also allows users to indicate that an entity record expired. It enables users to provide comments which will allow the GMEI utility validation team to research the Date of Expiry and Reason for Expiry, if applicable.
  • Challenging can also be used to indicate that an entity record is a duplicate of another record in the GMEI utility Issued Database or even on another pre-LOU dataset.
+Who can challenge an entity?
  • Any user, including any member of the public that establishes a user account in the GMEI utility portal, can challenge any entity on the portal via the Challenge process. These requests will be reviewed for validity. Publicly available authoritative sources should be noted in the comments of the challenge if possible. This will aid the GMEI utility validation team in effectively researching the entity record.
+What information is needed to challenge an entity?
  • An entity record will be pre-populated with the existing entity information. Updates to the existing information can then be made.
  • If the user is challenging that the record is a duplicate of another record on the GMEI utility portal, the user must indicate the other record.
  • If the user is challenging that the record is a duplicate of another globally accepted record not located on the GMEI utility portal, they can indicate this by providing additional information in the memo field.
+How much does challenging an entity cost?
  • There is no fee for challenging an entity's information.
+What actions will the GMEI utility validation team take to review my challenge submission?
  • Validation of all challenge requests will occur before changes are published to the portal database. Checks will be made for duplication, data accuracy and data formatting as well as persistence. The challenge may be accepted and published, corrected and published, or rejected.
  • Validation of all duplicate challenge requests will occur before changes are published to the GMEI utility Issued Database. Checks will be made to confirm that it is a valid duplicate and to identify which of the records should survive. If the duplicate challenge request is accepted, one of the records will be updated to indicate that it is a duplicate and the other record will remain as the surviving entity. The duplicate challenge request may also be rejected if it is deemed invalid.
  • Note: Challenges will fail persistence checks if the update proposed would change the identity of the record, and these changes are not supported by a valid corporate action.

Procedures for Updating an Entity Record

+How should I indicate an update to a record?
  • If you are the primary party of a record, you must maintain the record via the maintenance process prior to the submission of any challenge requests. After a record has been maintained, it can then be challenged until the maintenance period expires.
  • All fields are editable during the maintenance process.
  • If you are a third party that is providing updates to a record, you may challenge the record at any time to provide updated information.
  • You can also indicate that there is a duplicate record by utilizing the duplicate challenge process.
  • Additional assistance can be provided by emailing CustomerService@GMEIutility.org.
+How should I indicate a merger into an existing company?
  • This assumes that after a merger a single major entity continues to operate without change and subsumes the minor party which consequently ceases to exist.
  • For all LEIs which will cease, the Record State will be set to "DUPLICATE" and the LEI of the successor will be captured in the Duplicate Reference field. The GMEI utility validation team will add information for the Date of Expiry and Expiry Reason where available for the record as a result. Additional information can be provided during the challenge process by supplying notes regarding the change.
  • The surviving LEI record will remain active, with no change to its Record State field; the "Duplicate" record's LEI will be reflected in the surviving LEI record's Duplicate Reference field.
+How should I indicate a merger that creates a new entity?
  • Register a new LEI for the new entity.
  • For all entities which will cease, the Record State will be set to "DUPLICATE" and the new successor entity will be captured in the Duplicate Reference field.
+How should I indicate an acquisition or takeover?
  • Example: A stand-alone legal entity is taken over by another entity or ownership is transferred from one owner to another.
  • Change is required to the Ultimate Parent data attribute (the addition or change of Ultimate Parent LEI must occur) but the LEI of the entity being acquired remains the same.
+How should I indicate a legal name change?
  • An additional LEI should not be generated. Instead, the existing LEI should be updated to reflect the new legal name using the Maintain or Challenge function.
  • Care needs to be taken when corporations recycle dormant companies and switch names over at the same time. In this case it is necessary for the LEI to maintain the correct audit trail for each entity, accurately reflecting the legacy of the changes made.
+How should I indicate a registered address change?
  • Registered address changes are infrequent and not to be confused with changes to operational addresses.
  • The LEI remains the same but the Registered Address data is updated to reflect the new information.
+How should I indicate an operational address change?
  • The LEI remains the same but the Headquarters Address data is updated to reflect the new information.
+How should I indicate that an entity is in administration, liquidation, bankruptcy, or receivership?
  • The LEI record remains untouched as the entity status is technically still active.
+How should I indicate that an entity is in dissolution?
  • The record should be challenged and the Entity Status should be changed from "ACTIVE" to "INACTIVE". The user should also provide information for the "Date of Expiry" and "Reason for Expiry" in the comments box as well. The GMEI utility validation team will review publicly available sources of information for the entity and update the record accordingly.
  • This only happens when the company ceases to exist and is dissolved.
+How should I indicate that an entity has been re-incorporated in a new jurisdiction?
  • An additional LEI should not be generated. Instead, the existing LEI is updated to reflect the new registered address. The data is then revalidated against the new registry.
+How should I indicate that an entity's banking license has been revoked?
  • The LEI record remains untouched.
  • The Entity Status of the LEI remains "ACTIVE" if the company is still active.
+How should I indicate that there has been a spin-off or dispersal?
  • The existing LEI record remains untouched.
  • A new LEI should be created for the new company if needed.
+How should I indicate an entity is listed under two distinct LEIs?
  • Please use the duplicate challenge functionality to indicate the two records that you have determined are duplicates. This will initiate a validation review of the records to determine the best course of action.
  • The first LEI created will always remain active in this scenario.
  • For the other LEI record, the Record State will be set to "DUPLICATE" and the successor LEI will be captured in the "Duplicate Reference" field.
  • No change will be made to the LEI record which remains active.
+How should I indicate an entity is listed under two distinct LEIs, but only one of those LEIs is managed by the GMEI utility?
  • After visiting the Challenge page for the entity record that has a duplicate conflict on the GMEI utility portal, please select the appropriate checkbox at the top of the page.
  • Information regarding the duplicate can be supplied in the memo field at the bottom of the page.
  • After completing your submission, the GMEI utility validation team will review which of the records should be listed as a duplicate, and which record should survive. This is based on the LEI assignment date for the record.

Searching for an Entity Record

+How can I enhance my search results to find the record I'm looking for?
  • Filters can be added to limit search results. These filters are available on each Search page, and are additive. For example, a user can submit the search term "bank", and then add filters for an Entity Status of "Active" and a Registered Country of "United Kingdom". The search results will be limited to active entities which have a registered address in the United Kingdom with the word "bank" in their record contents.
  • Only records in the GMEI utility Issued Database and mutually accepted by global regulators will match a user's inquiry by default. This search can be expanded to include records in the staging file by selecting the appropriate checkbox below the search query textbox.
  • Use double quotes to create phrases instead of single word searches.

Payment

+What forms of payment are accepted?
  • Credit card and standard wire payment formats are available payment options on the GMEI utility portal.
  • Payments are accepted in US Dollars (USD) or Euros (EUR).
+What are the payment requirements of the GMEI utility portal?
  • Payment is required before any processing will occur.
  • Items awaiting payment selection can be found on the Pending Actions page of the GMEI utility portal. The link for the Pending Actions page can be found in the upper-right corner when a user is logged in. On this page, you will see a list of "Pending Actions" that includes items that have not been submitted. Please note that items in the "Pending Actions" table will be removed in seven days if they are not submitted.
  • If you elected to submit payment via wire, you may have a list of "Orders Pending Payment" on this page as well. After a wire has been received and can be matched to these items, these orders will be sent for processing. Items in the "Orders Pending Payment" table will be removed in 60 days if payment is not received and recognized.
+How can I pay via wire transfer?
  • During the checkout process, you can elect to pay for your order via wire. There will be a hold placed on the order until payment from you is received and recognized. Please allow five days after payment is sent for the payment to be recognized.
  • You must include the order code in the memo field of the wire payment to ensure that payment can be recognized successfully. The order code can be found in the email that is sent after an order is submitted and/or on the Pending Actions page.
  • Payments must be made on a "one payment per order" basis. At this time, payment cannot be sent for multiple orders at once, and partial payment cannot be applied against an order.
  • If you elect to pay via wire payment, specific instructions should be followed to ensure that your payment is recognized and can be linked to your order. These instructions are available for payment in Euro and US Dollar:
+Why is the charge "GMEI Utility Reg. Fee", possibly under the category "Bus Services", showing on my credit card statement?
  • In an office setting, a credit card is often shared among a number of individuals. Due to regulatory reporting requirements, the shared credit card has been used to register or maintain an entity record on the GMEI utility portal. Please note that "Bus Services" is an abbreviation for "Business Services".
  • Before contacting your credit card company regarding a query on this charge, please communicate with other users of the credit card to determine if it has been used for this purpose.
  • Please note that the holding company of the GMEI utility is "Business Entity Data B.V.", which is located in the Netherlands.
+What is the cost for the registration of a new LEI record?
  • The basic charge for a registration request is $200.00 or €183.70. In accordance with the 2014 funding plan for the Global Legal Entity Identifier Foundation (GLEIF), each registration is also subject to a $20.00 or €18.37 per record COU surcharge.
+What is the cost for maintaining an existing LEI record?
  • A maintenance request will set the "Next Maintenance Date" for the record to one year in the future from the time of the maintenance request. The cost of a maintenance request is based on the number of additional months that will be added to the record's Next Maintenance Date. The basic charge for maintenance is $100.00 or €91.85. In accordance with the 2014 funding plan for the Global Legal Entity Identifier Foundation (GLEIF), each maintenance submission is also subject to a $20.00 or €18.37 per record per year COU surcharge. The resulting maintenance pricing schedule is as follows:
    Maintenance Period USD Price COU Surcharge USD Total Cost EUR Price COU Surcharge EUR Total Cost
    1 month or less $ 8.34 $ 1.66 $ 10.00 € 7.66 € 1.54 € 9.20
    2 months $ 16.67 $ 3.33 $ 20.00 € 15.31 € 3.07 € 18.38
    3 months $ 25.00 $ 5.00 $ 30.00 € 22.97 € 4.60 € 27.57
    4 months $ 33.34 $ 6.66 $ 40.00 € 30.62 € 6.13 € 36.75
    5 months $ 41.67 $ 8.33 $ 50.00 € 38.28 € 7.66 € 45.94
    6 months $ 50.00 $ 10.00 $ 60.00 € 45.93 € 9.19 € 55.12
    7 months $ 58.34 $ 11.66 $ 70.00 € 53.58 € 10.72 € 64.30
    8 months $ 66.67 $ 13.33 $ 80.00 € 61.24 € 12.25 € 73.49
    9 months $ 75.00 $ 15.00 $ 90.00 € 68.89 € 13.78 € 82.67
    10 months $ 83.34 $ 16.66 $ 100.00 € 76.55 € 15.31 €91.86
    11 months $ 91.67 $ 18.33 $ 110.00 € 84.20 € 16.84 € 101.04
    12 Months+ or record listed as "NOT_CURRENT" $ 100.00 $ 20.00 $ 120.00 € 91.85 € 18.37 € 110.22

Downloading Public Files

+What files are available for download?
  • Thirty days of the GMEI utility Issuaed Database are made available. Two files will be made available on a daily basis. One file includes the entire GMEI utility database, while the other is a "delta" file that is limited to records that have been updated since the previously published delta file. These files contain LEIs that are mutually accepted by global regulators.
  • Thirty days of the staging database will be made available. The staging database only includes records that are currently under review for initial validation prior to being assigned an LEI. Two files will be made available on a daily basis. One file includes the entire staging dataset, while the other is a "delta" file that is limited to records that have been updated since the previously published delta file.
  • Thirty days of a consolidated listing from select pre-LOUs is also provided in a consolidated file.
+How will these files be accessed?
+Where can I learn about the format of these files?
+When will these files be made available?
  • These files will be made available on a daily basis, although the time of availability is dependent upon the time needed to process the files.

Site Requirements

+What are the compatibility requirements for the use of the GMEI utility portal?
  • For the best experience, this site has been certified as compatible with Internet Explorer 8. Other versions of Internet Explorer and other browsers may function adequately, but have not been confirmed as being compatible.
+What if a site feature does not appear to work?
  • Please check your browser security settings to ensure that they are not set to "High" or "Custom". JavaScript must be enabled to allow typical functioning of the site.
  • Additional assistance can be provided by emailing CustomerService@GMEIutility.org.