The Supreme Court of India held that while the Adjudicating Authority (NCLT) can recall the admission of an insolvency application if it was initiated based on fraudulent or collusive jurisdictional facts, finding such fraud does not automatically require the termination of the entire Corporate Insolvency Resolution Process (CIRP). A Bench of Justice Pamidighantam Sri Narasimha and Justice Alok Aradhe clarified that because insolvency becomes an in rem proceeding upon admission, the NCLT must evaluate whether continuing CIRP benefits the broader body of creditors and stakeholders.

Court: Supreme Court of India

Bench: Justice Pamidighantam Sri Narasimha and Justice Alok Aradhe

Date of Decision: September 30, 2026

Subject Area: Insolvency & Bankruptcy Code, 2016 (IBC) | Section 9 (Operational Creditor) | Recall Powers of NCLT | Section 65 (Fraudulent Initiation) | Proceedings In Rem | Section 12A

Key Legal Principles Restated by the Supreme Court

1. Inherent Power to Recall Admission Orders

The Court held that the NCLT/NCLAT possesses the inherent power to recall an order admitting a Section 7, 9, or 10 application if jurisdictional facts were proven to be fraudulent or collusive. Manipulation of jurisdictional facts violates a public law duty not to deceive judicial forums.

2. Transition from In Personam to In Rem

  • Stage 1 (Pre-Admission): The original applicant retains carriage of the proceedings.
  • Stage 2 (Post-Admission): The proceedings lose their individual character and transform into an action in rem. The management vests in the Resolution Professional (RP), and all creditors become key stakeholders.

3. Fraudulent Origin Does Not Mandate CIRP Termination

Even if the original petition was collusive (e.g., between suspended directors and a friendly operational creditor), automatically terminating the entire CIRP is impermissible. The NCLT must independently determine whether continuing the CIRP serves the larger statutory objective of resolving the corporate debtor’s insolvency and protecting genuine stakeholders (such as homebuyers).

4. Disqualification and Penalties Under Section 65

Upon finding collusion or fraud:

  • The original applicant must be disqualified and ousted from participating in the CIRP.
  • The NCLT may trigger penalty proceedings under Section 65 of the IBC against the colluding parties.
  • The tribunal must consult the RP, the Committee of Creditors (CoC), and third-party stakeholders before deciding whether to sustain or terminate the CIRP.

Case History & Procedural Journey

  1. Background: An operational creditor initiated CIRP concerning the Greenopolis residential project in Gurgaon through a Section 9 application.
  2. NCLT Ruling: Discovered that the initiation was based on collusion between the applicant and suspended directors, but refused to recall the admission, claiming it lacked statutory power to withdraw/recall an admitted petition.
  3. NCLAT Ruling: Reversed the NCLT, held that recall powers exist for fraud, and terminated the entire CIRP.
  4. Supreme Court Decision: Held that both forums erred:
    • NCLT Erred: By wrongly holding it lacked powers to recall fraudulent admissions.
    • NCLAT Erred: By automatically terminating the CIRP without considering whether continuing the process served the wider interests of creditors and homebuyers.
    • Outcome: The Supreme Court restored the CIRP to the NCLT with directions to re-evaluate the continuation of proceedings after hearing the RP, CoC, and homebuyers.

Summary of Statutory Guidance

AspectPre-Admission StagePost-Admission Stage (With Fraud)
Nature of ActionIn Personam (Creditor vs. Debtor)In Rem (Collective Creditor Proceeding)
Applicant ControlApplicant controls withdrawal/proceedingsApplicant loses control; Section 12A applies
Impact of FraudApplication dismissed/rejected under Sec 65Admission recalled, applicant ousted, but CIRP can continue for other creditors
Primary EvaluatorAdjudicating Authority (NCLT)NCLT in consultation with RP, CoC, and Stakeholders

Leave a Reply

Your email address will not be published. Required fields are marked *

This field is required.

This field is required.