<?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>2022 (3) TMI 454 - MADRAS HIGH COURT</title>
    <link>https://www.taxtmi.com/caselaws?id=419416</link>
    <description>Eligibility under the Sabka Vishwas (Legacy Dispute Resolution) Scheme, 2019 depended on service tax liability being quantified in writing on or before 30 June 2019. Where search and investigation had taken place but the duty had not crystallised by the cut-off date, the scheme condition was not met and rejection of the declaration was valid. A writ petition filed after the scheme had expired could not be entertained to revive consideration under the scheme, so the refusal to interfere was sustained.</description>
    <language>en-us</language>
    <pubDate>Wed, 23 Feb 2022 00:00:00 +0530</pubDate>
    <lastBuildDate>Fri, 21 Jun 2024 17:27:00 +0530</lastBuildDate>
    <generator>TaxTMI RSS Generator</generator>
    <atom:link href="https://www.taxtmi.com/rss_feed_blog?id=672585" rel="self" type="application/rss+xml"/>
    <item>
      <title>2022 (3) TMI 454 - MADRAS HIGH COURT</title>
      <link>https://www.taxtmi.com/caselaws?id=419416</link>
      <description>Eligibility under the Sabka Vishwas (Legacy Dispute Resolution) Scheme, 2019 depended on service tax liability being quantified in writing on or before 30 June 2019. Where search and investigation had taken place but the duty had not crystallised by the cut-off date, the scheme condition was not met and rejection of the declaration was valid. A writ petition filed after the scheme had expired could not be entertained to revive consideration under the scheme, so the refusal to interfere was sustained.</description>
      <category>Case-Laws</category>
      <law>Service Tax</law>
      <pubDate>Wed, 23 Feb 2022 00:00:00 +0530</pubDate>
      <guid isPermaLink="true">https://www.taxtmi.com/caselaws?id=419416</guid>
    </item>
  </channel>
</rss>