<?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>INCOME TAX RETURN FILED BY A DELAY OF 2 SECONDS</title>
    <link>https://www.taxtmi.com/article/detailed?id=14688</link>
    <description>The Tribunal considered whether a two second e filing delay recorded by the system, caused by portal congestion and technical glitch, should defeat the assessee&#039;s classification as a timely filer and thereby bar carry forward of business loss. Relying on precedents excusing minimal delays due to electronic portal malfunction or last hour rush, the Tribunal treated the original return as filed under section 139(1) and restored the consequences associated with timely filing.</description>
    <language>en-us</language>
    <pubDate>Tue, 24 Jun 2025 08:27:15 +0530</pubDate>
    <lastBuildDate>Tue, 24 Jun 2025 08:27:15 +0530</lastBuildDate>
    <generator>TaxTMI RSS Generator</generator>
    <atom:link href="https://www.taxtmi.com/rss_feed_blog?id=831242" rel="self" type="application/rss+xml"/>
    <item>
      <title>INCOME TAX RETURN FILED BY A DELAY OF 2 SECONDS</title>
      <link>https://www.taxtmi.com/article/detailed?id=14688</link>
      <description>The Tribunal considered whether a two second e filing delay recorded by the system, caused by portal congestion and technical glitch, should defeat the assessee&#039;s classification as a timely filer and thereby bar carry forward of business loss. Relying on precedents excusing minimal delays due to electronic portal malfunction or last hour rush, the Tribunal treated the original return as filed under section 139(1) and restored the consequences associated with timely filing.</description>
      <category>Articles</category>
      <law>Income Tax</law>
      <pubDate>Tue, 24 Jun 2025 08:27:15 +0530</pubDate>
      <guid isPermaLink="true">https://www.taxtmi.com/article/detailed?id=14688</guid>
    </item>
  </channel>
</rss>