<?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 (4) TMI 1038 - BOMBAY HIGH COURT</title>
    <link>https://www.taxtmi.com/caselaws?id=378594</link>
    <description>The High Court set aside the notice challenging the assessment under the Income Tax Act, ruling in favor of the Petitioner. The Court emphasized the importance of true and full disclosure by the Assessee and clarified the interpretation of relevant legal provisions. The judgment highlighted that non-disclosure cannot be blamed on the Assessee if the Assessing Officer had access to the information during the original assessment, ultimately allowing the petition challenging the reopening of the assessment.</description>
    <language>en-us</language>
    <pubDate>Fri, 05 Apr 2019 00:00:00 +0530</pubDate>
    <lastBuildDate>Wed, 21 Aug 2019 11:02:00 +0530</lastBuildDate>
    <generator>TaxTMI RSS Generator</generator>
    <atom:link href="https://www.taxtmi.com/rss_feed_blog?id=567407" rel="self" type="application/rss+xml"/>
    <item>
      <title>2019 (4) TMI 1038 - BOMBAY HIGH COURT</title>
      <link>https://www.taxtmi.com/caselaws?id=378594</link>
      <description>The High Court set aside the notice challenging the assessment under the Income Tax Act, ruling in favor of the Petitioner. The Court emphasized the importance of true and full disclosure by the Assessee and clarified the interpretation of relevant legal provisions. The judgment highlighted that non-disclosure cannot be blamed on the Assessee if the Assessing Officer had access to the information during the original assessment, ultimately allowing the petition challenging the reopening of the assessment.</description>
      <category>Case-Laws</category>
      <law>Income Tax</law>
      <pubDate>Fri, 05 Apr 2019 00:00:00 +0530</pubDate>
      <guid isPermaLink="true">https://www.taxtmi.com/caselaws?id=378594</guid>
    </item>
  </channel>
</rss>