<?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 (11) TMI 65 - JHARKHAND HIGH COURT</title>
    <link>https://www.taxtmi.com/caselaws?id=780597</link>
    <description>A tax appeal should not be rejected on a purely technical ground such as non-receipt of certified copies when an effective opportunity of hearing has not been afforded. The High Court held that a hyper-technical approach was inappropriate in proceedings involving financial liability, and that the appellate authority ought to have considered the matter on merits. The order rejecting the appeal was therefore unsustainable and was set aside, with a direction to hear and decide the appeal afresh on merits.</description>
    <language>en-us</language>
    <pubDate>Mon, 06 Oct 2025 00:00:00 +0530</pubDate>
    <lastBuildDate>Sat, 01 Nov 2025 08:17:02 +0530</lastBuildDate>
    <generator>TaxTMI RSS Generator</generator>
    <atom:link href="https://www.taxtmi.com/rss_feed_blog?id=861547" rel="self" type="application/rss+xml"/>
    <item>
      <title>2025 (11) TMI 65 - JHARKHAND HIGH COURT</title>
      <link>https://www.taxtmi.com/caselaws?id=780597</link>
      <description>A tax appeal should not be rejected on a purely technical ground such as non-receipt of certified copies when an effective opportunity of hearing has not been afforded. The High Court held that a hyper-technical approach was inappropriate in proceedings involving financial liability, and that the appellate authority ought to have considered the matter on merits. The order rejecting the appeal was therefore unsustainable and was set aside, with a direction to hear and decide the appeal afresh on merits.</description>
      <category>Case-Laws</category>
      <law>GST</law>
      <pubDate>Mon, 06 Oct 2025 00:00:00 +0530</pubDate>
      <guid isPermaLink="true">https://www.taxtmi.com/caselaws?id=780597</guid>
    </item>
  </channel>
</rss>