<?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>2019 (3) TMI 1147 - CESTAT CHENNAI</title>
    <link>https://www.taxtmi.com/caselaws?id=377126</link>
    <description>Transaction charges collected and paid over to the NSE were treated as reimbursable expenses, not brokerage retained by the intermediary, and were therefore outside the taxable value for service tax. The levy could not be sustained because the demand rested on Rule 5(1) of the Service Tax (Determination of Value) Rules, 2006, which had already been held ultra vires. Amounts merely recovered as third-party reimbursements cannot be included in service tax valuation when the enabling valuation rule is invalid.</description>
    <language>en-us</language>
    <pubDate>Wed, 20 Mar 2019 00:00:00 +0530</pubDate>
    <lastBuildDate>Sat, 23 Mar 2019 10:40:41 +0530</lastBuildDate>
    <generator>TaxTMI RSS Generator</generator>
    <atom:link href="https://www.taxtmi.com/rss_feed_blog?id=563900" rel="self" type="application/rss+xml"/>
    <item>
      <title>2019 (3) TMI 1147 - CESTAT CHENNAI</title>
      <link>https://www.taxtmi.com/caselaws?id=377126</link>
      <description>Transaction charges collected and paid over to the NSE were treated as reimbursable expenses, not brokerage retained by the intermediary, and were therefore outside the taxable value for service tax. The levy could not be sustained because the demand rested on Rule 5(1) of the Service Tax (Determination of Value) Rules, 2006, which had already been held ultra vires. Amounts merely recovered as third-party reimbursements cannot be included in service tax valuation when the enabling valuation rule is invalid.</description>
      <category>Case-Laws</category>
      <law>Service Tax</law>
      <pubDate>Wed, 20 Mar 2019 00:00:00 +0530</pubDate>
      <guid isPermaLink="true">https://www.taxtmi.com/caselaws?id=377126</guid>
    </item>
  </channel>
</rss>