<?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>2015 (11) TMI 492 - ITAT DELHI</title>
    <link>https://www.taxtmi.com/caselaws?id=267683</link>
    <description>The Tribunal upheld the CIT(A)&#039;s decision to delete the addition made by the Assessing Officer, ruling that the expenses incurred by the assessee for business purposes, after the commencement of business with the acquisition of development rights, should be allowed as revenue expenditure. The Tribunal dismissed the department&#039;s appeal, citing legal precedents that distinguish between setting up and commencement of business, and holding that expenses post-setting up but pre-commencement are deductible.</description>
    <language>en-us</language>
    <pubDate>Wed, 14 Oct 2015 00:00:00 +0530</pubDate>
    <lastBuildDate>Tue, 10 Nov 2015 21:39:17 +0530</lastBuildDate>
    <generator>TaxTMI RSS Generator</generator>
    <atom:link href="https://www.taxtmi.com/rss_feed_blog?id=404973" rel="self" type="application/rss+xml"/>
    <item>
      <title>2015 (11) TMI 492 - ITAT DELHI</title>
      <link>https://www.taxtmi.com/caselaws?id=267683</link>
      <description>The Tribunal upheld the CIT(A)&#039;s decision to delete the addition made by the Assessing Officer, ruling that the expenses incurred by the assessee for business purposes, after the commencement of business with the acquisition of development rights, should be allowed as revenue expenditure. The Tribunal dismissed the department&#039;s appeal, citing legal precedents that distinguish between setting up and commencement of business, and holding that expenses post-setting up but pre-commencement are deductible.</description>
      <category>Case-Laws</category>
      <law>Income Tax</law>
      <pubDate>Wed, 14 Oct 2015 00:00:00 +0530</pubDate>
      <guid isPermaLink="true">https://www.taxtmi.com/caselaws?id=267683</guid>
    </item>
  </channel>
</rss>