<?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 (9) TMI 1622 - ITAT KOLKATA</title>
    <link>https://www.taxtmi.com/caselaws?id=799596</link>
    <description>Prior written or electronic intimation to the assessee is mandatory before making an adjustment during return processing, including an adjustment under Section 143(1)(a)(vii). Failure to issue a show-cause notice or other prior intimation invalidates the resulting intimation and adjustment. Unavailability of accounts and absence of statutory notice, preventing access to the impugned order and timely pursuit of the remedy, constitute sufficient cause for condoning delay in filing an appeal under Section 249(3).</description>
    <language>en-us</language>
    <pubDate>Thu, 27 Aug 2026 00:00:00 +0530</pubDate>
    <lastBuildDate>Thu, 24 Sep 2026 08:27:17 +0530</lastBuildDate>
    <generator>TaxTMI RSS Generator</generator>
    <atom:link href="https://www.taxtmi.com/rss_feed_blog?id=925462" rel="self" type="application/rss+xml"/>
    <item>
      <title>2026 (9) TMI 1622 - ITAT KOLKATA</title>
      <link>https://www.taxtmi.com/caselaws?id=799596</link>
      <description>Prior written or electronic intimation to the assessee is mandatory before making an adjustment during return processing, including an adjustment under Section 143(1)(a)(vii). Failure to issue a show-cause notice or other prior intimation invalidates the resulting intimation and adjustment. Unavailability of accounts and absence of statutory notice, preventing access to the impugned order and timely pursuit of the remedy, constitute sufficient cause for condoning delay in filing an appeal under Section 249(3).</description>
      <category>Case-Laws</category>
      <law>Income Tax</law>
      <pubDate>Thu, 27 Aug 2026 00:00:00 +0530</pubDate>
      <guid isPermaLink="true">https://www.taxtmi.com/caselaws?id=799596</guid>
    </item>
  </channel>
</rss>