<?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 (2) TMI 1097 - MADRAS HIGH COURT</title>
    <link>https://www.taxtmi.com/caselaws?id=766550</link>
    <description>Reverse charge under the IGST framework cannot be used to substitute a taxable person different from the recipient contemplated by Section 5(3) of the Integrated Goods and Services Tax Act, 2017. Applying the Supreme Court&#039;s ruling in Mohit Minerals, the Madras HC treated the GST challenge as covered by binding precedent, held that the notification could not alter the statutorily prescribed recipient-liability structure, and allowed the writ petition, with the impugned order not surviving.</description>
    <language>en-us</language>
    <pubDate>Mon, 20 Jan 2025 00:00:00 +0530</pubDate>
    <lastBuildDate>Wed, 04 Jun 2025 13:37:00 +0530</lastBuildDate>
    <generator>TaxTMI RSS Generator</generator>
    <atom:link href="https://www.taxtmi.com/rss_feed_blog?id=802235" rel="self" type="application/rss+xml"/>
    <item>
      <title>2025 (2) TMI 1097 - MADRAS HIGH COURT</title>
      <link>https://www.taxtmi.com/caselaws?id=766550</link>
      <description>Reverse charge under the IGST framework cannot be used to substitute a taxable person different from the recipient contemplated by Section 5(3) of the Integrated Goods and Services Tax Act, 2017. Applying the Supreme Court&#039;s ruling in Mohit Minerals, the Madras HC treated the GST challenge as covered by binding precedent, held that the notification could not alter the statutorily prescribed recipient-liability structure, and allowed the writ petition, with the impugned order not surviving.</description>
      <category>Case-Laws</category>
      <law>GST</law>
      <pubDate>Mon, 20 Jan 2025 00:00:00 +0530</pubDate>
      <guid isPermaLink="true">https://www.taxtmi.com/caselaws?id=766550</guid>
    </item>
  </channel>
</rss>