<?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 (3) TMI 398 - CESTAT MUMBAI</title>
    <link>https://www.taxtmi.com/caselaws?id=356695</link>
    <description>The appellate tribunal ruled in favor of the appellant in a case involving the disallowance of cenvat credit and demand for recovery of amounts. The tribunal found that the appellant had correctly reversed the credit under Rule 6 (3) of the Cenvat Credit Rules, maintained separate accounts for common inputs, and ruled the demands unsustainable. The tribunal also held that the demand under Section 11D was not sustainable, providing consequential reliefs to the appellant and allowing the appeal on 31/01/2018.</description>
    <language>en-us</language>
    <pubDate>Wed, 31 Jan 2018 00:00:00 +0530</pubDate>
    <lastBuildDate>Sat, 10 Mar 2018 06:55:34 +0530</lastBuildDate>
    <generator>TaxTMI RSS Generator</generator>
    <atom:link href="https://www.taxtmi.com/rss_feed_blog?id=512083" rel="self" type="application/rss+xml"/>
    <item>
      <title>2018 (3) TMI 398 - CESTAT MUMBAI</title>
      <link>https://www.taxtmi.com/caselaws?id=356695</link>
      <description>The appellate tribunal ruled in favor of the appellant in a case involving the disallowance of cenvat credit and demand for recovery of amounts. The tribunal found that the appellant had correctly reversed the credit under Rule 6 (3) of the Cenvat Credit Rules, maintained separate accounts for common inputs, and ruled the demands unsustainable. The tribunal also held that the demand under Section 11D was not sustainable, providing consequential reliefs to the appellant and allowing the appeal on 31/01/2018.</description>
      <category>Case-Laws</category>
      <law>Central Excise</law>
      <pubDate>Wed, 31 Jan 2018 00:00:00 +0530</pubDate>
      <guid isPermaLink="true">https://www.taxtmi.com/caselaws?id=356695</guid>
    </item>
  </channel>
</rss>