<?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>2011 (11) TMI 2 - DELHI HIGH COURT</title>
    <link>https://www.taxtmi.com/caselaws?id=206589</link>
    <description>HC held that software and related professional expenses were revenue, not capital, for tax purposes. The court found that the need for updates, statutory or professional changes, or occasional corruption does not convert such recurring software costs into capital expenditure; multiple factors and subsequent-year expenditures cannot conclusively determine nature. The assessing officer erred in treating the costs as capital merely because of book treatment. The deduction claimed by the assessee was allowed.</description>
    <language>en-us</language>
    <pubDate>Fri, 04 Nov 2011 00:00:00 +0530</pubDate>
    <lastBuildDate>Fri, 19 Sep 2025 14:48:00 +0530</lastBuildDate>
    <generator>TaxTMI RSS Generator</generator>
    <atom:link href="https://www.taxtmi.com/rss_feed_blog?id=180076" rel="self" type="application/rss+xml"/>
    <item>
      <title>2011 (11) TMI 2 - DELHI HIGH COURT</title>
      <link>https://www.taxtmi.com/caselaws?id=206589</link>
      <description>HC held that software and related professional expenses were revenue, not capital, for tax purposes. The court found that the need for updates, statutory or professional changes, or occasional corruption does not convert such recurring software costs into capital expenditure; multiple factors and subsequent-year expenditures cannot conclusively determine nature. The assessing officer erred in treating the costs as capital merely because of book treatment. The deduction claimed by the assessee was allowed.</description>
      <category>Case-Laws</category>
      <law>Income Tax</law>
      <pubDate>Fri, 04 Nov 2011 00:00:00 +0530</pubDate>
      <guid isPermaLink="true">https://www.taxtmi.com/caselaws?id=206589</guid>
    </item>
  </channel>
</rss>