A container can clear every production milestone in Mexico, have a booked vessel slot, and still create a U.S. compliance problem before it leaves the foreign port. The question of when is ISF filing required comes down to the mode and purpose of the shipment, not its final destination or who arranged the drayage. For qualifying ocean freight, the filing must be handled before loading - not when the vessel reaches the United States.
When Is ISF Filing Required?
An Importer Security Filing, commonly called ISF or the 10+2 filing, is generally required when cargo is transported to the United States by vessel from a foreign port. The rule applies to goods intended for U.S. consumption, goods moving into a foreign-trade zone, and several in-bond movements that arrive by ocean.
For a standard commercial import, the responsible party files an ISF-10. The filing must reach U.S. Customs and Border Protection at least 24 hours before the container is laden aboard a vessel bound for the United States. That timing is the operational pressure point. A complete commercial invoice delivered after loading may still be enough to prepare a customs entry later, but it is too late to support a compliant ISF.
The ISF requirement is tied to the ocean leg. If freight moves from Monterrey to Laredo by truck and crosses into Texas over the land border, an ISF is not required simply because the goods originated in Mexico. That move requires the appropriate U.S. entry process and Mexican export documentation, but it is not an ocean ISF transaction.
If the same goods move from a Mexican port by vessel to Houston, Los Angeles, or another U.S. port, ISF requirements apply. A final truck leg after discharge does not change that. Neither does a move that combines ocean, rail, and truck transportation. If the shipment arrives in the United States on a vessel from abroad, start by determining the applicable ISF type.
ISF-10 versus ISF-5
Most importers dealing with merchandise entering U.S. commerce will use ISF-10. This is the standard filing for cargo destined for a U.S. consumption entry or a foreign-trade zone.
ISF-5 applies to certain cargo not intended to enter U.S. commerce, including foreign cargo remaining on board a vessel, immediate exportation movements, and transportation and exportation moves. For example, foreign cargo discharged at a U.S. port and transported under bond to Mexico may require an ISF-5 if it is moving under a transportation and exportation entry.
The distinction matters because the data requirements differ. Teams should not assume that a shipment avoids ISF just because it will ultimately leave the United States. The in-bond movement and cargo purpose determine whether an ISF-5 is needed.
The 24-Hour Rule Is a Loading Deadline
ISF is often treated as a pre-arrival filing. Operationally, that is the wrong mindset. For most containerized cargo, CBP requires the filing 24 hours before loading at the foreign port. The vessel's estimated arrival date is not the deadline.
That means a late commercial invoice, an unconfirmed importer of record number, or a missing container stuffing location can put the shipment at risk before departure. A booking confirmation does not solve the compliance gap. The filing data has to be transmitted and accepted against the correct bill of lading details.
Some ISF elements have more flexible timing under CBP rules. The container stuffing location and consolidator information may be filed as early as possible, but no later than 24 hours before the vessel arrives at a U.S. port. That flexibility is not a reason to delay the rest of the file. Treat it as a narrow exception for data that is genuinely unavailable at loading.
For breakbulk cargo, timing can differ from standard containerized freight. Bulk cargo also has separate treatment under the regulations. Those exceptions should be validated shipment by shipment with the customs broker and carrier rather than assumed from a broad cargo description.
What Data Is Required for an ISF-10?
An ISF-10 contains ten importer-supplied data elements, while the ocean carrier provides two additional vessel and container elements directly to CBP. The importer is responsible for making sure its data is complete, accurate, and aligned with the shipment documents.
The required importer data includes:
- Manufacturer or supplier name and address
- Seller or owner name and address
- Buyer or owner name and address
- Ship-to party name and address
- Container stuffing location
- Consolidator name and address
- Importer of record number
- Consignee number
- Country of origin
- Commodity HTSUS number
These fields look straightforward until data starts moving among a supplier, forwarder, NVOCC, carrier, broker, and warehouse. The problem is usually not a lack of documents. It is that each party has a different version, receives it at a different time, or manually rekeys it into a separate system.
Classification deserves particular attention. The HTSUS number in the ISF is not a placeholder. It must be reasonably accurate and should align with the classification used on the eventual customs entry. A last-minute classification change can create a mismatch that requires a correction and invites avoidable scrutiny.
ISF Is Not the Same as a Customs Entry
An ISF does not release cargo, calculate duties, replace a customs entry, or substitute for a Mexican pedimento. It is a security filing submitted ahead of ocean loading. The customs entry is a separate declaration used to enter merchandise into the United States.
For cross-border teams, this separation is where handoff failures begin. One party may have filed the ISF, another may be preparing the entry, and a third may control the bill of lading or delivery order. If those records do not reconcile, the shipment can arrive with compliance and release issues even though every provider says its part is complete.
The better operating model is to establish one shipment record early, assign a clear ISF owner, and keep product, party, and bill of lading data synchronized through entry filing and final delivery. This is especially valuable for importers moving recurring freight from Mexican suppliers through U.S. ports and then inland by truck or rail.
Who Is Responsible for Filing?
For an ISF-10, the ISF importer is generally the goods' owner, purchaser, consignee, or an authorized agent acting on that party's behalf. Many importers authorize a licensed customs broker or freight forwarder to transmit the filing, but delegation does not eliminate the importer's exposure when source data is incomplete or inaccurate.
The filing also requires bond coverage. Depending on the shipment profile, that may be supported by a continuous customs bond or a single-transaction bond. Bond availability should be confirmed before cargo is ready to load, not after a carrier asks for a filing confirmation.
Responsibility needs to be explicit in the shipping instructions. “The forwarder handles it” is not a control process. Identify who collects data from the supplier, who validates the HTSUS and parties, who submits the ISF, who monitors acceptance, and who files amendments when shipment facts change.
Common Situations That Trigger Late or Incorrect ISFs
The most frequent issues are operational, not theoretical. A supplier may provide a pro forma invoice without final country-of-origin data. A consolidator may not be identified until cargo is packed. A purchase order may show a U.S. headquarters address while the actual ship-to party is a distribution center. A bill of lading number may change between booking and loading.
These are manageable when the workflow starts before the cargo handoff. They become expensive when the ISF is treated as a document task assigned after the container is gated in.
CBP can assess liquidated damages of up to $5,000 per violation for late, inaccurate, or missing filings. The actual enforcement outcome depends on the facts, history, and corrective action, but the larger cost is often disruption: delayed delivery, manual escalation, and a shipment team spending hours reconciling data that should have been controlled at origin.
A practical checkpoint is simple: before the container is released for loading, confirm the filing type, the bill of lading reference, all ten ISF data elements, the filing party, and bond coverage. Then retain the accepted filing confirmation in the shipment record.
Ocean imports reward early control. When ISF ownership and source data are settled before loading, the U.S. port becomes the next planned step in the move - not the first place a preventable compliance issue surfaces.