<?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>2025 (8) TMI 1409 - MADRAS HIGH COURT</title>
    <link>https://www.taxtmi.com/caselaws?id=777221</link>
    <description>HC held that for CIRP applications under Sections 7 or 10 of the IB Code the RP proposed by the applicant must be appointed as IRP unless a disciplinary proceeding against the proposed RP is pending; NCLT has no discretion to substitute its own choice. The HC set aside the NCLT order that replaced the applicant-proposed IRP and directed the NCLT to pass fresh orders in accordance with the statutory scheme and principles of natural justice within six weeks of receipt of the HC order. Petition allowed.</description>
    <language>en-us</language>
    <pubDate>Wed, 13 Aug 2025 00:00:00 +0530</pubDate>
    <lastBuildDate>Wed, 27 Aug 2025 08:41:02 +0530</lastBuildDate>
    <generator>TaxTMI RSS Generator</generator>
    <atom:link href="https://www.taxtmi.com/rss_feed_blog?id=846090" rel="self" type="application/rss+xml"/>
    <item>
      <title>2025 (8) TMI 1409 - MADRAS HIGH COURT</title>
      <link>https://www.taxtmi.com/caselaws?id=777221</link>
      <description>HC held that for CIRP applications under Sections 7 or 10 of the IB Code the RP proposed by the applicant must be appointed as IRP unless a disciplinary proceeding against the proposed RP is pending; NCLT has no discretion to substitute its own choice. The HC set aside the NCLT order that replaced the applicant-proposed IRP and directed the NCLT to pass fresh orders in accordance with the statutory scheme and principles of natural justice within six weeks of receipt of the HC order. Petition allowed.</description>
      <category>Case-Laws</category>
      <law>IBC</law>
      <pubDate>Wed, 13 Aug 2025 00:00:00 +0530</pubDate>
      <guid isPermaLink="true">https://www.taxtmi.com/caselaws?id=777221</guid>
    </item>
  </channel>
</rss>