<?xml version="1.0" encoding="UTF-8"?>
<?xml-stylesheet type="text/xsl" href="https://www.taxtmi.com/rss_sitemap/rss_feed_blog.xsl?v=1750492856"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>2020 (10) TMI 442 - NATIONAL COMPANY LAW TRIBUNAL , CHENNAI BENCH</title>
    <link>https://www.taxtmi.com/caselaws?id=399468</link>
    <description>The Tribunal dismissed the application for initiating Corporate Insolvency Resolution Process (CIRP) against the Corporate Debtor, citing the existence of a valid pre-existing dispute between the parties regarding software implementation issues. The Tribunal found that the Corporate Debtor&#039;s contentions were not spurious, leading to the conclusion that the dispute required further investigation in the Civil Court, making the application for CIRP not maintainable.</description>
    <language>en-us</language>
    <pubDate>Tue, 05 May 2020 00:00:00 +0530</pubDate>
    <lastBuildDate>Mon, 12 Oct 2020 11:20:57 +0530</lastBuildDate>
    <generator>TaxTMI RSS Generator</generator>
    <atom:link href="https://www.taxtmi.com/rss_feed_blog?id=624781" rel="self" type="application/rss+xml"/>
    <item>
      <title>2020 (10) TMI 442 - NATIONAL COMPANY LAW TRIBUNAL , CHENNAI BENCH</title>
      <link>https://www.taxtmi.com/caselaws?id=399468</link>
      <description>The Tribunal dismissed the application for initiating Corporate Insolvency Resolution Process (CIRP) against the Corporate Debtor, citing the existence of a valid pre-existing dispute between the parties regarding software implementation issues. The Tribunal found that the Corporate Debtor&#039;s contentions were not spurious, leading to the conclusion that the dispute required further investigation in the Civil Court, making the application for CIRP not maintainable.</description>
      <category>Case-Laws</category>
      <law>Insolvency and Bankruptcy</law>
      <pubDate>Tue, 05 May 2020 00:00:00 +0530</pubDate>
      <guid isPermaLink="true">https://www.taxtmi.com/caselaws?id=399468</guid>
    </item>
  </channel>
</rss>