<?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>Resolution Applicants Shouldn&#039;t Face New Claims Post-Approval in CIRP; Avoid &quot;Hydra Head&quot; Disruptions in Business Takeovers.</title>
    <link>https://www.taxtmi.com/highlights?id=50241</link>
    <description>Corporate Insolvency resolution process (CIRP) - A successful resolution applicant cannot suddenly be faced with “undecided” claims after the resolution plan submitted by him has been accepted as this would amount to a hydra head popping up which would throw into uncertainty amounts payable by a prospective resolution applicant who successfully take over the business of the corporate debtor.</description>
    <language>en-us</language>
    <pubDate>Sat, 16 Nov 2019 12:35:50 +0530</pubDate>
    <lastBuildDate>Sat, 16 Nov 2019 12:35:50 +0530</lastBuildDate>
    <generator>TaxTMI RSS Generator</generator>
    <atom:link href="https://www.taxtmi.com/rss_feed_blog?id=594339" rel="self" type="application/rss+xml"/>
    <item>
      <title>Resolution Applicants Shouldn&#039;t Face New Claims Post-Approval in CIRP; Avoid &quot;Hydra Head&quot; Disruptions in Business Takeovers.</title>
      <link>https://www.taxtmi.com/highlights?id=50241</link>
      <description>Corporate Insolvency resolution process (CIRP) - A successful resolution applicant cannot suddenly be faced with “undecided” claims after the resolution plan submitted by him has been accepted as this would amount to a hydra head popping up which would throw into uncertainty amounts payable by a prospective resolution applicant who successfully take over the business of the corporate debtor.</description>
      <category>Highlights</category>
      <law>Insolvency and Bankruptcy</law>
      <pubDate>Sat, 16 Nov 2019 12:35:50 +0530</pubDate>
      <guid isPermaLink="true">https://www.taxtmi.com/highlights?id=50241</guid>
    </item>
  </channel>
</rss>