<?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 (6) TMI 1566 - UTTARAKHAND HIGH COURT</title>
    <link>https://www.taxtmi.com/caselaws?id=773453</link>
    <description>The pending application for revocation of cancellation of GST registration was linked to compliance with a procedural requirement: furnishing the GPS position of the place of business. The petitioner was given time to supply the missing geo-tagging particulars, and once that information was filed, the revocation request was to be considered and disposed of in accordance with law. The matter was therefore concluded by allowing an to cure the defect so the application could be decided on its merits.</description>
    <language>en-us</language>
    <pubDate>Mon, 09 Jun 2025 00:00:00 +0530</pubDate>
    <lastBuildDate>Mon, 23 Jun 2025 10:27:17 +0530</lastBuildDate>
    <generator>TaxTMI RSS Generator</generator>
    <atom:link href="https://www.taxtmi.com/rss_feed_blog?id=830861" rel="self" type="application/rss+xml"/>
    <item>
      <title>2025 (6) TMI 1566 - UTTARAKHAND HIGH COURT</title>
      <link>https://www.taxtmi.com/caselaws?id=773453</link>
      <description>The pending application for revocation of cancellation of GST registration was linked to compliance with a procedural requirement: furnishing the GPS position of the place of business. The petitioner was given time to supply the missing geo-tagging particulars, and once that information was filed, the revocation request was to be considered and disposed of in accordance with law. The matter was therefore concluded by allowing an to cure the defect so the application could be decided on its merits.</description>
      <category>Case-Laws</category>
      <law>GST</law>
      <pubDate>Mon, 09 Jun 2025 00:00:00 +0530</pubDate>
      <guid isPermaLink="true">https://www.taxtmi.com/caselaws?id=773453</guid>
    </item>
  </channel>
</rss>