Intraday Leverage Error, Peak Margin Shortfall and Penalty Recovery
Nirmal Securities clears futures and options for about 2,300 clients. On 12 June, a bulk parameter update loaded an "intraday leverage multiplier" of 4x against 41 client codes and stayed live for a little over 40 minutes before a supervisor reverted it.
During the exchange's random peak-margin snapshot at 12:00, the aggregate margin shortfall across those 41 codes was ₹18.6 lakh. By 14:10 all of them had either squared off or brought in funds, and end-of-day margin collection was complete. The exchange nevertheless issued a penalty statement computed on the ₹18.6 lakh shortfall.
Nirmal's operations team debited the 41 clients pro rata for the penalty plus interest. One client, whose share is ₹34,000, writes in: he never asked for leverage, he lost money on the trade anyway, and he refuses to pay. Separately, internal audit finds that none of the 41 shortfall cases were reported to the exchange in the prescribed format.
1. Can Nirmal debit the penalty amount to the clients? Answer with reasoning, and identify what it can legitimately recover.
Read the worked answer
No. The duty to collect upfront and peak margin from a client rests on the member. SEBI has clarified that the penalty for short collection or non-collection of margins is borne by the broker and cannot be passed on to clients. The cause here is internal - a 4x multiplier loaded by the broker's own staff - so the client had no role in creating the shortfall at the peak snapshot, and no role in the delay in rectifying it.
The exchange penalty of ₹18.6 lakh-linked amount is therefore a cost of the broker's process failure, to be absorbed in Nirmal's profit and loss, and the ₹34,000 and all other pro rata debits should be reversed with interest and the client ledgers rectified. A refusal-to-reverse complaint would be difficult to defend in an exchange arbitration.
What Nirmal can recover: the actual margin that was due and remained unpaid after a proper demand (subject to the client's own contractual obligation), brokerage and statutory charges, and delayed-payment interest as provided in the member-client agreement. It cannot recover the regulatory penalty by dressing it up as "interest on delayed margin" - auditors and exchanges look through such re-labelling, and it converts a process lapse into a client-grievance and misreporting issue.
2. What should Nirmal have reported after the shortfall, and what exposure does the unreported cases create now?
Read the worked answer
The framework requires the member to bring the shortfall or non-collection to the notice of the affected clients and to report client-wise details of margin shortfall/non-collection to the exchange in the prescribed format within the stipulated five working days of settlement. The report is client-level, not a lump sum, and it must be truthful about the amounts and dates.
Because audit has now found that none of the 41 cases were reported, Nirmal faces a second, independent breach on top of the original shortfall. The correct handling is: do not backdate any filing; prepare a factual disclosure of the parameter error, the shortfall, the penalty, the non-reporting, and the remediation, place it before the Board/audit committee, and file it through the exchange's inspection/audit route proactively. Proactive disclosure with a documented root cause is treated very differently from a discovery during inspection.
Practical follow-through: a single owner in compliance should maintain a margin-reporting calendar with a maker-checker sign-off, and the internal audit plan should test a sample of shortfall days against exchange filings each quarter.
3. Redesign the control around risk-parameter changes so that a 4x multiplier cannot go live again.
Read the worked answer
Maker-checker in production. No single individual should be able to change a margin or leverage parameter. The change should be raised as a ticket with a reason, approved by a second authorised person, and pushed through a scheduled deployment - not edited in the live database.
Reconciliation to the exchange file. Pre-trade checks should be driven by the exchange-published margin file, not by an internally maintained multiplier. Any manual overlay should be visible in a daily exception report signed off by risk.
Utilisation alerts and snapshot simulation. Track each client's margin utilisation in real time and alert at 90% and 100%. Simulate the four random peak snapshots internally at fixed intervals so that the firm's own risk view cannot diverge from the exchange's.
Change log with consequences. Maintain a full audit trail of who changed what and when, review it monthly at the risk committee, and treat any production change without a ticket as a disciplinary matter. The ₹18.6 lakh shortfall and its penalty were a cheap lesson; the same error at 20x leverage on a volatile expiry day may not be.