<?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 (6) TMI 148 - KARNATAKA HIGH COURT</title>
    <link>https://www.taxtmi.com/caselaws?id=381071</link>
    <description>Coercive recovery of disputed tax demand was held impermissible while stay applications under Section 220(6) remained pending, because the authority was required to decide the stay request first in accordance with the governing instructions and after hearing the assessee. The recovery notice was therefore quashed, and the matter was remitted for fresh consideration of the stay applications. The assessee obtained interim protection against enforcement until the stay issue was reconsidered lawfully.</description>
    <language>en-us</language>
    <pubDate>Tue, 05 Mar 2019 00:00:00 +0530</pubDate>
    <lastBuildDate>Mon, 03 Jun 2019 12:23:00 +0530</lastBuildDate>
    <generator>TaxTMI RSS Generator</generator>
    <atom:link href="https://www.taxtmi.com/rss_feed_blog?id=573868" rel="self" type="application/rss+xml"/>
    <item>
      <title>2019 (6) TMI 148 - KARNATAKA HIGH COURT</title>
      <link>https://www.taxtmi.com/caselaws?id=381071</link>
      <description>Coercive recovery of disputed tax demand was held impermissible while stay applications under Section 220(6) remained pending, because the authority was required to decide the stay request first in accordance with the governing instructions and after hearing the assessee. The recovery notice was therefore quashed, and the matter was remitted for fresh consideration of the stay applications. The assessee obtained interim protection against enforcement until the stay issue was reconsidered lawfully.</description>
      <category>Case-Laws</category>
      <law>Income Tax</law>
      <pubDate>Tue, 05 Mar 2019 00:00:00 +0530</pubDate>
      <guid isPermaLink="true">https://www.taxtmi.com/caselaws?id=381071</guid>
    </item>
  </channel>
</rss>