| Title: | Importer Security Filing (ISF) Warnings Incorrectly Sent to Filers |
|---|---|
| Date: | 2010-02-16 |
| To: | abi,ocean |
| Links: | previous, next |
On February 7, 2010, CSMS #10-000038 was issued detailing changes to CBP programming, which included edits validating certain bond information in Importer Security Filing (ISF) transactions.
On February 14, 2010, CBP added these edits to our system. Some warnings were incorrectly sent to filers, but the transactions were accepted by CBP. These warnings occurred on February 14 and February 15 before the edits were temporarily turned off on Monday night. The warnings and their descriptions are listed below:
ABI:
144 CONTINUOUS BOND NOT ON FILE
145 CONTINUOUS BOND NOT ACTIVE
146 BOND HOLDER NOT ACTIVE
147 CONTINUOUS BOND IS INSUFFICIENT
AMS:
SA7 CONT BOND NOT ON FILE
SA8 CONT BOND NOT ACTIVE
SA9 BOND HOLDER NOT ACTIVE
SAA CONT BOND IS INSUFFICIENT
For filers who received any of these warnings, there is no need to retransmit your ISF based solely on these warnings. If other errors were also received simultaneously with these, those may need to be addressed independently. If you only received these errors with an ACCEPTED WITH WARNINGS message, you should NOT retransmit your ISF in order to receive an ACCEPTED message.
Another trade concern with incorrectly receiving such warnings is that ISF Progress Reports will reflect badly on filers, or result in liquidated damages, when the problem was with CBP. This is not the case.
ISF Progress Reports are a general look at how a filer is performing with ISF transactions. They are primarily for the filer's use as an indication of what areas may need improvement. They do NOT provide enough detail to account specifically for every situation in regards to enforcement action. CBP will look at each ISF transaction on an individual basis for enforcement action and NOT the ISF Progress Report. Furthermore, CBP is aware of the instances in which CBP programming is the cause of a problem and will take this information into account when reviewing ISF Progress Reports. Again, the ISF Progress Reports are a broad-scope tool that may help identify problem areas, but will NOT be used for enforcement action that includes liquidated damages.
If you have any questions, please contact your assigned Client Representative or call 571-468-5500 for information.
CSMS #10-000055