New ISF Messages for BOL Type Errors, Changes to BAPLIE Responses
U.S. Customs and Border Protection has issued CSMS messages describing changes to Importer Security Filing Status Advisory (SA) messages and stow plan responses that will become effective no sooner than July 10, 2010.
Sign up for a free preview to unlock the rest of this article
Export Compliance Daily combines U.S. export control news, foreign border import regulation and policy developments into a single daily information service that reliably informs its trade professional readers about important current issues affecting their operations.
ISF Status Advisory Message Changes
The following ISF SA message changes will become effective no sooner than July 10, 2010. The changes have been posted in the ‘Pending Transaction Sets’ section of the 'Security Filing Transaction Sets' webpage.
More descriptive “No Bill on File” messages. Currently, CBP compares the Bill of Lading number submitted with an ISF against that filed in the Automated Manifest System (AMS), and issues a “No Bill on File” status advisory message when the bill number is not in AMS or there is a discrepancy with the bill type. With the planned change, a distinction will be made between a bill number not being on file in AMS and a bill number being on file in AMS, but with a different type than what was filed in the ISF.
- When a Bill has not been filed in AMS, the ISF Filer will receive a status message with an S2 disposition code and a “No Bill Match (Not on File)” description.
- When a Bill has been filed in AMS, but with a different type than what was filed in the ISF, the ISF Filer will receive a status message with an S6 disposition code and a “No Bill Match (Wrong Type)” description.
- When a Bill has not been filed in AMS, the ISF Filer will receive reminder status messages with S3, S4, and S5 disposition codes and a “No Bill Match (Not on File)” description after 5, 20, and 30 days, respectively.
- When a Bill has been filed in AMS but with a different type than what was filed in the ISF, the ISF Filer will receive reminder status messages with SA, SB, and SC disposition codes and a “No Bill Match (Wrong Type)” description after 5, 20, and 30 days, respectively.
Duplicate ISF filings. If an ISF is received by CBP with the same Bill Number and ISF Importer Number as one submitted in a previous ISF by a different filer, CBP accepts the duplicate ISF with a warning to let the filer know that a different party previously filed an ISF against the same shipment.
With the planned change, in addition to the above behavior, a status message with an S7 disposition code and a “Duplicate ISF by Another Filer” description will be sent to the initial ISF filer indicating that a duplicate ISF was filed.
Stow Plan Response Changes
The following changes to the way that CBP will respond to BAPLIE input stow plans will become effective no sooner than July 10, 2010:
CUSRES changes. An AAZ qualifier will be added to the RFF segment to identify the container operator. Also, a BGM02 segment will be added to echo back the reference number from the BGM02 of the input BAPLIE.
Unmanifested Container Message changes (CAMIR RC or X-12 350). The container port of lading code from the input BAPLIE will be echoed back in the C02 record or VID segment. No translation of the input code will be performed.
CSMS #10-000120 (dated 05/11/10) available at http://apps.cbp.gov/csms/viewmssg.asp?Recid=17902&page=&srch_argv=10-000120&srchtype=Seq_Msg_Num&btype=&sortby=&sby
CSMS #10-000121 (dated 05/11/10) available at http://apps.cbp.gov/csms/viewmssg.asp?Recid=17903&page=&srch_argv=10-000121&srchtype=all&btype=&sortby=&sby
ISF Pending Transaction Sets available at http://www.cbp.gov/xp/cgov/trade/automated/automated_systems/sf_transaction_sets/