<?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 (4) TMI 932 - ANDHRA PRADESH HIGH COURT</title>
    <link>https://www.taxtmi.com/caselaws?id=769018</link>
    <description>An assessment order under the GST framework issued without a DIN was treated as invalid because GST communications and orders are required to bear a DIN under the applicable CBIC circular. The Court followed the settled position that absence of a DIN goes to the validity of the proceeding, and the impugned assessment was set aside. The authority was permitted to proceed afresh after issuing notice and assigning a DIN, with time spent in the earlier proceeding excluded for limitation purposes.</description>
    <language>en-us</language>
    <pubDate>Wed, 09 Apr 2025 00:00:00 +0530</pubDate>
    <lastBuildDate>Thu, 05 Jun 2025 14:46:00 +0530</lastBuildDate>
    <generator>TaxTMI RSS Generator</generator>
    <atom:link href="https://www.taxtmi.com/rss_feed_blog?id=815131" rel="self" type="application/rss+xml"/>
    <item>
      <title>2025 (4) TMI 932 - ANDHRA PRADESH HIGH COURT</title>
      <link>https://www.taxtmi.com/caselaws?id=769018</link>
      <description>An assessment order under the GST framework issued without a DIN was treated as invalid because GST communications and orders are required to bear a DIN under the applicable CBIC circular. The Court followed the settled position that absence of a DIN goes to the validity of the proceeding, and the impugned assessment was set aside. The authority was permitted to proceed afresh after issuing notice and assigning a DIN, with time spent in the earlier proceeding excluded for limitation purposes.</description>
      <category>Case-Laws</category>
      <law>GST</law>
      <pubDate>Wed, 09 Apr 2025 00:00:00 +0530</pubDate>
      <guid isPermaLink="true">https://www.taxtmi.com/caselaws?id=769018</guid>
    </item>
  </channel>
</rss>