<?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 724 - ITAT PUNE</title>
    <link>https://www.taxtmi.com/caselaws?id=376703</link>
    <description>The Tribunal upheld the CIT(A)&#039;s decision, dismissing the Revenue&#039;s appeal. The Tribunal concluded that the product development expenses for existing product improvement qualified as revenue expenditure, not resulting in asset creation. Emphasizing the essential nature of the expenditure for efficient business operation, the Tribunal relied on precedents to support its decision. The appeal was deemed lacking in merit, affirming the treatment of product development expenses as revenue expenditure.</description>
    <language>en-us</language>
    <pubDate>Wed, 16 Jan 2019 00:00:00 +0530</pubDate>
    <lastBuildDate>Fri, 15 Mar 2019 08:26:36 +0530</lastBuildDate>
    <generator>TaxTMI RSS Generator</generator>
    <atom:link href="https://www.taxtmi.com/rss_feed_blog?id=562885" rel="self" type="application/rss+xml"/>
    <item>
      <title>2019 (3) TMI 724 - ITAT PUNE</title>
      <link>https://www.taxtmi.com/caselaws?id=376703</link>
      <description>The Tribunal upheld the CIT(A)&#039;s decision, dismissing the Revenue&#039;s appeal. The Tribunal concluded that the product development expenses for existing product improvement qualified as revenue expenditure, not resulting in asset creation. Emphasizing the essential nature of the expenditure for efficient business operation, the Tribunal relied on precedents to support its decision. The appeal was deemed lacking in merit, affirming the treatment of product development expenses as revenue expenditure.</description>
      <category>Case-Laws</category>
      <law>Income Tax</law>
      <pubDate>Wed, 16 Jan 2019 00:00:00 +0530</pubDate>
      <guid isPermaLink="true">https://www.taxtmi.com/caselaws?id=376703</guid>
    </item>
  </channel>
</rss>