<?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>2017 (4) TMI 373 - CESTAT MUMBAI</title>
    <link>https://www.taxtmi.com/caselaws?id=341403</link>
    <description>Clearances of separate manufacturing units could not be clubbed for SSI exemption where each unit was independently registered, used its own raw materials, carried out separate manufacture, and sold directly to its own customers. In the absence of evidence of common control, financial flowback, inter-unit movement of finished goods, or a sham arrangement to split activity and evade duty, each unit had to be treated on its own status for Notification No. 175/86-C.E. The Revenue&#039;s challenge was rejected.</description>
    <language>en-us</language>
    <pubDate>Tue, 30 Aug 2016 00:00:00 +0530</pubDate>
    <lastBuildDate>Sat, 08 Apr 2017 07:32:11 +0530</lastBuildDate>
    <generator>TaxTMI RSS Generator</generator>
    <atom:link href="https://www.taxtmi.com/rss_feed_blog?id=465236" rel="self" type="application/rss+xml"/>
    <item>
      <title>2017 (4) TMI 373 - CESTAT MUMBAI</title>
      <link>https://www.taxtmi.com/caselaws?id=341403</link>
      <description>Clearances of separate manufacturing units could not be clubbed for SSI exemption where each unit was independently registered, used its own raw materials, carried out separate manufacture, and sold directly to its own customers. In the absence of evidence of common control, financial flowback, inter-unit movement of finished goods, or a sham arrangement to split activity and evade duty, each unit had to be treated on its own status for Notification No. 175/86-C.E. The Revenue&#039;s challenge was rejected.</description>
      <category>Case-Laws</category>
      <law>Central Excise</law>
      <pubDate>Tue, 30 Aug 2016 00:00:00 +0530</pubDate>
      <guid isPermaLink="true">https://www.taxtmi.com/caselaws?id=341403</guid>
    </item>
  </channel>
</rss>