<?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>2023 (12) TMI 1200 - ITAT DELHI</title>
    <link>https://www.taxtmi.com/caselaws?id=447516</link>
    <description>The ITAT Delhi held that an AO&#039;s order without a DIN number mentioned in its body loses validity. The tribunal found no DIN number or reason for its absence in the assessment order. Subsequent separate communication of DIN was deemed superfluous. Citing Supreme Court precedent favoring assessee-friendly interpretation when two views are possible, and Delhi HC ruling that no income tax communication should be issued without computer-generated DIN after October 1, 2019, the tribunal decided against revenue.</description>
    <language>en-us</language>
    <pubDate>Tue, 26 Dec 2023 00:00:00 +0530</pubDate>
    <lastBuildDate>Thu, 28 Dec 2023 10:41:00 +0530</lastBuildDate>
    <generator>TaxTMI RSS Generator</generator>
    <atom:link href="https://www.taxtmi.com/rss_feed_blog?id=737334" rel="self" type="application/rss+xml"/>
    <item>
      <title>2023 (12) TMI 1200 - ITAT DELHI</title>
      <link>https://www.taxtmi.com/caselaws?id=447516</link>
      <description>The ITAT Delhi held that an AO&#039;s order without a DIN number mentioned in its body loses validity. The tribunal found no DIN number or reason for its absence in the assessment order. Subsequent separate communication of DIN was deemed superfluous. Citing Supreme Court precedent favoring assessee-friendly interpretation when two views are possible, and Delhi HC ruling that no income tax communication should be issued without computer-generated DIN after October 1, 2019, the tribunal decided against revenue.</description>
      <category>Case-Laws</category>
      <law>Income Tax</law>
      <pubDate>Tue, 26 Dec 2023 00:00:00 +0530</pubDate>
      <guid isPermaLink="true">https://www.taxtmi.com/caselaws?id=447516</guid>
    </item>
  </channel>
</rss>