India: NCLAT: Wider Definition Of "Dispute" To Resist An Action For Insolvency Under The Bankruptcy Code

  • The National Company Law Appellate Tribunal ("NCLAT") interprets the definition of "dispute" under Section 8 and 9 of the Insolvency and Bankruptcy Code ("Code") to include, apart from existing suits and arbitrations, any other actions, proceedings, conciliation, mediation pending before any Court or Tribunals under any existing act or law in relation to an operational debt.
  • Holds that an application initiating the insolvency resolution process would be rejected if the Corporate Debtor has raised the existence of a pending "dispute" with the applicant Operational Creditor.
  • Onus to prove existing dispute pending before competent court of law or authority on Corporate Debtor
  • National Company Law Tribunal ("NCLT") to form a prima facie view on the existence of dispute pertaining to debt and default and not go into adequacy of the same.


The NCLAT in a recent judgment, Kirusa Software Pvt. Ltd. ("Kirusa") v. Mobilox Innovations Pvt. Ltd. ("Mobilox") has broadly interpreted the term "dispute" to be of wide ambit and scope, stating that the term cannot be confined to pending proceedings or 'lis' within the limited ambit of a "suit or arbitration proceeding". Accordingly, an application for corporate insolvency resolution process ("CIRP") would be rejected if the Corporate Debtor has communicated the existence of a "dispute" which emanated prior to the initiation of the CIRP by an Operational Creditor. However, the NCLAT has also stated that a mere illusory dispute, raised for the first time by the Corporate Debtor while communicating the existence of a dispute, cannot be used as a tool to get an application for CIRP rejected by the Adjudicating Authority.

Brief Facts

Kirusa issued a demand notice to Mobilox as an Operational Creditor, demanding payment of certain dues. Mobilox issued a reply to the demand notice ("Mobilox Reply") inter alia stating that there exists certain serious and bona fide disputes between the parties and alleging a breach committed by Kirusa of the terms of a Non-Disclosure Agreement between the parties.

Kirusa filed an application before the NCLT, Mumbai for initiation of CIRP against Mobilox which was dismissed by the NCLT, Mumbai because a notice of dispute had been issued by Mobilox. Kirusa filed an appeal before the NCLAT, claiming that the Mobilox Reply does not constitute a notice of dispute as contemplated under the provisions of the Code.


What is the scope and ambit of the terms "dispute" and "existence of dispute" for determining the maintainability of an application filed by an Operational Creditor under Section 9 read with section 5 and 8 of the I&B Code?


The Appellate Tribunal, while relying on Section 9 (5) (ii) (d) of the Code, had to determine whether an application filed by an Operational Creditor should be rejected if the Corporate Debtor in response to a demand notice for payment of debt, raises the existence of a "dispute" with the Operational Creditor. (All relevant sections have been reproduced for reference as endnotes)

Therefore, the key question in the appeal hinged on the interpretation of the scope and ambit of the term "dispute" in context of Section 9 read with section 8 and 5(6) of the Code. The Appellate Tribunal stated that as per Section 9 the NCLT can admit an application filed by an Operational Creditor only if no notice raising a valid "dispute" is received by the Operational Creditor. Therefore, as per the NCLT the existence of a "dispute" in respect of the operational debt claimed by the Operational Creditor would preclude the NCLT from admitting an application for initiation of CIRP.

The Appellate Tribunal observed that Section 5(6) of the Code which defines "dispute" mentions only a pending "suit or arbitration proceedings". The Appellate Tribunal relied on the Supreme Court judgment of Mithlesh Singh v. Union of India 1 to observe that, while interpreting statutes Courts have always presumed the legislature to have used every word for a purpose and therefore every part of a statute should be given effect. Therefore, the inclusion of any term within a statute reflects deliberate legislative intent. Considering this, the Appellate Tribunal relied on the Supreme Court judgment of P. Kasilingam v. PSB College of Technology 2 to interpret the scope of a definition when it uses the expression "means" or "includes" individually or collectively. It identified that the term "means" refers to the restricted definition as provided for in the statute and does not leave any scope for expansion of the definition. Whereas the term "includes" enlarges the meaning of the defined expression so as to include the natural meaning of the defined term, along with the definition provided for in the statute. Therefore, the Appellate Tribunal, proceeded to examine the term "dispute" in its natural and ordinary meaning, and upon reading the Code as a whole observed that the scope of "dispute" should cover all disputes and not be limited to only two ways of disputing a demand made by the Operational Creditor.

The Appellate Tribunal went on to inspect the term considering the intent of the legislature and held that, if the legislature had intended the definition of 'dispute' to be exhaustive and limited to only a suit or arbitration proceeding, the sub-section would have simply read as "dispute means a dispute pending in arbitration or a suit" without making the requirement inclusive.

Considering the aforementioned observations, the Appellate Tribunal harmoniously constructed the definition of "dispute" appearing in section 5(6) read with the Section 8(2) of the Code to mean that the term "disputes" would apply to all kinds of disputes, in relation to a debt and default.

The Appellate Tribunal went on to conclude that definition of "dispute" under Section 8 and 9 of the Code, when interpreted with the object and purpose of the Code, would mean any proceeding initiated or pending before any consumer courts, tribunal, labour court, mediation or conciliation, as well as any action taken by a Corporate Debtor under any act or law such as replying to a notice under section 80 of the Code of Civil Procedure, 1908, or an action under section 59 of the Sale of Goods Act, 1930 or an action regarding the quality of goods provided by an Operational Creditor. It essentially, includes any dispute raised in relation to clause (a) or (b) or (c) of section 5(6).

However, the Appellate Tribunal importantly stated that a dispute would have to be "raised in a court of law or authority and proposed to be moved before the court of law or authority and not any got up or mala fide dispute just to stall the insolvency resolution process", for it to fall within the scope and ambit of section 8 and 9 of the Code. Therefore, the Corporate Debtor has the onus to prove that there exists a pending dispute raised before a competent court of law or authority prior to initiation of the CRIP.

Further, the Appellate Tribunal has also drawn a parallel between Section 8 and 9 of the Code with Section 8 of the recently amended Arbitration and Conciliation Act, 1996. It has stated that the NCLT, when presented with a notice of dispute, has to only prima facie decide whether there exists a dispute pertaining to the "debt" and "default" as referred to by the Operational Creditor. The Tribunal does not have the mandate to use its discretion to verify the adequacy of the dispute.

The Appellate Tribunal also highlighted the following differences between the initiation of a CIRP by a Financial and Operational Creditor


Financial Creditor

Operational Creditor

Filling of Application

No condition precedent

Needs to issue a notice a demand of unpaid debt/invoice demanding payment prior to filing

Right to file Application

Can file on default

Accrues after expiry of ten days from the date of delivery of the demand notice

Notice of dispute

No provision

Corporate Debtor can respond to the demand notice within ten days by issuing a notice of dispute

Admission/rejection of Application

Application admitted if existence of debt and occurrence of default ascertained

Application admitted in case there is no notice of dispute

Application rejected if there is a notice raising a valid dispute under the provisions of the Code


The I&B Code was enacted as a means to consolidate the already existing, but segregated laws in the country with regard to insolvency and bankruptcy. The Code is a positive step forward in creating a single platform for resolution of disputes and insolvency. However, the Code like any other nascent legislation is not free from ambiguity, one of the key interpretational issues that has arisen with respect to initiation of CIRP by an Operational Creditor is the scope of the definition of "dispute" as appearing in Section 8 and 9 of the Code.

Prior to the present judgment of the NCLAT, there were various conflicting decisions interpreting the meaning of the term "dispute". In Essar Projects India Ltd vs MCL Global Steel, 3 the Tribunal, while interpreting the definition of 'dispute' under the Code, held that 'dispute in existence' means and includes raising a dispute in a court of law or arbitral tribunal before the receipt of the Demand Notice issued under Section 8 of the Code. It also stated that a dispute raised by a Corporate Debtor for the first time in its reply to the demand notice cannot be treated as a dispute in existence in the absence of the same being disputed before any court of law prior to the receipt of the demand notice. The same view was taken by the NCLT in the case of Deutsche Forfait vs Uttam Galva Steel. 4 It said that the NCLT had made it clear that such a dispute must be validated by raising the issues in dispute before a court or arbitral tribunal prior to the date of receipt of a demand notice. Merely contesting the amount in question did not constitute a 'dispute' within the meaning of the Code. However, the Delhi NCLT had taken the exact opposite view while stating that a dispute raised post issuance of a demand notice could also be considered as a valid dispute under the scope of section 9 of the Code.

As is evident, the previously ambiguous position on the scope of the definition of "dispute" has been finally resolved by the NCLAT, by stating the following:

  • The term "dispute" must be interpreted in a wide an inclusive manner to mean any proceeding which had been initiated by the Corporate Debtor before any competent court of law or authority;
  • The dispute should be in respect of (a) existence of the amount of debt (b) quality of goods and services or (c) breach of representation and warranty;
  • The dispute should be raised prior to the issuance of a demand notice by the Operational Creditor;
  • The Corporate Debtor would have to particularize and prove the dispute in respect of the existence of the "debt" and the "default"
  • The dispute cannot be a mala fide, moonshine defense raised to defeat the insolvency proceedings.
  • The NCLT would have to prima facie verify the existence of the pending dispute and not judge the adequacy of the same

The previous law on insolvency of corporate entities had a similar position, whereby if the creditors' debt was bona fide disputed on substantial grounds, the Court would ideally dismiss the winding up petition and leave the creditor to establish his claim in a separate action. A dispute would be considered substantial and genuine if it was bona fide and not spurious, speculative, illusory or misconceived. 5

The initiation of CIRP by an Operational Creditor is a novel phenomenon in the Indian legal and corporate scenario and can prove to be a powerful tool in realizing operational debts even when the Corporate Debtor is not insolvent. Therefore, in light of the clarifications issued by the NCLAT and the requirements of the Code itself it has become vitally important and prudent for a Corporate Debtor to proactively take steps to raise a dispute in respect of unpaid invoices/dues of an Operational Creditor and put on record the existence of deficiency in service or goods or any breach of representation/warranty or any counter claim that the Debtor might have against the Operational Creditor so as to pre-empt any insolvency proceedings under Section 9 of the Code.

For Relevant section, please click here.


1 (2003) 3 SCC 309

21995 Supp. (2) SCC 348

3CP No. 20/1 & BP/NCLT/MAH/2017

4C.P. no. 45/I&BP/NCLT/MAH/2017

5IBA Health(India) Private Ltd. Vs Info-Drive Systems Sdn.Bhd. (2010(10) SCC 553); Mediqup Systems Pvt. Ltd. vs Proxima Medical System G.M.B.H (AIR 2005 SC 4175)

The content of this article is intended to provide a general guide to the subject matter. Specialist advice should be sought about your specific circumstances.

To print this article, all you need is to be registered on

Click to Login as an existing user or Register so you can print this article.

In association with
Related Video
Up-coming Events Search
Font Size:
Mondaq on Twitter
Register for Access and our Free Biweekly Alert for
This service is completely free. Access 250,000 archived articles from 100+ countries and get a personalised email twice a week covering developments (and yes, our lawyers like to think you’ve read our Disclaimer).
Email Address
Company Name
Confirm Password
Mondaq Topics -- Select your Interests
 Law Performance
 Law Practice
 Media & IT
 Real Estate
 Wealth Mgt
Asia Pacific
European Union
Latin America
Middle East
United States
Worldwide Updates
Check to state you have read and
agree to our Terms and Conditions

Terms & Conditions and Privacy Statement (the Website) is owned and managed by Mondaq Ltd and as a user you are granted a non-exclusive, revocable license to access the Website under its terms and conditions of use. Your use of the Website constitutes your agreement to the following terms and conditions of use. Mondaq Ltd may terminate your use of the Website if you are in breach of these terms and conditions or if Mondaq Ltd decides to terminate your license of use for whatever reason.

Use of

You may use the Website but are required to register as a user if you wish to read the full text of the content and articles available (the Content). You may not modify, publish, transmit, transfer or sell, reproduce, create derivative works from, distribute, perform, link, display, or in any way exploit any of the Content, in whole or in part, except as expressly permitted in these terms & conditions or with the prior written consent of Mondaq Ltd. You may not use electronic or other means to extract details or information about’s content, users or contributors in order to offer them any services or products which compete directly or indirectly with Mondaq Ltd’s services and products.


Mondaq Ltd and/or its respective suppliers make no representations about the suitability of the information contained in the documents and related graphics published on this server for any purpose. All such documents and related graphics are provided "as is" without warranty of any kind. Mondaq Ltd and/or its respective suppliers hereby disclaim all warranties and conditions with regard to this information, including all implied warranties and conditions of merchantability, fitness for a particular purpose, title and non-infringement. In no event shall Mondaq Ltd and/or its respective suppliers be liable for any special, indirect or consequential damages or any damages whatsoever resulting from loss of use, data or profits, whether in an action of contract, negligence or other tortious action, arising out of or in connection with the use or performance of information available from this server.

The documents and related graphics published on this server could include technical inaccuracies or typographical errors. Changes are periodically added to the information herein. Mondaq Ltd and/or its respective suppliers may make improvements and/or changes in the product(s) and/or the program(s) described herein at any time.


Mondaq Ltd requires you to register and provide information that personally identifies you, including what sort of information you are interested in, for three primary purposes:

  • To allow you to personalize the Mondaq websites you are visiting.
  • To enable features such as password reminder, newsletter alerts, email a colleague, and linking from Mondaq (and its affiliate sites) to your website.
  • To produce demographic feedback for our information providers who provide information free for your use.

Mondaq (and its affiliate sites) do not sell or provide your details to third parties other than information providers. The reason we provide our information providers with this information is so that they can measure the response their articles are receiving and provide you with information about their products and services.

If you do not want us to provide your name and email address you may opt out by clicking here .

If you do not wish to receive any future announcements of products and services offered by Mondaq by clicking here .

Information Collection and Use

We require site users to register with Mondaq (and its affiliate sites) to view the free information on the site. We also collect information from our users at several different points on the websites: this is so that we can customise the sites according to individual usage, provide 'session-aware' functionality, and ensure that content is acquired and developed appropriately. This gives us an overall picture of our user profiles, which in turn shows to our Editorial Contributors the type of person they are reaching by posting articles on Mondaq (and its affiliate sites) – meaning more free content for registered users.

We are only able to provide the material on the Mondaq (and its affiliate sites) site free to site visitors because we can pass on information about the pages that users are viewing and the personal information users provide to us (e.g. email addresses) to reputable contributing firms such as law firms who author those pages. We do not sell or rent information to anyone else other than the authors of those pages, who may change from time to time. Should you wish us not to disclose your details to any of these parties, please tick the box above or tick the box marked "Opt out of Registration Information Disclosure" on the Your Profile page. We and our author organisations may only contact you via email or other means if you allow us to do so. Users can opt out of contact when they register on the site, or send an email to with “no disclosure” in the subject heading

Mondaq News Alerts

In order to receive Mondaq News Alerts, users have to complete a separate registration form. This is a personalised service where users choose regions and topics of interest and we send it only to those users who have requested it. Users can stop receiving these Alerts by going to the Mondaq News Alerts page and deselecting all interest areas. In the same way users can amend their personal preferences to add or remove subject areas.


A cookie is a small text file written to a user’s hard drive that contains an identifying user number. The cookies do not contain any personal information about users. We use the cookie so users do not have to log in every time they use the service and the cookie will automatically expire if you do not visit the Mondaq website (or its affiliate sites) for 12 months. We also use the cookie to personalise a user's experience of the site (for example to show information specific to a user's region). As the Mondaq sites are fully personalised and cookies are essential to its core technology the site will function unpredictably with browsers that do not support cookies - or where cookies are disabled (in these circumstances we advise you to attempt to locate the information you require elsewhere on the web). However if you are concerned about the presence of a Mondaq cookie on your machine you can also choose to expire the cookie immediately (remove it) by selecting the 'Log Off' menu option as the last thing you do when you use the site.

Some of our business partners may use cookies on our site (for example, advertisers). However, we have no access to or control over these cookies and we are not aware of any at present that do so.

Log Files

We use IP addresses to analyse trends, administer the site, track movement, and gather broad demographic information for aggregate use. IP addresses are not linked to personally identifiable information.


This web site contains links to other sites. Please be aware that Mondaq (or its affiliate sites) are not responsible for the privacy practices of such other sites. We encourage our users to be aware when they leave our site and to read the privacy statements of these third party sites. This privacy statement applies solely to information collected by this Web site.

Surveys & Contests

From time-to-time our site requests information from users via surveys or contests. Participation in these surveys or contests is completely voluntary and the user therefore has a choice whether or not to disclose any information requested. Information requested may include contact information (such as name and delivery address), and demographic information (such as postcode, age level). Contact information will be used to notify the winners and award prizes. Survey information will be used for purposes of monitoring or improving the functionality of the site.


If a user elects to use our referral service for informing a friend about our site, we ask them for the friend’s name and email address. Mondaq stores this information and may contact the friend to invite them to register with Mondaq, but they will not be contacted more than once. The friend may contact Mondaq to request the removal of this information from our database.


From time to time Mondaq may send you emails promoting Mondaq services including new services. You may opt out of receiving such emails by clicking below.

*** If you do not wish to receive any future announcements of services offered by Mondaq you may opt out by clicking here .


This website takes every reasonable precaution to protect our users’ information. When users submit sensitive information via the website, your information is protected using firewalls and other security technology. If you have any questions about the security at our website, you can send an email to

Correcting/Updating Personal Information

If a user’s personally identifiable information changes (such as postcode), or if a user no longer desires our service, we will endeavour to provide a way to correct, update or remove that user’s personal data provided to us. This can usually be done at the “Your Profile” page or by sending an email to

Notification of Changes

If we decide to change our Terms & Conditions or Privacy Policy, we will post those changes on our site so our users are always aware of what information we collect, how we use it, and under what circumstances, if any, we disclose it. If at any point we decide to use personally identifiable information in a manner different from that stated at the time it was collected, we will notify users by way of an email. Users will have a choice as to whether or not we use their information in this different manner. We will use information in accordance with the privacy policy under which the information was collected.

How to contact Mondaq

You can contact us with comments or queries at

If for some reason you believe Mondaq Ltd. has not adhered to these principles, please notify us by e-mail at and we will use commercially reasonable efforts to determine and correct the problem promptly.