<?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 (9) TMI 1417 - CESTAT MUMBAI</title>
    <link>https://www.taxtmi.com/caselaws?id=778928</link>
    <description>CESTAT held that service of the show-cause notice by email, though dispatched to the email address confirmed by the appellant under RTI, did not satisfy requirements of sections 28(1)/(4) and the proceedings could not be validly concluded under section 28(6). The adjudicating authority failed to prove that email service was effective; apparent clerical error in the address was not controverted. The impugned order confirming differential duty, interest and penalties was set aside and the appeal allowed.</description>
    <language>en-us</language>
    <pubDate>Tue, 23 Sep 2025 00:00:00 +0530</pubDate>
    <lastBuildDate>Thu, 25 Sep 2025 08:37:30 +0530</lastBuildDate>
    <generator>TaxTMI RSS Generator</generator>
    <atom:link href="https://www.taxtmi.com/rss_feed_blog?id=854393" rel="self" type="application/rss+xml"/>
    <item>
      <title>2025 (9) TMI 1417 - CESTAT MUMBAI</title>
      <link>https://www.taxtmi.com/caselaws?id=778928</link>
      <description>CESTAT held that service of the show-cause notice by email, though dispatched to the email address confirmed by the appellant under RTI, did not satisfy requirements of sections 28(1)/(4) and the proceedings could not be validly concluded under section 28(6). The adjudicating authority failed to prove that email service was effective; apparent clerical error in the address was not controverted. The impugned order confirming differential duty, interest and penalties was set aside and the appeal allowed.</description>
      <category>Case-Laws</category>
      <law>Customs</law>
      <pubDate>Tue, 23 Sep 2025 00:00:00 +0530</pubDate>
      <guid isPermaLink="true">https://www.taxtmi.com/caselaws?id=778928</guid>
    </item>
  </channel>
</rss>