The Importer Security Filing, the 10+2, is due 24 hours before cargo is laden aboard the vessel at the foreign port. It is a short data set. It still produces liquidated damages claims, because the standard is not just filed, it is timely, accurate, and complete, and those are three separate ways to fail.
The three failure modes
Late is the obvious one: data transmitted after the deadline, or a bill of lading matched too late for CBP to risk assess the shipment. Inaccurate is quieter: a manufacturer name that is a trading company, a consolidator listed where the actual supplier belongs, an HTS code to six digits that does not match the entry.
Incomplete filings sit between the two. A placeholder entered to beat the clock and never updated is treated as an accuracy problem when CBP compares the ISF against the entry summary and finds the story changed without an amendment.
Which data elements go wrong most
Manufacturer or supplier name and address lead the list, especially where a buying agent sits between the importer and the factory. The party shown must be the manufacturer, not the intermediary, and getting that right requires the purchase documents, not the forwarder's guess.
Ship to party and consolidator cause repeat errors on consolidated cargo, and the container stuffing location is often copied from a template after the actual stuffing site changed. Each element is small. Together they are the risk picture CBP scores before the vessel sails.
Correcting a filing
ISF data can be updated before the vessel arrives, and a correction made early reads very differently from one made after a claim issues. The amendment should reflect the true data and the reason for the change should sit in the file: a corrected booking confirmation, a supplier declaration, the document that proves the new figure.
Where a claim for liquidated damages does arrive, mitigation is possible and the petition turns on the importer's compliance history and the cause of the error. A one off keying error in an otherwise clean record is argued differently from a pattern of late filings across a season.
Building the check into booking
The durable fix is timing inside the company, not pressure on the filer. Purchase order data, supplier identity, and the first six HTS digits need to reach the filer when the booking is made, not when the container is at the terminal. A weekly report of ISF filings matched against bookings catches the shipment nobody filed for, which is the most expensive error of all.
Confirm filing deadlines and data requirements for a specific shipment with a licensed customs broker, because vessel cut offs and carrier practices move the real deadline earlier than the regulatory one.
Keep reading
Related guides on this site: Post Summary Corrections: Fixing an Entry After the Goods Have Cleared When CBP Says Your Bond Is Not Sufficient: What Changed and What To Do Answers for teams shipping Shopify orders across borders.
Frequently asked questions
When is the ISF due?
The Importer Security Filing is generally due no later than 24 hours before the cargo is laden aboard the vessel at the foreign port. Carriers and forwarders often impose earlier internal cut offs to meet it.
What happens if ISF data is wrong?
Inaccurate, late, or incomplete filings can draw liquidated damages claims. Errors caught and amended before arrival, with documentation in the file, are treated more favourably in mitigation than patterns of repeat errors.
Who is responsible for the ISF?
The importer of record is responsible, even when a broker or forwarder transmits the filing. Delegating the transmission does not delegate the liability for bad data.