LEI checksum checker

Client

Regulatory and onboarding packs often paste LEI codes beside IBAN or securities identifiers. This page strips separators, confirms the twenty-character layout, and recomputes the published MOD‑97‑10 check digits—pair with IBAN validate when the same entity row also lists a payment account.

What this checks

A Legal Entity Identifier is twenty characters: eighteen body symbols plus two MOD‑97‑10 check digits (ISO 17442, same checksum family as IBAN). The tool confirms layout and recomputes the trailing pair—it does not prove registration status.

Privacy: checksum math runs locally in your tab. Toolcore does not query GLEIF, LEI registry, or entity master files—format and check digits only.
?

After cleanup the identifier is 20 characters: an 18-character body plus two decimal check digits (MOD‑97‑10, same family as IBAN). The first four characters are the LOU prefix— this page does not query GLEIF for entity names.

Result

KYC packs often list LEI beside IBAN wires—open IBAN validate or ISIN validate on the same issuer row.

Passes LEI MOD‑97‑10 check for 5493000IBP32UQZ0KL24.

Body (18)
5493000IBP32UQZ0KL
Check digits
24
LOU prefix
5493

Nearby workflows on Toolcore

  • IBAN validate — when the same onboarding row lists payment rails beside the entity LEI.
  • ISIN validate — for securities identifiers issued by the same legal entity in another column.
  • FIGI format check — for instrument-level OpenFIGI symbols beside entity-level LEI codes.

Common use cases

  • Sanity-check a LEI copied from a KYC or EMIR reporting file before loading it into an internal security master.
  • Explain why a twenty-character LEI fails MOD‑97‑10 while a related IBAN on the same row still passes its checksum.
  • Spot transposed characters in the eighteen-character body when only the LEI column is available in legacy CSV feeds.
  • Contrast LEI MOD‑97‑10 with ISIN Luhn expansion when compliance teams mix entity and instrument identifiers.

Common mistakes to avoid

  • Treating a passing check as proof of registration or good standing

    Checksum validation confirms arithmetic only—not legal existence, sanctions status, or regulatory approvals.

  • Applying ISIN Luhn to LEI bodies

    LEI appends 00 to the eighteen-character body, expands letters to numbers, and derives two check digits as 98 − (value mod 97)—different from ISO 6166 ISIN rules.

  • Expecting GLEIF entity metadata

    Legal name, address, and registration status require GLEIF or licensed feeds—this page performs local format math only.

FAQ

Does Toolcore query GLEIF or the LEI registry?

No—the check digit and layout rules run entirely in your browser tab.

How does the check digit work?

Expand the first eighteen characters to digits (A=10 through Z=35), append 00, take mod 97, and set the last two characters to 98 minus that remainder (zero-padded).

Can LEI check digits be 00?

Check digits are two decimals in the range implied by MOD‑97‑10; this tool validates the published algorithm only—not whether the LOU still allocates the prefix.

Common search terms

Phrases people search for that match this tool. See the full long-tail keyword index.

  • lei checker online mod 97 10
  • validate legal entity identifier checksum
  • iso 17442 lei format browser
  • lei validate no gleif lookup

More tools

Related utilities you can open in another tab—mostly client-side.