<?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>2018 (9) TMI 429 - NATIONAL COMPANY LAW TRIBUNAL, KOLKATA</title>
    <link>https://www.taxtmi.com/caselaws?id=366693</link>
    <description>The resolution plan submitted by CP Ispat Private Limited was approved by the adjudicating authority, with objections from other applicants dismissed for lack of evidence. The Bench highlighted the importance of guidelines on insolvency resolution costs and fees to prevent excessive charges. The approved plan became binding on all stakeholders, ending the moratorium order, and required all relevant records to be forwarded to the Insolvency and Bankruptcy Board of India.</description>
    <language>en-us</language>
    <pubDate>Tue, 13 Mar 2018 00:00:00 +0530</pubDate>
    <lastBuildDate>Sat, 08 Sep 2018 08:10:08 +0530</lastBuildDate>
    <generator>TaxTMI RSS Generator</generator>
    <atom:link href="https://www.taxtmi.com/rss_feed_blog?id=533626" rel="self" type="application/rss+xml"/>
    <item>
      <title>2018 (9) TMI 429 - NATIONAL COMPANY LAW TRIBUNAL, KOLKATA</title>
      <link>https://www.taxtmi.com/caselaws?id=366693</link>
      <description>The resolution plan submitted by CP Ispat Private Limited was approved by the adjudicating authority, with objections from other applicants dismissed for lack of evidence. The Bench highlighted the importance of guidelines on insolvency resolution costs and fees to prevent excessive charges. The approved plan became binding on all stakeholders, ending the moratorium order, and required all relevant records to be forwarded to the Insolvency and Bankruptcy Board of India.</description>
      <category>Case-Laws</category>
      <law>Insolvency and Bankruptcy</law>
      <pubDate>Tue, 13 Mar 2018 00:00:00 +0530</pubDate>
      <guid isPermaLink="true">https://www.taxtmi.com/caselaws?id=366693</guid>
    </item>
  </channel>
</rss>