<?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 (10) TMI 1333 - GUJARAT HIGH COURT</title>
    <link>https://www.taxtmi.com/caselaws?id=369367</link>
    <description>Compliance with the earlier order required respondents to ensure that any goods released during the litigation were properly accounted for and that the importer was informed that the petition remained pending. The respondent stated that the order had already been communicated and compliance effected, but the Court still directed a formal compliance report to be placed on record. The matter was then adjourned for final disposal and fixed for 26.9.2018, with the compliance report to be filed by that date.</description>
    <language>en-us</language>
    <pubDate>Wed, 05 Sep 2018 00:00:00 +0530</pubDate>
    <lastBuildDate>Fri, 26 Oct 2018 06:22:14 +0530</lastBuildDate>
    <generator>TaxTMI RSS Generator</generator>
    <atom:link href="https://www.taxtmi.com/rss_feed_blog?id=539619" rel="self" type="application/rss+xml"/>
    <item>
      <title>2018 (10) TMI 1333 - GUJARAT HIGH COURT</title>
      <link>https://www.taxtmi.com/caselaws?id=369367</link>
      <description>Compliance with the earlier order required respondents to ensure that any goods released during the litigation were properly accounted for and that the importer was informed that the petition remained pending. The respondent stated that the order had already been communicated and compliance effected, but the Court still directed a formal compliance report to be placed on record. The matter was then adjourned for final disposal and fixed for 26.9.2018, with the compliance report to be filed by that date.</description>
      <category>Case-Laws</category>
      <law>Customs</law>
      <pubDate>Wed, 05 Sep 2018 00:00:00 +0530</pubDate>
      <guid isPermaLink="true">https://www.taxtmi.com/caselaws?id=369367</guid>
    </item>
  </channel>
</rss>