Title: | Pending Transaction Sets for unified Importer Security Filing (ISF) filings |
---|---|
Date: | 2009-11-12 |
To: | abi |
Links: | previous, next |
On October 15, 2009, CSMS #09-000325 was issued to notify the trade community about changes to ISF transaction sets that were posted the Pending Transaction Sets page:
http://www.cbp.gov/xp/cgov/trade/automated/automated_systems/sf_transaction_sets/pending_sets/
There are also a number of changes that apply to the unified Entry Summary/SF document, the Cargo Release/SF document, and the FTZ/SF document. These unified documents have also been modified to more accurately reflect the possible scenarios that would occur with a unified submission to CBP.
While a number of these changes may require programming modifications, they will NOT cause rejects until mid-December. Also, many of the codes that have been removed should not have been used in the past due to the inability to file certain combinations for unified submissions. For example, Shipment Type Code 06 (carnet) is not possible for an Entry Summary and could not have been filed properly if it were used in a unified Entry Summary/SF submission.
>>>The following changes were made to the Entry Summary/SF and Cargo Release/SF documents:
I. SF10
1. Shipment Type Code
A. Removed codes '03', '05', and '06'
B. Added code '09'
2. Action Reason Code
A. Must always = 'CT' for Add/Replace Transactions
B. New definition description for code
3. ISF Importer Number Qualifier and ISF Importer Number are now mandatory
4. Positions 29-36 are now reserved and must be space-filled
5. ISF Transaction Number
A. New format NNNN replaces CCYY
B. The ISF transaction number will be returned in this field for Duplicate rejects rather than the second SF90 record
6. Bond fields
A. Code '16' replaces '99' for ISF Bond
B. New explanations regarding how to submit bond information
7. Positions 79-80 are now reserved and must be space-filled
II. SF20
1. New Reference Identifier Qualifiers added
2. New explanation of code requirements
III. SF30, SF35, SF36 – Improved explanations and/or descriptions
IV. SF90 (effective mid-December)
1. New Message Type Codes
2. Message Type Code is now a mandatory field
3. Error Code is now a conditional field
>>>The following changes were made to the FTZ/SF document:
I. SF10
1. Shipment Type Code must always = '08'
2. Action Reason Code
A. Must always = 'CT' for Add/Replace Transactions
B. New definition description for code
3. ISF Importer Number Qualifier and ISF Importer Number are now mandatory
4. Positions 29-36 are now reserved and must be space-filled
5. ISF Transaction Number
A. New format NNNN replaces CCYY
B. The ISF transaction number will be returned in this field for Duplicate rejects rather than the second SF90 record
6. Bond fields
A. Code '16' replaces '99' for ISF Bond
B. New explanations regarding how to submit bond information
7. Positions 79-80 are now reserved and must be space-filled
II. SF20
1. New Reference Identifier Qualifiers added
2. New explanation of code requirements
III. SF25 record added to allow submission of container/equipment information
IV. SF30
1. Entity Code FTZ removed
2. Improved explanations and/or descriptions
V. SF35, SF36 – Improved explanations and/or descriptions
VI. SF90 (effective mid-December)
1. New Message Type Codes
2. Message Type Code is now a mandatory field
3. Error Code is now a conditional field
If you have any questions, please contact your assigned Client Representative or call 703-650-3500.