# Importer security filing ISF 10+2: rules, timing, and penalties explained
The importer security filing ISF 10+2 is a CBP requirement for ocean cargo headed to the United States: key shipment data must be filed before the goods are loaded at the foreign port. Late or inaccurate filings can draw penalties and delay cargo, so importers need a reliable process for getting the filing done correctly and on time.
An Importer Security Filing is an advance data filing that gives CBP cargo information before vessel loading, and the importer security filing ISF 10+2 framework is how that obligation is structured. The "10+2" refers to ten data elements supplied by the importer and two supplied by the carrier. This article explains who files, what is filed, when it is due, and what goes wrong when it is not, in general terms. Verify all specifics against current official CBP sources.
Key takeaways
- ISF applies to ocean cargo destined for the US and must be filed before loading at the foreign port, not after the vessel sails.
- The importer is responsible for the ten importer data elements; the carrier handles the two carrier elements.
- Late, incomplete, or inaccurate filings can trigger penalties and cargo holds, so treat the filing deadline as non-negotiable.
- Most importers file through their customs broker or a filing agent, but the legal responsibility stays with the importer.
- Build ISF into your standard operating procedure for every ocean shipment, because one missed filing can disrupt an entire container. Verify current rules and requirements against official CBP sources.
What is the importer security filing and what does 10+2 mean?
The Importer Security Filing is a CBP security program that requires advance cargo information for containerized ocean shipments bound for the United States. The importer security filing ISF 10+2 structure defines who provides what: the importer supplies product and party information, the carrier supplies vessel information. The purpose is straightforward: CBP wants to know what is coming before it arrives, so it can assess risk while the cargo is still overseas. The filing is about security screening, not duty collection, which is why it happens before loading rather than at entry.
The "10+2" breaks down the data. Ten data elements come from the importer side: information about the seller, the buyer, the importer of record, the ship-to party, the manufacturer or supplier, the country of origin, the HTS classification, the container stuffing location, and the consolidator, plus the bill of lading number. Two additional elements come from the carrier side: the vessel stow plan and container status messages. The importer is responsible for the ten; the carrier handles the two.
Note that this article describes the data elements in general terms. The exact definitions and formatting requirements are set by CBP and can be updated, so confirm the current data requirements against official CBP sources or with your filing agent before relying on any summary. The point here is the structure of the obligation under the importer security filing ISF 10+2: the importer supplies product and party information, the carrier supplies vessel information, and both must be filed on time.
The importer security filing ISF 10+2 applies to ocean cargo. It does not apply to air cargo, which operates under different advance-data rules. If you import by both ocean and air, make sure your team knows which regime covers which shipment, because assuming one process covers everything is how filings get missed.
Who is responsible for filing the importer security filing ISF 10+2?
The importer of record is responsible for the timely and accurate filing of the ten importer data elements under the importer security filing ISF 10+2 requirement. In practice, most importers do not file directly; they authorize their customs broker or a specialized filing agent to transmit the ISF on their behalf. That delegation is normal and expected, but it does not transfer the legal responsibility. If the filing is late or wrong, CBP holds the importer accountable, not the agent.
This makes your choice of filing agent and your communication with them important. Your agent can only file what you provide, and they can only file it on time if you provide it on time. The most common ISF failures are not technical filing errors; they are information failures upstream: the supplier's details arrive late, the HTS code is not finalized, or nobody told the broker the shipment existed until the container was already at the port.
If you use a freight forwarder who also handles your customs brokerage, clarify who owns the ISF step. In forwarder-managed supply chains, responsibilities can blur, and each party may assume the other filed. Get it in writing: who files the importer security filing ISF 10+2 for each shipment, what information they need from you, and by when. A one-line confirmation per shipment beats an assumption every time.
For importers new to ocean freight, the practical move is to make the importer security filing ISF 10+2 part of the purchase order process. When you place the order with the supplier, start the ISF data collection at the same time: confirm the manufacturer details, the HTS classification, and the other data elements while production is underway, not when the goods are ready to ship. By the time the container is being stuffed, the filing should be ready to transmit, not still being assembled.
When must the ISF be filed?
Under the importer security filing ISF 10+2 rule, the ISF must be filed before the cargo is loaded onto the vessel at the foreign port. That is the key timing concept: the filing happens upstream of loading, giving CBP the advance window the program is designed around. It is not filed at arrival, not filed at entry, and not filed after sailing. Before loading is the rule.
What this means operationally is that your importer security filing ISF 10+2 process has to run ahead of your logistics, not alongside it. The data must be complete and transmitted while the container is still on land. Importers who treat ISF as a port-side formality discover the problem too late: once loading has happened without a filing, the violation has already occurred, and no amount of rushing afterward undoes it.
Build backward from the vessel's loading schedule. Your filing agent needs the complete data in hand with enough lead time to file and confirm acceptance before loading begins. How much lead time that requires depends on your agent's process and the complexity of the shipment, so agree on an internal cutoff with your agent: the date by which they must have everything. Then hold your suppliers and your own team to an earlier internal deadline, because data always arrives later than expected.
Amendments to an importer security filing ISF 10+2 are possible when information changes after filing, and you should update the filing if the facts change. But an amendment is for genuine updates, not a substitute for filing on time in the first place. File complete and accurate data as early as you responsibly can, and amend if something legitimately changes. Verify the current amendment procedures against official CBP sources.
What happens if the filing is late or inaccurate?
Late, incomplete, or inaccurate filings under the importer security filing ISF 10+2 can draw CBP penalties. This article does not quote penalty amounts, because they are set by CBP and subject to change; verify current penalty provisions against official CBP sources. The practical point is that the penalties are real, they apply per violation, and they are entirely avoidable with a working process.
Beyond penalties, ISF problems cause operational pain. Cargo with ISF issues can be held for examination, which means delays, storage charges, and missed delivery commitments to your customers. A container sitting at the port while an ISF problem gets sorted out costs money every day and disrupts everything downstream: warehouse appointments, trucking, and customer promises. The penalty is the headline; the delay is often the bigger cost.
CBP also tracks compliance patterns. An importer with repeated importer security filing ISF 10+2 violations looks different to CBP than an importer with one mistake and a clean record. Patterns of non-compliance can lead to increased scrutiny of future shipments, which slows everything down. Each filing is a small event, but the pattern across filings shapes how CBP treats you.
Inaccurate filings deserve their own warning. Filing on time with wrong data is not a safe alternative to filing late under the importer security filing ISF 10+2; it is a separate violation. Common accuracy problems include wrong manufacturer information, incorrect HTS codes, and outdated party details copied from a previous shipment. Every data element should reflect the actual shipment, not the last one. Copy-paste is the enemy of ISF accuracy.
How do importers get ISF filing right in practice?
The importers who never have importer security filing ISF 10+2 problems share one trait: the filing is a built-in step in their process, not a separate task someone remembers at the last minute. Build a standard ISF checklist for every ocean shipment: the data elements needed, who provides each one, the internal deadline for receiving them, and confirmation that the filing was accepted before loading.
Standardize your product data. Much of the ten-element data repeats across shipments: your importer details, your usual manufacturers, your HTS classifications. Keep a master data file for each supplier and product so the filing agent is not reconstructing basic facts for every shipment. When something changes, update the master file. This single habit eliminates a large share of accuracy errors in importer security filing ISF 10+2 data.
Communicate loading schedules clearly. Your filing agent needs to know when loading happens to manage the filing timing. Share vessel schedules and any changes promptly. If a shipment rolls to a later vessel, confirm with your agent whether the filing needs updating. Silence between the importer and the agent is where ISF failures breed.
Audit your importer security filing ISF 10+2 filings periodically. Ask your agent for a record of filings over a recent period and spot-check them against your shipment data. Look for patterns: late filings on certain lanes, accuracy issues with certain suppliers, or shipments where the filing trail is unclear. A short quarterly review catches process drift before it becomes a penalty pattern.
Finally, train the people involved. Anyone who places purchase orders, manages suppliers, or coordinates freight should understand what ISF is, why the timing matters, and what information they need to provide. ISF failures are usually communication failures, and communication improves when everyone understands the stakes.
Bottom line: how should importers treat ISF filing?
Treat the importer security filing ISF 10+2 as a non-negotiable step in every ocean shipment: data collected during production, filing completed before loading at the foreign port, accuracy verified against the actual shipment. Assign clear responsibility, set internal deadlines ahead of the loading schedule, and keep master data current so each filing is routine rather than a scramble.
The importers who struggle with ISF are the ones who treat it as paperwork to be dealt with at the port. The importers who never think about it are the ones who built it into their process so thoroughly that it happens automatically. Aim for the second group. And whenever the specifics matter, such as current data requirements or penalty provisions, verify against current official CBP sources rather than relying on summaries.
Frequently asked questions
### What is an Importer Security Filing in simple terms?
An Importer Security Filing is advance cargo data that CBP requires for ocean shipments to the United States, filed before the goods are loaded at the foreign port. It gives CBP shipment information for security screening while the cargo is still overseas. The "10+2" refers to ten data elements from the importer and two from the carrier.
### Who files the ISF, the importer or the broker?
The importer of record is legally responsible for the ten importer data elements. Most importers authorize their customs broker or a filing agent to transmit the filing, which is normal practice, but the responsibility stays with the importer. Clarify in writing who files for each shipment and what information they need from you.
### Does ISF apply to air freight?
No. The Importer Security Filing applies to ocean cargo. Air cargo operates under different advance-data requirements. If you import by both modes, make sure your team applies the right process to each shipment.
### What happens if my ISF is filed late?
Late filings under the importer security filing ISF 10+2 can draw CBP penalties and cause cargo delays, holds for examination, storage charges, and missed deliveries. Once loading has occurred without a filing, the violation has already happened. Verify current penalty provisions against official CBP sources, and build your process so filings are completed before loading.
### Can I amend an ISF after filing?
Amendments are possible when information genuinely changes after filing, and you should update the filing to keep it accurate. But amendments are for legitimate updates, not a substitute for timely filing. File complete and accurate data as early as you responsibly can. Verify current amendment procedures against official CBP sources.