<?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>2001 (4) TMI 99 - HIGH COURT OF JUDICATURE AT MADRAS</title>
    <link>https://www.taxtmi.com/caselaws?id=46009</link>
    <description>A common show cause notice under Central Excise law is not without jurisdiction merely because it names more than one noticee where the alleged suppression period overlaps and the liabilities are interconnected. The jurisdictional objection failed, and the writ petition was not entertained. The petitioner remained free to raise all objections before the adjudicating authority, including the contention that separate notices should be issued if the demand is ultimately found to be distinct.</description>
    <language>en-us</language>
    <pubDate>Wed, 18 Apr 2001 00:00:00 +0530</pubDate>
    <lastBuildDate>Thu, 15 Jul 2010 12:00:32 +0530</lastBuildDate>
    <generator>TaxTMI RSS Generator</generator>
    <atom:link href="https://www.taxtmi.com/rss_feed_blog?id=84535" rel="self" type="application/rss+xml"/>
    <item>
      <title>2001 (4) TMI 99 - HIGH COURT OF JUDICATURE AT MADRAS</title>
      <link>https://www.taxtmi.com/caselaws?id=46009</link>
      <description>A common show cause notice under Central Excise law is not without jurisdiction merely because it names more than one noticee where the alleged suppression period overlaps and the liabilities are interconnected. The jurisdictional objection failed, and the writ petition was not entertained. The petitioner remained free to raise all objections before the adjudicating authority, including the contention that separate notices should be issued if the demand is ultimately found to be distinct.</description>
      <category>Case-Laws</category>
      <law>Central Excise</law>
      <pubDate>Wed, 18 Apr 2001 00:00:00 +0530</pubDate>
      <guid isPermaLink="true">https://www.taxtmi.com/caselaws?id=46009</guid>
    </item>
  </channel>
</rss>