Quick Summary
On August 12, 2025, SEBI Adjudicating Officer Amar Navlani fined Motilal Oswal Financial Services ₹11 lakh, the second largest of the five penalties since 2022. She upheld delayed return of idle client funds in 649 instances, ledger reporting errors, admin terminals used by unapproved users and five technical resilience lapses. She gave the firm the benefit of doubt on peak ledger reporting. This page tells the story and what it means for your unused balance.
Most traders have a few thousand rupees sitting idle in their broker account. They forget it, and the broker is supposed to remember it.
SEBI’s rule says the broker must send that money back on time.
This order shows where one large broker fell short, and where it did not.
How Did the January 2024 Inspection on Motilal Oswal Unfold?
In January 2024, SEBI and the exchanges carried out a joint inspection. They looked at April 1, 2022 to October 31, 2023.
SEBI sent its findings on April 26, 2024, and the firm replied on May 20.
A show cause notice followed on September 27, 2024, and the hearing was held on November 7, 2024.
The order arrived on August 12, 2025, after nearly nine months of further process.
Was Idle Client Money Returned on Time?
The first allegation was the one that touches ordinary investors most.
The rule says that if a client with a credit balance has not traded for 30 days, the broker must return the balance within the next three working days.
SEBI first alleged 1,928 instances across 1,794 clients, worth ₹6.33 crore. Then the firm began to chip away at the number.
In 1,182 instances, the client had traded that month. In another 97, the client had added fresh funds and traded within 30 days.
That left 649 instances. For these, the firm admitted the delay, blamed gaps in its software logic and said the clients were settled later.
The officer held the finding established.
The ₹6.33 crore figure covers all 1,928 instances, not the 649. The officer does not confirm the rupee value of the 649.
Credit balances also sat at the center of another order. The Motilal Oswal SEBI Order January 2025 found securities of 3,574 clients with credit balances moved to the wrong account.
Where Did Motilal Oswal Win on Ledger Reporting?
Brokers report clients’ cash balances to the exchange, and SEBI raised errors in end of day balances, peak balances and uncleared cheques.
On end of day balances, the officer upheld 12 instances.
Eleven came from depository charges that were left out, ranging from ₹17.70 to ₹5,959.50, and one from a surveillance margin deposit that was missed.
On peak balances, the story turned. The dispute centered on how to treat the previous day’s debit bill, and an exchange circular of September 2024 later said such a bill need not be deducted.
The officer did not uphold that finding.
A fair retelling has to include this. It is a point where the firm’s argument won.
Who Was Using the Admin Terminals?
The inspectors then found three admin terminals.
One was used through remote access, and two were used by someone other than the approved user.
The firm explained that these were risk management terminals, used over its internal network, with no client trades.
The officer noted that the firm itself accepted the terminals were used by others, and held the finding established.
Related article: Motilal Oswal SEBI Order June 2025, the same unapproved-user problem, with four NSE terminals run by people other than the approved users.
What Happened When the Systems Were Tested?
The last chapter is about technology.
An exchange circular of December 2022 sets rules for how brokers handle technical glitches, and the officer held that the firm fell short on five points.
A root cause analysis due on December 18, 2023 for an incident on December 4 was filed a day late.
A capacity alert was set at 90 percent, not the required 70 percent.
The firm calculated peak load by averaging three years instead of using the peak.
It also did not trade live from its disaster recovery site from April to September 2023.
Finally, the disaster recovery site did not meet the location rule until a compliant site went live on February 29, 2024.
The officer wrote that later steps, such as a load test in August 2024, do not absolve violations in the inspection period.
How Did the Officer Decide on ₹11 Lakh In Motilal Oswal SEBI Order August 2025?
She imposed a single penalty of ₹11 lakh under Section 15HB, with no breakup by finding and recorded no quantified gain or investor loss.
She also listed the firm’s earlier penalty orders, from February 2020, April 2022, December 2024, January 2025 and June 2025.
Five orders over five years prompt many investors to ask, is Motilal Oswal safe? A single order can’t answer that.
This one covers idle balances and system resilience, so check your own ledger for the same things.
What Does This Mean for Your Unused Balance?
Look at your ledger for idle cash. If you have not traded for a month, expect your broker to return it within days, not months.
If it does not, write to the broker and keep proof.
Your broker’s messages only help if they reach you. The Motilal Oswal SEBI Order December 2024 held the mobile and email mismatches on NSE established, so confirm the details on file are yours.
A SEBI SCORES complaint puts the delay on SEBI’s system, and a SMART ODR complaint portal filing can help settle it online.
If it stays unresolved, you can file complaint in NSE and move to arbitration.
For the full set of penalty orders, see our master page on the SEBI penalty against Motilal Oswal.
Is your broker holding your money?
We read your ledger, check it against SEBI’s return timelines and draft the complaint. Register with us for a free consultation.
Report. Recover. Stay Fraud Free.
Frequently Asked Questions
Under the rule applied in this order, within three working days after 30 calendar days of no trading. This is the rule as cited in the order.
No. The officer recorded no quantified investor loss. The findings are process and compliance failures.
You can find the original SEBI order on the official SEBI website under Orders section.
Add us as a preferred source on Google »
