Case Law Analysis

Section 92 Companies Act | Mere 'C/o' Listing in Records Does Not Impose Liability on Landlord : Meghalaya HC

The Meghalaya High Court ruled that a landlord listed as 'C/o' in company records cannot be held liable under Section 92 of the Companies Act, 2013, for non-compliance by the company. Liability requires functional responsibility, not mere administrative registration. This clarifies that property ownership alone does not attract regulatory penalties under corporate law.

Cassie News NetworkCassie News Network
Mar 11, 2026, 2:07 AM(Updated: Nov 3, 2026)
•5 min read
Be the first to share in your circle
Section 92 Companies Act | Mere 'C/o' Listing in Records Does Not Impose Liability on Landlord : Meghalaya HC

The Meghalaya High Court has delivered a significant clarification on the limits of criminal liability under the Companies Act, 2013, holding that a person’s name appearing as 'C/o' in company records due to property ownership cannot, by itself, justify criminal prosecution for non-filing of annual returns. This ruling reinforces the principle that liability must be tied to actual involvement in corporate management, not incidental association.

Background & Facts

The Dispute

The petitioner, Smti. Nirmali Kaur, is a landlord who leased her premises to M/s Suntechno Mutual Benefit India Limited for business operations. At the time of the company’s registration with the Registrar of Companies (ROC), her name and address were recorded as 'C/o' of the company, reflecting the location of its registered office. She had no role in the company’s management, no directorship, and no authority to make filings or decisions.

Procedural History

  • 2016: The ROC filed three criminal complaints under Section 92(5) of the Companies Act, 2013 against the company and its directors for failure to file annual returns and balance sheets for three consecutive years.
  • Simultaneously: Bailable warrants were issued against the petitioner solely because her name appeared as 'C/o' in the ROC’s registration records.
  • 2025: The petitioner filed three criminal petitions before the Meghalaya High Court seeking quashing of the proceedings and warrants.

Relief Sought

The petitioner sought quashing of all criminal proceedings and bailable warrants against her, arguing that her inclusion was purely administrative and lacked any basis in law or fact. She submitted a copy of the lease agreement to establish her status as a landlord with no corporate role.

The central question was whether the mere listing of a person’s name as 'C/o' in the ROC’s records - due to ownership of the company’s registered premises - constitutes sufficient grounds to invoke criminal liability under Section 92(5) of the Companies Act, 2013.

Arguments Presented

For the Petitioner

Learned counsel for the petitioner relied on the lease agreement to demonstrate that the petitioner had no involvement in the company’s affairs. He argued that Section 92(5) imposes liability only on officers in default, defined under Section 2(60) as directors, managers, secretaries, or other officers responsible for compliance. The petitioner, he submitted, was neither an officer nor a person in control of the company’s operations. He cited S. Sreesanth v. State of Rajasthan to emphasize that criminal liability cannot be imposed on persons without mens rea or functional responsibility.

For the Respondent

The ROC’s counsel conceded that the petitioner was not a director or officer of the company. He admitted that her name was included in the complaints only because the ROC’s database reflected her address as the registered office. However, he initially defended the inclusion as a procedural formality, arguing that the ROC was bound by the information submitted at the time of registration.

The Court's Analysis

The Court examined the statutory framework under Section 92(5) and the definition of 'officer in default' under Section 2(60). It held that liability under Section 92 is strictly personal and must be tied to functional responsibility, not administrative convenience. The Court rejected the notion that property ownership or address listing could substitute for legal accountability.

"The inclusion of the petitioner’s name as 'C/o' in the ROC records is a mere reflection of the registered office address and does not imply any role, responsibility, or control over the company’s compliance obligations."

The Court emphasized that criminal proceedings must be grounded in a prima facie case of culpable involvement. Since the petitioner had no authority to file returns, no access to company records, and no participation in management, her prosecution was legally unsustainable. The Court further noted that allowing such liability based on property ownership would open the floodgates to arbitrary prosecutions of landlords, property owners, and even service providers.

The Verdict

The petitioner succeeded. The Meghalaya High Court quashed all criminal proceedings and bailable warrants against her. It held that mere listing as 'C/o' due to property ownership does not attract criminal liability under Section 92 of the Companies Act, 2013. The ROC was directed to delete her name from its records.

What This Means For Similar Cases

C/o Listing Is Not a Proxy for Liability

  • Practitioners must challenge criminal complaints where individuals are named solely as 'C/o' without any corporate role or authority.
  • ROC filings based on address records cannot be used to impute liability under compliance-related offences.
  • Defence strategies should immediately raise jurisdictional and substantive defects in such cases.

Burden of Proof Lies with the Prosecution

  • The prosecution must establish a direct link between the accused and the failure to comply, not rely on registry entries.
  • Lease agreements, affidavits of non-involvement, and corporate governance documents are critical evidence to rebut presumptions of liability.
  • Courts will not permit criminal proceedings to proceed on the basis of administrative errors or outdated registration data.

Procedural Fairness Requires Rectification

  • Regulatory authorities must proactively correct erroneous records upon proof of non-involvement.
  • Failure to remove names after admission of error may constitute abuse of process.
  • Practitioners should file applications under Section 482 CrPC for quashing and simultaneous requests for record correction under Section 12 of the Companies Act, 2013.

Case Details

Smti. Nirmali Kaur v. The Registrar of Companies, Assam, Meghalaya, Tripura, Manipur, Nagaland, Mizoram and Arunachal Pradesh

2026:MLHC:163
PDF
Court
High Court of Meghalaya
Date
09 March 2026
Case Number
Crl.Petn.No. 81/2025, Crl.Petn.No.82/2025, Crl.Petn.No.83/2025
Bench
Revati Mohite Dere
Counsel
Pet: S. Thapa, B. Snaitang
Res: R. Debnath

Frequently Asked Questions

No. The Meghalaya HC held that liability under Section 92 applies only to officers in default as defined under Section 2(60). A landlord whose name appears as 'C/o' solely due to property ownership has no statutory duty to file returns and cannot be held criminally liable.
An 'officer in default' includes directors, managers, secretaries, or other officers responsible for the company’s compliance. Mere association with the company’s registered address, such as being a landlord, does not qualify a person as an officer in default.
Yes. The Court directed the ROC to delete the petitioner’s name from its records, affirming that regulatory authorities must correct erroneous entries upon proof of non-involvement. Failure to do so may amount to abuse of process.
0

Disclaimer

This article is for informational purposes only and does not constitute legal advice. The views expressed are based on the judgment analysis and should not be taken as professional counsel. Please consult with a qualified attorney for advice specific to your situation.