<?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=25704</link>
    <description>Carriers must transmit separate passenger and crew API flat files using a prescribed filename convention and a fixed sequence of pipe-delimited fields covering flight identifiers, travel document particulars, personal and contact information, crew license details, and visa data; null values are required where data are unavailable, each passenger record is single-line, passport may be optional for certain nationalities, and submission may alternatively follow the UN/EDIFACT PAXLST API implementation guide.</description>
    <language>en-us</language>
    <pubDate>Wed, 14 Jun 2017 16:19:31 +0530</pubDate>
    <lastBuildDate>Wed, 14 Jun 2017 16:28:33 +0530</lastBuildDate>
    <generator>TaxTMI RSS Generator</generator>
    <atom:link href="https://www.taxtmi.com/rss_feed_blog?id=472198" rel="self" type="application/rss+xml"/>
    <item>
      <title>ANNEXURE</title>
      <link>https://www.taxtmi.com/acts?id=25704</link>
      <description>Carriers must transmit separate passenger and crew API flat files using a prescribed filename convention and a fixed sequence of pipe-delimited fields covering flight identifiers, travel document particulars, personal and contact information, crew license details, and visa data; null values are required where data are unavailable, each passenger record is single-line, passport may be optional for certain nationalities, and submission may alternatively follow the UN/EDIFACT PAXLST API implementation guide.</description>
      <category>Act-Rules</category>
      <law>Customs</law>
      <pubDate>Wed, 14 Jun 2017 16:19:31 +0530</pubDate>
      <guid isPermaLink="true">https://www.taxtmi.com/acts?id=25704</guid>
    </item>
  </channel>
</rss>