<?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>Establishment of connectivity with both NSDL and CDSL- Shifting from Trade for Trade Segment (TFTS) to Rolling Segment</title>
    <link>https://www.taxtmi.com/circulars?id=59490</link>
    <description>Where companies listed in Annexure A have established connectivity with both depositories on or before the cutoff, stock exchanges shall shift those scrips from the Trade-for-Trade segment to the Rolling Segment from the eligible date specified for each scrip, provided there are no other grounds to retain them in TFTS; exchanges must report the action taken in the Monthly Development Report (Section II, item no. 13) for October.</description>
    <language>en-us</language>
    <pubDate>Mon, 19 Sep 2005 00:00:00 +0530</pubDate>
    <lastBuildDate>Thu, 07 Feb 2019 16:55:00 +0530</lastBuildDate>
    <generator>TaxTMI RSS Generator</generator>
    <atom:link href="https://www.taxtmi.com/rss_feed_blog?id=556890" rel="self" type="application/rss+xml"/>
    <item>
      <title>Establishment of connectivity with both NSDL and CDSL- Shifting from Trade for Trade Segment (TFTS) to Rolling Segment</title>
      <link>https://www.taxtmi.com/circulars?id=59490</link>
      <description>Where companies listed in Annexure A have established connectivity with both depositories on or before the cutoff, stock exchanges shall shift those scrips from the Trade-for-Trade segment to the Rolling Segment from the eligible date specified for each scrip, provided there are no other grounds to retain them in TFTS; exchanges must report the action taken in the Monthly Development Report (Section II, item no. 13) for October.</description>
      <category>Circulars</category>
      <law>SEBI</law>
      <pubDate>Mon, 19 Sep 2005 00:00:00 +0530</pubDate>
      <guid isPermaLink="true">https://www.taxtmi.com/circulars?id=59490</guid>
    </item>
  </channel>
</rss>