<?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>2010 (12) TMI 880 - ITAT, Mumbai</title>
    <link>https://www.taxtmi.com/caselaws?id=207946</link>
    <description>The ITAT Mumbai remanded the case to the AO for reexamination of Software Expenses to determine if they should be treated as Capital Expenditure, emphasizing the need to apply the functional test and principles established by the Special Bench. Regarding Web-Hosting Expenses, the ITAT ruled in favor of treating them as revenue expenditure, citing their essential nature for online business interactions and lack of creation of a capital asset. The appeal was allowed for statistical purposes.</description>
    <language>en-us</language>
    <pubDate>Wed, 22 Dec 2010 00:00:00 +0530</pubDate>
    <lastBuildDate>Fri, 30 Dec 2011 09:05:00 +0530</lastBuildDate>
    <generator>TaxTMI RSS Generator</generator>
    <atom:link href="https://www.taxtmi.com/rss_feed_blog?id=181419" rel="self" type="application/rss+xml"/>
    <item>
      <title>2010 (12) TMI 880 - ITAT, Mumbai</title>
      <link>https://www.taxtmi.com/caselaws?id=207946</link>
      <description>The ITAT Mumbai remanded the case to the AO for reexamination of Software Expenses to determine if they should be treated as Capital Expenditure, emphasizing the need to apply the functional test and principles established by the Special Bench. Regarding Web-Hosting Expenses, the ITAT ruled in favor of treating them as revenue expenditure, citing their essential nature for online business interactions and lack of creation of a capital asset. The appeal was allowed for statistical purposes.</description>
      <category>Case-Laws</category>
      <law>Income Tax</law>
      <pubDate>Wed, 22 Dec 2010 00:00:00 +0530</pubDate>
      <guid isPermaLink="true">https://www.taxtmi.com/caselaws?id=207946</guid>
    </item>
  </channel>
</rss>