<?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 (6) TMI 522 - CESTAT MUMBAI</title>
    <link>https://www.taxtmi.com/caselaws?id=361695</link>
    <description>A rectification application in a refund dispute arising from service tax paid under a wrong assessee code was treated as outside the litigation policy exclusion for recurring issues and refund or classification disputes. The Tribunal noted that the instruction dated 17.08.2011 did not cover such a case, and that the later amendment dated 04.04.2018 expanded the policy to include matters below the specified monetary threshold. On that basis, the ROM application was found not maintainable and was dismissed.</description>
    <language>en-us</language>
    <pubDate>Mon, 23 Apr 2018 00:00:00 +0530</pubDate>
    <lastBuildDate>Wed, 13 Jun 2018 08:53:27 +0530</lastBuildDate>
    <generator>TaxTMI RSS Generator</generator>
    <atom:link href="https://www.taxtmi.com/rss_feed_blog?id=523291" rel="self" type="application/rss+xml"/>
    <item>
      <title>2018 (6) TMI 522 - CESTAT MUMBAI</title>
      <link>https://www.taxtmi.com/caselaws?id=361695</link>
      <description>A rectification application in a refund dispute arising from service tax paid under a wrong assessee code was treated as outside the litigation policy exclusion for recurring issues and refund or classification disputes. The Tribunal noted that the instruction dated 17.08.2011 did not cover such a case, and that the later amendment dated 04.04.2018 expanded the policy to include matters below the specified monetary threshold. On that basis, the ROM application was found not maintainable and was dismissed.</description>
      <category>Case-Laws</category>
      <law>Service Tax</law>
      <pubDate>Mon, 23 Apr 2018 00:00:00 +0530</pubDate>
      <guid isPermaLink="true">https://www.taxtmi.com/caselaws?id=361695</guid>
    </item>
  </channel>
</rss>