<?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>2002 (10) TMI 680 - HIGH COURT OF DELHI</title>
    <link>https://www.taxtmi.com/caselaws?id=108548</link>
    <description>The court dismissed the petition, stating that accidental clearance without overdraft facilities did not constitute a valid loan transaction. Emphasizing the necessity of consideration in transactions, the court highlighted that winding-up proceedings required an admitted debt for the petition to be entertained. The judgment distinguished between accidental clearances and enforceable loan transactions, providing insights into legal principles governing banking transactions and winding-up proceedings.</description>
    <language>en-us</language>
    <pubDate>Wed, 09 Oct 2002 00:00:00 +0530</pubDate>
    <lastBuildDate>Mon, 02 Apr 2012 14:13:55 +0530</lastBuildDate>
    <generator>TaxTMI RSS Generator</generator>
    <atom:link href="https://www.taxtmi.com/rss_feed_blog?id=145565" rel="self" type="application/rss+xml"/>
    <item>
      <title>2002 (10) TMI 680 - HIGH COURT OF DELHI</title>
      <link>https://www.taxtmi.com/caselaws?id=108548</link>
      <description>The court dismissed the petition, stating that accidental clearance without overdraft facilities did not constitute a valid loan transaction. Emphasizing the necessity of consideration in transactions, the court highlighted that winding-up proceedings required an admitted debt for the petition to be entertained. The judgment distinguished between accidental clearances and enforceable loan transactions, providing insights into legal principles governing banking transactions and winding-up proceedings.</description>
      <category>Case-Laws</category>
      <law>Companies Law</law>
      <pubDate>Wed, 09 Oct 2002 00:00:00 +0530</pubDate>
      <guid isPermaLink="true">https://www.taxtmi.com/caselaws?id=108548</guid>
    </item>
  </channel>
</rss>