<?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>2006 (6) TMI 9 - CESTAT, BANGALORE</title>
    <link>https://www.taxtmi.com/caselaws?id=572</link>
    <description>Composite contracts for design, development, supply and installation-related activities were treated as an indivisible works arrangement, not separate taxable contracts for each component. Because the billing pattern did not create distinct service contracts and the goods element had already suffered excise duty, the contract could not be vivisected to levy Service Tax on isolated activities as Consulting Engineer services for the relevant period. The demand, interest and penalties were therefore not sustainable.</description>
    <language>en-us</language>
    <pubDate>Thu, 15 Jun 2006 00:00:00 +0530</pubDate>
    <lastBuildDate>Tue, 01 Jul 2008 12:10:00 +0530</lastBuildDate>
    <generator>TaxTMI RSS Generator</generator>
    <atom:link href="https://www.taxtmi.com/rss_feed_blog?id=40017" rel="self" type="application/rss+xml"/>
    <item>
      <title>2006 (6) TMI 9 - CESTAT, BANGALORE</title>
      <link>https://www.taxtmi.com/caselaws?id=572</link>
      <description>Composite contracts for design, development, supply and installation-related activities were treated as an indivisible works arrangement, not separate taxable contracts for each component. Because the billing pattern did not create distinct service contracts and the goods element had already suffered excise duty, the contract could not be vivisected to levy Service Tax on isolated activities as Consulting Engineer services for the relevant period. The demand, interest and penalties were therefore not sustainable.</description>
      <category>Case-Laws</category>
      <law>Service Tax</law>
      <pubDate>Thu, 15 Jun 2006 00:00:00 +0530</pubDate>
      <guid isPermaLink="true">https://www.taxtmi.com/caselaws?id=572</guid>
    </item>
  </channel>
</rss>