<?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 (5) TMI 740 - ITAT RAIPUR</title>
    <link>https://www.taxtmi.com/caselaws?id=791538</link>
    <description>Penalty under Section 271D could not be sustained because the assessment order accepted the returned income, made no quantum addition, and recorded no satisfaction for initiating penalty proceedings. The Tribunal held that penalty for breach of Section 269SS must have a valid jurisdictional foundation in the assessment order itself; a separate show-cause notice issued later could not cure the absence of such satisfaction. On that basis, the penalty order was set aside and the assessee&#039;s appeal succeeded.</description>
    <language>en-us</language>
    <pubDate>Mon, 11 May 2026 00:00:00 +0530</pubDate>
    <lastBuildDate>Wed, 13 May 2026 08:36:19 +0530</lastBuildDate>
    <generator>TaxTMI RSS Generator</generator>
    <atom:link href="https://www.taxtmi.com/rss_feed_blog?id=901582" rel="self" type="application/rss+xml"/>
    <item>
      <title>2026 (5) TMI 740 - ITAT RAIPUR</title>
      <link>https://www.taxtmi.com/caselaws?id=791538</link>
      <description>Penalty under Section 271D could not be sustained because the assessment order accepted the returned income, made no quantum addition, and recorded no satisfaction for initiating penalty proceedings. The Tribunal held that penalty for breach of Section 269SS must have a valid jurisdictional foundation in the assessment order itself; a separate show-cause notice issued later could not cure the absence of such satisfaction. On that basis, the penalty order was set aside and the assessee&#039;s appeal succeeded.</description>
      <category>Case-Laws</category>
      <law>Income Tax</law>
      <pubDate>Mon, 11 May 2026 00:00:00 +0530</pubDate>
      <guid isPermaLink="true">https://www.taxtmi.com/caselaws?id=791538</guid>
    </item>
  </channel>
</rss>