<?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>2023 (9) TMI 1777 - DELHI HIGH COURT</title>
    <link>https://www.taxtmi.com/caselaws?id=470811</link>
    <description>SEIS benefits under the Foreign Trade Policy 2015-20 cannot be denied merely because a service exporter lacked an active Importer Exporter Code when services were rendered or exported. Paragraph 2.05 requires service providers to hold an Importer Exporter Code when claiming Chapter 3 benefits, rather than at the time of export. Where the same issue has already been conclusively resolved in the claimant&#039;s earlier proceedings and no new basis for denial exists, the SEIS claim remains admissible.</description>
    <language>en-us</language>
    <pubDate>Tue, 12 Sep 2023 00:00:00 +0530</pubDate>
    <lastBuildDate>Tue, 11 Aug 2026 10:01:00 +0530</lastBuildDate>
    <generator>TaxTMI RSS Generator</generator>
    <atom:link href="https://www.taxtmi.com/rss_feed_blog?id=916327" rel="self" type="application/rss+xml"/>
    <item>
      <title>2023 (9) TMI 1777 - DELHI HIGH COURT</title>
      <link>https://www.taxtmi.com/caselaws?id=470811</link>
      <description>SEIS benefits under the Foreign Trade Policy 2015-20 cannot be denied merely because a service exporter lacked an active Importer Exporter Code when services were rendered or exported. Paragraph 2.05 requires service providers to hold an Importer Exporter Code when claiming Chapter 3 benefits, rather than at the time of export. Where the same issue has already been conclusively resolved in the claimant&#039;s earlier proceedings and no new basis for denial exists, the SEIS claim remains admissible.</description>
      <category>Case-Laws</category>
      <law>Customs</law>
      <pubDate>Tue, 12 Sep 2023 00:00:00 +0530</pubDate>
      <guid isPermaLink="true">https://www.taxtmi.com/caselaws?id=470811</guid>
    </item>
  </channel>
</rss>