Bharatiya Global Infomedia gets 3-month AGM extension from ROC
- Bharatiya Global Infomedia received a 3-month extension for its FY26 AGM
- Original AGM deadline was September 30, 2026, per Companies Act Section 96
- Delay attributed to a crash in the company's accounting software
- ROC Delhi-1 granted the extension following an application filed on September 2, 2026

*this image is generated using AI for illustrative purposes only.
Bharatiya Global Infomedia Limited has been granted a three-month extension by the Registrar of Companies (ROC) Delhi-1 to conduct its Annual General Meeting (AGM) for the financial year ended March 31, 2026.
The company disclosed the development in a filing with the National Stock Exchange and Bombay Stock Exchange on September 15, 2026. The original deadline to hold the meeting, as mandated under Section 96 of the Companies Act, 2013, was September 30, 2026.
Reason for Extension
The company attributed the delay to a technical issue involving a crash in its accounting software. This disruption prevented the timely finalization of accounts required for the AGM. The ROC order, dated September 15, 2026, explicitly cited this technical failure as the ground for granting the relief.
Regulatory Compliance
Bharatiya Global Infomedia filed the application for the extension under the proviso to Section 96(1) of the Companies Act, 2013. The ROC approved the request, extending the timeline by three months from the original due date.
The regulatory body advised the company to exercise caution in future compliance matters to ensure adherence to statutory timelines. The company stated it is taking this information on record in compliance with Regulation 30 of the SEBI (Listing Obligations and Disclosure Requirements) Regulations, 2015.
Will Bharatiya Global Infomedia face any additional regulatory penalties or increased scrutiny from SEBI due to this compliance lapse?
How might the accounting software failure impact investor confidence and the company's stock price in the short term?
What specific measures is the company implementing to prevent similar technical disruptions in future financial reporting cycles?
























