<?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>Updation of Split Indicator Flag in SCMTR application</title>
    <link>https://www.taxtmi.com/circulars?id=69203</link>
    <description>The SCMTR application now requires a Split Indicator to be declared: Y where an MBL/BL is split across multiple filings (all split records must use Y and collectively match the original BL), N where the BL is a single complete filing, and F for the last split record only, which is mandatory to enable system validation and closure. Incorrect or inconsistent use may produce validation errors, delays, or rejections, and stakeholders must ensure accurate, consistent declaration at filing.</description>
    <language>en-us</language>
    <pubDate>Tue, 17 Feb 2026 00:00:00 +0530</pubDate>
    <lastBuildDate>Tue, 24 Feb 2026 12:49:00 +0530</lastBuildDate>
    <generator>TaxTMI RSS Generator</generator>
    <atom:link href="https://www.taxtmi.com/rss_feed_blog?id=887756" rel="self" type="application/rss+xml"/>
    <item>
      <title>Updation of Split Indicator Flag in SCMTR application</title>
      <link>https://www.taxtmi.com/circulars?id=69203</link>
      <description>The SCMTR application now requires a Split Indicator to be declared: Y where an MBL/BL is split across multiple filings (all split records must use Y and collectively match the original BL), N where the BL is a single complete filing, and F for the last split record only, which is mandatory to enable system validation and closure. Incorrect or inconsistent use may produce validation errors, delays, or rejections, and stakeholders must ensure accurate, consistent declaration at filing.</description>
      <category>Circulars</category>
      <law>Customs</law>
      <pubDate>Tue, 17 Feb 2026 00:00:00 +0530</pubDate>
      <guid isPermaLink="true">https://www.taxtmi.com/circulars?id=69203</guid>
    </item>
  </channel>
</rss>