ISF 10+2 Data Elements: A Complete Compliance Checklist for U.S. Importers

The Importer Security Filing regulation has been in effect since January 2009, yet ISF violations remain one of the most consistent sources of CBP enforcement actions and cargo delays for U.S. importers. The reason is rarely ignorance of the requirement itself. Most experienced importers and freight professionals know ISF exists. The breakdowns happen at the data level: the wrong party name, a missing consolidator entry, a country of origin that does not match the commercial invoice, or a filing that goes out 22 hours before loading instead of the required 24.

This checklist covers every one of the 10+2 data elements in plain operational terms. It explains what each field requires, where the data comes from, who is responsible for it, and where errors most commonly occur. It is written for importers, freight forwarders, NVOCCs, and compliance teams who need clarity on what CBP actually expects, not just a summary of the regulatory text.

If your team is reviewing its ISF process, evaluating a filing partner, or preparing for a CBP audit, use this as your working reference. The goal is zero surprises at the vessel cut-off.

What Is ISF and Why Does Every Field Matter

The Importer Security Filing, formally codified under 19 CFR Part 149, is a mandatory pre-arrival data submission required by U.S. Customs and Border Protection for all containerized ocean cargo destined for the United States. It is not a customs entry. It is not a bill of lading. It is a dedicated security filing that gives CBP advance visibility into who is shipping what, from where, through which supply chain parties, and via which vessel and routing.

CBP uses ISF data in its automated targeting system to assess risk before a container ever loads at the foreign port. When the data is complete and accurate, a shipment moves through targeting without flags. When data is missing, inconsistent with the AMS manifest, or submitted late, automated systems generate alerts that can result in a "do not load" instruction, an enhanced examination on arrival, or a penalty assessed against the importer's ISF bond.

The "10+2" structure refers to ten data elements the ISF Importer must submit and two additional elements the ocean carrier submits through a separate process. Each element serves a specific purpose in CBP's targeting model, which is why field-level accuracy matters as much as the overall filing timeline. A filing submitted on time with a wrong manufacturer address is still a compliance problem.

The 10 Importer Data Elements: Field-by-Field Breakdown

The following ten elements are the responsibility of the ISF Importer. This party is defined by CBP as the owner, purchaser, or consignee of the goods, or a licensed customs broker acting on their behalf. In LCL shipments, the NVOCC or freight forwarder often files as the authorized agent of the importer. Whoever files, the legal obligation sits with the importer of record.

The 2 Carrier Data Elements

The two carrier elements are submitted by the ocean carrier through a separate filing process independent of the importer's ISF submission. While importers are not directly responsible for filing these, they need to understand what they are, because CBP cross-references the carrier elements against the importer's ISF data during targeting.

For importers working with NVOCCs on consolidation shipments, it is worth confirming which party is coordinating ISF filing against the AMS manifest data. Discrepancies between the ISF seller/buyer data and the HBL consignee information on the AMS submission are one of the most common sources of automated CBP flags on LCL cargo. If you want to understand how ISF and AMS interact in practice, the relationship between these two filing programmes is something that ocean importers working through consolidators should understand clearly before cargo loads.

Where ISF Compliance Breaks Down: The Most Common Filing Errors

Twenty years of ISF filings reveal a consistent set of errors that account for the majority of CBP flags, amendment requests, and penalty actions. None of these are exotic edge cases. They happen routinely in operations that are otherwise running smoothly.

• Manufacturer vs. Supplier confusion: Many importers list their supplier, not the actual manufacturer who produced the goods. CBP's targeting model specifically values manufacturer data. When the party named as manufacturer is actually a trading company or forwarder in a third country, it creates a risk signal that would not exist with accurate data.
• HTS code mismatches with entry: When the 6-digit HTS filed on the ISF does not match the HTS used on the formal customs entry later, CBP systems flag the inconsistency. This is particularly common when the ISF is filed before the commercial invoice is finalized and the entry is prepared from a different product classification review.
• Ship-to party left as consignee: The ship-to party field frequently defaults to the consignee address, which is accurate for direct shipments but incorrect when goods are shipped to a distribution center, a third-party logistics provider, or a bonded warehouse. The ship-to must reflect the actual first U.S. destination.
• Late updates to Container Stuffing Location and Consolidator: These two fields are sometimes submitted as "to be determined" at initial filing and then never updated. Under CBP rules, they must be finalized before vessel arrival, not just before loading.
• Seller name format inconsistencies: When the seller field uses a short trade name or abbreviation that does not match the full legal entity name on the commercial invoice, CBP cross-reference matching fails. Legal names with exact spelling must be used consistently across all filing documents.
• Filing against the wrong bill of lading: In LCL environments, ISF filings must be linked to the correct HBL. When a filing is linked to the MBL instead of the applicable HBL, or to an outdated bill of lading number that was corrected after ISF submission, the filing effectively becomes unmatched in CBP's system.

The ISF Filing Timeline: What Needs to Happen When

Managing ISF compliance is as much a scheduling discipline as it is a data discipline. The regulation sets specific timeframes for each action, and vessel cut-offs add another layer of time pressure that the 24-hour rule alone does not fully capture.

The practical challenge is that the 24-hour clock starts at loading, not at booking. For many trans-Pacific routes, the vessel may load 36 to 48 hours after the booking confirmation, which compresses the window significantly if the commercial invoice or packing list is not available at booking. Getting ISF data collection built into the pre-shipment workflow, rather than treating it as a filing task triggered by a cut-off notice, is how operations with clean ISF records consistently maintain compliance.

How ISF Data Interacts with AMS and Why Consistency Matters

ISF does not exist in isolation. CBP's automated targeting system correlates the ISF data with the AMS cargo manifest submitted by the ocean carrier or NVOCC. When the same shipment is described differently across these two filings, the inconsistency itself becomes a compliance signal.

The most consequential cross-reference points are the consignee name and number, the commodity description and HTS code, the port of lading, and the vessel and voyage number. A freight forwarder filing ISF on behalf of a client while a different NVOCC is handling the AMS submission creates a coordination dependency that, without active management, regularly produces mismatches. For operations running high volumes of LCL consolidation shipments, understanding this relationship is especially important. The difference between ISF and AMS, what each covers, who submits each, and how CBP uses both together, sits at the core of what makes ocean import compliance manageable or problematic at scale.

ISF Penalties: What CBP Can Assess and How Violations Are Triggered

CBP has the authority to assess liquidated damages of up to $5,000 per ISF violation. A single shipment can generate multiple violations if several elements are missing, if the filing is late, and if required amendments are not submitted. In practice, CBP enforcement has focused on patterns of non-compliance rather than isolated first-time errors, but that enforcement posture does not reduce the financial exposure for importers with systemic ISF problems.

Violations are typically triggered in three ways. First, the ISF is not filed at all or is filed after cargo has already loaded, which is an absolute late filing. Second, the ISF is filed on time but with data that is materially inaccurate, for example a manufacturer name that does not match any known entity associated with the declared country of origin. Third, the ISF is filed and accepted but is never updated with the final Container Stuffing Location and Consolidator data before the vessel reaches the U.S. port.

Importers using a fragmented filing setup, where one vendor handles ISF and a separate party handles the AMS or the formal entry, carry elevated risk because no single party has visibility into the full compliance picture for each shipment. When something goes wrong, identifying the source of the error and correcting it before CBP escalates requires coordination across multiple systems. This is one of the structural arguments for managing all customs filing obligations through a single integrated platform rather than distributing them across separate vendors and tools.

ISF-5: When the Standard 10-Element Filing Does Not Apply

Not all ocean cargo bound for the United States requires the full ISF-10 submission. CBP established the ISF-5 as a simplified filing variant for specific cargo categories where the standard 10-element structure does not fit the supply chain model.

ISF-5 applies to cargo that remains on the vessel continuously during its U.S. port call and is not offloaded for customs clearance (in-transit cargo), vessel supplies and equipment intended for use on the vessel, cargo that is not for commercial sale and does not enter U.S. commerce, and certain government cargo categories. For standard commercial shipments brought into U.S. commerce, ISF-10 is the applicable framework without exception.

If your operation includes a mix of through-transit cargo and standard commercial imports on the same vessel, confirming the correct ISF variant for each shipment type is an important step in pre-filing review. Filing ISF-10 for cargo that qualifies for ISF-5 is not a compliance problem, but filing ISF-5 for cargo that should have been filed as ISF-10 is a significant error.

ISF in LCL Shipments: Responsibilities Across the Consolidation Chain

LCL shipments introduce a layer of complexity to ISF compliance that FCL importers do not face. In a consolidation environment, the NVOCC or freight forwarder is typically issuing the House Bill of Lading and, in many cases, is also the party coordinating the ISF filing on behalf of the actual importer. This creates a question of authority and accountability that needs to be clearly established in the service agreement before the first shipment moves.

The ISF Importer, as defined by CBP, is always the owner, purchaser, or consignee of the goods. The NVOCC or forwarder filing the ISF is acting as an authorized agent. That distinction matters when something goes wrong. CBP's penalty assessment targets the ISF Importer, not the filing agent, even if the agent made the error. Importers using NVOCCs to file ISF on their behalf should ensure their filing agent has a documented process for data validation, amendment handling, and penalty response.

The Container Stuffing Location and Consolidator fields are particularly important in LCL scenarios. For consolidation shipments, the CFS or freight station where cargo is stuffed is a specific, identifiable entity, and that information is available before the vessel loads in most cases. Leaving these fields blank in LCL filings where the data is available is an unnecessary compliance gap.

How Info-X Supports ISF Compliance for Importers and Freight Professionals

Info-X has been managing ISF filings for U.S. importers, NVOCCs, and freight forwarders for more than 20 years. The service covers the complete ISF lifecycle: data collection against your shipment documents, validation across all 10 importer elements before submission, direct CBP connectivity for status confirmation, amendment management throughout the voyage, and audit-ready filing records for every shipment.

For teams running high volumes of ocean imports, the value of working with a dedicated ISF filing partner is not just in having someone to handle the submission. It is in having a compliance team that flags data problems before they become CBP flags, that manages amendment windows proactively, and that maintains a consistent data standard across every filing rather than relying on individual operators to catch inconsistencies in a high-volume workflow.

For NVOCCs and freight forwarders managing ISF on behalf of their importer clients, Info-X operates as an extension of the compliance team. Every ISF filing goes out with the same validation standards, the same data quality checks, and the same direct authority connectivity. There is no intermediary system adding delay between submission and CBP acceptance.

Importers whose trade lanes extend beyond the United States benefit from a consolidated approach to pre-arrival filings. The same supply chain discipline that applies to ISF for U.S. imports applies to ICS2 for EU imports, MPCI for UAE cargo, and other pre-load programmes across global trade corridors. The structural question of whether to manage each programme through a separate vendor or through one integrated partner directly affects how well compliance holds up under the time pressure of real shipping operations. Teams evaluating that question will find that the case for consolidating customs filing under a single partner is stronger at scale than it appears when each programme is evaluated in isolation.

Your ISF 10+2 Pre-Filing Checklist

Use this as your operational reference before every ISF submission. Every item here corresponds to a real source of CBP flags or penalty actions. Walk through it with your compliance team and your filing partner before the vessel cut-off, not after.

Data Collection and Accuracy

• Full legal name and address of the Seller confirmed against the commercial invoice
• Full legal name and address of the Buyer confirmed against the purchase order or contract
• IRS EIN or CBP-assigned number of the Importer of Record confirmed and active
• IRS EIN or CBP-assigned number of the Consignee confirmed, with note if same as importer
• Full legal name and physical address of the Manufacturer (not supplier or trading company) confirmed
• Correct Ship-to Party address confirmed: first U.S. destination, not default consignee address if different
• Country of Origin confirmed against manufacturing records, not country of export or trans-shipment
• HTS number confirmed at 6-digit minimum, 10-digit preferred, consistent with formal entry classification

Timing and Submission

• ISF confirmed filed at least 24 hours before container loading at the foreign port
• CBP acceptance status confirmed (not just submission): watch for rejection notices
• ISF linked to the correct HBL (not MBL) for LCL consolidation shipments
• Filing timestamp documented for audit reference

Elements 9 and 10: Update Tracking

• Container Stuffing Location (name and address) available and entered, or flagged for update before U.S. arrival
• Consolidator (name and address) available and entered, or flagged for update before U.S. arrival
• Amendment deadline for Elements 9 and 10 calendared: 24 hours before first U.S. port arrival

AMS Cross-Reference

• Consignee name on ISF matches consignee on AMS/HBL exactly
• HTS code on ISF consistent with commodity description on AMS manifest
• Vessel and voyage number on ISF match AMS submission
• Port of lading on ISF matches AMS

Amendment and Bond Management

• ISF bond confirmed active and sufficient before filing
• Process in place to monitor for amendment needs after original submission
• Contact protocol established with filing agent for cut-off amendments: who calls, how fast they respond

Importers who find this checklist highlights gaps in their current ISF workflow are often also reviewing broader questions about how their ocean compliance programme is structured. The ISF filing process sits at the front of a chain that includes AMS coordination, formal customs entry, and post-entry audit readiness. For high-volume ocean importers, ensuring that each step in that chain is connected and consistent is a programme-level decision, not just a filing task. The strategic approach to ISF filing for ocean importers is worth reviewing alongside this checklist if your volumes have grown beyond what a transactional filing relationship can reliably support.