<?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>1980 (6) TMI 71 - ITAT JAIPUR</title>
    <link>https://www.taxtmi.com/caselaws?id=67730</link>
    <description>A firm was treated as a real and existing family concern, so a mistaken description of one partner as a minor did not by itself defeat registration where the error was bona fide and later cured by a deed showing all partners as majors. The delay in filing the registration application was also treated as directory rather than fatal, because the application was filed before assessment was completed. On these facts, technical defects in the deed and timing of the application were not sufficient to deny registration.</description>
    <language>en-us</language>
    <pubDate>Mon, 23 Jun 1980 00:00:00 +0530</pubDate>
    <lastBuildDate>Mon, 14 Mar 2011 12:39:16 +0530</lastBuildDate>
    <generator>TaxTMI RSS Generator</generator>
    <atom:link href="https://www.taxtmi.com/rss_feed_blog?id=106165" rel="self" type="application/rss+xml"/>
    <item>
      <title>1980 (6) TMI 71 - ITAT JAIPUR</title>
      <link>https://www.taxtmi.com/caselaws?id=67730</link>
      <description>A firm was treated as a real and existing family concern, so a mistaken description of one partner as a minor did not by itself defeat registration where the error was bona fide and later cured by a deed showing all partners as majors. The delay in filing the registration application was also treated as directory rather than fatal, because the application was filed before assessment was completed. On these facts, technical defects in the deed and timing of the application were not sufficient to deny registration.</description>
      <category>Case-Laws</category>
      <law>Income Tax</law>
      <pubDate>Mon, 23 Jun 1980 00:00:00 +0530</pubDate>
      <guid isPermaLink="true">https://www.taxtmi.com/caselaws?id=67730</guid>
    </item>
  </channel>
</rss>