<?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 (7) TMI 1449 - Supreme Court</title>
    <link>https://www.taxtmi.com/caselaws?id=383753</link>
    <description>SC held the assessment void where the jurisdictional notice under s.143(2) was issued to a non-existent amalgamating entity and the order was framed against the amalgamating company; this constituted substantive illegality not curable under s.292B. Participation by the taxpayer could not estop the law. Relying on the co-ordinate bench precedent, the Court applied the same view to the relevant assessment year to preserve consistency and certainty in tax litigation, resulting in the assessment being set aside.</description>
    <language>en-us</language>
    <pubDate>Thu, 25 Jul 2019 00:00:00 +0530</pubDate>
    <lastBuildDate>Wed, 18 Mar 2026 15:49:00 +0530</lastBuildDate>
    <generator>TaxTMI RSS Generator</generator>
    <atom:link href="https://www.taxtmi.com/rss_feed_blog?id=581699" rel="self" type="application/rss+xml"/>
    <item>
      <title>2019 (7) TMI 1449 - Supreme Court</title>
      <link>https://www.taxtmi.com/caselaws?id=383753</link>
      <description>SC held the assessment void where the jurisdictional notice under s.143(2) was issued to a non-existent amalgamating entity and the order was framed against the amalgamating company; this constituted substantive illegality not curable under s.292B. Participation by the taxpayer could not estop the law. Relying on the co-ordinate bench precedent, the Court applied the same view to the relevant assessment year to preserve consistency and certainty in tax litigation, resulting in the assessment being set aside.</description>
      <category>Case-Laws</category>
      <law>Income Tax</law>
      <pubDate>Thu, 25 Jul 2019 00:00:00 +0530</pubDate>
      <guid isPermaLink="true">https://www.taxtmi.com/caselaws?id=383753</guid>
    </item>
  </channel>
</rss>