Can an Unpaid Vendor Use the IBC to Recover Dues?
8 min read
Yes, but only if the debt is genuinely undisputed.
In Mobilox Innovations Private Limited v. Kirusa Software Private Limited (2017), the Supreme Court confirmed that an operational creditor may use Section 9 of the Insolvency and Bankruptcy Code, 2016 to trigger the Corporate Insolvency Resolution Process when an operational debt exceeding Rs 1 lakh remains due and unpaid. The strict exception is a genuine dispute: if the corporate debtor shows that a real dispute existed before the demand notice was received and gave notice of it within the 10-day window, the National Company Law Tribunal must reject the application. A pending suit or arbitration is not required; the dispute must simply exist in fact and not be spurious.
MOBILOX INNOVATIONS PRIVATE LIMITED v. KIRUSA SOFTWARE PRIVATE LIMITED
Supreme Court of India · 2 judges
What the Court held
Appeal allowed and the NCLAT's judgment was set aside; Kirusa Software's Section 9 application was liable to be dismissed because a genuine dispute existed.
| Outcome | Appeal(s) allowed The Court accepted the appeal or petition, so it ruled in favour of the person who brought it. |
|---|---|
| Decided | 21 September 2017 |
| Case number | CIVIL APPEAL No. 9405/2017 |
| Judges | R.F. Nariman, Sanjay Kishan Kaul |
Original judgment link not recorded
The laws it applied
| Act | Sections |
|---|---|
| Insolvency and Bankruptcy Code, 2016 | 5(6), 8(2)(a), 9(1), 9(3) and 9(5) |
| Companies Act, 2013 | 271, as amended by Section 255 read with the Eleventh Schedule of the Code |
Why Mobilox Innovations Refused to Pay Kirusa Software’s Nach Baliye Invoice
Kirusa Software supplied toll-free telephone numbers and customised software for Star TV's “Nach Baliye” tele-voting. Mobilox Innovations managed the voting and issued purchase orders to Kirusa between October and December 2013. Kirusa performed the work and sent monthly invoices from December 2013 to November 2014.
On 26 December 2014 the two companies executed a non-disclosure agreement with effect from 1 November 2013. On 30 January 2015, Mobilox told Kirusa that it was withholding payment because Kirusa had displayed Mobilox's confidential client and campaign information on a public platform, which Mobilox said breached the agreement. Kirusa denied the breach on 10 February 2015 and demanded Rs 19,08,202.57 within one week. Mobilox replied on 26 February 2015 that it had lost business because of Kirusa's conduct.
The correspondence then became quiet. Kirusa sent e-mails on 20 June 2016 and 25 June 2016 trying to revive business relations and arrange a meeting. Mobilox replied on 28 June 2016. Nothing came of those exchanges, and on 19 September 2016 Mobilox reiterated that no payments were due because of the alleged breach.
Kirusa issued a demand notice under Section 8 of the Code on 23 December 2016 for Rs 20,08,202.55. Mobilox responded on 27 December 2016 that a serious and bona fide dispute existed. Kirusa filed its Section 9 application on 30 December 2016. On 19 January 2017, the NCLT orally told Kirusa to remove a defect in the application because it did not contain Mobilox's notice of dispute. Kirusa rectified this by an affidavit in compliance dated 24 January 2017, supplying various other documents too. The NCLT rejected the application on 27 January 2017, holding that the admitted receipt of Mobilox's dispute notice brought the claim within Section 9(5)(ii)(d). Kirusa's appeal to the NCLAT was allowed on 24 May 2017, with the NCLAT calling the defence vague, got-up and motivated to evade liability. The Supreme Court set aside that judgment.
The Section 8(2)(a) Deadlock: Reading “And” as “Or” Before the NCLT
Section 8 requires an operational creditor to deliver a demand notice or copy of an invoice. The corporate debtor then has 10 days to repay the debt or bring a dispute to the creditor's notice. If neither happens, the creditor may file a Section 9 application. If a notice of dispute has been received, Section 9(5)(ii)(d) requires the NCLT to reject the application.
The textual problem was the word “and” in Section 8(2)(a). Read literally, it seemed to require both a dispute and a pending suit or arbitration. The Supreme Court rejected that construction and held that “and” must be read as “or.” Otherwise, a dispute arising shortly before the demand notice could leave no time to file a suit, and a company could be dragged into bankruptcy over a contested invoice. The difference between CIRP and liquidation matters here: this judgment concerns only the trigger for a Corporate Insolvency Resolution Process, not liquidation.
The Supreme Court's Verdict: A Real Dispute, Not a Pending Suit, Stops Section 9
The Court traced the evolution of the definition of “dispute.” In the earlier Bill, the definition used “means” and described a “bona fide suit or arbitration proceeding.” In the Code, “includes” replaced “means,” and the word “bona fide” before “suit or arbitration proceedings” was deleted. Because “includes” is expansive, the NCLT could not confine a dispute to the three illustrative matters listed in Section 5(6).
The Court then set out the standard for rejecting a Section 9 application:
“So long as a dispute truly exists in fact and is not spurious, hypothetical or illusory, the adjudicating authority has to reject the application.”
Two points closed the loopholes:
- The NCLT cannot insist that a dispute already be pending in a court or arbitral tribunal. A genuine dispute existing before the demand notice is enough.
- The NCLT only checks whether the defence is plausible and not patently feeble or unsupported by evidence. It does not weigh the merits or predict whether the debtor will ultimately win.
The Court also rejected Mobilox's late argument that Kirusa's application should have been thrown out for want of a bank certificate. That objection was never raised before the NCLT, so it could not be used for the first time at the Supreme Court stage.
Real-World Scenarios: When Kirusa-Style Section 9 Applications Can and Cannot Proceed
Can the vendor trigger CIRP?
Debt is genuinely disputed before the demand notice
No. Section 9(5)(ii)(d) requires rejection if a notice of dispute has been received
Debt is due, unpaid, undisputed and above Rs 1 lakh
Yes. Section 9(5)(i) permits admission if the application is complete and no dispute notice exists
Debt is repaid after the invoice but before the application
No. Repayment of the unpaid operational debt is a ground for rejection under Section 9(5)(ii)(b)
Demand notice or invoice was never delivered to the debtor
No. Section 9(5)(ii)(c) requires rejection if the creditor has not delivered the invoice or notice
Debtor raises only a sham dispute with no evidence
Yes. A spurious, hypothetical or illusory defence does not stop the application; the dispute must truly exist in fact
Documents and Practical Steps to Apply the Mobilox Rule Before the NCLT
- If you are the creditor, keep the contract, purchase orders, invoices and correspondence showing delivery or performance. Send the demand notice in Form 3 or Form 4 and keep proof of service. File the Section 9 application in Form 5 before the NCLT with the invoice or demand notice, an affidavit that no dispute notice was received and a certificate from your bank confirming that no payment was made.
- If you are the debtor, use the 10-day window wisely. Send a detailed dispute notice identifying the real dispute and the material supporting it. A purely bare denial risks failing the Court's plausibility check.
- The NCLT must decide the application within 14 days. An appeal to the NCLAT lies within 30 days, extendable by 15 days. An appeal from the NCLAT to the Supreme Court lies within 45 days, with a further grace period not exceeding 15 days.
- Do not raise a missing document for the first time on appeal. In Mobilox, the NCLT never dismissed the application for want of the IDBI certificate, so the Supreme Court refused to entertain that objection at a later stage.
Common Questions on IBC Operational Debt and CIRP
1. Who initiates the liquidation process of a corporate debtor?
1. Who initiates the liquidation process of a corporate debtor?
Mobilox does not decide who initiates liquidation. It concerns the admission stage of a Section 9 application by an operational creditor before the NCLT.
2. What are the types of liquidation under the IBC?
2. What are the types of liquidation under the IBC?
The judgment does not classify liquidation under the IBC. It deals only with whether a genuine dispute requires rejection of a Section 9 application.
3. Who is the liquidator under the IBC and what does the liquidator do?
3. Who is the liquidator under the IBC and what does the liquidator do?
Mobilox does not discuss the liquidator's appointment or duties. Its holding is limited to the NCLT's obligation to reject an application under Section 9(5)(ii)(d) when a genuine dispute exists.
4. What is voluntary liquidation under the IBC?
4. What is voluntary liquidation under the IBC?
The judgment does not address voluntary liquidation. The dispute arose under Section 8 and Section 9 of the Code, which govern an operational creditor's application to trigger CIRP.
5. Who hears an operational creditor's application under Section 9 of the IBC?
5. Who hears an operational creditor's application under Section 9 of the IBC?
The National Company Law Tribunal hears it. An appeal lies to the National Company Law Appellate Tribunal, and the judgment notes the statutory limitation timelines for those appeals.
6. Can inability to pay debts alone still be a ground for winding up a company under the Companies Act?
6. Can inability to pay debts alone still be a ground for winding up a company under the Companies Act?
No. Section 255, read with the Eleventh Schedule of the Code, amended Section 271 of the Companies Act, 2013 so that inability to pay debts is no longer a ground for winding up a company. The Supreme Court held that the old Madhusudan rule therefore no longer applies.

Comments