<?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 (7) TMI 1731 - DELHI HIGH COURT</title>
    <link>https://www.taxtmi.com/caselaws?id=795845</link>
    <description>Concurrent factual findings on the attribution of a seized document cannot be disturbed in an appeal under Section 260A unless shown to be perverse. Where the original seized document was unavailable and the appellate authorities found that the scanned entry referred to another entity rather than the assessee, the challenge raised only a factual dispute. The High Court found no perversity in that concurrent finding and therefore declined interference, deciding the issue in favour of the assessee.</description>
    <language>en-us</language>
    <pubDate>Thu, 23 Jul 2026 00:00:00 +0530</pubDate>
    <lastBuildDate>Tue, 28 Jul 2026 08:30:44 +0530</lastBuildDate>
    <generator>TaxTMI RSS Generator</generator>
    <atom:link href="https://www.taxtmi.com/rss_feed_blog?id=913846" rel="self" type="application/rss+xml"/>
    <item>
      <title>2026 (7) TMI 1731 - DELHI HIGH COURT</title>
      <link>https://www.taxtmi.com/caselaws?id=795845</link>
      <description>Concurrent factual findings on the attribution of a seized document cannot be disturbed in an appeal under Section 260A unless shown to be perverse. Where the original seized document was unavailable and the appellate authorities found that the scanned entry referred to another entity rather than the assessee, the challenge raised only a factual dispute. The High Court found no perversity in that concurrent finding and therefore declined interference, deciding the issue in favour of the assessee.</description>
      <category>Case-Laws</category>
      <law>Income Tax</law>
      <pubDate>Thu, 23 Jul 2026 00:00:00 +0530</pubDate>
      <guid isPermaLink="true">https://www.taxtmi.com/caselaws?id=795845</guid>
    </item>
  </channel>
</rss>