How to use LEI data for counterparty due diligence in India

Every transaction with a new counterparty carries a question: who exactly are we dealing with? In India, that question now sits at the heart of RBI’s KYC framework, SEBI’s reporting obligations, and the day-to-day work of any compliance team. The Legal Entity Identifier gives you a fast, reliable way to answer it — if you know how to read the data.

This guide walks through how Indian compliance teams can use LEI records for counterparty due diligence: what fields to check, what each LEI status means, and how to combine LEI data with other Indian identifiers like CIN and PAN. India is now the second-largest LEI jurisdiction globally, with strong adoption growth — 8.1% in Q1 2026 according to GLEIF — so the LEI is increasingly likely to be available for the entities you work with.

Why the LEI is a strong starting point

Indian regulated entities already perform Customer Due Diligence (CDD) under RBI’s KYC Master Directions and similar SEBI rules. The LEI does not replace CDD — it strengthens it.

A single LEI gives you four things at once:

• A unique global identifier that survives name changes, mergers, and rebrands
• Standardised legal name and address as registered in the official Indian company register
• The entity’s registration status and LEI status, both updated annually
• Parent and subsidiary relationships where reported, useful for group-level exposure

Crucially, all of this comes from a single, free, authoritative database — the Global LEI Index, maintained by GLEIF. For an Indian compliance team, that means consistent counterparty data across borders, asset classes, and reporting frameworks.

For cross-border relationships, the value compounds. A counterparty in Singapore, the EU, or the United States may not share India’s CIN or PAN system, but every regulated entity in those markets is increasingly required to hold an LEI. The same 20-character code therefore works as a universal reference — which is exactly why the LEI underpins so much of the global KYC infrastructure.

Step 1: Find the LEI

Start with the GLEIF search tool or any free LEI lookup. Enter either the entity’s full legal name or its 20-character LEI code.

A few practical tips:

• Use the full registered legal name as it appears in the MCA register or the equivalent foreign register, not the trading name.
• For common Indian names (think any “ABC Industries Private Limited”), filter by country = IN to narrow the list.
• If you have the entity’s CIN, BIC, or ISIN, you can use those instead — the GLEIF search supports them all.

If no LEI is found, that itself is information. The counterparty may not have applied for one yet, or may have allowed an LEI to lapse. Both situations matter for risk assessment.

Step 2: Read the Level 1 data

Once you open the LEI record, you will see Level 1 data — the “who is who” of the entity. The fields that matter most for due diligence are:

• Legal name — compare letter-for-letter against the contract or onboarding form. A mismatch is a red flag.
• Registered address and headquarters address — check that they match what the counterparty has supplied.
• Country of formation and jurisdiction — confirm where the entity is legally incorporated, not where it operates.
• Local registration authority and registration number — for Indian entities, this is typically the Ministry of Corporate Affairs and the CIN.
• Entity legal form — private limited, public limited, LLP, partnership, trust, and so on.
• Entity status — ACTIVE means the entity is still operating; INACTIVE means it is not.

Combined with the entity’s CIN and PAN, this gives you three independent reference points that should all line up. If the LEI record’s CIN does not match the CIN your counterparty has provided, pause and investigate before proceeding.

Pay attention to the last update field as well. An LEI that was last updated more than a year ago is either due for renewal or already lapsed. Either way, the reference data on the record may not reflect the entity’s current state. The LEI Issuer field tells you which Local Operating Unit (LOU) manages the record — in India, this is typically Legal Entity Identifier India Limited (LEIL), although Indian entities can hold LEIs issued by any accredited LOU worldwide.

Step 3: Check the LEI status carefully

The LEI status is the single most important field for compliance purposes. It tells you whether the LEI is currently valid for use in regulatory reporting and financial transactions.

LEI status	What it means
ISSUED	The LEI is current and valid. This is the status you want to see.
LAPSED	The entity has missed its annual renewal. The LEI cannot be used for regulatory reporting.
PENDING_TRANSFER	The LEI is being moved to a different LOU. It remains valid during the transfer.
TRANSFERRED	The LEI has moved to a new LOU. The new record is the authoritative one.
MERGED	The entity has been absorbed by another. The LEI is no longer in use.
RETIRED	The entity has ceased operations without being merged.
ANNULLED	The LEI was issued in error and is treated as never valid.
DUPLICATE	A second LEI was issued to the same entity. Use the surviving LEI.

A lapsed LEI is not just a technical issue. Under Indian rules — including the RBI’s March 2026 Master Direction consolidating LEI requirements across government securities, money market instruments, foreign exchange, and derivatives — a lapsed LEI has the same effect as having no LEI. Transactions can be paused, and reporting may fail.

The good news for Indian counterparties: India was the third-highest jurisdiction globally for renewal rates in Q1 2026, at 77.6%. That said, the remaining 22.4% of Indian LEIs do lapse at some point each year — so always check the status, never assume it.

A practical habit worth building: log the LEI status alongside other onboarding data, and re-check it quarterly for active counterparties and before any high-value transaction. The check itself takes seconds, but the cost of relying on a lapsed LEI in a regulatory filing is much higher.

Step 4: Use Level 2 data for group-level checks

Level 2 data — the “who owns whom” of the LEI system — shows the entity’s direct parent, ultimate parent, and any subsidiary entities that have reported their parent relationships. For counterparty due diligence, this is where you uncover:

• Group-level concentration risk — multiple counterparties that all roll up to the same ultimate parent
• Sanctions exposure — a clean immediate counterparty whose ultimate parent sits in a higher-risk jurisdiction
• Beneficial ownership signals — a starting point for further investigation, not a substitute for full UBO checks
• Connected party detection — relationships you might not have known existed

Level 2 data is reported by the entity itself, with exceptions allowed where the parent is not a legal entity, the relationship is not consolidated, or disclosure would breach local law. Treat reporting exceptions as questions worth asking, not automatic red flags.

Step 5: Combine LEI data with Indian identifiers

The LEI works best alongside India’s own corporate identifiers. A simple cross-check matrix:

• LEI to CIN — the LEI record should reference the same CIN your counterparty has provided. Verify on the MCA portal.
• LEI to PAN — the legal name on the LEI record should match the name on the PAN. See our explainer on LEI vs PAN for the differences.
• LEI to GSTIN — align the registered address on the LEI with the address on the GST registration.

Three matching reference points across the LEI, CIN, and PAN give you strong assurance that the entity in front of you is the entity you think it is.

Common pitfalls to avoid

A few mistakes show up repeatedly in Indian compliance reviews:

• Treating any LEI hit as a clean result. A counterparty may have multiple LEIs across group entities. Always confirm you are looking at the correct legal entity, not a parent or sister company with a similar name.
• Ignoring the renewal date. An ISSUED LEI that renews next month is, in practical terms, a status risk worth flagging on long-dated transactions.
• Skipping Level 2 data on smaller counterparties. Group-level concentration risk does not only come from large institutions. Smaller Indian counterparties often share parents in ways that are not immediately obvious.
• Relying solely on the LEI for sanctions screening. The LEI is a strong identity layer, but sanctions and PEP screening still need to run against names, dates of birth for individuals, and country lists. Use the LEI to make those screens more accurate, not to replace them.

Building this into your workflow

You do not need a new system to use LEI data well. Most Indian compliance teams can integrate it into existing onboarding workflows in three steps:

1. At onboarding, request the counterparty’s LEI alongside the CIN and PAN, and run a GLEIF lookup to confirm legal name, address, and ISSUED status.
2. At periodic review, re-check the LEI status — a lapsed LEI is an early signal that the counterparty’s compliance hygiene may be slipping.
3. At transaction time, flag any counterparty whose LEI status changes from ISSUED to LAPSED. Many regulatory reports will reject a lapsed LEI outright.

For higher-risk relationships, also pull Level 2 data and document the parent and subsidiary chain.

A small step that pays off

Counterparty due diligence is where many compliance frustrations begin — mismatched names, expired identifiers, unclear ownership. The LEI does not solve all of that, but it removes a surprising amount of friction by giving you one consistent identifier, one authoritative record, and one clear status field.

If your entity needs to obtain or renew an LEI so that your counterparties can verify you with the same confidence, LEI Register provides a fast, India-focused service. Keeping your own LEI active and accurate is the simplest favour you can do for everyone you do business with.