PNB–Nirav Modi Case: LoU Controls, SWIFT Risk and Legal Status
The Punjab National Bank case exposed how high-value obligations could be created through messaging and guarantee processes without timely reflection in the bank’s core records.
Current position
In February 2018, PNB disclosed unauthorised transactions initially estimated at about US$1.77 billion. PNB’s financial results for the quarter ended 30 June 2018 later reported the amount involved at ₹14,356.84 crore. Investigations and proceedings followed against specified persons. RBI publicly denied reports that it had directed PNB to meet all commitments. Articles must distinguish the bank’s disclosure, agency allegations, charges, extradition proceedings and any final findings.
Key facts at a glance
| Initial PNB disclosure | About US$1.77 billion in February 2018 |
|---|---|
| Later PNB reporting | ₹14,356.84 crore in financial results for the quarter ended 30 June 2018 |
| Instrument | Letters of Undertaking and related overseas credit |
| Control issue | Messaging obligations were not properly reconciled with core systems |
| RBI clarification | RBI denied directing PNB to meet all commitments |
What this means in practice
1. Read the substance
Every external financial message must reconcile automatically to authorised limits and accounting records.
2. Measure the right risk
Maker-checker controls fail when access is shared, overrides are not monitored or staff rotate poorly.
3. Turn the lesson into a control
Legal status must be attached to each person and proceeding, not to the headline as a whole.
Practical example
If a SWIFT message creates a ₹100 crore obligation but the core banking system shows no corresponding entry, a daily exception report should block further transactions and trigger independent review.
A four-step decision framework
1. Identify the exact entity and period
Start with the legal entity, forum, reporting period or product actually covered. In this article, the first anchor is initial pnb disclosure: About US$1.77 billion in February 2018. Similar brand names or later events should not be assumed to have the same treatment.
2. Reconcile the number with its definition
The next anchor is instrument: Letters of Undertaking and related overseas credit. Check whether a figure is a balance, flow, claim, estimate, transaction value, accounting revenue or management-reported operating metric before comparing it.
3. Read the operative status
Use the latest applicable order, filing or policy statement and note its date. Do not rely on an older headline where an appeal, implementation step, later law or winding-up event has changed the position.
4. Convert the lesson into a control
The useful output is a documented action: Identify the regulated entity, product issuer and legal status relevant to PNB–Nirav Modi Case. Assign an owner, a deadline and the evidence needed to show that the control worked.
Action checklist
- Identify the regulated entity, product issuer and legal status relevant to PNB–Nirav Modi Case.
- Reconcile balances, rates, maturities and transaction references.
- Model liquidity and rate sensitivity under a realistic adverse scenario.
- Check official customer instructions before moving or committing funds.
- Escalate unresolved errors through the institution’s formal grievance route.
Evidence and document checklist
- Account statements and transaction references
- Product terms, sanction letter or rate-reset notice
- KYC and customer-service correspondence
- Liquidity or maturity analysis
- Regulator communication and complaint acknowledgement
Common mistakes and red flags
Common mistakes
- Assuming a brand and its regulated entity are identical
- Comparing balances, flows and revenue as though they are the same metric
- Ignoring reset dates, fees or maturity mismatch
- Sharing OTP, PIN or credentials during a dispute
Red flags
- Unexplained transaction or balance mismatch
- Concentrated short-term funding against long-term assets
- Repeated unresolved supervisory or audit issues
- Requests to use unofficial links or accounts
Escalation route
Complain first to the regulated entity. If eligible and unresolved, use RBI’s Complaint Management System or the applicable regulator and preserve every acknowledgement.