<?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>Formation of IGST Refund helpdesk</title>
    <link>https://www.taxtmi.com/circulars?id=59054</link>
    <description>Two IGST refund helpdesks have been established to assist exporters with pending IGST refund claims caused by systems and PFMS integration errors. EDI modules developed by the Directorate of Systems and Data Management provide Shipping Bill/IEC-wise status reports, enabling generation of successful scrolls and publication of Shipping Bill status on the Commissionerate website; designated officers and contact details for the Pipavav and Jamnagar helpdesks are provided for resolving processing errors.</description>
    <language>en-us</language>
    <pubDate>Fri, 12 Jan 2018 00:00:00 +0530</pubDate>
    <lastBuildDate>Thu, 10 Jan 2019 17:34:00 +0530</lastBuildDate>
    <generator>TaxTMI RSS Generator</generator>
    <atom:link href="https://www.taxtmi.com/rss_feed_blog?id=552088" rel="self" type="application/rss+xml"/>
    <item>
      <title>Formation of IGST Refund helpdesk</title>
      <link>https://www.taxtmi.com/circulars?id=59054</link>
      <description>Two IGST refund helpdesks have been established to assist exporters with pending IGST refund claims caused by systems and PFMS integration errors. EDI modules developed by the Directorate of Systems and Data Management provide Shipping Bill/IEC-wise status reports, enabling generation of successful scrolls and publication of Shipping Bill status on the Commissionerate website; designated officers and contact details for the Pipavav and Jamnagar helpdesks are provided for resolving processing errors.</description>
      <category>Circulars</category>
      <law>Customs</law>
      <pubDate>Fri, 12 Jan 2018 00:00:00 +0530</pubDate>
      <guid isPermaLink="true">https://www.taxtmi.com/circulars?id=59054</guid>
    </item>
  </channel>
</rss>