<?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 (6) TMI 1247 - MADRAS HIGH COURT</title>
    <link>https://www.taxtmi.com/caselaws?id=773134</link>
    <description>HC examined the validity of service of GST notices through common portal and procedural fairness. The court found that uploading notices on portal alone does not constitute effective service. When taxpayer remains unresponsive, authorities must explore alternative service modes like registered post. The ex parte assessment order was set aside, with directions for fresh proceedings ensuring proper notice and personal hearing, mandating 25% tax deposit and providing opportunity to present submissions.</description>
    <language>en-us</language>
    <pubDate>Wed, 04 Jun 2025 00:00:00 +0530</pubDate>
    <lastBuildDate>Wed, 18 Jun 2025 09:04:16 +0530</lastBuildDate>
    <generator>TaxTMI RSS Generator</generator>
    <atom:link href="https://www.taxtmi.com/rss_feed_blog?id=829761" rel="self" type="application/rss+xml"/>
    <item>
      <title>2025 (6) TMI 1247 - MADRAS HIGH COURT</title>
      <link>https://www.taxtmi.com/caselaws?id=773134</link>
      <description>HC examined the validity of service of GST notices through common portal and procedural fairness. The court found that uploading notices on portal alone does not constitute effective service. When taxpayer remains unresponsive, authorities must explore alternative service modes like registered post. The ex parte assessment order was set aside, with directions for fresh proceedings ensuring proper notice and personal hearing, mandating 25% tax deposit and providing opportunity to present submissions.</description>
      <category>Case-Laws</category>
      <law>GST</law>
      <pubDate>Wed, 04 Jun 2025 00:00:00 +0530</pubDate>
      <guid isPermaLink="true">https://www.taxtmi.com/caselaws?id=773134</guid>
    </item>
  </channel>
</rss>