<?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 (3) TMI 549 - KARNATAKA HIGH COURT</title>
    <link>https://www.taxtmi.com/caselaws?id=450768</link>
    <description>Under the GST transit-document framework, a transporter was not required to carry the original tax invoice; the statutory scheme contemplated issuance of the invoice in triplicate, with different copies meant for the recipient, transporter and supplier. On that basis, insisting on the original invoice during transit was inconsistent with the law. Because the tax and penalty orders rested only on that basis, they could not be sustained, and the assessee was also entitled to refund of the excess amount paid.</description>
    <language>en-us</language>
    <pubDate>Wed, 28 Feb 2024 00:00:00 +0530</pubDate>
    <lastBuildDate>Mon, 28 Apr 2025 16:09:00 +0530</lastBuildDate>
    <generator>TaxTMI RSS Generator</generator>
    <atom:link href="https://www.taxtmi.com/rss_feed_blog?id=746720" rel="self" type="application/rss+xml"/>
    <item>
      <title>2024 (3) TMI 549 - KARNATAKA HIGH COURT</title>
      <link>https://www.taxtmi.com/caselaws?id=450768</link>
      <description>Under the GST transit-document framework, a transporter was not required to carry the original tax invoice; the statutory scheme contemplated issuance of the invoice in triplicate, with different copies meant for the recipient, transporter and supplier. On that basis, insisting on the original invoice during transit was inconsistent with the law. Because the tax and penalty orders rested only on that basis, they could not be sustained, and the assessee was also entitled to refund of the excess amount paid.</description>
      <category>Case-Laws</category>
      <law>GST</law>
      <pubDate>Wed, 28 Feb 2024 00:00:00 +0530</pubDate>
      <guid isPermaLink="true">https://www.taxtmi.com/caselaws?id=450768</guid>
    </item>
  </channel>
</rss>