<?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 (3) TMI 500 - ITAT KOLKATA</title>
    <link>https://www.taxtmi.com/caselaws?id=325316</link>
    <description>The Tribunal upheld the CIT(A)&#039;s decisions on all grounds, dismissing the Revenue&#039;s appeal. The payments towards NPV were considered revenue expenditure necessary for business continuity. Expenses for the unsuccessful project bidding were viewed as part of ongoing operations. Bad debts and prior period expenses were allowed as legitimate business expenditures. The Tribunal emphasized the statutory and business necessity of these expenses, classifying them as revenue expenses under the Income Tax Act.</description>
    <language>en-us</language>
    <pubDate>Wed, 02 Mar 2016 00:00:00 +0530</pubDate>
    <lastBuildDate>Tue, 15 Mar 2016 14:23:00 +0530</lastBuildDate>
    <generator>TaxTMI RSS Generator</generator>
    <atom:link href="https://www.taxtmi.com/rss_feed_blog?id=420280" rel="self" type="application/rss+xml"/>
    <item>
      <title>2016 (3) TMI 500 - ITAT KOLKATA</title>
      <link>https://www.taxtmi.com/caselaws?id=325316</link>
      <description>The Tribunal upheld the CIT(A)&#039;s decisions on all grounds, dismissing the Revenue&#039;s appeal. The payments towards NPV were considered revenue expenditure necessary for business continuity. Expenses for the unsuccessful project bidding were viewed as part of ongoing operations. Bad debts and prior period expenses were allowed as legitimate business expenditures. The Tribunal emphasized the statutory and business necessity of these expenses, classifying them as revenue expenses under the Income Tax Act.</description>
      <category>Case-Laws</category>
      <law>Income Tax</law>
      <pubDate>Wed, 02 Mar 2016 00:00:00 +0530</pubDate>
      <guid isPermaLink="true">https://www.taxtmi.com/caselaws?id=325316</guid>
    </item>
  </channel>
</rss>