<?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>Procedure for Movement of Import Cargo in Containers from the Port to a CFS</title>
    <link>https://www.taxtmi.com/circulars?id=58960</link>
    <description>Electronic EDI messaging governs port-to-CFS container movement through three messages: Cargo Movement Approval (message 19) from Customs to shipping agents, port/terminal operators and destination CFSs; Gate Pass (message 20) from the source custodian to Customs upon port exit; and CFS Arrival (message 21) from destination custodian upon receipt. Automatic movement approval is granted at entry inward if IGM contains mandatory fields (destination CFS code, cargo type &#039;C&#039; or &#039;CP&#039;, cargo movement &#039;LC&#039;, and MLO code); otherwise a manual application per Annexure C is required. Terminals must generate and Customs endorse EIRs at exit. A mail-based procedure remains until messaging stabilizes.</description>
    <language>en-us</language>
    <pubDate>Tue, 26 Feb 2008 00:00:00 +0530</pubDate>
    <lastBuildDate>Sat, 05 Jan 2019 15:05:00 +0530</lastBuildDate>
    <generator>TaxTMI RSS Generator</generator>
    <atom:link href="https://www.taxtmi.com/rss_feed_blog?id=551236" rel="self" type="application/rss+xml"/>
    <item>
      <title>Procedure for Movement of Import Cargo in Containers from the Port to a CFS</title>
      <link>https://www.taxtmi.com/circulars?id=58960</link>
      <description>Electronic EDI messaging governs port-to-CFS container movement through three messages: Cargo Movement Approval (message 19) from Customs to shipping agents, port/terminal operators and destination CFSs; Gate Pass (message 20) from the source custodian to Customs upon port exit; and CFS Arrival (message 21) from destination custodian upon receipt. Automatic movement approval is granted at entry inward if IGM contains mandatory fields (destination CFS code, cargo type &#039;C&#039; or &#039;CP&#039;, cargo movement &#039;LC&#039;, and MLO code); otherwise a manual application per Annexure C is required. Terminals must generate and Customs endorse EIRs at exit. A mail-based procedure remains until messaging stabilizes.</description>
      <category>Circulars</category>
      <law>Customs</law>
      <pubDate>Tue, 26 Feb 2008 00:00:00 +0530</pubDate>
      <guid isPermaLink="true">https://www.taxtmi.com/circulars?id=58960</guid>
    </item>
  </channel>
</rss>