<?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>2003 (5) TMI 229 - ITAT LUCKNOW</title>
    <link>https://www.taxtmi.com/caselaws?id=68763</link>
    <description>The Tribunal allowed the appeal of the assessee, holding that the assessment order was beyond time and lacked jurisdiction due to procedural irregularities under section 148. The Tribunal did not delve into the merits of the share dealings or the set off of loss against other income, as the primary reason for allowing the appeal was the invalidity of the proceedings initiated under section 148. The CIT(A)&#039;s order was set aside due to the failure to address critical issues related to the assessment process.</description>
    <language>en-us</language>
    <pubDate>Wed, 28 May 2003 00:00:00 +0530</pubDate>
    <lastBuildDate>Fri, 01 Apr 2011 13:19:36 +0530</lastBuildDate>
    <generator>TaxTMI RSS Generator</generator>
    <atom:link href="https://www.taxtmi.com/rss_feed_blog?id=107140" rel="self" type="application/rss+xml"/>
    <item>
      <title>2003 (5) TMI 229 - ITAT LUCKNOW</title>
      <link>https://www.taxtmi.com/caselaws?id=68763</link>
      <description>The Tribunal allowed the appeal of the assessee, holding that the assessment order was beyond time and lacked jurisdiction due to procedural irregularities under section 148. The Tribunal did not delve into the merits of the share dealings or the set off of loss against other income, as the primary reason for allowing the appeal was the invalidity of the proceedings initiated under section 148. The CIT(A)&#039;s order was set aside due to the failure to address critical issues related to the assessment process.</description>
      <category>Case-Laws</category>
      <law>Income Tax</law>
      <pubDate>Wed, 28 May 2003 00:00:00 +0530</pubDate>
      <guid isPermaLink="true">https://www.taxtmi.com/caselaws?id=68763</guid>
    </item>
  </channel>
</rss>