ISF Filing Deadline: The 24-Hour Rule, Late Filings, and Penalties

Key Points

• For most ocean cargo (ISF-10), the filing must be transmitted to CBP no later than 24 hours before the shipment is laden aboard the vessel at the foreign port.
• A late, inaccurate, incomplete, or non-matching ISF can trigger liquidated damages of $5,000 per violation, capped at $10,000 per ISF transaction, assessed against the importer security filing bond under 19 CFR part 113.
• Flexible ISF data elements must be finalized no later than 24 hours before the vessel arrives at the first U.S. port of unlading, even if the initial filing was on time.
• CBP may issue a cargo hold, a do-not-load message, or order a physical examination when an ISF is missing, late, or inaccurate; these operational consequences can delay cargo regardless of whether a penalty is ultimately assessed.
• A first-time violation may be mitigated through a petition filed with the port director, and factors such as the filer's compliance history and whether CBP cargo security was compromised weigh heavily in the outcome.

On this page

1. What the ISF filing deadline rule requires
2. ISF-5 and special in-bond cargo deadlines
3. The duty to update, finalize, and withdraw
4. Liquidated damages: how they are assessed
5. Operational consequences: holds, exams, and do-not-load messages
6. Mitigation: the petition process and key factors
7. What importers should do
8. Key references

The ISF filing deadline under 19 CFR part 149 requires that an Importer Security Filing be transmitted to CBP no later than 24 hours before cargo is laden at the foreign port. Missing that window, or submitting an ISF that is inaccurate or does not match the bill of lading, exposes the filer's bond to liquidated damages of up to $10,000 per ISF transaction. The rules also impose ongoing obligations to update data as shipment details firm up and to withdraw a filing if cargo will not arrive.

The links in this article go to the primary documents: the regulations, CBP guidance pages, and official statutes themselves. Read the source. For a full breakdown of the ten importer data elements and two carrier data elements that make up an ISF-10, see the companion article ISF Filing Explained: 10+2 Elements, Deadlines, and Who Files.

What the ISF filing deadline rule requires

19 CFR part 149 establishes the Importer Security Filing program, which applies to cargo arriving in the United States by vessel. The core deadline for a standard ISF-10 shipment is straightforward: the filing must reach CBP no later than 24 hours before the shipment is laden aboard the vessel at the foreign port. "Lading" means the physical loading of the container or break-bulk cargo onto the ship, not departure.

Why the lading clock matters

Many filers confuse the ISF deadline with the vessel departure or arrival time. The obligation runs backward from the moment cargo is placed on the ship. If a vessel departs a foreign port at noon local time, and loading begins at 6 a.m. the ISF must have been on file with CBP before 6 a.m. the day prior. Waiting until departure or sailing notice is already too late.

ISF-5 and special in-bond cargo deadlines

Not all ocean shipments use the ISF-10 form. 19 CFR part 149 carves out a separate, simplified filing called the ISF-5 for two distinct cargo categories:

• Foreign Cargo Remaining on Board (FROB): Cargo that transits a U.S. port but is not destined for the United States. An ISF-5 for FROB must be filed any time before the cargo is laden at the foreign port. There is no 24-hour advance requirement for FROB, making it more flexible than an ISF-10.
• Immediate Exportation (IE) and Transportation and Exportation (T&E) in-bond cargo: An ISF-5 for IE and T&E movements must be filed no later than 24 hours before lading at the foreign port, the same timing standard that applies to ISF-10 shipments.

Choosing the wrong ISF type, or filing an ISF-5 when an ISF-10 is required, is itself treated as an inaccurate or incomplete filing and can trigger liquidated damages.

The duty to update, finalize, and withdraw

The ISF obligation does not end once the initial filing is submitted. 19 CFR part 149 imposes three ongoing duties:

1. Update as soon as more accurate information is known

If any ISF data element changes after the initial filing, the filer must update the record as soon as the more accurate or precise information becomes available. Waiting until a routine review before arrival is not compliant if the filer already possesses corrected data.

2. Finalize flexible elements no later than 24 hours before first U.S. port arrival

Certain data elements of the ISF-10 are designated as "flexible" because they may not be fully known at the time of the initial 24-hours-before-lading filing. These flexible elements must be finalized, meaning updated to their final accurate values, no later than 24 hours before the vessel arrives at the first U.S. port of unlading. An ISF that carries placeholder or estimated data past that point is non-compliant, even if it was filed on time originally.

3. Withdraw if cargo will not arrive

If a shipment is cancelled, diverted, or otherwise will not enter the United States, the ISF must be withdrawn. Leaving an open ISF on file for cargo that will not arrive creates a record mismatch and can result in a violation finding.

Liquidated damages: how they are assessed

ISF violations do not produce traditional customs penalties under the fraud or negligence framework. Instead, CBP assesses liquidated damages against the bond that secures the ISF obligation. Under the bond conditions in 19 CFR part 113, liquidated damages may be assessed for any of the following:

• A late ISF filing
• An inaccurate or incomplete ISF
• A failure to update the ISF when better information is available
• A failure to withdraw an ISF when cargo will not arrive
• An ISF that does not match the bill of lading

The $5,000 per violation cap at $10,000 per transaction

Each qualifying violation carries a liquidated damages exposure of $5,000. Because a single ISF transaction can produce more than one violation (for example, a late filing combined with a bill-of-lading mismatch), CBP caps the total liquidated damages at $10,000 per ISF transaction. This cap means two or more violations arising from the same ISF filing will not stack beyond $10,000 in damages, but each separate shipment is its own transaction with its own cap.

The liquidated damages are assessed against the bond, not directly against an importer's cash account. However, the surety will seek recovery from the bond principal, and repeated violations can affect bond capacity and surety relationships over time.

Operational consequences: holds, exams, and do-not-load messages

Liquidated damages are the financial consequence of an ISF violation, but the immediate operational consequence can be more disruptive. When CBP's automated targeting systems flag a missing or non-compliant ISF, the agency has several enforcement tools:

• Do-not-load (DNL) message: CBP can direct the carrier not to load a specific container at the foreign port. The cargo stays behind while the vessel sails, causing delays of days or weeks until the next available sailing.
• Cargo hold: If the shipment has already been laden and is in transit, CBP can place an intensive examination hold that prevents the cargo from being released at the U.S. port until the ISF issue is resolved and any required examination is completed.
• Physical examination: A non-compliant or missing ISF increases the probability that CBP will order a full examination of the container, including unloading and re-stuffing costs that fall to the importer.

These operational consequences apply independently of any liquidated damages proceeding. CBP can release a hold after an ISF is corrected or filed, but the delay costs, storage fees, and demurrage charges are not refundable by CBP.

Mitigation: the petition process and key factors

A liquidated damages claim is not necessarily the final word. CBP maintains published mitigation guidelines for ISF violations, and filers have the right to petition for mitigation or cancellation of a claim.

Filing the petition

A petition for mitigation is filed with the port director at the port where the violation was identified. The petition must be submitted within the timeframe specified in the liquidated damages notice. Missing the petition deadline forfeits the right to seek mitigation for that claim.

Factors CBP weighs

CBP's ISF mitigation guidelines identify several factors that can work in a petitioner's favor or against them:

• Compliance history: A first-time ISF violation is more likely to receive favorable mitigation than a pattern of repeated late or inaccurate filings. CBP looks at the filer's overall ISF track record, not just the single incident at issue.
• Whether cargo security was compromised: If the ISF deficiency meant CBP could not perform its risk assessment before lading, the agency treats that as a more serious violation than a technical error that did not affect targeting.
• Prompt correction: Filers who corrected the ISF quickly after discovering the deficiency, or who self-disclosed the issue, are generally in a better position than those who did not act until CBP contacted them.
• Circumstances beyond the filer's control: Documented carrier delays in providing bill-of-lading data, or system outages (such as those that can occasionally affect ACE), may support a mitigation argument when the filer acted promptly once data was available.

First violations and prior good record

CBP's guidelines recognize that a first violation with no prior history of ISF non-compliance may be mitigated, potentially to a significantly reduced amount or, in some cases, to cancellation. However, mitigation is not automatic, and the burden is on the petitioner to present the facts clearly and completely. Subsequent violations for the same type of deficiency receive progressively less favorable treatment.

What importers should do

• Build the 24-hour lading deadline into your supply chain workflow. Confirm with freight forwarders and carriers that booking confirmations trigger ISF preparation, not vessel departure notices. The lading clock, not the sailing clock, controls compliance.
• Monitor and update flexible elements before the 24-hours-before-arrival cutoff. Assign a responsible party to review open ISF records as each vessel approaches its first U.S. port and confirm that all flexible elements have been finalized with accurate data.
• Respond to liquidated damages notices immediately. Calculate the petition deadline from the date of the notice and prepare a factual record documenting compliance history, the cause of the deficiency, and any corrective action taken. Missing the petition window eliminates the opportunity for mitigation.
• Track your ISF compliance rate over time. Because compliance history is a primary mitigation factor, importers and brokers who maintain records of on-time ISF filings across their shipment portfolio have documentation to support future mitigation petitions if a violation occurs.

Key references

• 19 CFR Part 149 -- The complete Importer Security Filing regulation, including deadlines, data requirements, update obligations, and enforcement authority.
• 19 CFR Part 113 -- CBP bond conditions under which ISF liquidated damages are assessed.
• CBP Importer Security Filing (10+2) page -- CBP's official program overview, including links to guidance documents and the ISF mitigation guidelines.
• Federal Register -- Search for "Importer Security Filing" to locate the original rulemaking and any subsequent amendments to 19 CFR part 149.
• ISF Filing Explained: 10+2 Elements, Deadlines, and Who Files -- Companion article covering the specific data elements required in an ISF-10 and ISF-5 filing.