<?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>2006 (8) TMI 494 - CESTAT, BANGALORE</title>
    <link>https://www.taxtmi.com/caselaws?id=122066</link>
    <description>A change in the capacity-determination parameter under the Compound Levy Scheme could operate only prospectively, so past duty demand based on the later measurement was not sustainable. The record showed no wilful suppression, mala fides, or other basis to invoke the extended demand period or penalties, and the scheme was treated as a self-contained code that excluded general interest and penalty provisions on these facts. The retrospective demand, interest and penalty were therefore rejected.</description>
    <language>en-us</language>
    <pubDate>Mon, 14 Aug 2006 00:00:00 +0530</pubDate>
    <lastBuildDate>Wed, 08 Aug 2012 13:21:44 +0530</lastBuildDate>
    <generator>TaxTMI RSS Generator</generator>
    <atom:link href="https://www.taxtmi.com/rss_feed_blog?id=159056" rel="self" type="application/rss+xml"/>
    <item>
      <title>2006 (8) TMI 494 - CESTAT, BANGALORE</title>
      <link>https://www.taxtmi.com/caselaws?id=122066</link>
      <description>A change in the capacity-determination parameter under the Compound Levy Scheme could operate only prospectively, so past duty demand based on the later measurement was not sustainable. The record showed no wilful suppression, mala fides, or other basis to invoke the extended demand period or penalties, and the scheme was treated as a self-contained code that excluded general interest and penalty provisions on these facts. The retrospective demand, interest and penalty were therefore rejected.</description>
      <category>Case-Laws</category>
      <law>Central Excise</law>
      <pubDate>Mon, 14 Aug 2006 00:00:00 +0530</pubDate>
      <guid isPermaLink="true">https://www.taxtmi.com/caselaws?id=122066</guid>
    </item>
  </channel>
</rss>