<?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>2018 (4) TMI 665 - CESTAT MUMBAI</title>
    <link>https://www.taxtmi.com/caselaws?id=358554</link>
    <description>For refund claims under Rule 5 and the notification, the one-year filing period is to be computed from the date of receipt of convertible foreign exchange, evidenced by the FIRC, rather than from the date of invoice for the export service. The Tribunal recorded that this position was already settled and consistently followed in its earlier view, so the Revenue&#039;s objection based on invoice date was not sustainable. On that basis, the refund claim was treated as filed within the relevant limitation period.</description>
    <language>en-us</language>
    <pubDate>Tue, 20 Feb 2018 00:00:00 +0530</pubDate>
    <lastBuildDate>Sat, 14 Apr 2018 07:14:11 +0530</lastBuildDate>
    <generator>TaxTMI RSS Generator</generator>
    <atom:link href="https://www.taxtmi.com/rss_feed_blog?id=516876" rel="self" type="application/rss+xml"/>
    <item>
      <title>2018 (4) TMI 665 - CESTAT MUMBAI</title>
      <link>https://www.taxtmi.com/caselaws?id=358554</link>
      <description>For refund claims under Rule 5 and the notification, the one-year filing period is to be computed from the date of receipt of convertible foreign exchange, evidenced by the FIRC, rather than from the date of invoice for the export service. The Tribunal recorded that this position was already settled and consistently followed in its earlier view, so the Revenue&#039;s objection based on invoice date was not sustainable. On that basis, the refund claim was treated as filed within the relevant limitation period.</description>
      <category>Case-Laws</category>
      <law>Service Tax</law>
      <pubDate>Tue, 20 Feb 2018 00:00:00 +0530</pubDate>
      <guid isPermaLink="true">https://www.taxtmi.com/caselaws?id=358554</guid>
    </item>
  </channel>
</rss>