<?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 (7) TMI 2015 - CESTAT AHMEDABAD</title>
    <link>https://www.taxtmi.com/caselaws?id=282192</link>
    <description>Refund under Notification No. 41/2012-ST cannot be denied merely because the claimant filed the refund in two parts instead of one where the input services were used for export of goods. The export nexus and use of the services were undisputed, so the procedural objection did not defeat the substantive entitlement to refund. The denial was therefore unsustainable because a minor filing irregularity should not override the notification&#039;s purpose of relieving export-related service tax burden.</description>
    <language>en-us</language>
    <pubDate>Mon, 09 Jul 2018 00:00:00 +0530</pubDate>
    <lastBuildDate>Tue, 27 Aug 2019 17:47:00 +0530</lastBuildDate>
    <generator>TaxTMI RSS Generator</generator>
    <atom:link href="https://www.taxtmi.com/rss_feed_blog?id=581258" rel="self" type="application/rss+xml"/>
    <item>
      <title>2018 (7) TMI 2015 - CESTAT AHMEDABAD</title>
      <link>https://www.taxtmi.com/caselaws?id=282192</link>
      <description>Refund under Notification No. 41/2012-ST cannot be denied merely because the claimant filed the refund in two parts instead of one where the input services were used for export of goods. The export nexus and use of the services were undisputed, so the procedural objection did not defeat the substantive entitlement to refund. The denial was therefore unsustainable because a minor filing irregularity should not override the notification&#039;s purpose of relieving export-related service tax burden.</description>
      <category>Case-Laws</category>
      <law>Service Tax</law>
      <pubDate>Mon, 09 Jul 2018 00:00:00 +0530</pubDate>
      <guid isPermaLink="true">https://www.taxtmi.com/caselaws?id=282192</guid>
    </item>
  </channel>
</rss>