<?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>2026 (4) TMI 960 - ITAT DELHI</title>
    <link>https://www.taxtmi.com/caselaws?id=789891</link>
    <description>Foreign contribution fully disclosed in the books and return could not be added merely because it was placed in the wrong schedule. The ITAT Delhi applied the principle that tax cannot be levied beyond what is legitimately due and treated the mistake as an inadvertent clerical or schedule-entry error. As the disclosure was otherwise complete and the only objection was the absence of a revised return, the addition made while processing the return under section 143(1) was held unsustainable and deleted.</description>
    <language>en-us</language>
    <pubDate>Wed, 25 Mar 2026 00:00:00 +0530</pubDate>
    <lastBuildDate>Thu, 16 Apr 2026 08:34:10 +0530</lastBuildDate>
    <generator>TaxTMI RSS Generator</generator>
    <atom:link href="https://www.taxtmi.com/rss_feed_blog?id=896996" rel="self" type="application/rss+xml"/>
    <item>
      <title>2026 (4) TMI 960 - ITAT DELHI</title>
      <link>https://www.taxtmi.com/caselaws?id=789891</link>
      <description>Foreign contribution fully disclosed in the books and return could not be added merely because it was placed in the wrong schedule. The ITAT Delhi applied the principle that tax cannot be levied beyond what is legitimately due and treated the mistake as an inadvertent clerical or schedule-entry error. As the disclosure was otherwise complete and the only objection was the absence of a revised return, the addition made while processing the return under section 143(1) was held unsustainable and deleted.</description>
      <category>Case-Laws</category>
      <law>Income Tax</law>
      <pubDate>Wed, 25 Mar 2026 00:00:00 +0530</pubDate>
      <guid isPermaLink="true">https://www.taxtmi.com/caselaws?id=789891</guid>
    </item>
  </channel>
</rss>