<?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>2026 (5) TMI 1851 - Supreme Court</title>
    <link>https://www.taxtmi.com/caselaws?id=471245</link>
    <description>Clubbing and transfer of FIRs arising from the same allegations and forming one transaction require a consistent investigative forum, as parallel investigation is improper. The operative direction was corrected to align with that reasoning: the later FIR registered at Gurugram must be clubbed with and transferred to the earlier FIR registered with the Economic Offences Wing, Delhi. The clarification only rectified the transfer inconsistency and did not permit selection of an investigating agency.</description>
    <language>en-us</language>
    <pubDate>Thu, 21 May 2026 00:00:00 +0530</pubDate>
    <lastBuildDate>Wed, 26 Aug 2026 21:12:05 +0530</lastBuildDate>
    <generator>TaxTMI RSS Generator</generator>
    <atom:link href="https://www.taxtmi.com/rss_feed_blog?id=919242" rel="self" type="application/rss+xml"/>
    <item>
      <title>2026 (5) TMI 1851 - Supreme Court</title>
      <link>https://www.taxtmi.com/caselaws?id=471245</link>
      <description>Clubbing and transfer of FIRs arising from the same allegations and forming one transaction require a consistent investigative forum, as parallel investigation is improper. The operative direction was corrected to align with that reasoning: the later FIR registered at Gurugram must be clubbed with and transferred to the earlier FIR registered with the Economic Offences Wing, Delhi. The clarification only rectified the transfer inconsistency and did not permit selection of an investigating agency.</description>
      <category>Case-Laws</category>
      <law>Indian Laws</law>
      <pubDate>Thu, 21 May 2026 00:00:00 +0530</pubDate>
      <guid isPermaLink="true">https://www.taxtmi.com/caselaws?id=471245</guid>
    </item>
  </channel>
</rss>