Mobilox Innovations Pvt. Ltd. v. Kirusa Software Pvt. Ltd.

The Legal Question Before the Court

Kirusa Software (operational creditor) filed an application under Section 9 of the Insolvency and Bankruptcy Code, 2016 to initiate a Corporate Insolvency Resolution Process (CIRP) against Mobilox Innovations for non-payment of service fees. Mobilox contended that the debt was disputed — it had counter-claims and had raised the dispute before the demand notice was served. The NCLT and NCLAT admitted the application. Mobilox appealed, raising the question of what standard applies when determining whether a "dispute" exists to resist a Section 9 application.

The Court's Decision

The court held that the NCLT must reject a Section 9 application if it is satisfied that there is a genuine dispute about the debt — even if only raised in the debtor's reply to the demand notice, provided the dispute was pre-existing and is not a sham defence created only to resist insolvency. The standard is not proof of the dispute at a full trial; it is whether the dispute is genuine — i.e., not spurious, hypothetical, illusory, or patently unmeritorious.

The court interpreted "dispute" in Section 5(6) of the IBC expansively: it includes a pending suit, arbitration proceedings, or a dispute raised in the reply to the demand notice — provided the dispute is bona fide and not contrived. The "existence of a dispute" is a jurisdictional fact: if it exists, the NCLT has no jurisdiction to admit the Section 9 application.

The Court's Reasoning

The bench drew a critical distinction between the Section 7 route (financial creditor) and the Section 9 route (operational creditor). For a financial creditor, a default alone suffices — there is no "dispute" defence available. The IBC treats financial creditors differently because they are lenders who have conducted structured due diligence and whose exposure is financial in the conventional sense.

Operational creditors, by contrast, typically arise from commercial disputes — service agreements, supply contracts, and trade relationships where the fact, quantum, and quality of performance are regularly contested. It would be commercially unreasonable and procedurally oppressive to allow an operational creditor to use the IBC as a debt collection weapon by initiating CIRP every time a trade debt is unpaid — even where a genuine contractual dispute exists. The IBC is not a substitute for a civil suit or arbitration to resolve disputed claims.

Practical Implications — What This Means Today

Mobilox is the governing authority on the Section 9 admission threshold. A corporate debtor facing an operational creditor's CIRP application can resist it by demonstrating a genuine pre-existing dispute — arising from quality objections, counter-claims, set-off rights, or contractual non-performance by the creditor itself. The defence is available even if raised only in the reply to the demand notice, provided it is substantive and not a post-hoc invention.

For businesses in Kerala and across India that routinely have disputes with vendors, service providers, or contractors, this ruling provides an important protection: a genuine trade dispute will prevent the nuclear option of CIRP from being weaponised over a contested invoice. However, the dispute must be documented and consistent — a well-drafted dispute correspondence trail maintained throughout the commercial relationship, not constructed at the moment a demand notice arrives, is the most reliable protection.

Relevant Statutory Provisions

• Section 9, Insolvency and Bankruptcy Code, 2016 — Operational creditor's application to initiate CIRP
• Section 5(6), Insolvency and Bankruptcy Code, 2016 — Definition of "dispute" — broad, includes pending arbitration/suit
• Section 8, Insolvency and Bankruptcy Code, 2016 — Demand notice by operational creditor
• Section 5(20), Insolvency and Bankruptcy Code, 2016 — Definition of "operational creditor"

Analysis by Vinode V. Luka, Advocate | Published: May 2026 | Last reviewed: May 2026