ISF mistakes that cost $5,000, and how to catch them before lading

Entry-writer job postings sometimes list the Importer Security Filing as the very first duty, ahead of the entry itself. That order makes sense. The ISF is the first thing your desk sends to CBP about an ocean shipment. It usually goes before the paperwork is final, and it can cost money on its own even when the entry that follows is perfect.

This post is for the person who files it: the entry writer, the LCB who reviews the work, or the owner who does both. It covers the deadline, what a mistake can cost, where each data element usually comes from, and the point where the ISF and the later entry tend to stop agreeing.

The deadline is lading, not arrival

For ocean cargo bound for the United States, the ISF is due no later than 24 hours before the cargo is laden aboard the vessel at the foreign port (19 CFR 149.2; CBP). That is the moment everything else is measured from, and it is usually days or weeks before your desk sees a final commercial invoice.

The regulation gives you some room on four points:

• Container stuffing location and consolidator can come later, but no later than 24 hours before arrival at a US port (19 CFR 149.2).
• Manufacturer (or supplier), ship-to party, country of origin and HTS number can be filed as a range of possible values when the exact one isn't known yet. They must then be updated as soon as better information is available, and no later than 24 hours before arrival.
• Any element must be updated if it changes, or if more accurate information becomes available, after filing and before the goods enter the limits of a US port. If the goods are no longer headed to the US, the filer must withdraw the ISF and give the reason (19 CFR 149.2).

That last point matters most. The ISF is not a one-time transmission. It is a statement you are obliged to keep true until the ship reaches port.

What a mistake costs

What the trade calls the ISF penalty is, strictly, a claim under the bond. The ISF bond conditions provide for liquidated damages of $5,000 per violation (19 CFR 113.62(j) and Appendix D to Part 113). The bond doesn't list breaches one by one; it covers any failure to meet the ISF requirements in Part 149. In practice that means late, inaccurate or incomplete filings, and failing to update or withdraw a filing when the regulation requires it.

The $5,000 is where a claim starts, not always where it ends. Under CBP's ISF mitigation guidelines, a first violation for a late or inaccurate ISF, or an inaccurate update, may be cancelled on payment of $1,000 to $2,000, depending on mitigating and aggravating factors. That relief applies only if CBP decides the violation didn't compromise law enforcement goals (CBP ISF mitigation guidelines).

Mitigation is a petition, not a given. It takes someone's time to prepare, and the violation stays in the importer's history. The cheaper path is not making the mistake at all.

Where each ISF element comes from

The ISF importer supplies ten elements; the carrier supplies the other two (the vessel stow plan and container status messages). The table below lists the ten (19 CFR 149.3), the document that usually carries each one at ISF time, and where it tends to disagree with what later goes on the entry. The "usual source" column reflects common practice, not a CBP rule. Your clients' paperwork may differ.

ISF element	Usually comes from	Where it drifts from the entry
Seller	PO, pro forma invoice	Pro forma names a trading company; the final invoice names another party.
Buyer	PO	A parent company buys, a subsidiary imports.
Importer of record number	Client master file	New IOR set up for a new line of business.
Consignee number(s)	Client master file	Ultimate consignee differs from the IOR.
Manufacturer (or supplier)	Pro forma, supplier list	ISF names the supplier; the entry's MID must identify the manufacturer.
Ship-to party	PO, delivery instructions	Delivery warehouse changes after booking.
Country of origin	Pro forma, supplier's statement	Production moved, or final assembly happens somewhere else.
HTS number (6 digits)	Client's parts list, product description	ISF classified from a vague description; the entry from the final one.
Container stuffing location	Forwarder or origin agent	The supplier doesn't know; the CFS does.
Consolidator (stuffer)	Forwarder or NVOCC	Same. The shipper rarely has it.

In practice, two rows need the most care.

Manufacturer vs shipper

The ISF element is not the B/L shipper. It is the party that last manufactures, assembles, produces or grows the goods, or the party that supplies the finished goods. The filer may instead give the manufacturer name and address used to build the MID for the entry (19 CFR 149.3). Filing the supplier can be correct on the ISF and still leave you with a different party on the entry, where the MID has to identify the manufacturer. How to build that code from the invoice is covered in How to build an MID code from a commercial invoice.

Origin and HTS as a set

Manufacturer, country of origin and the HTS number must be linked to one another at the line-item level (19 CFR 149.3). If one of the three changes, check the other two on that line as well.

The update trap: filed on the pro forma

Here is how it usually goes wrong.

The vessel is still at sea, so the ISF can still be fixed. The regulation requires an update when more accurate information becomes available before the goods enter port limits. Transmit the update now, with the manufacturer, origin and HTS corrected together, since they are linked on the line.

Now run the same example with the final invoice arriving the day after the vessel docks. The update window has closed. The entry will be filed on the final documents, and the ISF on record says something different. That is the case you want to find while the ship is still at sea.

The lesson isn't "never file on a pro forma." Often it's the only document you have 24 hours before lading. It is this: when the final invoice arrives, compare it against the ISF before you start keying the entry, while you can still send an update.

An "ISF on receipt" checklist

Run this when the booking data comes in, and again when the final documents arrive. It sits alongside the wider pre-transmission checklist for entry writers, which covers the entry itself.

When the booking arrives

1. Work back from lading, not arrival. Write the ISF due time on the file: the estimated lading time minus 24 hours. If you don't know the lading time, ask the forwarder today.
2. Match seller and buyer to the PO, not to the B/L shipper and consignee.
3. Decide what you are filing as "manufacturer." If it's a supplier or trading company, note that in the file so whoever writes the entry knows the MID may point to someone else.
4. Check that origin, HTS-6 and manufacturer agree on each line. A product description too vague to classify at six digits is a question for the client now, not at entry time.
5. Ask the forwarder for the stuffing location and consolidator. The supplier often doesn't know them.
6. Record which document each value came from, with its date. You will want this if a claim arrives later.

When the final documents arrive

7. Compare the final invoice and packing list against the ISF, element by element: seller, manufacturer, origin, HTS-6 and ship-to.
8. If anything changed and the vessel hasn't reached port, update the ISF. Log when you sent the update and why.
9. If the shipment was cancelled or rerouted away from the US, withdraw the ISF and give the reason.
10. If the difference turns up after arrival, record it in the file and tell the LCB. Don't quietly file the entry as though the two match.

None of this needs special software. It needs the ISF and the final documents open side by side at the right moment.

Where the time goes

The ISF and the entry are built from the same shipment, days or weeks apart, by people working from different versions of the same documents. The costly mistakes in this post aren't typos. They are pro forma values that nobody rechecked once the final paperwork arrived.

Tools that read the final documents alongside the ISF you filed and put disagreeing values side by side, like EntryWrite, can bring that comparison forward; the decision about what to file stays with the broker.