Large-value bank transfers can fail operationally if the finance team treats the Legal Entity Identifier (LEI) as a last-minute banking field. For specified high-value payments through NEFT and RTGS, RBI expects LEI information to travel with the payment message. The practical task is not only to know your own LEI, but also to identify when the rule is triggered, obtain the counterparty LEI in advance, confirm that the identifiers are valid, and keep evidence with the payment approval file.
The primary source is the RBI FAQ on LEI for Large Value Transactions in Centralised Payment Systems. For issuance and renewal mechanics, Legal Entity Identifier India Limited (LEIL), which RBI recognises as an LEI issuer in India, publishes a detailed LEIL FAQ.
What is an LEI?
An LEI is a 20-character alphanumeric code used to uniquely identify legal entities participating in financial transactions. RBI explains that the system is intended to improve the quality and accuracy of financial data used for risk management. LEIs are issued through Local Operating Units accredited by the Global Legal Entity Identifier Foundation; RBI's FAQ specifically identifies LEIL as an issuer in India.
An LEI does not replace the bank account number, IFSC, payment approval, KYC or beneficiary verification. It is an additional legal-entity identifier used in the payment message where the RBI requirement applies.
When does the ₹50 crore NEFT/RTGS rule apply?
RBI states that all single payment transactions of ₹50 crore and above undertaken by entities, meaning non-individuals, should include the LEI information of both the remitter and the beneficiary. The requirement applies to NEFT and RTGS. For RTGS, RBI says the requirement covers both customer payments and inter-bank transactions that meet the criterion.
The words single payment transaction are important. The payment desk should therefore test each proposed transfer against the ₹50 crore threshold before release. Genuine transactions should follow the underlying commercial arrangement and bank controls rather than be structured around the threshold.
Three trigger questions for the payment desk
- Is the transfer being sent through NEFT or RTGS?
- Is the single payment amount ₹50 crore or more?
- Does the transaction involve an entity rather than falling within the individual-only exception described by RBI?
If the rule is triggered, the finance team should have the sender and beneficiary LEIs ready before the payment reaches final bank authorisation.
Government departments and government-owned entities are not treated the same
RBI's FAQ says the Central Government, State Governments and their Departments or Ministries do not need to obtain or mention an LEI for these NEFT/RTGS payments. However, that exemption does not extend to Government Corporations or Undertakings merely because they are government-owned. RBI states that such corporations and undertakings need an LEI, and their single NEFT/RTGS payment transactions of ₹50 crore and above should include remitter and beneficiary LEI information.
This distinction matters for treasury teams dealing with public-sector counterparties. Do not assume that a counterparty is exempt simply because its shareholder is the Government; identify whether the counterparty is actually a Government Department or Ministry, or a separate corporation or undertaking.
What about individual transactions?
RBI says LEI is not required for a customer transaction where both the remitter and beneficiary are individuals. Its FAQ separately states that where either or both parties are non-individuals, LEI requirements need to be considered. In practice, a bank may need to validate the parties and message fields before processing a large-value transfer, so mixed individual/entity cases should be checked with the remitting bank rather than resolved from an internal label alone.
Who must capture the LEI information?
RBI places the operational responsibility on the remitting bank to ensure that the LEI information for both sender and beneficiary is captured. The FAQ also says an inward transaction with inappropriate or missing LEI information should not be rejected by the beneficiary bank solely for that reason. After credit, however, the remitting and beneficiary banks should maintain valid and verified LEI information for payment transactions of ₹50 crore and above.
The bank operates the payment message, but the corporate customer should still maintain accurate master data and provide the counterparty identifier when required.
Worked example: ₹62 crore supplier payment
Assume an Indian company has an approved invoice and contractual payment obligation of ₹62 crore to a corporate supplier and plans to pay through RTGS. Because this is a single payment of at least ₹50 crore between non-individual entities, the payment workflow should capture both entities' LEIs.
A practical file would contain the payment approval, beneficiary bank details, both LEIs, evidence of validity and the bank-generated transaction reference after release. The LEI does not establish that the supplier bank account is genuine, so normal beneficiary-bank verification remains necessary.
LEI validity and renewal: do not check only the code
LEIL's current FAQ states that an LEI is valid for one year from the date of issuance or the last renewal date. If it is not renewed, its status becomes lapsed. Therefore, a treasury master should not store a 20-character code permanently without monitoring its status and next renewal date.
A useful control is to review LEI status before a material payment is due, especially for infrequent counterparties. If an LEI is close to renewal or appears lapsed, resolve the issue with the entity and bank before the payment date rather than during the final authorisation window.
Finance-team checklist before a large-value payment
- Test the payment: identify the rail, amount and nature of the parties before payment approval.
- Capture both identifiers: where the RBI rule applies, maintain the remitter and beneficiary LEIs in the payment support.
- Validate status: do not rely only on a code copied from an old invoice, email or vendor master.
- Separate LEI from bank verification: independently validate account number, IFSC, beneficiary name and change-of-bank requests.
- Document exemptions: if relying on the Government Department or Ministry exception, retain the basis for that classification.
- Plan renewal: track the entity's own LEI renewal date and build an escalation well before expiry.
- Check bank procedures: banks may have their own maker-checker screens, cut-offs, validations and documentation requirements around large payments.
Common mistakes to avoid
- Collecting only the payer's LEI and discovering at release time that the beneficiary LEI is also required.
- Assuming every government-owned company qualifies for the Government exemption.
- Treating an LEI as proof that bank-account details are authentic.
- Keeping a code in the vendor master without checking whether the LEI remains current.
- Applying the ₹50 crore payment rule mechanically to every LEI question. Other RBI, SEBI or financial-market frameworks can impose separate LEI requirements, so this particular threshold should not be treated as the universal LEI threshold for all purposes.
Practical takeaway
For NEFT and RTGS, the RBI large-value payment rule is easiest to manage as a pre-payment master-data control. Identify every single payment of ₹50 crore or more, determine whether the parties fall within the covered entity population, capture both LEIs where required, confirm their validity and retain the evidence with the payment file. The result is a cleaner treasury workflow and a much lower risk of discovering an LEI problem only when a time-sensitive payment is ready for release.
