Importer Security Filing (ISF) Checklist: Data, Timing, Penalties

An Importer Security Filing (ISF), often called “ISF 10+2,” is one of the few U.S. import requirements where timing matters as much as accuracy. If you miss the 24-hour rule, or file with “placeholder” data that never gets corrected, you can trigger penalties and downstream operational pain (cargo holds, exams, rolled drayage appointments, and avoidable demurrage and detention).

This checklist is designed for importers, BCOs, and logistics teams who want a practical, repeatable way to submit ISF cleanly for ocean freight.

What ISF is (and when you need it)

Importer Security Filing (ISF) is a U.S. Customs and Border Protection (CBP) advance data filing required for most cargo moving to the United States by vessel. It is separate from the customs entry (CBP 3461/7501 process) and is focused on advance security risk screening.

Key scope points:

• Mode: ISF is for ocean shipments (including containerized moves such as FCL and LCL, and also other vessel cargo types). It is not an air freight filing.

• Who enforces it: CBP.

• Where to confirm official guidance: CBP’s ISF resources are the best starting point for requirements and policy updates.

For CBP background, see CBP’s overview of Importer Security Filing (ISF).

Who is responsible for filing ISF

CBP places responsibility on the ISF Importer (commonly the Importer of Record, depending on the transaction). Many companies have an authorized agent file on their behalf (often a customs broker or freight forwarder), but delegating the filing does not eliminate importer liability.

In practice, ISF success depends on aligning four parties early:

• Importer (owns commercial truth, parties, HTS direction)

• Supplier (owns manufacturing and packing facts)

• Freight forwarder/NVOCC (owns booking details and routing milestones)

• Customs broker or filing agent (owns transmission, validations, amendments)

If your team is still standardizing import roles and documents, SHIPIT’s broader process overview can help you map the end-to-end flow: Freight Shipping: A Step-by-Step Process for Importers.

ISF 10+2 data checklist (what to collect)

The “10+2” refers to:

• 10 data elements provided by the importer (or its agent)

• 2 data sets provided by the carrier (vessel operating carrier)

The 10 importer ISF elements

You should be able to source these from your purchase order, commercial invoice draft, shipper’s instructions, supplier stuffing plan, and booking confirmation.

• Importer of Record number (typically EIN, or CBP-assigned number)

• Consignee number(s)

• Seller (owner) name and address

• Buyer (owner) name and address

• Ship-to name and address

• Manufacturer (supplier) name and address

• Country of origin

• HTSUS number (at least the 6-digit level is commonly used in practice, but align with your broker)

• Container stuffing location

• Consolidator (stuffer) name and address

The “+2” carrier elements

These are transmitted by the carrier, not the importer:

• Vessel stow plan

• Container status messages

Timing rules you must plan around

The hard rule: the 24-hour filing requirement

For U.S.-bound vessel cargo, ISF must be filed no later than 24 hours before the cargo is laden aboard the vessel at the foreign port.

That is a compliance cutoff, not a commercial preference. Missing it is one of the most common causes of ISF penalties.

The practical reality: you will face earlier “data cutoffs”

Even though CBP’s rule is 24 hours before lading, forwarders, NVOCCs, and carriers often impose earlier documentation and data cutoffs to avoid rolled bookings and to ensure filings can be validated in time.

This becomes more important for:

• LCL shipments (consolidator and container stuffing details may firm up earlier in the CFS process)

• Peak season weeks when documentation teams are overloaded

• First-time importers who are still stabilizing product and shipper master data

If you want a broader view of how compliance and operational cutoffs stack together on real lanes, see: Shipping From China to United States: Docs and Cutoff Timeline.

Amendments: treat ISF as “file early, correct fast”

Some ISF fields are more likely to change than others (especially in LCL, multi-supplier consolidations, or when factories switch stuffing sites). CBP allows updates, but operationally you should assume:

• File as early as you can with the best available verified information.

• Amend immediately when the commercial facts change.

• Put ownership in writing (who monitors changes and who instructs the filer to amend).

If you struggle with recurring holds, compliance misses, or document mismatch problems, this prevention guide is a useful companion: International Logistics: How to Prevent Customs and Port Holds.

Penalties and consequences: what’s really at risk

CBP’s ISF enforcement is commonly felt as a financial penalty plus operational friction.

Monetary penalties

CBP may assess up to $5,000 per ISF violation. Violations can include late filing, inaccurate filing, and incomplete filing.

Because ISF enforcement often ties to bond conditions, importers can also encounter liquidated damages claims when CBP alleges a breach tied to the ISF obligation.

Operational consequences that cost even more than the fine

Even when the dollar penalty is “only” a few thousand, the knock-on costs can be larger:

• Delayed release or targeted exams (more storage and dwell)

• Rolled drayage appointments (especially painful at congested ports)

• Demurrage and detention exposure if cargo cannot be picked up or returned fast

• Warehouse and transload schedule disruption (labor and dock planning)

• Customer service damage when delivery dates slip unexpectedly

A practical ISF quality-control checklist (before you hit “submit”)

ISF errors are usually not “random,” they are predictable mismatches between commercial documents, booking data, and physical reality. Use this QC pass before filing.

1) Party and address consistency checks

Confirm these match across your PO, invoice draft, shipper’s letter of instruction (if used), and booking:

• Seller vs manufacturer (not always the same)

• Buyer vs importer of record (not always the same)

• Ship-to (your DC, 3PL, or Amazon-style facility) is a valid deliver-to address

2) HTS and country of origin alignment

ISF is not the same as entry, but bad HTS direction and origin confusion is a reliable way to invite scrutiny later.

Best practice for teams that import repeatedly:

• Maintain a controlled product classification file (SKU to HTS guidance, origin logic, and a change log)

• Route any “new SKU” or “new factory” through a compliance review before booking

3) Stuffing and consolidator truth test

These two fields drive a large share of amendments.

• If it is FCL and the factory loads the container, stuffing location often equals the factory site.

• If it is LCL and cargo moves to a CFS for consolidation, stuffing location is often the consolidator/CFS location.

Do not guess. Ask your forwarder what the consolidator will report, and keep your ISF aligned.

ISF data element table (source and common failure points)

Use this as a handoff tool between your purchasing team, supplier, and filing agent.

ISF element	Typical source	Who should confirm	Common failure point
Importer of Record number	Internal master data, customs bond file	Importer + broker	Wrong EIN, wrong party listed as IOR
Consignee number	Customer master data	Importer	Consignee differs from ship-to or changes late
Seller name/address	Purchase contract, invoice draft	Importer + supplier	Trading company vs factory confusion
Buyer name/address	PO, invoice draft	Importer	Buyer entity differs from importing entity
Ship-to name/address	Delivery plan, warehouse receiving profile	Importer + warehouse/3PL	Using “HQ” address instead of deliver-to
Manufacturer name/address	Factory profile	Supplier + importer	Multiple factories used for one PO
Country of origin	Supplier COO statement, product spec	Supplier + importer + broker	COO changes with factory shift
HTSUS number	Classification guidance, broker review	Importer + broker	Wrong chapter, wrong assumption by SKU name
Container stuffing location	Factory stuffing plan or CFS receipt	Forwarder/NVOCC + supplier	LCL CFS stuffing location not captured
Consolidator name/address	NVOCC/CFS details	Forwarder/NVOCC	Consolidator changes due to routing change

Timeline template: when to gather what

For most import teams, the biggest ISF improvement comes from moving data collection earlier, before booking, instead of trying to “patch” missing fields right before departure.

Milestone (typical)	What to lock	Output
PO issued / production start	Parties, ship-to strategy, target ETD	A “shipment fact pattern” owned by logistics
2 to 3 weeks pre-ETD (or earlier for LCL)	Manufacturer, COO, product descriptions, HTS direction	Customs-ready commercial draft packet
Booking confirmed	Container plan, routing, forwarder/NVOCC reference numbers	ISF filer has booking + lane info
Before the 24-hour rule	Stuffing location and consolidator confirmed	ISF transmitted and validated
Post-filing, pre-arrival	Amendments only if facts change	ISF kept current, exceptions documented

How ISF connects to drayage, transloading, and warehousing (why operations teams should care)

ISF is sometimes treated as “just a broker task,” but it directly affects your U.S. gateway execution.

When ISF is late or inconsistent:

• Containers can be flagged, which increases the risk of delayed availability.

• Drayage planning becomes reactive, and that can lead to missed terminal appointments and extra storage.

• If you are running a transloading program, any delay at the port compresses your warehouse schedule (labor, dock doors, outbound trailer positioning). That increases the chance of detention, expedite linehaul, or missed delivery windows.

If your operating model relies on port-adjacent execution, it helps to design the gateway as one coordinated system. Related reading:

• Logistics Shipping: How Transloading Cuts Dwell and Fees

• Warehousing Los Angeles: What to Look For Near the Ports

Common ISF scenarios (and what changes)

FCL factory load

• Stuffing location is often the factory.

• Consolidator may be the shipper, or a named party depending on who physically stuffs and controls the load.

• Risk: last-minute factory address formatting errors, or wrong manufacturer when multiple plants exist.

LCL via consolidator/CFS

• Stuffing location is typically the consolidation facility, not the factory.

• Consolidator is the party doing the consolidation.

• Risk: importer assumes factory stuffing details and files early without coordinating with the consolidator.

ISF-5 moves (special transit types)

Some shipments moving under special customs transit or export statuses use an ISF-5 process instead of ISF-10. If you have in-bond or foreign cargo that will not enter U.S. commerce, confirm the correct filing type with your broker and forwarder early.

Implementation tips that reduce ISF errors at scale

• Standardize a pre-booking data packet: one template that purchasing, suppliers, and logistics update each shipment.

• Assign a single owner for “ISF truth”: one internal role accountable for resolving party, address, HTS, and origin questions.

• Build a change-notification habit: when any of these change, your filer should be told immediately: ship-to, manufacturer, stuffing plan, consolidator, PO split/merge.

• Use fewer handoffs: every additional party touching bookings and documents increases mismatch risk.

How SHIPIT Logistics can help (without changing your operating model)

If you need support aligning ISF preparation with real-world execution, SHIPIT Logistics can assist as an international freight forwarder and logistics provider across ocean freight, pickup and delivery, drayage, warehousing, and transloading, depending on the scope you want to outsource.

If your immediate goal is simply “no surprises” compliance on a specific lane, start by sharing a quote-ready shipment brief and your intended service scope. You can also use this broader guide to tighten your process around documents and cutoffs: Ocean Shipment Checklist: Cutoffs, Docs, and Common Holds.

Note: This article is for operational guidance only and is not legal advice. For binding interpretations, consult CBP guidance and your licensed customs broker.