Introduction

The Insolvency and Bankruptcy Code, 2016 (IBC), provides a structured mechanism for resolving insolvency disputes, particularly through the Corporate Insolvency Resolution Process (CIRP). A critical aspect of this framework is the concept of a pre-existing disputes under IBC, which, if established, can render an application under Section 9 non-maintainable.

A key question arises: Can disputes raised or legal proceedings initiated after the issuance of a demand notice under Section 8 of the IBC qualify as pre-existing disputes, thereby invalidating a Section 9 application? Through statutory provisions and judicial precedents, this article explores the legal position on post-notice disputes and their impact on CIRP proceedings.

Legal Framework for Pre-Existing Disputes Under IBC

Statutory Provisions: Sections 8 and 9 of the IBC

Section 8(1) of the IBC requires an operational creditor to issue a demand notice to a corporate debtor for unpaid operational debt. The corporate debtor then has 10 days to either:

• Settle the debt, or
• Notify the creditor of a pre-existing dispute under Section 8(2).

If no resolution occurs, the operational creditor may file a Section 9 application to initiate CIRP. However, under Section 9(5)(ii)(d), the adjudicating authority must reject the application if a pre-existing dispute is established.

The IBC defines a “dispute” under Section 5(6) as a legal proceeding related to:

• The existence of the amount of debt,
• The quality of goods or services, or
• The breach of a representation or warranty.

Judicial Interpretation of Pre-Existing Disputes Under IBC

The Supreme Court in Mobilox Innovations Pvt. Ltd. v. Kirusa Software Pvt. Ltd. (2017) established that a dispute qualifies as “pre-existing” only if it existed before the receipt of a Section 8 notice. The Court held:

“The word ‘and’ in Section 8(2)(a) must be read as ‘or’ to prevent corporate debtors from using frivolous disputes to stall legitimate claims. However, the dispute must have arisen prior to the notice to qualify as pre-existing.”

This principle ensures that disputes manufactured after the notice cannot derail CIRP applications.

Judicial Precedents on Post-Notice Disputes

1. G.T. Polymers v. Keshava Medi Devices Pvt. Ltd. (NCLAT)

The corporate debtor filed a commercial suit after receiving a Section 8 notice, claiming it was a pre-existing dispute. The NCLAT rejected this argument, ruling:

“A dispute raised after a demand notice, even if formalized through litigation, cannot retroactively invalidate a Section 9 application.”

2. Vaibhav Aggarwal v. Sunil Sachdeva (NCLAT, 2023)

Here, the corporate debtor failed to respond to the demand notice but later claimed a pre-existing dispute. The tribunal reaffirmed that:

“Failure to reply within 10 days does not preclude proving a pre-existing dispute, but the dispute itself must have existed before the notice.”

3. Brandy Realty Services Ltd. v. Sir John Bakeries India Pvt. Ltd. (NCLAT)

The debtor attempted to introduce post-notice evidence of service quality disputes. The tribunal held that:

“Post-notice evidence can be considered only if it substantiates a pre-notice dispute.”

Evidentiary Standards for Pre-Existing Disputes

Courts have set clear requirements for proving a pre-existing dispute:

1. Burden of Proof – The corporate debtor must provide documentary evidence (emails, invoices, legal notices) showing that the dispute existed before the Section 8 notice.
2. Timing of Arbitration or Suit Initiation – Only disputes initiated before the demand notice can be considered.
3. Frivolous Defenses – Tactical disputes raised post-notice without supporting evidence are not entertained.

For instance, in R.S. Fuel Pvt. Ltd. v. Ankit Metal & Power Ltd., emails challenging service quality before the notice were deemed sufficient to establish a pre-existing dispute.

Critical Analysis of Conflicting Interpretations

Post-Notice Communications as Evidence of Pre-Existing Disputes

Some cases, like Greymatter Entertainment Pvt. Ltd. v. Pro Sportify Pvt. Ltd., allow corporate debtors to submit post-notice evidence if it corroborates a pre-existing dispute. The tribunal stated:

“Verbal disagreements before the notice, later documented in legal responses, may qualify as pre-existing disputes.”

Exceptions for Ongoing Negotiations

In iValue Advisors Pvt. Ltd. v. Srinagar Banihal Expressway Ltd., the NCLAT ruled that ongoing discussions do not amount to a dispute unless they were formally raised before the notice.

WhatsApp Messages and Informal Communications

In Kashyap Infraprojects Pvt. Ltd. v. Hi-Tech Sweet Water Technologies Pvt. Ltd., the NCLT noted that WhatsApp messages can be considered evidence, but their weight depends on corroboration through official documents.

Distinguishing Genuine vs. Tactical Disputes

Courts have drawn a distinction between:

• Genuine pre-existing disputes – Supported by prior evidence such as emails, termination notices, or legal correspondences.
• Tactical post-notice disputes – Raised solely to delay insolvency proceedings and unsupported by pre-notice evidence.

For instance, in Shashank Keshav Kalkar v. Raychem RPG Pvt. Ltd., a post-notice arbitration notice was dismissed as irrelevant.

Conclusion: The Imperative of Temporal Specificity 

The IBC aims to streamline debt resolution by preventing frivolous delays. Courts have consistently ruled that:

• A dispute must have originated before the Section 8 notice.
• Mere post-notice litigation or arbitration does not qualify as a pre-existing dispute.
• Documentary evidence supporting pre-notice disputes is essential.

This reinforces the IBC’s objective of balancing creditor rights with safeguards against misuse by debtors.

The post Post-Notice Disputes as Pre-Existing Disputes Under IBC: A Legal Analysis appeared first on Bhatt & Joshi Associates.

In October 2019, the e-commerce giant Flipkart India faced an unprecedented legal challenge when the National Company Law Tribunal admitted it into corporate insolvency proceedings following a petition by one of its suppliers. This case highlighted the growing importance of operational creditors under India’s insolvency framework and demonstrated how even profitable companies can face insolvency proceedings for payment defaults. The subsequent intervention by the Karnataka High Court brought into sharp focus the jurisdictional boundaries between tribunals and constitutional courts in insolvency matters.

Background of the Dispute

The dispute originated from a commercial relationship between Flipkart India and CloudWalker Streaming Technologies, a Mumbai-based company that imported and supplied LED televisions. CloudWalker entered into supply agreements with Flipkart in 2016, wherein the latter expressed keen interest in selling CloudWalker’s LED TV products, citing their superior technology and competitive advantages over other suppliers in the market.

According to CloudWalker’s petition before the NCLT, Flipkart placed substantial purchase orders for LED televisions worth Rs 103.62 crores. However, problems arose when Flipkart allegedly delayed accepting delivery of the ordered goods, initially citing lack of warehouse space. CloudWalker agreed to temporarily store the goods in their own warehouse, but Flipkart reportedly never collected the delivery despite making several excuses. The total outstanding operational debt claimed by CloudWalker amounted to Rs 26.95 crores, which included Rs 13.95 crores for the product cost, Rs 5.25 crores as customer charges, and Rs 7.75 crores as interest accumulated until March 2019.

The Legal Framework: Section 8 and Section 9 of the Insolvency and Bankruptcy Code

The Insolvency and Bankruptcy Code, 2016 [1] established a time-bound framework for resolving corporate insolvency in India. Under this framework, operational creditors are entities to whom operational debts are owed, including suppliers of goods and services. The procedural mechanism for operational creditors to initiate insolvency proceedings is governed by Sections 8 and 9 of the Code.

Before filing an application under Section 9, an operational creditor must first comply with Section 8, which requires delivery of a demand notice or invoice to the corporate debtor. The corporate debtor then has ten days to either make payment or notify the operational creditor about the existence of any dispute. Only if the operational creditor receives neither payment nor notice of dispute within this period can they file an application before the NCLT for initiating corporate insolvency resolution process.

The Supreme Court in Macquarie Bank Limited v. Shilpi Cable Technologies Ltd. [2] clarified that certain documentary requirements under Section 9(3)(c) are directory rather than mandatory in nature. The Court held that a certificate from a financial institution confirming non-payment, while important evidence, is not a threshold bar or condition precedent for triggering insolvency proceedings. This interpretation facilitated operational creditors, particularly foreign ones, in accessing the insolvency framework without facing unnecessary procedural hurdles.

CloudWalker’s Petition and Statutory Compliance

CloudWalker Streaming Technologies filed its application under Section 9 of the Insolvency and Bankruptcy Code before the Bengaluru bench of the NCLT in July 2019. The petition alleged that Flipkart had committed default on payment obligations despite repeated demands. CloudWalker claimed it had sent a demand notice under Section 8 to Flipkart, but received no response regarding either payment or existence of any dispute.

In its petition, CloudWalker asserted that the corporate debtor, Flipkart, was commercially insolvent and unable to pay its debts. The supplier argued that Flipkart had consistently and persistently failed, omitted, and neglected to discharge its admitted and acknowledged debt and liability. CloudWalker maintained that the corporate debtor company was not economically viable and posed a threat to commercial morality, justifying the need for insolvency proceedings.

Flipkart’s Defense and Contentions

Flipkart contested the petition vigorously before the NCLT, arguing that the application was not maintainable either in law or on facts and was liable to be rejected with exemplary costs. The e-commerce company presented evidence showing it had already paid Rs 85.57 crores toward the invoices raised by CloudWalker against total purchase orders worth Rs 103.62 crores.

Flipkart maintained that it was a profit-making company with sufficient financial strength and was actively conducting business operations. The company characterized the allegation that it lacked money to pay its liabilities or debts as baseless, frivolous, bereft of truth, and filed with malafide intentions. Flipkart further contended that an amount of Rs 42.96 crores payable to CloudWalker had been withheld due to deficiency in services provided by the supplier.

The central thrust of Flipkart’s defense was the existence of a pre-existing dispute regarding the quality and quantity of goods supplied, the terms of payment, and the calculation of amounts due. The company argued that CloudWalker was misusing the insolvency and bankruptcy framework as a debt recovery mechanism, which was contrary to the legislative intent behind the Code.

NCLT’s Order Admitting Insolvency Proceedings

On October 24, 2019, the Bengaluru bench of the NCLT, after examining the submissions and evidence presented by both parties, admitted CloudWalker’s petition and ordered the initiation of Corporate Insolvency Resolution Process against Flipkart India. The tribunal observed that Flipkart could not deny the existence of debt and that the company had defaulted on committed debt obligations.

The NCLT appointed Mr. Deepak Saruparia, a former Managing Director of Bank of Rajasthan, as the Interim Resolution Professional to conduct the corporate insolvency resolution process. The tribunal also imposed a moratorium under Section 14 of the Insolvency and Bankruptcy Code, which prohibited pending case judgments, sale of assets and property, and required the board of directors to extend full cooperation to the IRP. The NCLT directed that a report be filed on November 25, 2019, regarding the progress of the resolution process.

The moratorium provisions under Section 14 are crucial to the insolvency framework as they provide a standstill period during which creditors cannot enforce their claims individually. This allows for an orderly resolution process where all creditors can be treated fairly through the committee of creditors mechanism.

Karnataka High Court’s Intervention

Immediately upon the NCLT’s order being made available on November 5, 2019, Flipkart approached the Karnataka High Court by filing a writ petition under Articles 226 and 227 of the Constitution of India. The petition, presented before Justice B. Veerappa, challenged the jurisdiction of the NCLT to admit the company into corporate insolvency resolution process. Senior Advocate Dhyan Chinnappa appeared for Flipkart and made submissions contending that the NCLT had travelled beyond its jurisdiction in admitting the company into CIRP.

On October 25, 2019, just one day after the NCLT’s oral order, the Karnataka High Court exercised its extraordinary writ jurisdiction and granted a stay on the NCLT’s order. The High Court’s swift intervention prevented the insolvency process from proceeding further. The writ petition was taken up for hearing again on October 31, 2019, when the High Court directed continuation of the stay until the next date of hearing.

The legal basis for the High Court’s intervention deserves examination. Senior Counsel for Flipkart argued that the petition filed by CloudWalker was merely a claim for damages which the NCLT could not have adjudicated upon. The counsel submitted that there existed substantial disputes regarding the transaction, making the case inappropriate for resolution through the insolvency framework.

Jurisdictional Questions: High Court vs. NCLT

The Flipkart case raised important questions about the interplay between the jurisdiction of High Courts under Articles 226 and 227 of the Constitution and the statutory appellate mechanism under the Insolvency and Bankruptcy Code. The Code provides for a three-tier adjudicatory mechanism: the NCLT as the adjudicating authority, the National Company Law Appellate Tribunal as the appellate authority, and the Supreme Court as the final authority.

The Supreme Court in Embassy Property Developments Pvt. Ltd. v. State of Karnataka [3] had clarified the scope of High Court intervention in NCLT matters. The Court held that although the availability of a statutory alternative remedy generally bars writ jurisdiction, High Courts can entertain writ petitions when the challenge relates to lack of jurisdiction rather than wrongful exercise of available jurisdiction.

The Supreme Court observed that the NCLT, being a creature of special statute to discharge specific functions, cannot be elevated to the status of a superior court having power of judicial review over administrative action. When the NCLT acts without jurisdiction or as coram non judice, the High Court is justified in entertaining writ petitions despite the availability of statutory appeal before NCLAT.

In the context of the Flipkart case, the Karnataka High Court appears to have taken the view that entertaining the writ petition was appropriate given the circumstances. The case demonstrated that despite the complete code framework under the IBC, constitutional courts retain their supervisory jurisdiction over tribunals in exceptional situations.

The Concept of Pre-Existing Dispute

One of the central issues in the Flipkart-CloudWalker dispute was whether there existed a pre-existing dispute that would preclude admission of the insolvency petition. Section 9(5)(ii)(d) of the Code mandates that the NCLT must reject an application if notice of dispute has been received by the operational creditor or there is a record of dispute in the information utility.

The threshold for establishing a pre-existing dispute has been subject to judicial interpretation. The NCLT must satisfy itself that there exists a plausible contention requiring further investigation and that the dispute is not patently feeble or spurious. However, the tribunal is not required to undertake a detailed adjudication of the dispute at the admission stage.

Flipkart’s contention that substantial amounts had already been paid and that the balance was withheld due to service deficiencies suggested the existence of a dispute. However, CloudWalker argued that despite correspondence and demands, Flipkart had not formally raised the dispute before receiving the Section 8 demand notice, thereby failing to establish a pre-existing dispute within the meaning of the Code.

Moratorium and Its Implications

The moratorium imposed by the NCLT under Section 14 of the Code has far-reaching consequences for the corporate debtor. During the moratorium period, the institution of suits or continuation of pending suits or proceedings against the corporate debtor is prohibited. Additionally, no action can be taken to foreclose, recover, or enforce any security interest created by the corporate debtor. The transfer, encumbrance, alienation, or disposal of any assets or legal rights or beneficial interests of the corporate debtor is also restricted.

In the Flipkart case, the moratorium would have significantly impacted the company’s operations and its relationships with other creditors and stakeholders. The stay granted by the Karnataka High Court prevented these consequences from materializing, allowing Flipkart to continue its business operations under its existing management without the restrictions imposed by the moratorium.

Operational Creditors vs. Financial Creditors

The Flipkart case highlights the position of operational creditors under the IBC framework. While both operational and financial creditors can initiate insolvency proceedings, there are important procedural differences. Operational creditors must comply with the additional requirement under Section 8 of sending a demand notice, whereas financial creditors can directly approach the NCLT under Section 7.

Furthermore, financial creditors play a dominant role in the committee of creditors, with voting rights proportionate to their financial debt. Operational creditors, on the other hand, have limited participation rights and no voting rights in the committee of creditors unless their aggregate dues exceed ten percent of the debt.

Despite these limitations, Section 9 provides operational creditors with an important mechanism to recover dues and enforce payment discipline. The provision recognizes that suppliers and service providers are integral to the business ecosystem and deserve protection when corporate debtors default on operational debts.

Impact on E-Commerce Sector

The Flipkart insolvency proceedings, though stayed by the High Court, sent ripples through the e-commerce industry. The case demonstrated that even large, well-funded companies backed by international investors like Walmart could face insolvency petitions from suppliers over payment disputes. This highlighted the importance of maintaining transparent commercial relationships and resolving disputes promptly.

For suppliers and vendors working with e-commerce platforms, the case illustrated that the IBC framework could be utilized to enforce payment obligations. However, the swift stay granted by the High Court also showed that companies with substantial resources could effectively challenge insolvency admissions through superior courts.

Resolution and Current Status

Following the Karnataka High Court’s stay order, Flipkart issued a statement clarifying that it was not undergoing corporate insolvency resolution process and was continuing its operations on a going concern basis under its present management. The company emphasized that it maintains amicable relationships with its customers, vendors, and service providers.

The case was characterized by Flipkart as ongoing commercial litigation which the company was challenging. While the specific outcome of the writ petition and the ultimate resolution of the dispute between Flipkart and CloudWalker are not extensively documented in public records, the stay order effectively suspended the insolvency proceedings initiated by the NCLT.

Broader Implications for Insolvency Jurisprudence

The Flipkart case contributes to the evolving jurisprudence on corporate insolvency in India. It raises questions about the threshold for admitting insolvency petitions, the interpretation of pre-existing disputes, and the balance between creditor rights and debtor protections. The case also demonstrates the interplay between statutory tribunals and constitutional courts in the insolvency framework.

For operational creditors, the case serves as both encouragement and caution. While Section 9 provides a powerful tool for debt recovery, successful admission of a petition requires careful compliance with procedural requirements and the absence of genuine pre-existing disputes. Corporate debtors, on the other hand, can take comfort from the fact that improper or premature admissions can be challenged through constitutional remedies.

Conclusion

The Flipkart-CloudWalker insolvency dispute represents a significant case study in the application of the Insolvency and Bankruptcy Code to operational debt defaults. The NCLT’s admission of the petition demonstrated the tribunal’s willingness to hold even large corporations accountable for payment obligations. However, the Karnataka High Court’s prompt stay order illustrated that constitutional courts continue to exercise supervisory jurisdiction over tribunal decisions, particularly when jurisdictional questions arise.

The case underscores the importance of maintaining proper documentation, responding promptly to statutory notices, and resolving commercial disputes through appropriate mechanisms rather than allowing them to escalate into insolvency proceedings. As India’s insolvency framework matures, cases like Flipkart’s contribute to the development of jurisprudence that balances the interests of creditors, debtors, and the broader economy.

For the e-commerce sector and suppliers, the case provides valuable lessons about the legal remedies available under the IBC and the importance of maintaining transparent commercial relationships. The framework created by the Code continues to evolve through judicial interpretation, striking a balance between providing creditors with effective recovery mechanisms while protecting viable businesses from precipitate insolvency proceedings.

References

[1] Ministry of Law and Justice. (2016). The Insolvency and Bankruptcy Code, 2016. Retrieved from https://www.indiacode.nic.in/show-data?actid=AC_CEN_2_11_00055_201631_1517807328273&orderno=9 

[2] Macquarie Bank Limited v. Shilpi Cable Technologies Ltd., Civil Appeal No. 15135 of 2017, Supreme Court of India (2017). Retrieved from https://indiankanoon.org/doc/185937110/ 

[3] Embassy Property Developments Pvt. Ltd. v. State of Karnataka & Ors., (2019) SCC OnLine SC 1542, Supreme Court of India. Retrieved from https://ibclaw.in/whether-nclt-can-exercise-jurisdiction-over-matters-of-public-domain-in-ibc-proceedings-supreme-court-clarifies/?print=print 

[4] Business Today. (2019). NCLT orders Flipkart insolvency for Rs 27 crore default; company gets stay. Retrieved from https://www.businesstoday.in/latest/corporate/story/flipkart-faces-insolvency-litigation-for-rs-27-crore-default-gets-a-stay-237616-2019-11-06 

[5] Business Standard. (2019). Karnataka HC stays NCLT proceeding against co in insolvency case: Flipkart. Retrieved from https://www.business-standard.com/article/pti-stories/karnataka-hc-stays-nclt-proceeding-against-co-in-insolvency-case-flipkart-119110601630_1.html 

[6] LiveLaw. (2019). Karnataka HC Stays Insolvency Proceedings Against Flipkart. Retrieved from https://www.livelaw.in/corporate/nclt-bengaluru-initiates-insolvency-proceedings-against-flipkart-149547 

[7] The News Minute. (2019). NCLT Bengaluru initiates insolvency proceedings against Flipkart, HC stays order. Retrieved from https://www.thenewsminute.com/article/nclt-bengaluru-initiates-insolvency-proceedings-against-flipkart-hc-stays-order-111837 

[8] Moneylife. (2019). Karnataka HC Stays NCLT Order against Flipkart. Retrieved from https://www.moneylife.in/article/karnataka-hc-stays-nclt-order-against-flipkart/58599.html 

[9] IBC Laws. Writ Jurisdiction of High Court over matters decided by NCLT under IBC. Retrieved from https://ibclaw.in/writ-jurisdiction-of-high-court-over-matters-decided-by-nclt-by-rapaka-sravya/ 

Published and Authorized by Prapti Bhatt

The post Flipkart’s Corporate Insolvency Case Journey: NCLT Order and High Court Intervention appeared first on Bhatt & Joshi Associates.