<?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>2025 (5) TMI 977 - KARNATAKA HIGH COURT</title>
    <link>https://www.taxtmi.com/caselaws?id=770705</link>
    <description>Karnataka HC held that the revenue authority erred in passing a final assessment order without awaiting conclusion of Dispute Resolution Panel proceedings. The court found that since the petitioner had filed objections before DRP, despite website glitches preventing proper intimation, the assessing officer should have waited for DRP&#039;s outcome. The assessment order was set aside and DRP was directed to conclude proceedings by considering the objections in accordance with law. Petition was allowed.</description>
    <language>en-us</language>
    <pubDate>Wed, 16 Apr 2025 00:00:00 +0530</pubDate>
    <lastBuildDate>Thu, 15 May 2025 07:32:21 +0530</lastBuildDate>
    <generator>TaxTMI RSS Generator</generator>
    <atom:link href="https://www.taxtmi.com/rss_feed_blog?id=821832" rel="self" type="application/rss+xml"/>
    <item>
      <title>2025 (5) TMI 977 - KARNATAKA HIGH COURT</title>
      <link>https://www.taxtmi.com/caselaws?id=770705</link>
      <description>Karnataka HC held that the revenue authority erred in passing a final assessment order without awaiting conclusion of Dispute Resolution Panel proceedings. The court found that since the petitioner had filed objections before DRP, despite website glitches preventing proper intimation, the assessing officer should have waited for DRP&#039;s outcome. The assessment order was set aside and DRP was directed to conclude proceedings by considering the objections in accordance with law. Petition was allowed.</description>
      <category>Case-Laws</category>
      <law>Income Tax</law>
      <pubDate>Wed, 16 Apr 2025 00:00:00 +0530</pubDate>
      <guid isPermaLink="true">https://www.taxtmi.com/caselaws?id=770705</guid>
    </item>
  </channel>
</rss>