<?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>NO DEMAND CAN BE RAISED AFTER A RESOLUTION PLAN HAS BEEN APPROVED UNDER INSOLVENCY AND BANKRUPTCY CODE, 2016</title>
    <link>https://www.taxtmi.com/article/detailed?id=15914</link>
    <description>A resolution plan approved under the Insolvency and Bankruptcy Code prevents fresh demands for periods prior to approval; where a tax department participated in insolvency proceedings and its claims were considered and quantified in the resolution process, it cannot raise new pre-plan demands or pursue recovery that would saddle the incoming management, and such post-approval recovery attempts can be set aside.</description>
    <language>en-us</language>
    <pubDate>Sat, 21 Feb 2026 09:31:19 +0530</pubDate>
    <lastBuildDate>Sat, 21 Feb 2026 09:31:19 +0530</lastBuildDate>
    <generator>TaxTMI RSS Generator</generator>
    <atom:link href="https://www.taxtmi.com/rss_feed_blog?id=887439" rel="self" type="application/rss+xml"/>
    <item>
      <title>NO DEMAND CAN BE RAISED AFTER A RESOLUTION PLAN HAS BEEN APPROVED UNDER INSOLVENCY AND BANKRUPTCY CODE, 2016</title>
      <link>https://www.taxtmi.com/article/detailed?id=15914</link>
      <description>A resolution plan approved under the Insolvency and Bankruptcy Code prevents fresh demands for periods prior to approval; where a tax department participated in insolvency proceedings and its claims were considered and quantified in the resolution process, it cannot raise new pre-plan demands or pursue recovery that would saddle the incoming management, and such post-approval recovery attempts can be set aside.</description>
      <category>Articles</category>
      <law>Corporate Laws / IBC / SEBI</law>
      <pubDate>Sat, 21 Feb 2026 09:31:19 +0530</pubDate>
      <guid isPermaLink="true">https://www.taxtmi.com/article/detailed?id=15914</guid>
    </item>
  </channel>
</rss>