<?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>ANNEXURE</title>
    <link>https://www.taxtmi.com/acts?id=22086</link>
    <description>The regulation mandates separate electronic files for passenger and crew manifests with a specified flat-file naming convention and a pipe-delimited record structure of 53 data elements. It prescribes fixed field lengths and types for flight identifiers, timings, ports, counts, PNR, passenger/crew biographics, travel-document and visa details, crew-license fields, and carrier contact information, identifies certain non-mandatory fields, and endorses furnishing data via UN/EDIFACT PAXLST API messaging.</description>
    <language>en-us</language>
    <pubDate>Sat, 20 Aug 2016 10:25:01 +0530</pubDate>
    <lastBuildDate>Sat, 20 Aug 2016 10:25:28 +0530</lastBuildDate>
    <generator>TaxTMI RSS Generator</generator>
    <atom:link href="https://www.taxtmi.com/rss_feed_blog?id=438761" rel="self" type="application/rss+xml"/>
    <item>
      <title>ANNEXURE</title>
      <link>https://www.taxtmi.com/acts?id=22086</link>
      <description>The regulation mandates separate electronic files for passenger and crew manifests with a specified flat-file naming convention and a pipe-delimited record structure of 53 data elements. It prescribes fixed field lengths and types for flight identifiers, timings, ports, counts, PNR, passenger/crew biographics, travel-document and visa details, crew-license fields, and carrier contact information, identifies certain non-mandatory fields, and endorses furnishing data via UN/EDIFACT PAXLST API messaging.</description>
      <category>Act-Rules</category>
      <law>Customs</law>
      <pubDate>Sat, 20 Aug 2016 10:25:01 +0530</pubDate>
      <guid isPermaLink="true">https://www.taxtmi.com/acts?id=22086</guid>
    </item>
  </channel>
</rss>