<?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 (2) TMI 1939 - ITAT COCHIN</title>
    <link>https://www.taxtmi.com/caselaws?id=468911</link>
    <description>Where a return is filed within the CBDT-extended due date, it cannot be treated as belated for the purpose of denying deduction under section 80P merely because processing under section 143(1) proceeds on an incorrect assumption of delay. The revised return was also furnished before the defect notice under section 139(9), so the original return was not non est. On those facts, the disallowance based solely on timeliness could not survive, and the intimation was directed to be rectified in favour of the assessee.</description>
    <language>en-us</language>
    <pubDate>Mon, 10 Feb 2025 00:00:00 +0530</pubDate>
    <lastBuildDate>Mon, 25 May 2026 20:05:31 +0530</lastBuildDate>
    <generator>TaxTMI RSS Generator</generator>
    <atom:link href="https://www.taxtmi.com/rss_feed_blog?id=903723" rel="self" type="application/rss+xml"/>
    <item>
      <title>2025 (2) TMI 1939 - ITAT COCHIN</title>
      <link>https://www.taxtmi.com/caselaws?id=468911</link>
      <description>Where a return is filed within the CBDT-extended due date, it cannot be treated as belated for the purpose of denying deduction under section 80P merely because processing under section 143(1) proceeds on an incorrect assumption of delay. The revised return was also furnished before the defect notice under section 139(9), so the original return was not non est. On those facts, the disallowance based solely on timeliness could not survive, and the intimation was directed to be rectified in favour of the assessee.</description>
      <category>Case-Laws</category>
      <law>Income Tax</law>
      <pubDate>Mon, 10 Feb 2025 00:00:00 +0530</pubDate>
      <guid isPermaLink="true">https://www.taxtmi.com/caselaws?id=468911</guid>
    </item>
  </channel>
</rss>