<?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>2024 (5) TMI 33 - MADRAS HIGH COURT</title>
    <link>https://www.taxtmi.com/caselaws?id=751980</link>
    <description>Writ jurisdiction was not entertained against a revisional order because the petitioner had an effective statutory appellate remedy and the dispute involved contested factual issues arising from survey, assessment, revision, and demand proceedings. The court treated the availability of an appeal as the proper course for challenging the revisional action and declined to examine the merits in writ proceedings. The petition was therefore disposed of, with liberty to pursue the statutory appeal remedy.</description>
    <language>en-us</language>
    <pubDate>Tue, 23 Apr 2024 00:00:00 +0530</pubDate>
    <lastBuildDate>Wed, 01 May 2024 08:42:56 +0530</lastBuildDate>
    <generator>TaxTMI RSS Generator</generator>
    <atom:link href="https://www.taxtmi.com/rss_feed_blog?id=751552" rel="self" type="application/rss+xml"/>
    <item>
      <title>2024 (5) TMI 33 - MADRAS HIGH COURT</title>
      <link>https://www.taxtmi.com/caselaws?id=751980</link>
      <description>Writ jurisdiction was not entertained against a revisional order because the petitioner had an effective statutory appellate remedy and the dispute involved contested factual issues arising from survey, assessment, revision, and demand proceedings. The court treated the availability of an appeal as the proper course for challenging the revisional action and declined to examine the merits in writ proceedings. The petition was therefore disposed of, with liberty to pursue the statutory appeal remedy.</description>
      <category>Case-Laws</category>
      <law>Income Tax</law>
      <pubDate>Tue, 23 Apr 2024 00:00:00 +0530</pubDate>
      <guid isPermaLink="true">https://www.taxtmi.com/caselaws?id=751980</guid>
    </item>
  </channel>
</rss>