Tax Management India. Com
Law and Practice  :  Digital eBook
Research is most exciting & rewarding
  TMI - Tax Management India. Com
Follow us:
  Facebook   Twitter   Linkedin   Telegram

Home Case Index All Cases Insolvency and Bankruptcy Insolvency and Bankruptcy + Tri Insolvency and Bankruptcy - 2019 (9) TMI Tri This

  • Login
  • Cases Cited
  • Summary

Forgot password       New User/ Regiser

⇒ Register to get Live Demo



 

2019 (9) TMI 892 - Tri - Insolvency and Bankruptcy


Issues Involved:
1. Whether the petitioner qualifies as an "Operational Creditor" under the Insolvency and Bankruptcy Code, 2016.
2. Whether there was a pre-existing dispute between the parties before the initiation of the Corporate Insolvency Resolution Process (CIRP).
3. Whether the debt claimed by the petitioner falls under the definition of "Operational Debt."
4. Whether the petition is maintainable under the Insolvency and Bankruptcy Code, 2016.

Issue-Wise Detailed Analysis:

1. Whether the petitioner qualifies as an "Operational Creditor" under the Insolvency and Bankruptcy Code, 2016:
The petitioner claimed to be an Operational Creditor, asserting that the Corporate Debtor defaulted in rendering services for which an advance payment of ?23,00,000 was made. The petitioner argued that the amount paid was for services to be rendered under a Master Services Agreement (MSA) dated 15.05.2016, which included four task orders. The Corporate Debtor's failure to deliver the final product dossiers by the stipulated date constituted a default. The tribunal acknowledged that the petitioner paid the amount for services, which qualifies as an operational debt, thereby recognizing the petitioner as an Operational Creditor.

2. Whether there was a pre-existing dispute between the parties before the initiation of the CIRP:
The Corporate Debtor contended that there was a pre-existing dispute regarding the payment of an additional ?7,50,000, which the petitioner had agreed to pay for additional expenses incurred by the Corporate Debtor. This dispute was evidenced by email correspondences and meeting minutes from May 2018, indicating that the petitioner acknowledged the liability but later imposed conditions on the payment. The tribunal found that the dispute over the additional payment existed before the demand notice was issued, thus constituting a pre-existing dispute.

3. Whether the debt claimed by the petitioner falls under the definition of "Operational Debt":
The petitioner argued that the debt arose from the non-completion of task orders under the MSA, making it an operational debt. The tribunal noted that the MSA and task orders were not fulfilled by the Corporate Debtor, and the petitioner had paid ?23,00,000 as an advance for these services. The tribunal concluded that the amount paid for services qualifies as operational debt under the Insolvency and Bankruptcy Code, 2016.

4. Whether the petition is maintainable under the Insolvency and Bankruptcy Code, 2016:
The Corporate Debtor argued that the petition is not maintainable due to the pre-existing dispute and the petitioner's failure to pay the additional ?7,50,000. The tribunal examined the correspondences and found that the petitioner had agreed to pay the additional amount but later imposed conditions for its payment. Given the pre-existing dispute, the tribunal held that the petition is not maintainable under the Insolvency and Bankruptcy Code, 2016.

Conclusion:
The tribunal concluded that there was a pre-existing dispute between the parties regarding the payment of ?7,50,000, which existed before the demand notice was issued. Consequently, the petition was rejected on the grounds of the pre-existing dispute, rendering it not maintainable under the Insolvency and Bankruptcy Code, 2016. The tribunal emphasized that the existence of a dispute prior to the demand notice precludes the initiation of the Corporate Insolvency Resolution Process.

 

 

 

 

Quick Updates:Latest Updates