<?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 (7) TMI 2023 - ITAT CHENNAI</title>
    <link>https://www.taxtmi.com/caselaws?id=468962</link>
    <description>Late fee under section 234E was held not to be leviable while processing quarterly TDS statements under section 200A for periods before 01.06.2015, because section 234E created the substantive liability but section 200A(1)(c) was the enabling provision for computation at processing stage and operated only from that date. For pre-01.06.2015 periods, the processing mechanism did not authorise levy of the fee through section 200A, so the levy was directed to be deleted in favour of the assessee.</description>
    <language>en-us</language>
    <pubDate>Tue, 15 Jul 2025 00:00:00 +0530</pubDate>
    <lastBuildDate>Tue, 26 May 2026 21:06:12 +0530</lastBuildDate>
    <generator>TaxTMI RSS Generator</generator>
    <atom:link href="https://www.taxtmi.com/rss_feed_blog?id=903915" rel="self" type="application/rss+xml"/>
    <item>
      <title>2025 (7) TMI 2023 - ITAT CHENNAI</title>
      <link>https://www.taxtmi.com/caselaws?id=468962</link>
      <description>Late fee under section 234E was held not to be leviable while processing quarterly TDS statements under section 200A for periods before 01.06.2015, because section 234E created the substantive liability but section 200A(1)(c) was the enabling provision for computation at processing stage and operated only from that date. For pre-01.06.2015 periods, the processing mechanism did not authorise levy of the fee through section 200A, so the levy was directed to be deleted in favour of the assessee.</description>
      <category>Case-Laws</category>
      <law>Income Tax</law>
      <pubDate>Tue, 15 Jul 2025 00:00:00 +0530</pubDate>
      <guid isPermaLink="true">https://www.taxtmi.com/caselaws?id=468962</guid>
    </item>
  </channel>
</rss>