"It takes twenty years to build a reputation and five minutes to ruin it."
- Warren Buffett
Rajesh Exports had a rule for exactly this. The rule just never had to be followed.
THE SIGNAL
On June 3, 2026, SEBI ( Securities and Exchange Board of India) issued a 109-page interim order against Bengaluru-based Rajesh Exports Ltd., alleging the company misrepresented roughly ₹15.15 lakh crore in consolidated revenue between FY2020-21 and FY2024-25.
The core finding: revenue attributed to its Swiss subsidiary, Valcambi SA, could not be reconciled with Valcambi’s own audited standalone books.
SEBI also identified ₹926 crore moved through accounts linked to Chairman Rajesh Mehta with no board or audit committee approval, and ₹215.85 crore that flowed to Elest, a battery company Mehta co-founded with his brother, without proper related-party disclosure.
SEBI barred the company and Mehta from market access. The National Financial Reporting Authority has since opened its own investigation into the statutory auditor.
THE FAILURE POINT
The related-party approval process at Rajesh Exports existed in policy for years. It never once stopped a transaction initiated by the chairman himself. That’s the break. Not the absence of a rule, the absence of a rule with teeth.
SIGNAL WITHIN THE SIGNAL
For five years, the company optimized for one thing: a growth story large enough to support “world’s largest gold refiner” positioning.
It did not optimize for the thing that story depended on staying true, a subsidiary’s books that could reconcile with the parent’s claims. Pressure exceeded regulation for half a decade before anyone with subpoena power checked the math.
Worth checking where your own team sits on that same gap before assuming it's someone else's problem.
Score your gap →
BEHAVIOR UNDER PRESSURE
Leadership routed money through personal-linked accounts instead of the committee built to review exactly that kind of transaction.
Documentation for ₹1,035 crore in claimed African gold-mining investments never materialized. When the formal process would have slowed things down or invited a question, the process got skipped instead of engaged.
SYSTEM DRIVER - MOS
The approval gate was a step on a flowchart, not a functioning checkpoint.
Nothing in five years of related-party transactions shows the audit committee acting as a real constraint on the person the gate existed to constrain.
The fix isn’t a new policy.
It’s making the existing one binding on the one person most likely to route around it.
LEADER DRIVER - INTERNAL OPERATING SYSTEM (IOS) - REGULATE
The pattern reads as a leader who treated scrutiny as friction against a growth narrative he needed to protect, not as a check worth respecting.
That’s a read on behavior, not a confirmed internal state. But five years of transactions moving the same direction, around the same gate, is hard to explain as coincidence.
IF YOU DO ONE THING TODAY
Pull every related-party transaction from your organization’s last 24 months.
For each one, find the contemporaneous board or committee sign-off, not a retroactive justification written after the fact.
Where you can’t produce it, the gate isn’t real.
Fix it this week, before a regulator finds it for you.
FINAL SIGNAL
A gate that only stops people who weren’t going to walk through it anyway was never a gate.
CTA
Find out where your gap is before it costs you. Score your own gap here, takes about three minutes.
mosei.org/gap-diagnostic.html
SOURCES
SEBI interim order, June 3, 2026 (Rajesh Exports Ltd.); National Financial Reporting Authority investigation announcement.