<?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>2006 (1) TMI 187 - ITAT DELHI-G</title>
    <link>https://www.taxtmi.com/caselaws?id=65446</link>
    <description>The Tribunal focused on the jurisdictional validity of the block assessment order under s. 158BC of the IT Act and the adherence to the statutory limitation period under s. 158BE. It found the assessment to be beyond the permissible timeframe, rendering it invalid. As a result, the Department&#039;s appeal was dismissed, and the assessee&#039;s cross-objections were allowed, with no costs awarded. The Tribunal&#039;s decision emphasized the importance of jurisdiction and statutory timelines in such assessments.</description>
    <language>en-us</language>
    <pubDate>Fri, 20 Jan 2006 00:00:00 +0530</pubDate>
    <lastBuildDate>Wed, 18 Jul 2012 12:29:00 +0530</lastBuildDate>
    <generator>TaxTMI RSS Generator</generator>
    <atom:link href="https://www.taxtmi.com/rss_feed_blog?id=103885" rel="self" type="application/rss+xml"/>
    <item>
      <title>2006 (1) TMI 187 - ITAT DELHI-G</title>
      <link>https://www.taxtmi.com/caselaws?id=65446</link>
      <description>The Tribunal focused on the jurisdictional validity of the block assessment order under s. 158BC of the IT Act and the adherence to the statutory limitation period under s. 158BE. It found the assessment to be beyond the permissible timeframe, rendering it invalid. As a result, the Department&#039;s appeal was dismissed, and the assessee&#039;s cross-objections were allowed, with no costs awarded. The Tribunal&#039;s decision emphasized the importance of jurisdiction and statutory timelines in such assessments.</description>
      <category>Case-Laws</category>
      <law>Income Tax</law>
      <pubDate>Fri, 20 Jan 2006 00:00:00 +0530</pubDate>
      <guid isPermaLink="true">https://www.taxtmi.com/caselaws?id=65446</guid>
    </item>
  </channel>
</rss>