<?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>Clarification on execution of Bond Undertaking by the SEZ Developer or SEZ Unit in terms of rule 22(1 )(iv) of the SEZ Rules, 2006.</title>
    <link>https://www.taxtmi.com/circulars?id=8409</link>
    <description>SEZ developers and units must monitor their Bond-cum-Legal Undertaking quarterly or annually using their progress or performance reports and furnish additional bond amounts for any shortfall. Units must cover duty liability for three months, developers must cover projected requirements, and either may elect to furnish a longer-term Bond-cum-Legal Undertaking (e.g., one or five years) to reduce monitoring frequency.</description>
    <language>en-us</language>
    <pubDate>Tue, 30 Nov 2010 00:00:00 +0530</pubDate>
    <lastBuildDate>Fri, 20 Feb 2015 12:39:00 +0530</lastBuildDate>
    <generator>TaxTMI RSS Generator</generator>
    <atom:link href="https://www.taxtmi.com/rss_feed_blog?id=262657" rel="self" type="application/rss+xml"/>
    <item>
      <title>Clarification on execution of Bond Undertaking by the SEZ Developer or SEZ Unit in terms of rule 22(1 )(iv) of the SEZ Rules, 2006.</title>
      <link>https://www.taxtmi.com/circulars?id=8409</link>
      <description>SEZ developers and units must monitor their Bond-cum-Legal Undertaking quarterly or annually using their progress or performance reports and furnish additional bond amounts for any shortfall. Units must cover duty liability for three months, developers must cover projected requirements, and either may elect to furnish a longer-term Bond-cum-Legal Undertaking (e.g., one or five years) to reduce monitoring frequency.</description>
      <category>Circulars</category>
      <law>SEZ</law>
      <pubDate>Tue, 30 Nov 2010 00:00:00 +0530</pubDate>
      <guid isPermaLink="true">https://www.taxtmi.com/circulars?id=8409</guid>
    </item>
  </channel>
</rss>