<?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>Recovery of Confirmed Demands during pendency of Stay applications</title>
    <link>https://www.taxtmi.com/article/detailed?id=1997</link>
    <description>CBEC Circular No. 967/01/2013 rescinds prior circulars and mandates recovery of confirmed excise demands where stay applications are not granted within a short administrative period for Commissioner (Appeals) and the Tribunal, and requires immediate recovery where no stay exists in higher courts; the Circular changes timing of enforcement and is said to conflict with the statutory proviso and operational realities, making it susceptible to legal challenge.</description>
    <language>en-us</language>
    <pubDate>Fri, 04 Jan 2013 11:41:24 +0530</pubDate>
    <lastBuildDate>Fri, 04 Jan 2013 11:41:24 +0530</lastBuildDate>
    <generator>TaxTMI RSS Generator</generator>
    <atom:link href="https://www.taxtmi.com/rss_feed_blog?id=302475" rel="self" type="application/rss+xml"/>
    <item>
      <title>Recovery of Confirmed Demands during pendency of Stay applications</title>
      <link>https://www.taxtmi.com/article/detailed?id=1997</link>
      <description>CBEC Circular No. 967/01/2013 rescinds prior circulars and mandates recovery of confirmed excise demands where stay applications are not granted within a short administrative period for Commissioner (Appeals) and the Tribunal, and requires immediate recovery where no stay exists in higher courts; the Circular changes timing of enforcement and is said to conflict with the statutory proviso and operational realities, making it susceptible to legal challenge.</description>
      <category>Articles</category>
      <law>Central Excise</law>
      <pubDate>Fri, 04 Jan 2013 11:41:24 +0530</pubDate>
      <guid isPermaLink="true">https://www.taxtmi.com/article/detailed?id=1997</guid>
    </item>
  </channel>
</rss>