<?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>2002 (5) TMI 63 - HIGH COURT OF DELHI</title>
    <link>https://www.taxtmi.com/caselaws?id=46345</link>
    <description>A fiscal notification became enforceable on publication in the Official Gazette, and later public sale or actual knowledge was not required to give it effect. The Delhi HC rejected the assessee&#039;s contention that the excise notification and related circular were inoperative because the Gazette was not immediately available to the public. On that principle, the restriction on utilisation of Cenvat credit for the relevant period was held binding, and the plea of non-availability to the public failed.</description>
    <language>en-us</language>
    <pubDate>Fri, 10 May 2002 00:00:00 +0530</pubDate>
    <lastBuildDate>Sat, 17 Jul 2010 12:30:29 +0530</lastBuildDate>
    <generator>TaxTMI RSS Generator</generator>
    <atom:link href="https://www.taxtmi.com/rss_feed_blog?id=84871" rel="self" type="application/rss+xml"/>
    <item>
      <title>2002 (5) TMI 63 - HIGH COURT OF DELHI</title>
      <link>https://www.taxtmi.com/caselaws?id=46345</link>
      <description>A fiscal notification became enforceable on publication in the Official Gazette, and later public sale or actual knowledge was not required to give it effect. The Delhi HC rejected the assessee&#039;s contention that the excise notification and related circular were inoperative because the Gazette was not immediately available to the public. On that principle, the restriction on utilisation of Cenvat credit for the relevant period was held binding, and the plea of non-availability to the public failed.</description>
      <category>Case-Laws</category>
      <law>Central Excise</law>
      <pubDate>Fri, 10 May 2002 00:00:00 +0530</pubDate>
      <guid isPermaLink="true">https://www.taxtmi.com/caselaws?id=46345</guid>
    </item>
  </channel>
</rss>