ISF Filing: 10+2 Requirements, Deadlines, and Penalty Amounts

A freight forwarder in Houston filed 47 ISF submissions for a machinery importer in February 2025. Every filing got an acceptance message from CBP's ACE system. Two months later, 11 of those 47 generated liquidated damages notices at $5,000 each, totaling $55,000, because the Bill of Lading numbers referenced the master bill instead of the house bill. The ISF filing obligation under 19 CFR 149, known as the 10+2 rule, requires 12 data elements for every containerized ocean shipment entering the United States, submitted at least 24 hours before cargo loads at the foreign port. No de minimis exemption exists. Even Section 321 shipments under $800 need an ISF on file.

What the 10+2 Rule Requires from Every Ocean Importer

Under 19 CFR Part 149, ISF filing splits into two obligation sets. An importer of record, or a licensed customs broker acting under Power of Attorney, submits 10 data elements through ACE. The ocean carrier submits 2 more. CBP then cross-references all 12 against Automated Manifest System (AMS) data to flag shipments for inspection before they dock.

Ten elements fall on the importer: seller name and address, buyer name and address, importer of record number (EIN or CBP-assigned), consignee number, manufacturer or supplier name and address, ship-to party, country of origin, commodity HTS number at the 6-digit level, container stuffing location, and consolidator name and address. Carriers provide the vessel stow plan and container status messages.

We've seen importers treat the 6-digit HTS requirement as an afterthought. That backfires. CBP compares the HTS number on the ISF against what shows up on the customs entry. A mismatch triggers an inaccuracy flag. We talked to an electronics distributor in Dallas who got hit with 14 liquidated damages claims in Q1 2025 because their Shenzhen supplier kept sending 4-digit codes. Nobody caught it for three months.

Fourteen claims. Over a copy-paste habit.

Legal responsibility sits with the ISF importer under 19 CFR 149.2(a) regardless of who transmits the filing. Your freight forwarder handles the keystrokes, but if the data comes back wrong, the importer of record pays the $5,000. Most import compliance programs miss this distinction entirely. Delegating ISF work to a third-party ISF service provider does not move the liability.

ISF-5 covers a narrower set: goods transiting the U.S. in bond that never enter domestic commerce. Only 5 data elements required for those: booking party, foreign port of unlading, place of delivery, ship-to party, and commodity HTS number.

ISF Filing Deadlines and the 24-Hour Submission Window

CBP's ISF filing deadline lands 24 hours before cargo loads onto the vessel at the foreign port. Not before departure. Not before U.S. arrival. Before loading. CBP benchmarks timeliness using the vessel departure date minus 24 hours.

That window sounds workable until you're chasing data. Ocean carriers hand over Bill of Lading numbers days before loading. In LCL shipments, the container stuffing location comes from a consolidator overseas who may not respond for 48 hours. We've watched shipments get flagged because a carrier rolled the booking to a different vessel and nobody updated the customs ISF to reflect the new Bill of Lading. CBP accepted the original filing without rejection or warning, but the AMS mismatch produced a liquidated damages case 90 days later.

Get ISF data to your customs broker 72 hours before estimated loading. That buffer covers weekends and holidays, plus the back-and-forth with overseas suppliers who send partial information in three separate emails. Filing the ISF at the 23rd hour leaves zero room for correction.

After submission, CBP permits amendments until the vessel arrives at the first U.S. port of discharge. Corrections after arrival get harder to push through, and the original inaccuracy may still generate a $5,000 claim. Once the vessel docks, the amendment window is effectively closed.

One approach that consistently fails: relying on the ACE acceptance message as proof that your ISF customs submission is complete. CBP will accept a filing with blank data elements without telling you anything is missing. The acceptance confirms receipt. Not accuracy. We've seen importers go months thinking their filings were clean, only to get stacked liquidated damages notices because two fields were empty on every submission.

Penalty Amounts for Late or Inaccurate ISF Submissions

CBP assesses $5,000 in liquidated damages per ISF filing for each noncompliance category. Five categories: failure to file, late filing, inaccurate filing, incomplete filing, failure to withdraw an invalid ISF. A single shipment can hit $10,000 if CBP finds multiple categories on one filing.

For an importer running 50 ocean containers per month with a 10% error rate, that exposure looks like $25,000 monthly in liquidated damages alone. Add demurrage, detention, and examination costs from cargo holds. Port exam fees run $2,500-$5,000 per container depending on the facility. Storage charges compound daily. A held container at the Port of Los Angeles racks up $150-$300/day in storage after the free time expires.

First-time violations qualify for mitigation. CBP can cancel liquidated damages on a first offense for $1,000-$2,000 if the importer shows corrective steps and a low violation ratio relative to total filings. Second and later violations settle at $2,500. C-TPAT Tier 2 and Tier 3 importers get up to 50% off the mitigated amount on top of that.

Nobody budgets for this part: CBP ports now initiate liquidated damages locally, within 90 days of spotting the violation. The old three strikes warning died years ago. A $5,000 notice shows up in April for a shipment that cleared in January. By then the importer has moved on and the original Bill of Lading is buried in an email thread from the freight forwarder's back office.

Voluntary disclosure helps, but only at the margins. If an importer spots an ISF error before CBP does and self-reports through the prior disclosure process under 19 CFR 162.74, first-offense mitigation can drop to $1,000. Paying assessed fines within 30 days also improves the outcome. But the liquidated damages case still opens. Neither option makes it disappear. We've talked to importers who assumed voluntary disclosure would wipe the slate clean. It does not.

Beyond fines, cargo holds create their own damage. CBP can issue a do-not-load order to the carrier, keeping the container off the vessel entirely. At the discharge port, CBP can hold a container for intensive exam. We've seen a single held container at the Port of Long Beach run up $8,000-$12,000 in demurrage and storage alone, before re-delivery charges even hit the invoice. Seasonal importers have had holiday product launches derailed by a single ISF hold in October, goods sitting at the port while the sales window closes.

Common ISF Filing Errors That Trigger CBP Enforcement

Bill of Lading mismatches generate more ISF penalties than any other error type. HTS discrepancies come second. Timing failures round out the trio.

On the Bill of Lading side: the ISF must reference the lowest bill level filed in AMS. Could be a house bill, could be a regular (master) bill. When an NVOCC issues a house bill but the ISF references the master bill, CBP can't match the filing to the manifest. The shipment looks unfiled. A customs broker we work with in Long Beach estimated 30% of the ISF penalty cases crossing her desk in 2025 trace back to this single mismatch.

HTS cross-checking tightened in the last two years. CBP now compares the 6-digit code from the ISF against the classification on the customs entry. Before this, importers could file a generic HTS on the ISF and refine it later on the entry without consequence. That gap closed. An ISF application declaring HTS 8471.30 for laptops while the entry shows 8471.49 generates an inaccuracy finding. No exceptions.

Timing failures hit importers who had no part in the delay. Carrier rolls a booking to a different vessel. Loading date shifts. The ISF was filed for the original schedule and now sits outside the 24-hour window on the new vessel. CBP's mitigation guidelines acknowledge vessel diversions as outside the importer's control, but you need documentation proving the carrier caused it. Without that paper trail, the $5,000 stands.

A detail that teams forget about in the noise around Bill of Lading and HTS issues: failure to withdraw. Every canceled shipment needs its ISF formally withdrawn through ACE. A compliance manager at a consumer goods company in Atlanta told us she found 23 orphaned ISFs from canceled orders sitting in her company's ACE account during an internal audit in June 2025. Each one represented exposure for a failure-to-withdraw penalty. Nobody on the team knew the withdrawals had to be filed separately.

Other patterns that keep showing up: missing container stuffing locations on LCL shipments (the overseas consolidator never sends the address, and brokers we work with put the gap at 15-20% of LCL filings) and trading companies listed as manufacturers instead of actual factories.

We watched a mid-size apparel importer in New Jersey accumulate $35,000 in ISF penalties between September 2025 and February 2026. Not negligence. One data entry pattern. Their freight forwarder used the NVOCC's master bill on every submission instead of the house bill. Every filing showed as accepted. CBP couldn't match any of them to AMS. A port audit in March 2026 surfaced the whole pattern at once.

ISF Software and Automation for High-Volume Importers

Once an importer passes 20-30 ocean containers per month, manual ISF filing stops being viable. At that volume, the same errors recur every week. Transposed Bill of Lading numbers, outdated HTS codes copy-pasted from last month's shipments. Missing stuffing location data that nobody chased. Each error sits in ACE as a potential $5,000 hit. Compliance automation exists to catch these before submission.

Good customs filing software connects directly to ACE, pulls Bill of Lading data from carrier EDI feeds, checks HTS codes against classification records, and blocks filings that are incomplete. That pre-send validation alone eliminates the most common penalty triggers before they reach CBP.

Standalone ISF tools work for importers who only need filing automation. For operations that also handle entry filing, duty calc, and bond tracking, bundled customs entry software or customs management software makes more sense. Volume decides the architecture. An importer pulling from 3 Chinese suppliers has different import management software needs than one working 15 manufacturers across 8 countries.

Where we see money wasted: paying $30-$50 per filing to an ISF service provider at 100 filings/month. That's $3,000-$5,000 monthly on ISF alone. An annual ISF solution with a direct CBP application interface often runs less than half that. At scale, per-filing pricing makes no financial sense.

But no software fixes bad upstream data. If the overseas supplier sends the wrong manufacturer address, or the freight forwarder provides an incomplete Bill of Lading, the filing goes to CBP with those errors baked in. Lenzo sits upstream of the filing step: it checks product classification against HTS codes, screens trade partners, and flags regulatory obligations before the data reaches your customs compliance platform. Pairing Lenzo with your importer security filing stack means the data going into ACE has already been validated at the source.

ISF records need 5-year retention for CBP audit purposes. Any ISF software selection has to handle long-term archival and search across importer number, date range, and port of entry. During a focused assessment, CBP auditors will request complete ISF filing histories going back several years. Pulling those records from email chains and broker correspondence burns weeks of staff time. A proper system returns them in minutes.

FAQ

Does ISF apply to air freight shipments entering the United States?

No. ISF covers containerized ocean cargo only, per 19 CFR 149. Air freight falls under a separate program, the Air Cargo Advance Screening (ACAS), with different data requirements and its own enforcement framework.

Can an importer file ISF without a customs broker?

Yes, through CBP's ACE portal with compatible customs filing software. Self-filers carry the same $5,000 liquidated damages exposure per error as broker-filed submissions. Below 10 monthly shipments, self-filing is feasible. Above that, error rates on manual submissions climb fast enough that broker fees pay for themselves.

What happens if ISF data changes after filing?

Amendments are allowed before the vessel reaches the first U.S. port. After arrival, corrections get harder and the original inaccuracy can still trigger a penalty. Self-reporting errors before CBP finds them produces better mitigation outcomes.

Is a separate bond required for ISF filing?

A customs bond must be in place before filing. Continuous bonds (annual, starting at $50,000) usually cover ISF already. Without one, you'll need a single-entry bond or standalone ISF bond per shipment, each guaranteeing up to $10,000 in potential penalties.

CBP's localized enforcement authority, granted to individual ports in 2025, changed the math on ISF filing. The $5,000 notices no longer come from headquarters after a multi-month review process. They come from the local port, within 90 days, with no preliminary warning. The actual filing takes minutes when the systems work. Getting clean data from your overseas suppliers, carriers, and consolidators before those minutes start, that part takes discipline.