<?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>1998 (4) TMI 564 - DELHI HIGH COURT</title>
    <link>https://www.taxtmi.com/caselaws?id=283045</link>
    <description>An assessing authority must give effect to an appellate order once it has modified the assessment, and cannot refuse implementation merely because a rectification application under section 154 is pending. Recovery action under section 226(3) based on that refusal is not sustainable. Where attachment notices and the underlying assessment are founded on non-compliance with the appellate order, they are liable to be quashed, and the tax liability must instead be recomputed in accordance with the appellate order.</description>
    <language>en-us</language>
    <pubDate>Fri, 03 Apr 1998 00:00:00 +0530</pubDate>
    <lastBuildDate>Wed, 04 Sep 2019 16:26:19 +0530</lastBuildDate>
    <generator>TaxTMI RSS Generator</generator>
    <atom:link href="https://www.taxtmi.com/rss_feed_blog?id=586040" rel="self" type="application/rss+xml"/>
    <item>
      <title>1998 (4) TMI 564 - DELHI HIGH COURT</title>
      <link>https://www.taxtmi.com/caselaws?id=283045</link>
      <description>An assessing authority must give effect to an appellate order once it has modified the assessment, and cannot refuse implementation merely because a rectification application under section 154 is pending. Recovery action under section 226(3) based on that refusal is not sustainable. Where attachment notices and the underlying assessment are founded on non-compliance with the appellate order, they are liable to be quashed, and the tax liability must instead be recomputed in accordance with the appellate order.</description>
      <category>Case-Laws</category>
      <law>Income Tax</law>
      <pubDate>Fri, 03 Apr 1998 00:00:00 +0530</pubDate>
      <guid isPermaLink="true">https://www.taxtmi.com/caselaws?id=283045</guid>
    </item>
  </channel>
</rss>