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 + AT Insolvency and Bankruptcy - 2022 (12) TMI AT This

  • Login
  • Cases Cited
  • Referred In
  • Summary

Forgot password       New User/ Regiser

⇒ Register to get Live Demo



 

2022 (12) TMI 144 - AT - Insolvency and Bankruptcy


Issues Involved:

1. Whether the debt claimed by appellants can be considered as financial debt under Section 5(8) of the I & B Code 2016?
2. Whether the impugned order passed by the Adjudicating Authority was incorrect in holding the Appellants as related parties under the provisions of the I & B Code 2016 and IBBI rules and regulations?
3. Whether the Resolution Plan was approved correctly when no provision had been made for the claims of the Appellants?

Issue-wise Detailed Analysis:

Issue No. (I): Whether the debt claimed by appellants can be considered as financial debt under Section 5(8) of the I & B Code 2016?

The appellants claimed that their investment of more than Rs. 17 Crores should be considered as a financial debt, thus qualifying them as financial creditors. The debt, as defined under Section 3(11) of IBC, includes financial debt and operational debt. Financial debt, under Section 5(8) of the I & B Code, 2016, is defined as a debt disbursed against the consideration for the time value of money. The Tribunal referred to the judgment in Phoenix Arc Pvt. Ltd. vs Ketulbhai Ramubhai Patel, which emphasized that the debt must carry the essential elements of disbursal against the consideration for the time value of money. The Tribunal found that the appellants' investment did not meet this criterion as it lacked the direct element of time value of money. Therefore, the investment could not be classified as financial debt, and the appellants could not be treated as financial creditors.

Issue No. (II): Whether the impugned order passed by the Adjudicating Authority was incorrect in holding the Appellants as related parties under the provisions of the I & B Code 2016 and IBBI rules and regulations?

The term "Related Party" under Section 5(24) of the I & B Code, 2016, includes various relationships that signify control or significant influence over the corporate debtor. The Tribunal found that the appellants were involved in the day-to-day operations of the corporate debtor, with Appellant No. 2 serving as a key managerial personnel and being a relative of a director on the Board of Directors. The appellants also fell within the provisions of Section 5(24)(h), 5(24)(m)(i), and 5(24)(m)(iv) due to their involvement in policy-making processes and provision of essential technical information. Thus, the Tribunal upheld the decision of the Interim Resolution Professional and the Adjudicating Authority in classifying the appellants as related parties.

Issue No. (III): Whether the Resolution Plan was approved correctly when no provision had been made for the claims of the Appellants?

A resolution plan, as defined under Section 5(26) of the I & B Code, 2016, must comply with mandatory requirements and be approved by the Committee of Creditors (CoC). The Tribunal noted that the Resolution Professional's role is administrative, not quasi-judicial, and that the CoC's approval is binding. The CoC, which included only Pegasus Assets Reconstruction Pvt. Ltd., rejected the appellants' claims. The Tribunal found that the Resolution Professional and the Adjudicating Authority were justified in approving the Resolution Plan as the appellants' claims were not admitted as financial debt. The Tribunal emphasized that the I & B Code, 2016, is intended for the resolution of insolvency cases and not for debt recovery, suggesting that the appellants could seek remedies through other legal avenues.

Conclusion:

The Tribunal dismissed the appeals, upholding the impugned order dated 30.05.2022, and found it legally valid, tenable, just, and proper. The connected pending Interlocutory Applications, if any, were also closed.

 

 

 

 

Quick Updates:Latest Updates