<?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>2016 (9) TMI 690 - CESTAT NEW DELHI</title>
    <link>https://www.taxtmi.com/caselaws?id=332429</link>
    <description>The Tribunal ruled in favor of the appellant, setting aside the demand for service tax on supervision charges received from the Madhya Pradesh government. It was determined that the charges were reimbursement for establishment costs and not for consulting engineer services as defined in the Finance Act, 1994. The absence of a formal consultancy agreement, the nature of the charges, and the appellant company&#039;s composition supported the decision to allow the appeal and negate the service tax levy.</description>
    <language>en-us</language>
    <pubDate>Mon, 22 Aug 2016 00:00:00 +0530</pubDate>
    <lastBuildDate>Fri, 07 Apr 2017 14:44:00 +0530</lastBuildDate>
    <generator>TaxTMI RSS Generator</generator>
    <atom:link href="https://www.taxtmi.com/rss_feed_blog?id=441401" rel="self" type="application/rss+xml"/>
    <item>
      <title>2016 (9) TMI 690 - CESTAT NEW DELHI</title>
      <link>https://www.taxtmi.com/caselaws?id=332429</link>
      <description>The Tribunal ruled in favor of the appellant, setting aside the demand for service tax on supervision charges received from the Madhya Pradesh government. It was determined that the charges were reimbursement for establishment costs and not for consulting engineer services as defined in the Finance Act, 1994. The absence of a formal consultancy agreement, the nature of the charges, and the appellant company&#039;s composition supported the decision to allow the appeal and negate the service tax levy.</description>
      <category>Case-Laws</category>
      <law>Service Tax</law>
      <pubDate>Mon, 22 Aug 2016 00:00:00 +0530</pubDate>
      <guid isPermaLink="true">https://www.taxtmi.com/caselaws?id=332429</guid>
    </item>
  </channel>
</rss>