<?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>2024 (9) TMI 1939 - KARNATAKA HIGH COURT</title>
    <link>https://www.taxtmi.com/caselaws?id=469601</link>
    <description>A composite show cause notice was held unsustainable where demands relating to five separately registered divisions were clubbed together despite each division filing returns independently. The court treated the separate registrations as requiring distinct consideration and found that a single consolidated proceeding could not be used to raise demands for different divisions under the service tax and GST transitional framework. The composite notice and the consequential order-in-original were quashed.</description>
    <language>en-us</language>
    <pubDate>Wed, 04 Sep 2024 00:00:00 +0530</pubDate>
    <lastBuildDate>Tue, 23 Jun 2026 19:00:17 +0530</lastBuildDate>
    <generator>TaxTMI RSS Generator</generator>
    <atom:link href="https://www.taxtmi.com/rss_feed_blog?id=908316" rel="self" type="application/rss+xml"/>
    <item>
      <title>2024 (9) TMI 1939 - KARNATAKA HIGH COURT</title>
      <link>https://www.taxtmi.com/caselaws?id=469601</link>
      <description>A composite show cause notice was held unsustainable where demands relating to five separately registered divisions were clubbed together despite each division filing returns independently. The court treated the separate registrations as requiring distinct consideration and found that a single consolidated proceeding could not be used to raise demands for different divisions under the service tax and GST transitional framework. The composite notice and the consequential order-in-original were quashed.</description>
      <category>Case-Laws</category>
      <law>GST</law>
      <pubDate>Wed, 04 Sep 2024 00:00:00 +0530</pubDate>
      <guid isPermaLink="true">https://www.taxtmi.com/caselaws?id=469601</guid>
    </item>
  </channel>
</rss>