<?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>2012 (6) TMI 685 - BOMBAY HIGH COURT</title>
    <link>https://www.taxtmi.com/caselaws?id=214386</link>
    <description>The court ruled in favor of the Revenue, considering the professional fees as capital expenditure for an existing business extension. The court relied on precedents establishing that expenses for exploring the feasibility of a new business venture are capital in nature. Despite the applicant&#039;s advocate arguing for a different interpretation based on interconnection between existing and new business, the court upheld the previous decisions. The reference was disposed of with no order as to costs.</description>
    <language>en-us</language>
    <pubDate>Fri, 15 Jun 2012 00:00:00 +0530</pubDate>
    <lastBuildDate>Thu, 28 Jun 2012 18:48:00 +0530</lastBuildDate>
    <generator>TaxTMI RSS Generator</generator>
    <atom:link href="https://www.taxtmi.com/rss_feed_blog?id=187781" rel="self" type="application/rss+xml"/>
    <item>
      <title>2012 (6) TMI 685 - BOMBAY HIGH COURT</title>
      <link>https://www.taxtmi.com/caselaws?id=214386</link>
      <description>The court ruled in favor of the Revenue, considering the professional fees as capital expenditure for an existing business extension. The court relied on precedents establishing that expenses for exploring the feasibility of a new business venture are capital in nature. Despite the applicant&#039;s advocate arguing for a different interpretation based on interconnection between existing and new business, the court upheld the previous decisions. The reference was disposed of with no order as to costs.</description>
      <category>Case-Laws</category>
      <law>Income Tax</law>
      <pubDate>Fri, 15 Jun 2012 00:00:00 +0530</pubDate>
      <guid isPermaLink="true">https://www.taxtmi.com/caselaws?id=214386</guid>
    </item>
  </channel>
</rss>