| Title: | Pending Transaction Sets for Importer Security Filing (ISF) |
|---|---|
| Date: | 2009-10-15 |
| To: | abi,ocean |
| Links: | previous, next |
CBP has again modified its website to include the posting of future/pending transaction sets for ABI and AMS Importer Security
Filings (ISF). A link to the pending transaction sets has been added to the ISF Transaction Sets page at:
http://www.cbp.gov/xp/cgov/trade/automated/automated_systems/sf_transaction_sets/pending_sets/
This page includes updated stand-alone ISF CATAIR, CAMIR, and X-12 309 documentation along with a separate outline detailing the changes identified in each document. These documents include a number of programming changes that have been identified and explained below in this document, which will become effective November 14, 2009.
A new CUSRES response to support BAPLIE stow plan submissions has also been published. Additionally, a revised list of ISF error codes will be included on this page. Please, note that the error code descriptions have been modified to more clearly define the error. Also, the error codes themselves have changed for both CAMIR and X-12 versions. The CUSRES and error code modifications will be effective in mid-December.
Note: On October 1, 2009, CSMS #09-000322 was issued describing changes to the transaction sets that are explanatory in nature. There were a couple minor programming changes added to that documentation, which will be included in the descriptions below.
The following changes will become effective November 14, 2009. A reminder notice will be issued approximately one week in advance.
>>SF10 Record Changes in CATAIR and CAMIR:
1. Shipment Type Code 01 is now mandatory for ISF Submission Type 2 (ISF-5).
2. Shipment Type Codes 08 (FTZ Shipments) and 09 (International Mail Shipments) have been added to expand the possible code values to nine possibilities.
3. A new Action Reason Code FX has been used to identify a combination of FR (flexible range) and FT (flexible timing) options. Please read the revised definitions based on this additional code.
4. An ISF filer will now be permitted to transmit a Standard Carrier Alpha Code (SCAC) for the ISF Importer, but this will ONLY occur for an ISF-5 submission. The ISF Importer Number Qualifier and ISF Importer Number fields will be modified to allow this.
5. The format for the ISF Transaction Number is being modified slightly.
a) The ABI format will now be FFF-NNNNNNNNNNN
b) The AMS format will now be FFFFNNNNNNNNNNN
6. An ISF Transaction Number is normally returned in the SF10 record. In the case of a transaction that is rejected for Duplicate ISF on File, the ISF Transaction Number is currently being returned in the second SF90 record line following the SF90 that includes the duplicate error. The second SF90 line is going to be eliminated and the transaction number will be returned in the SF10 record as it would in other transactions.
7. The Bond Activity Code for the ISF Bond is being changed to 16. There are a number of explanation changes relating to how to properly submit the bond information.
NOTE: Bond information will not be required until January 26, 2010. Submitting an ISF with the bond data missing will NOT result in a rejected transaction. HOWEVER, as of the November 14, 2009 implementation date, any bond data that IS transmitted in the wrong format or not following the technical requirements set forth in this document WILL BE REJECTED! For example, submitting 1234 (an invalid format) as the Bond Holder will cause the transaction to reject. Submitting a Bond Activity Code 03 with a Bond Type 9 will cause the transaction to reject. Submitting a Bond Activity Code that the Bond Holder does not possess will cause the transaction to reject. If the transaction includes any bond data, ALL of the bond information MUST be present and correct for the transaction to accept.
>>SF20 Record Changes in CATAIR and CAMIR:
1. A new Reference Identifier Qualifier 6C has been added for ISF reporting of a carnet. The format will be a two character country code (representing the issuing country) followed by the carnet number. (ie, UScarnet#) This is required if the Shipment Type code is 06.
2. A new Reference Identifier Qualifier SBN has been added to report the Bond Reference Number. This is not a bond number; it is a reference number that the surety will put on a single transaction bond. This must be present if the Bond Activity code is 16 and the Bond Type is 9.
>>M10 Segment Changes in X-12 309:
1. M1014 - Shipment Type Code 01 is now mandatory for ISF Submission Type 2 (ISF-5).
2. M1014 - Shipment Type Codes 08 (FTZ Shipments) and 09 (International Mail Shipments) have been added to expand the possible code values to nine possibilities.
3. M1016 - A new Action Reason Code FX has been used to identify a combination of FR (flexible range) and FT (flexible timing) options. Please read the revised definitions based on this additional code.
>>N9 Segment Changes in X-12 309:
1. A new Reference Identifier Qualifier 6C has been added for ISF reporting of a carnet. The format will be a two character country code (representing the issuing country) followed by the carnet number. (ie, UScarnet#) This is required if the Shipment Type code is 06.
2. A new Reference Identifier Qualifier SBN has been added to report the Bond Reference Number. This is not a bond number; it is a reference number that the surety will put on a single transaction bond. This must be present if the Bond Activity code is 16 and the Bond Type is 9.
3. The format for the ISF Transaction Number is being modified slightly to FFFFNNNNNNNNNNN.
4. An ISF Transaction Number is normally returned in the N9 segment with a 7U qualifier. In the case of a transaction that is rejected for Duplicate ISF on File, the ISF Transaction Number is currently being returned in the second K1 segment following the K1 segment that includes the duplicate error. The second K1 segment is going to be eliminated and the transaction number will be returned in the N9 segment as it would in other transactions.
>>NM1 Segment Changes in X-12 309:
1. An ISF filer will now be permitted to transmit a Standard Carrier Alpha Code (SCAC) for the ISF Importer, but this will ONLY occur for an ISF-5 submission. This will not be permitted for the Importer of Record. The ISF Importer Number Qualifier and ISF Importer Number fields will be modified to allow this.
>>REF Segment Changes in X-12 309:
The Bond Activity Code for the ISF Bond is being changed to 16. There are a number of explanation changes relating to how to properly submit the bond information.
NOTE: Bond information will not be required until January 26, 2010. Submitting an ISF with the bond data missing will NOT result in a rejected transaction. HOWEVER, as of the November 14, 2009 implementation date, any bond data that IS transmitted in the wrong format or not following the technical requirements set forth in this document WILL BE REJECTED! For example, submitting 1234 (invalid format) as the Bond Holder will cause the transaction to reject. Submitting a Bond Activity Code 03 with a Bond Type 9 will cause the transaction to reject. Submitting a Bond Activity Code that the Bond Holder does not possess will cause the transaction to reject. If the transaction includes any bond data, ALL of the bond information MUST be present and correct for the transaction to accept.
>>Other notable changes:
A subsequent CSMS message will be issued including changes effective mid-December. Those changes include the SF90 record in CATAIR and CAMIR, a list of ISF error codes, and the new CUSRES document.
If you have any questions, please contact your assigned Client Representative or call 703-650-3500.
CSMS #10-000013, 09-000350, 09-000349, 09-000334, 09-000327, 09-000326