Sign in Subscribe
Enforcement

SEBI Warns Reliance's Compliance Officer: A Regulation 9(3) Monitoring Failure, Not a Tipping Case

Dolphin Infotek

• 5 min read
Share

Primary source: SEBI Administrative Warning Letter Ref. No. 1/14806/2026, dated June 24, 2026, issued to the Company Secretary & Compliance Officer of Reliance Industries Limited, disclosed via RIL's Regulation 30 filing dated July 6, 2026 (news coverage; letter filed with BSE/NSE).

Every FAQ post on this blog about Designated Persons, immediate relatives and trading-window monitoring has treated Regulation 9(3) as a background obligation — something the Compliance Officer is supposed to do. This week SEBI made that obligation the actual subject of an enforcement action, and it did so against India's largest listed company. The target of the warning was not the trading employees. It was the Company Secretary and Compliance Officer, personally, for failing to catch their trades.

Why this matters

Administrative warnings carry no monetary penalty and are, by SEBI's own description, "cautionary in nature." It would be easy to read this as a minor footnote. It shouldn't be. This is a live, named illustration of SEBI enforcing Regulation 9(3) and 2(1)(c) directly against a Compliance Officer — not the company, not the trading employees — for a monitoring failure. For every compliance officer who has ever wondered whether SEBI actually checks whether the surveillance system is catching trades in real time, this is the answer: yes, and it will trace the failure to you personally, even absent any allegation that you yourself traded or tipped anyone.

What SEBI found

SEBI investigated dealings in Reliance shares over the period June 1 to August 30, 2024. It found that three individuals — two employees and one immediate relative of an employee — traded in RIL shares while each was a connected person or deemed-connected immediate relative, in violation of Regulation 4(1) of the PIT Regulations and Section 12A(d) and (e) of the SEBI Act:

  • Harsh Jain (employee) — bought shares worth Rs. 6,385 on July 5, 2024.
  • Kamini Jain (immediate relative of employee Mahesh Goyal) — sold shares worth Rs. 1,09,695 on July 10, 2024, then bought shares worth Rs. 78,871 the very next day, July 11, 2024.
  • Hirai Umang Doshi (employee) — sold shares worth Rs. 47,625 on July 18, 2024.

These are small trade values by RIL's scale — none exceeds roughly Rs. 1.1 lakh — which is itself instructive: SEBI's letter does not suggest the trades were large enough to matter to the market. What mattered was that they happened at all, inside a UPSI window, without being caught.

The letter states plainly that "it is only after the receipt of communication from SEBI, the company RELIANCE took cognizance of the violations" — in other words, RIL's internal surveillance did not flag any of these three trades on its own. SEBI's investigation surfaced them from outside.

The Regulation 9(3) charge: the real point of the letter

The operative paragraph of the warning is short and unambiguous: "As per Regulation 9(3) and 2(1)(c) of PIT Regulations, it is the responsibility of the Compliance Officer to monitor trades, administer the code of conduct and monitor compliance with PIT Regulations. By failing to do so, the Compliance Officer has violated Regulation 9(3) and 2(1)(c) of PIT Regulations."

Note what is and is not alleged here. SEBI does not allege the Compliance Officer possessed UPSI, tipped anyone, or personally benefited. The violation is purely one of monitoring failure — the code of conduct existed, the trading employees were presumably on RIL's designated-persons list, and yet three trades by connected persons during a UPSI-sensitive window went undetected until SEBI's own investigation flagged them nearly two years later.

What SEBI intends: Regulation 9(3) was written to make the Compliance Officer function the frontline defence against insider trading — not just a policy custodian but an active monitor of actual trade data against the designated-persons list and known UPSI windows. This letter operationalises that intent: SEBI is signalling that "we had a code of conduct on paper" is not a defence if the surveillance built to enforce that code doesn't actually catch violations. The regulatory logic mirrors what SEBI has done with SDD audits and system-driven disclosures more broadly — moving from paper compliance to demonstrable, working detection systems.

Practical takeaway: This is a useful data point on scale, too. RIL is about as well-resourced a compliance function as exists in corporate India, with a large legal and secretarial team, and it still missed three sub-lakh trades by connected persons over a three-month window until SEBI told it. If your organisation's PIT surveillance relies on periodic manual reconciliation rather than automated, real-time matching of trading-account data against your designated-persons and immediate-relatives register, this is the moment to escalate that gap internally — using this letter as the concrete precedent.

What this does — and doesn't — mean for RIL

RIL's own disclosure to the exchanges is careful to note that "SEBI's letter is cautionary in nature and does not impose any financial or operational restrictions on the Company," and that the company "will take necessary steps to address the concern." That's an accurate characterisation: this is the lightest tool in SEBI's enforcement kit, well short of an adjudication order or penalty proceeding. But the letter also contains an explicit warning that recurrence will trigger "appropriate action... in accordance with the provisions of SEBI Act, 1992 and Rules and Regulations framed thereunder" — language that puts the Compliance Officer on notice that the next finding of this kind, even at the same low trade values, may not stay at the warning-letter level.

A note on the timeline

It's worth clocking the gap: the trades occurred in July 2024, the investigation period ran June–August 2024, and the warning letter is dated June 24, 2026 — nearly two years later. That lag is itself a reminder that SEBI's PIT investigations routinely reach back well beyond the trading window itself, using call data records, IP records and bank statements (as in the RHI Magnesita order covered separately this week) built up over a long investigation period. A trade that clears your internal system today is not necessarily beyond SEBI's later scrutiny.

Bottom line for your compliance checklist

  • Regulation 9(3) is not a paperwork obligation — SEBI will trace a monitoring failure to the named Compliance Officer even where there's no allegation of UPSI possession or tipping.
  • Confirm your trade-surveillance system actually cross-matches broker/depository trade data against your full designated-persons and immediate-relatives list, in near-real-time, rather than relying on self-reported pre-clearance alone.
  • Sub-lakh trade values are not a safe harbour — SEBI acted here on trades as small as Rs. 6,385; size did not factor into whether the violation was pursued.
  • "Immediate relative" trades (here, an employee's relative trading independently) are exactly as much your monitoring responsibility as the designated person's own trades — this is a live illustration of the deemed-connected-person coverage already discussed in our Designated Person & Immediate Relatives FAQ.
  • Where your own detection relies on the trading employee to self-report, consider whether that gap would survive the same test SEBI just applied to RIL — the company only became aware "after the receipt of communication from SEBI."

This post is an interpretation of a publicly disclosed SEBI communication for general informational purposes and does not constitute legal advice. Please verify details against the original filings on the BSE/NSE and SEBI's website and consult a qualified professional before relying on this analysis for compliance decisions.