<?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>2018 (1) TMI 1168 - MADRAS HIGH COURT</title>
    <link>https://www.taxtmi.com/caselaws?id=354432</link>
    <description>Credit validly taken under the CENVAT scheme was considered not liable to reversal merely because the final product later became exempt from duty. The Court noted that the issue was already covered by an earlier Division Bench decision of the same Court, which had answered the identical question in favour of the assessee. Applying that binding precedent, the Court rejected the Revenue&#039;s contention and treated the subsequent exemption as not triggering reversal of the credit in the manner argued.</description>
    <language>en-us</language>
    <pubDate>Fri, 08 Dec 2017 00:00:00 +0530</pubDate>
    <lastBuildDate>Mon, 29 Jan 2018 08:12:14 +0530</lastBuildDate>
    <generator>TaxTMI RSS Generator</generator>
    <atom:link href="https://www.taxtmi.com/rss_feed_blog?id=506371" rel="self" type="application/rss+xml"/>
    <item>
      <title>2018 (1) TMI 1168 - MADRAS HIGH COURT</title>
      <link>https://www.taxtmi.com/caselaws?id=354432</link>
      <description>Credit validly taken under the CENVAT scheme was considered not liable to reversal merely because the final product later became exempt from duty. The Court noted that the issue was already covered by an earlier Division Bench decision of the same Court, which had answered the identical question in favour of the assessee. Applying that binding precedent, the Court rejected the Revenue&#039;s contention and treated the subsequent exemption as not triggering reversal of the credit in the manner argued.</description>
      <category>Case-Laws</category>
      <law>Central Excise</law>
      <pubDate>Fri, 08 Dec 2017 00:00:00 +0530</pubDate>
      <guid isPermaLink="true">https://www.taxtmi.com/caselaws?id=354432</guid>
    </item>
  </channel>
</rss>