<?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>2015 (7) TMI 57 - DELHI HIGH COURT</title>
    <link>https://www.taxtmi.com/caselaws?id=261096</link>
    <description>The court addressed discrepancies in the share exchange ratio and lack of clarity in a joint application under Sections 391 to 394 of the Companies Act, 1956 for a Scheme of Amalgamation. The matter was reserved for further examination, with the court directing clarification on the ratio and valuation basis discrepancies within two weeks. The absence of a supporting Board Resolution from the holding company for the scheme&#039;s consents was noted, requiring resolution before the next review date.</description>
    <language>en-us</language>
    <pubDate>Fri, 13 Feb 2015 00:00:00 +0530</pubDate>
    <lastBuildDate>Thu, 23 Jul 2015 10:47:00 +0530</lastBuildDate>
    <generator>TaxTMI RSS Generator</generator>
    <atom:link href="https://www.taxtmi.com/rss_feed_blog?id=389009" rel="self" type="application/rss+xml"/>
    <item>
      <title>2015 (7) TMI 57 - DELHI HIGH COURT</title>
      <link>https://www.taxtmi.com/caselaws?id=261096</link>
      <description>The court addressed discrepancies in the share exchange ratio and lack of clarity in a joint application under Sections 391 to 394 of the Companies Act, 1956 for a Scheme of Amalgamation. The matter was reserved for further examination, with the court directing clarification on the ratio and valuation basis discrepancies within two weeks. The absence of a supporting Board Resolution from the holding company for the scheme&#039;s consents was noted, requiring resolution before the next review date.</description>
      <category>Case-Laws</category>
      <law>Companies Law</law>
      <pubDate>Fri, 13 Feb 2015 00:00:00 +0530</pubDate>
      <guid isPermaLink="true">https://www.taxtmi.com/caselaws?id=261096</guid>
    </item>
  </channel>
</rss>