<?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>High Court can hear winding up petition CP 1 of 2016 but proceedings paused pending NCLT decision on resolution plan.</title>
    <link>https://www.taxtmi.com/highlights?id=50721</link>
    <description>Winding up petition - Jurisdiction of High Court - This Court possesses the jurisdiction to hear out the winding up petition being CP 1 of 2016 along with all connected applications. However, the winding up petition and the connected applications thereto should not be proceeded with till NCLT comes to the conclusion as to whether the resolution plan in respect of the said company is either approved or rejected.</description>
    <language>en-us</language>
    <pubDate>Mon, 16 Dec 2019 09:49:34 +0530</pubDate>
    <lastBuildDate>Mon, 16 Dec 2019 09:49:34 +0530</lastBuildDate>
    <generator>TaxTMI RSS Generator</generator>
    <atom:link href="https://www.taxtmi.com/rss_feed_blog?id=597397" rel="self" type="application/rss+xml"/>
    <item>
      <title>High Court can hear winding up petition CP 1 of 2016 but proceedings paused pending NCLT decision on resolution plan.</title>
      <link>https://www.taxtmi.com/highlights?id=50721</link>
      <description>Winding up petition - Jurisdiction of High Court - This Court possesses the jurisdiction to hear out the winding up petition being CP 1 of 2016 along with all connected applications. However, the winding up petition and the connected applications thereto should not be proceeded with till NCLT comes to the conclusion as to whether the resolution plan in respect of the said company is either approved or rejected.</description>
      <category>Highlights</category>
      <law>Companies Law</law>
      <pubDate>Mon, 16 Dec 2019 09:49:34 +0530</pubDate>
      <guid isPermaLink="true">https://www.taxtmi.com/highlights?id=50721</guid>
    </item>
  </channel>
</rss>