<?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 1535 - GUJARAT HIGH COURT</title>
    <link>https://www.taxtmi.com/caselaws?id=777347</link>
    <description>HC quashed the impugned recovery order and allowed the petitioner to rectify an inadvertent clerical error in outward supplies by filing a corrected GSTR-1 within four weeks. The court found the petitioner had mistakenly reported a sister concern&#039;s turnover for Q3 FY 2017-18; the respondent must manually accept and process the rectified GSTR-1 in accordance with law. The challenge to disallowance of excess ITC was disposed by permitting correction rather than sustaining the recovery order.</description>
    <language>en-us</language>
    <pubDate>Thu, 07 Aug 2025 00:00:00 +0530</pubDate>
    <lastBuildDate>Thu, 28 Aug 2025 08:32:48 +0530</lastBuildDate>
    <generator>TaxTMI RSS Generator</generator>
    <atom:link href="https://www.taxtmi.com/rss_feed_blog?id=846287" rel="self" type="application/rss+xml"/>
    <item>
      <title>2025 (8) TMI 1535 - GUJARAT HIGH COURT</title>
      <link>https://www.taxtmi.com/caselaws?id=777347</link>
      <description>HC quashed the impugned recovery order and allowed the petitioner to rectify an inadvertent clerical error in outward supplies by filing a corrected GSTR-1 within four weeks. The court found the petitioner had mistakenly reported a sister concern&#039;s turnover for Q3 FY 2017-18; the respondent must manually accept and process the rectified GSTR-1 in accordance with law. The challenge to disallowance of excess ITC was disposed by permitting correction rather than sustaining the recovery order.</description>
      <category>Case-Laws</category>
      <law>GST</law>
      <pubDate>Thu, 07 Aug 2025 00:00:00 +0530</pubDate>
      <guid isPermaLink="true">https://www.taxtmi.com/caselaws?id=777347</guid>
    </item>
  </channel>
</rss>