<?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>2018 (9) TMI 220 - CALCUTTA HIGH COURT</title>
    <link>https://www.taxtmi.com/caselaws?id=366484</link>
    <description>The Court affirmed the Tribunal&#039;s decision that expenditures for software licenses and routine maintenance should be treated as revenue expenditure, not capital assets. The Court dismissed the appeal, highlighting that the expenses did not create new assets, as the term &#039;license&#039; implies limited use without transferring title. The judgment emphasized the nature of the expenses and upheld the Tribunal&#039;s factual finding that such expenditures should not be classified as capital assets.</description>
    <language>en-us</language>
    <pubDate>Thu, 28 Jun 2018 00:00:00 +0530</pubDate>
    <lastBuildDate>Wed, 05 Sep 2018 10:33:40 +0530</lastBuildDate>
    <generator>TaxTMI RSS Generator</generator>
    <atom:link href="https://www.taxtmi.com/rss_feed_blog?id=533227" rel="self" type="application/rss+xml"/>
    <item>
      <title>2018 (9) TMI 220 - CALCUTTA HIGH COURT</title>
      <link>https://www.taxtmi.com/caselaws?id=366484</link>
      <description>The Court affirmed the Tribunal&#039;s decision that expenditures for software licenses and routine maintenance should be treated as revenue expenditure, not capital assets. The Court dismissed the appeal, highlighting that the expenses did not create new assets, as the term &#039;license&#039; implies limited use without transferring title. The judgment emphasized the nature of the expenses and upheld the Tribunal&#039;s factual finding that such expenditures should not be classified as capital assets.</description>
      <category>Case-Laws</category>
      <law>Income Tax</law>
      <pubDate>Thu, 28 Jun 2018 00:00:00 +0530</pubDate>
      <guid isPermaLink="true">https://www.taxtmi.com/caselaws?id=366484</guid>
    </item>
  </channel>
</rss>