CBP to Deploy CUSRES Pending ISF Transaction Set, New Bond Edits, Etc.
U.S. Customs and Border Protection has issued a CSMS message stating that it will deploy the CUSRES (Customs Response Message) pending Importer Security Filing transaction set on February 24, 2010. Testing in the Certification environment for this change will begin on February 14, 20101.
Sign up for a free preview to unlock the rest of this article
If your job depends on informed compliance, you need International Trade Today. Delivered every business day and available any time online, only International Trade Today helps you stay current on the increasingly complex international trade regulatory environment.
CBP is also announcing additional ISF changes (bond-related edits, etc.), which will be effective February 14, 2010.
These changes are intended to tighten the edits for Security Filing information that is submitted by importers and carriers (10+2 information) for vessel (maritime) cargo, and result in CBP receiving higher quality data.
CUSRES Pending ISF Transaction Set
The CUSRES pending ISF transaction set includes a programming change with a new CUSRES response to support BAPLIE (Bayplan/stowage plan occupied and empty locations message) stow plan submissions.
10-day test period for trade begins Feb 14. Based on feedback from trade participants, CBP will allow the trade ten days to test their programming in the AMS Certification system. The CUSRES will be sent as a response to the BAPLIE in the Certification environment beginning February 14, 2010. Additionally, CBP will send back Unmanifested Container messages (CAMIR RC or X-12 350) in Certification. Due to the lack of matching bills related to BAPLIEs in Certification, every Unmanifested Container message sent in Certification will read as 'all Loads Manifested.'
On February 14, 2010, the Unmanifested Container messages will include the proper translation of the next port of call submitted in the input BAPLIE to the schedule D code. They will also include the proper mode of transportation.
CUSRES to be in production on Feb 24. On February 24, 2010, the CUSRES will be sent as a BAPLIE response in the Production environment.
New Bond-Related Edits for ISFs
New ISF bond-related edits, which enforce business rules, will be added to the ISF programming and will be warnings for no less than two weeks. After that time, these warnings will be changed to rejections without further notice. (BP is checking to see if these new ISF bond-related edits will be implemented on February 14, 2010.)
The bond-related data edits for which warnings have been sent regularly prior to February 14, 2010 will be changed to rejections on that date.
(See ITT's Online Archives or 02/03/10 news, 10020305, for Part II of BP's summary of the updated 10+2 FAQs, which states that CBP would soon update its systems to have specific bond edits in place, etc.)
ISF Transactions Filed by Different Filers Will Now be Accepted
ISF transactions filed by different filers, which have been rejected in the past for Duplicate ISF Transaction, will now be accepted by CBP. In the case where a second identical ISF transaction is submitted by the same filer as the original ISF, that filer will still receive a reject for Duplicate ISF Transaction along with the ISF transaction number associated with the original filing.
If, after February 14, 2010, a filer receives a Duplicate ISF Transaction without an ISF transaction number, the filer should contact their assigned Client Representative for assistance.
CBP Will Accept New ISF Transaction Type 10 for OCS Shipments
Beginning February 14, 2010, ISF transactions will allow the Shipment Type code '10' to represent Outer Continental Shelf (OCS) Shipments. CBP notes that documentation will reflect these changes in the next few days.
1CBP previously planned to implement the CUSRES response in mid-December with other ISF transaction set changes, but was delayed based on a number of concerns, including proximity to the holiday season and significant feedback from the trade indicating that the complexity of this new data format required additional time in order to complete system modification. CBP agreed to delay the implementation for approximately 30 days from January 13, 2010.
(See ITT's Online Archives or 02/04/10 news, 10020410, for Part III of BP's summary of the updated 10+2 FAQs, which covers the new transaction type, etc.)
(See ITT's Online Archives or 01/15/10 news, 10011515, for BP summary announcing that CBP was delaying implementation of the CUSRES pending ISF transaction set.)
CSMS 10-000038 (dated 02/07/10) available at http://apps.cbp.gov/csms/viewmssg.asp?Recid=17819&page=&srch_argv=&srchtype=&btype=&sortby=&sby
CUSRES pending ISF transaction set (posted 10/15/09) available at http://www.cbp.gov/linkhandler/cgov/trade/automated/automated_systems/sf_transaction_sets/pending_sets/cusres_pending.ctt/cusres_pending.doc