<?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>2009 (10) TMI 462 - PUNJAB &amp; HARYANA HIGH COURT</title>
    <link>https://www.taxtmi.com/caselaws?id=77679</link>
    <description>The dominant issue was whether penalty under s. 271D was exigible for accepting share application money in cash in contravention of s. 269SS. The HC held that the appellate authority&#039;s finding that the transaction was bona fide and the breach was merely technical, attracting the protective ambit of reasonable cause and not warranting penal consequences, was neither perverse nor unreasonable; consequently, the deletion of penalty was sustained and the revenue&#039;s appeal was dismissed.</description>
    <language>en-us</language>
    <pubDate>Thu, 22 Oct 2009 00:00:00 +0530</pubDate>
    <lastBuildDate>Sat, 10 Jan 2026 13:44:00 +0530</lastBuildDate>
    <generator>TaxTMI RSS Generator</generator>
    <atom:link href="https://www.taxtmi.com/rss_feed_blog?id=115842" rel="self" type="application/rss+xml"/>
    <item>
      <title>2009 (10) TMI 462 - PUNJAB &amp; HARYANA HIGH COURT</title>
      <link>https://www.taxtmi.com/caselaws?id=77679</link>
      <description>The dominant issue was whether penalty under s. 271D was exigible for accepting share application money in cash in contravention of s. 269SS. The HC held that the appellate authority&#039;s finding that the transaction was bona fide and the breach was merely technical, attracting the protective ambit of reasonable cause and not warranting penal consequences, was neither perverse nor unreasonable; consequently, the deletion of penalty was sustained and the revenue&#039;s appeal was dismissed.</description>
      <category>Case-Laws</category>
      <law>Income Tax</law>
      <pubDate>Thu, 22 Oct 2009 00:00:00 +0530</pubDate>
      <guid isPermaLink="true">https://www.taxtmi.com/caselaws?id=77679</guid>
    </item>
  </channel>
</rss>