<?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>2026 (5) TMI 1291 - ANDHRA PRADESH HIGH COURT</title>
    <link>https://www.taxtmi.com/caselaws?id=792089</link>
    <description>An assessment summary in FORM GST DRC-07 issued without the assessing officer&#039;s signature was held to be fundamentally defective and invalid, because the omission could not be cured by the saving provisions invoked and an unsigned communication was treated as no service in law. On that basis, delay in challenging the summary did not defeat the writ petition, as limitation could not run against a defectively served order. The unsigned assessment summary was set aside, and the challenge succeeded.</description>
    <language>en-us</language>
    <pubDate>Wed, 06 May 2026 00:00:00 +0530</pubDate>
    <lastBuildDate>Fri, 22 May 2026 07:06:44 +0530</lastBuildDate>
    <generator>TaxTMI RSS Generator</generator>
    <atom:link href="https://www.taxtmi.com/rss_feed_blog?id=903216" rel="self" type="application/rss+xml"/>
    <item>
      <title>2026 (5) TMI 1291 - ANDHRA PRADESH HIGH COURT</title>
      <link>https://www.taxtmi.com/caselaws?id=792089</link>
      <description>An assessment summary in FORM GST DRC-07 issued without the assessing officer&#039;s signature was held to be fundamentally defective and invalid, because the omission could not be cured by the saving provisions invoked and an unsigned communication was treated as no service in law. On that basis, delay in challenging the summary did not defeat the writ petition, as limitation could not run against a defectively served order. The unsigned assessment summary was set aside, and the challenge succeeded.</description>
      <category>Case-Laws</category>
      <law>GST</law>
      <pubDate>Wed, 06 May 2026 00:00:00 +0530</pubDate>
      <guid isPermaLink="true">https://www.taxtmi.com/caselaws?id=792089</guid>
    </item>
  </channel>
</rss>