<?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 (6) TMI 1515 - MADRAS HIGH COURT</title>
    <link>https://www.taxtmi.com/caselaws?id=289703</link>
    <description>An assessment order under Section 22(4) of the Tamil Nadu Value Added Tax Act, 2006 is vulnerable where the dealer is not given the reasonable opportunity of being heard required by the proviso. The record did not establish due service of the notice allegedly issued, and the chronology in the order made the claimed hearing doubtful. On that basis, the court found that the requirement of personal hearing was not satisfied and the impugned order was set aside for breach of the statutory proviso.</description>
    <language>en-us</language>
    <pubDate>Thu, 27 Jun 2019 00:00:00 +0530</pubDate>
    <lastBuildDate>Mon, 17 Aug 2020 07:35:44 +0530</lastBuildDate>
    <generator>TaxTMI RSS Generator</generator>
    <atom:link href="https://www.taxtmi.com/rss_feed_blog?id=619739" rel="self" type="application/rss+xml"/>
    <item>
      <title>2019 (6) TMI 1515 - MADRAS HIGH COURT</title>
      <link>https://www.taxtmi.com/caselaws?id=289703</link>
      <description>An assessment order under Section 22(4) of the Tamil Nadu Value Added Tax Act, 2006 is vulnerable where the dealer is not given the reasonable opportunity of being heard required by the proviso. The record did not establish due service of the notice allegedly issued, and the chronology in the order made the claimed hearing doubtful. On that basis, the court found that the requirement of personal hearing was not satisfied and the impugned order was set aside for breach of the statutory proviso.</description>
      <category>Case-Laws</category>
      <law>VAT and Sales Tax</law>
      <pubDate>Thu, 27 Jun 2019 00:00:00 +0530</pubDate>
      <guid isPermaLink="true">https://www.taxtmi.com/caselaws?id=289703</guid>
    </item>
  </channel>
</rss>