ISF filing is one of the most important parts of a customs entry. It has to be filed before your client's cargo is even loaded onto the vessel, which makes it a process you have to get done on time and with care. 

But ISF filing is not that simple. You need to take care of the elements, the deadlines and everything that sits upstream. 

In this guide, we walk through how it works, what the deadlines and penalties actually are, and where the process tends to go wrong.

What is ISF filing

An Importer Security Filing, or ISF, is a set of data that U.S. Customs and Border Protection requires before ocean cargo is loaded onto a vessel bound for the United States. You submit it electronically, ahead of loading at the foreign port. The requirement sits in 19 CFR Part 149 and applies to cargo arriving by vessel. 

That requirement comes from the SAFE Port Act of 2006. Section 203 of the Act directed CBP to collect advance cargo data before loading so it could flag high-risk shipments before they reached the United States, and the ISF is the rule CBP built to meet that mandate.

You will also see the ISF called "10+2." The name describes how the data is split. Ten elements come from the importer side, including the seller, the buyer, the manufacturer, and the country of origin. 

Two come from the carrier: the vessel stow plan and the container status messages. The importer, or the broker filing on the importer's behalf, provides the ten. The carrier provides the two.

ISF-5 and ISF-10: which filing applies

CBP defines two versions of the ISF, and which one applies depends on what happens to the cargo at a US port. Most brokerage work runs on ISF-10s, so the deadlines and penalties below are written around that filing.

The 10 data elements and who is responsible for each 

The ISF is made up of ten elements from the importer side. Each element has a specific source where they can be found. Some come straight off the commercial invoice or the bill of lading. 

Others are on file with you already. A few have to come from the shipper or forwarder. This table lays out each element and where it comes from:

ISF deadlines

ISF elements are not all due at the same time. 19 CFR 149.2 sets different deadlines depending on the element. Most are due before the goods are loaded at the foreign port. Two are not due until the vessel is close to arriving at a U.S. port. This table shows which elements are due when:

Penalties for late or incorrect ISF

The penalties for ISF are worth understanding in detail, because they are not a single fine and they do not all work the same way. Here is how each part works:

1. Liquidated damages

Every ISF has to be backed by a bond. The ISF Importer either posts one or files under an agent's bond, and the bond can be a Basic Importation and Entry Bond, Basic Custodial Bond, International Carrier Bond, Foreign Trade Zone Operator Bond, or a dedicated Importer Security Filing Bond under 19 CFR 113.62, 113.63, 113.64, 113.73, and Appendix D to Part 113.

Liquidated damages are a fixed amount the bond principal agrees in advance to pay if a bond condition is breached. There is no argument over actual loss. The amount is set by the bond terms. For ISF, CBP may assess liquidated damages of $5,000 per violation. When a filing breaks the rules, CBP makes a claim for that amount, and the claim runs against the bond.

The ways to be in violation

The $5,000 is not tied to a single mistake. CBP names several separate violations under the guidelines, and one shipment can trigger more than one of them:

• Failure to file: No ISF was submitted for a shipment that required one.

• Late filing: The ISF was submitted after the deadline had passed.

• Inaccurate filing: A submitted element was wrong.

• Failure to update: Some elements can be filed on your best available information and corrected before arrival. Skip the correction, or get it wrong, and CBP assesses the first inaccurate update at $5,000.

• Failure to withdraw: The shipment was cancelled and the ISF was not pulled back, which 19 CFR 149.2(e) requires.

  
  

Two violations on one shipment mean two claims, which brings the liquidated damages to $10,000. That is the ceiling for liquidated damages on a single ISF. For serious or repeat offenders, CBP can also assess a statutory penalty under 19 U.S.C. 1595a(b), which runs outside the bond and requires CBP Headquarters approval.

The cost that is not the fine

The fine is the visible number. The larger cost usually sits in what happens to the cargo. When an ISF is missing or non-compliant, CBP has several holds available:

• A do not load (DNL) hold can be issued at the foreign port. The container does not board the vessel. A DNL is not a fine. It is a missed sailing, and the next available vessel can be a week or more out. 

• CBP can withhold the release or transfer of the cargo until the required ISF is filed and reviewed. The shipment sits at the terminal while storage and demurrage accrue. 

• CBP can delay or deny the vessel's permit to unlade, and once the ISF data is received it can order a non-intrusive or intrusive exam. Exams add fees, container moves, and days. 

  
  

This is where the operational cost lives. A $5,000 claim can be mitigated for a first offense. A missed vessel and a held container cannot be undone by a petition.

How ISF filing happens and where errors come in

Filing an ISF follows the same steps on nearly every shipment, and errors tend to enter at the same points every time. Here is how the process runs and where it breaks:

1. Document intake

Every entry starts with paperwork from the importer and shipper: a commercial invoice, packing list, bill of lading, and purchase order. They arrive by email or fax as PDFs, scans, and sometimes photos, each shipper formatted differently, and someone on your team reads each one and moves the data into the systems you file from.

Now the area where errors come in is that documents often arrive incomplete or hard to read, so you are short on data before you start, and the figures are not always reliable. 

One broker described an importer's invoice where "they just typed in a total and didn't use the formula," which left the team asking, "how do we get to this total here?". You cannot file off a number you cannot verify, so the entry stalls until someone confirms it.

2. Data extraction from source documents

Half the ISF is already sitting on the documents you have. The seller, buyer, manufacturer, ship to party, and country of origin are all on the commercial invoice and the bill of lading. Getting them into the filing is the manual part. Your team reads each document and types those fields into the filing one at a time, and repeats that for every shipment.

Where errors come in: typing is where wrong values get in. A digit gets keyed incorrectly, or a country of origin from the last entry gets carried into this one, and the filing no longer matches the document it came from. CBP treats that as an inaccurate filing, which is a $5,000 violation counted separately from a late one.

3. Collection of missing elements

When you assemble an ISF, some of the ten elements will not be sitting with you. For example, the container stuffing location and the consolidator information lives with the shipper or the forwarder, because they are the ones who load and consolidate the container. So before you can complete the filing, you have to reach out and ask for those elements.

This is where errors come in, and the root of it is that you depend on parties who are not careful with what they send. As one broker put it, "unfortunately, importers and exporters, both, don't provide proper paperwork. Their invoices are, most of the time, incomplete, or descriptions very generic."

So the request goes out as an email, and email is easy to answer halfway. You ask for two elements and get one back, so you follow up for the rest. Meanwhile the 24-hour cutoff does not move. It keeps approaching while you wait on someone who has no deadline of their own.

That is why chasing missing data, not filling out the form, is the most common reason an ISF goes in late.

4. Transmission to CBP

Once all ten elements are assembled, you transmit the ISF to CBP through ABI or ACE. This has to happen no later than 24 hours before the goods are loaded at the foreign port. The transmission itself is not the hard part. Whether you hit the deadline depends entirely on whether the data was ready in time, and by this step that is already decided.

This is where errors come in. If an element is still missing when the cutoff arrives, you are forced into a choice, and both ways cost you. You can file late, which is a violation. 

Or you can file with the gap and correct it once the missing piece comes in, which makes it an inaccurate filing, a separate violation. So a delay that started three steps earlier, while you were waiting on a shipper, surfaces here as a $5,000 charge you cannot avoid once the clock has run out.

5. Updates and withdrawals

Transmitting the ISF does not close the shipment. The filing has to stay accurate until the goods arrive, and two things can change after you file.

The data can change while the shipment goes ahead, like an invoice that gets corrected to a new value. Or the shipment can fall off, like an order that gets cancelled. The regulation treats these differently. Under 19 CFR 149.2(d) you update the ISF to match the corrected data. Under 149.2(e) you withdraw it.

This is where errors come in. Either action depends on the filing staying connected to the documents it came from. In a manual process, that connection is a person remembering that an invoice already went out as an ISF.

When a corrected invoice arrives weeks later, nobody links it back, so the update never happens. A filing that was accurate the day you sent it is wrong by the time the vessel arrives, and CBP assesses that as an inaccurate filing.

How to file ISF on time and without errors

If you look closely at where each error came from, not one of them started with the ISF itself. They started upstream, in the documents. Every failure point in the process is a document handling step, and every one of them is done by a person.

That is the argument for document automation, and it is a narrow one. 

You are not handing over judgment, and you are not handing over the filing. You are handing over the reading, the keying, the chasing, and the cross-checking, the work that never needed a person to begin with. 

That layer is where Docxster sits, between your inbox and the filing software you already run. It assembles the filing and checks it, then gives it back to you to approve.

Here is how that changes each step:

1. Intake and extraction

This is the step where most errors start happening. Every entry starts with documents in a dozen formats, and every value on the filing has to be read off one of those documents and typed in by a person. It is the most repetitive part of the day, which is exactly why it is the easiest place to slip and the highest-value place to automate.

Docxster takes the reading and the typing out of it. It pulls the commercial invoice, packing list, and bill of lading from your inbox in whatever shape they arrive, printed, scanned, faxed, or PDF, and lifts the elements the ISF needs:

• Seller and buyer

• Manufacturer or supplier

• Ship to party

• Country of origin

  
  

Each one is mapped to the right ISF field no matter where a given shipper places it on their invoice. Nothing is keyed across, so the two ways an inaccurate filing happens, the mis-key and the value pulled from a previous entry, have no way in.

2. Chasing missing elements

The elements you have to request from the shipper or forwarder are the ones that usually run the filing late.

Docxster closes that loop in one pass. It identifies everything the filing is still missing, then collects all of it in a single request instead of one email per field. That request goes out as one consolidated email to the shipper, or as a form they fill in, and when the reply comes back Docxster reads it and writes the answers into the entry. One ask, one response, no thread to manage.

3. Assembly and transmission

Before an ISF is transmitted, the values that appear on more than one document have to match. When the consignee or the declared value reads one way on the invoice and another on the bill of lading, that conflict has to be resolved first. Reconciling that at your desk is quick. If it goes out unresolved, CBP records it as an inaccurate filing.

Docxster pulls all ten elements together from the documents and the carrier feeds, then compares the fields that should match across the invoice, packing list, and bill of lading. It surfaces only the ones that don’t match, so you review the conflicts instead of re-reading every page.

Docxster hands the checked ISF to the software you transmit through, so what goes out over ABI or ACE is complete and consistent and goes before the cutoff. Every approval is logged with who signed off and when, so the filing carries its own record.

4. Updates and withdrawals

At Docxster we understand that the obligation does not end at transmission. A corrected invoice means the ISF has to be updated, and a cancelled order means it has to be withdrawn, both before the goods arrive. 

At Docxster, the filing stays tied to the documents it came from, so a corrected invoice is caught by the same consistency check instead of disappearing into an inbox. And it can track the vessel and notify you as arrival nears, so you see the window to update or withdraw while there is still time to act.

Choosing a software that helps your ISF filing process

The ISF deadline is set the moment the booking is made. You cannot negotiate the 24 hours, and you cannot make the seller or the forwarder move faster. The only thing in your control is how quickly and how cleanly the data comes together before the cutoff.

Most of that data is already in your hands. Half the ten elements sit on the commercial invoice and bill of lading you already hold. Filings go late or wrong for two reasons: the elements you have to chase from third parties, and the values that get mis-keyed on the way into the filing. Fix how the data is collected and checked, and the filing goes out on time and correct on its own.

That is the part Docxster handles. It reads the documents, collects the missing elements, checks the fields that have to agree, and gives you a complete ISF to approve before the cutoff, without changing the software you file through. Book a demo to see it run on your own documents.

FAQs