<?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>2004 (5) TMI 398 - CESTAT, MUMBAI</title>
    <link>https://www.taxtmi.com/caselaws?id=111945</link>
    <description>Rubber and metal bonded parts manufactured specifically for Indian Railways were treated as classifiable under Heading 8607.00 because their design was railway-specific and they had no use outside railway applications. The appellate classification finding on the same material was accepted, and no reason was found to depart from it. The operative effect is that exclusive railway use and specialised design supported classification under the railway heading rather than the alternative heading claimed.</description>
    <language>en-us</language>
    <pubDate>Wed, 26 May 2004 00:00:00 +0530</pubDate>
    <lastBuildDate>Wed, 25 Apr 2012 18:44:51 +0530</lastBuildDate>
    <generator>TaxTMI RSS Generator</generator>
    <atom:link href="https://www.taxtmi.com/rss_feed_blog?id=148961" rel="self" type="application/rss+xml"/>
    <item>
      <title>2004 (5) TMI 398 - CESTAT, MUMBAI</title>
      <link>https://www.taxtmi.com/caselaws?id=111945</link>
      <description>Rubber and metal bonded parts manufactured specifically for Indian Railways were treated as classifiable under Heading 8607.00 because their design was railway-specific and they had no use outside railway applications. The appellate classification finding on the same material was accepted, and no reason was found to depart from it. The operative effect is that exclusive railway use and specialised design supported classification under the railway heading rather than the alternative heading claimed.</description>
      <category>Case-Laws</category>
      <law>Central Excise</law>
      <pubDate>Wed, 26 May 2004 00:00:00 +0530</pubDate>
      <guid isPermaLink="true">https://www.taxtmi.com/caselaws?id=111945</guid>
    </item>
  </channel>
</rss>