<?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 (6) TMI 1123 - GUJARAT HIGH COURT</title>
    <link>https://www.taxtmi.com/caselaws?id=186084</link>
    <description>The High Court upheld the Tribunal&#039;s decision, classifying losses from share transactions as speculation losses under the Explanation to Section 73 of the Income Tax Act. The Court agreed with the revenue&#039;s stance that the deeming fiction in the Explanation applies, regardless of actual delivery of shares. Emphasizing legislative intent, the Court ruled in favor of the revenue, dismissing the appeal and affirming that both business loss and valuation loss should be treated as speculation loss.</description>
    <language>en-us</language>
    <pubDate>Wed, 29 Jun 2016 00:00:00 +0530</pubDate>
    <lastBuildDate>Sat, 13 May 2017 12:37:00 +0530</lastBuildDate>
    <generator>TaxTMI RSS Generator</generator>
    <atom:link href="https://www.taxtmi.com/rss_feed_blog?id=440306" rel="self" type="application/rss+xml"/>
    <item>
      <title>2016 (6) TMI 1123 - GUJARAT HIGH COURT</title>
      <link>https://www.taxtmi.com/caselaws?id=186084</link>
      <description>The High Court upheld the Tribunal&#039;s decision, classifying losses from share transactions as speculation losses under the Explanation to Section 73 of the Income Tax Act. The Court agreed with the revenue&#039;s stance that the deeming fiction in the Explanation applies, regardless of actual delivery of shares. Emphasizing legislative intent, the Court ruled in favor of the revenue, dismissing the appeal and affirming that both business loss and valuation loss should be treated as speculation loss.</description>
      <category>Case-Laws</category>
      <law>Income Tax</law>
      <pubDate>Wed, 29 Jun 2016 00:00:00 +0530</pubDate>
      <guid isPermaLink="true">https://www.taxtmi.com/caselaws?id=186084</guid>
    </item>
  </channel>
</rss>