LEI Validator ISO 17442
Check a 20-character LEI — structure and check digits — instantly in your browser. And find out what a valid checksum does NOT prove.
What is a LEI?
A LEI (Legal Entity Identifier, ISO 17442) is a 20-character code that identifies a legal entity — a company, a fund, a public body — uniquely and worldwide. It is required to report financial transactions, and it is carried by ISO 20022 payment messages and by the European electronic invoice (scheme 0199 of the ICD and EAS code lists). Its last two characters are check digits computed with ISO/IEC 7064 MOD 97-10, the same scheme as the IBAN, so typos can be caught offline. This free tool verifies that checksum entirely in your browser — nothing is uploaded.
About the LEI validator
A LEI has 20 characters: the first four identify the LOU (Local Operating Unit) that issued it, the next fourteen identify the entity, and the last two are check digits. It answers the question "who is the party?", where an IBAN answers "which account?" — which is why the two are complementary rather than alternatives.
ValidateFin checks the LEI locally in your browser: 20 characters, uppercase letters and digits only, and check digits matching ISO/IEC 7064 MOD 97-10. Because the ISO standards are sold rather than published, the algorithm here was not copied from them: it was established against GLEIF's own public data, which is released under CC0, and verified on 2,400 real LEIs. A valid checksum means the code is well-formed and free of typos — it does not prove the entity exists, nor that its LEI is still active. That would require the GLEIF Global LEI Repository, which is an online lookup, and this tool is deliberately offline.
Key facts about the LEI
- A LEI is exactly 20 characters: a 4-character LOU prefix, a 14-character entity part and 2 check digits.
- The check digits use ISO/IEC 7064 MOD 97-10 — the same algorithm as the IBAN, so a single typo always breaks the code.
- A valid checksum proves only that there is no typo. It does NOT prove the entity exists, nor that the LEI is active.
- A LEI must be renewed every year: a perfectly well-formed LEI can be LAPSED, RETIRED or ANNULLED.
- Characters 5-6 are described as "reserved" — but 8% of real LEIs do not follow that rule, so it must not be enforced.
Frequently asked questions
What is a Legal Entity Identifier (LEI)?
It is a 20-character code, defined by ISO 17442, that identifies a legal entity uniquely and worldwide. It is issued by a LOU accredited by GLEIF (the Global Legal Entity Identifier Foundation) and is required to report financial transactions in most jurisdictions.
How are the LEI check digits calculated?
From the first 18 characters, using ISO/IEC 7064 MOD 97-10 — the same scheme as the IBAN. Letters are converted to numbers (A=10 … Z=35), and the whole 20-character code, read as one long number, must leave a remainder of 1 when divided by 97.
Does a valid LEI mean the company exists?
No, and this is the most common misunderstanding. A valid checksum only proves the code was typed correctly. It does not prove the LEI was ever issued, nor which entity it belongs to, nor that it is still active. Only the GLEIF Global LEI Repository can answer those questions, and that is an online lookup.
Can a LEI expire?
Yes. A LEI must be renewed annually. Its registration status can be ISSUED, LAPSED, RETIRED or ANNULLED. A LEI whose checksum is perfectly valid may well be lapsed — the format says nothing about the status.
Are characters 5 and 6 of a LEI always "00"?
No. The standard describes them as reserved, but reality disagrees: measured against GLEIF's own public data, about 8% of real LEIs do not carry "00" there and are nevertheless perfectly valid. A validator that enforced this rule would reject roughly one entity in twelve.
Where is a LEI used?
In financial transaction reporting (MiFID II, EMIR), in ISO 20022 payment messages, which carry an LEI element for the parties, and in the European electronic invoice, where the LEI is scheme 0199 of the ISO 6523 ICD and EAS code lists.
Is my LEI sent anywhere?
No. The identifier is validated entirely in your browser with JavaScript. Nothing is ever sent to a server.