<?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 (11) TMI 766 - MADRAS HIGH COURT</title>
    <link>https://www.taxtmi.com/caselaws?id=388517</link>
    <description>The court found the recovery proceedings initiated under the GST Act unsustainable as they were based on an admission lacking clarity and consistency. Despite the respondents&#039; reliance on Section 83 for provisional attachment, the court ruled that attachment could only occur when specific proceedings were pending, which was not the case. The court allowed the writ petition, setting aside the recovery proceedings without expressing an opinion on the merits, leaving resolution to proper legal procedures.</description>
    <language>en-us</language>
    <pubDate>Fri, 08 Nov 2019 00:00:00 +0530</pubDate>
    <lastBuildDate>Wed, 28 Oct 2020 11:54:00 +0530</lastBuildDate>
    <generator>TaxTMI RSS Generator</generator>
    <atom:link href="https://www.taxtmi.com/rss_feed_blog?id=594428" rel="self" type="application/rss+xml"/>
    <item>
      <title>2019 (11) TMI 766 - MADRAS HIGH COURT</title>
      <link>https://www.taxtmi.com/caselaws?id=388517</link>
      <description>The court found the recovery proceedings initiated under the GST Act unsustainable as they were based on an admission lacking clarity and consistency. Despite the respondents&#039; reliance on Section 83 for provisional attachment, the court ruled that attachment could only occur when specific proceedings were pending, which was not the case. The court allowed the writ petition, setting aside the recovery proceedings without expressing an opinion on the merits, leaving resolution to proper legal procedures.</description>
      <category>Case-Laws</category>
      <law>GST</law>
      <pubDate>Fri, 08 Nov 2019 00:00:00 +0530</pubDate>
      <guid isPermaLink="true">https://www.taxtmi.com/caselaws?id=388517</guid>
    </item>
  </channel>
</rss>