ISF filing for non-resident importers: the 10+2 rules for ocean shipments of servers into the US
By Comex IOR Services · Published · Last updated · 14 min read

In this guide
- What is the ISF, and why does it apply before the ship even leaves?
- Who is the ISF importer when the seller is a foreign company?
- What goes into the 10+2 for a server shipment?
- What does the timeline look like for an ocean shipment of servers?
- Does a non-resident ISF importer need its own customs bond?
- Who actually transmits the filing, and what paperwork backs it?
- What happens if the ISF is late, wrong or missing?
- ISF filing for non-resident importers: how to set it up without a US entity
- Frequently asked questions
ISF filing for non-resident importers follows the same rules as for US companies: ten data elements must reach US Customs and Border Protection at least 24 hours before your servers are loaded abroad, backed by a US customs bond. A foreign company can be the ISF importer, but it needs a bond, a recognized importer number and a filer.
If you sell or ship servers into the United States by sea and you have no US entity, the Importer Security Filing is usually the first US obligation you hit, days or weeks before the container reaches Long Beach, Savannah or New York. It is also one of the easiest to get wrong, because it happens on the export side, at the foreign port, often while everyone is still focused on the sale. This guide explains who must file, what goes into the "10+2", how the bond works for a foreign company and how to set up the flow so a missing filing does not cost you 5,000 dollars per shipment or a container held on arrival.
What is the ISF, and why does it apply before the ship even leaves?
The Importer Security Filing is an advance cargo data requirement for goods arriving in the United States by vessel. CBP uses it to screen cargo before loading, so the deadline sits at the foreign port of lading, not at US arrival.
The rule is formally called Importer Security Filing and Additional Carrier Requirements. It was published by CBP in the Federal Register on November 25, 2008, and took effect on January 26, 2009. It is known as "10+2" because the importer side supplies ten data elements and the ocean carrier supplies two more: the vessel stow plan and container status messages. The regulations for the importer side are in 19 CFR Part 149.
The timing is what catches foreign sellers. Under 19 CFR 149.2, most elements must reach CBP no later than 24 hours before the cargo is laden aboard the vessel at the foreign port. For a rack of GPU servers leaving Kaohsiung or Rotterdam, that means the filing is due before the container is loaded, not when the ship approaches the US coast. The official overview is on CBP's Importer Security Filing 10+2 page, which also states that noncompliance can lead to monetary penalties, increased inspections and cargo delays.
One point that saves time for hardware companies: the ISF applies only to ocean cargo. Servers flown into the US do not need an ISF, because air cargo has its own advance data program, Air Cargo Advance Screening, which is handled by carriers and forwarders. The moment you switch a large order to sea freight to save on cost, the ISF comes into play.
Who is the ISF importer when the seller is a foreign company?
The ISF importer is the party causing the goods to arrive in a US port by vessel. For a regular import, that is the owner, purchaser or consignee of the goods, or an agent such as a licensed customs broker. A foreign company can hold that role.
The definition in 19 CFR 149.1 is about control of the shipment, not residency. If your company in Germany, Israel or Brazil sells servers on DDP terms and arranges the ocean freight, you are the party causing the goods to arrive, and the ISF responsibility is yours unless the contract clearly places it on the US buyer. If you sell FOB or EXW and the US buyer books the freight, the buyer is normally the ISF importer.
This is where many non-resident sellers create a gap. The sales team quotes delivered pricing, the forwarder at origin books the vessel, and nobody in the chain has a US bond or a filer agreement. The container gets loaded, the ISF is late or missing, and the problem only appears when the cargo arrives and CBP places a hold.
It also helps to separate three roles that are easy to blur. The ISF importer is responsible for the advance filing. The importer of record is the party liable for duties and the entry, and its number is one of the ten ISF elements. The licensed customs broker files the entry. In many shipments one company plays two or all three roles, but they do not have to be the same, and you should know who is who before the first booking. If the concept of the importer of record is new to you, our guide on what an Importer of Record is and when you need one covers the basics.
What goes into the 10+2 for a server shipment?
The importer side of the ISF has ten data elements: six due 24 hours before lading, two that can be filed later and two that relate to how the container was stuffed. For servers, the elements that cause trouble are the manufacturer, country of origin and HTS number.
19 CFR 149.3 lists the ten importer elements:
- Seller: the last known entity selling the goods.
- Buyer: the last known entity buying the goods.
- Importer of record number: the IRS number, EIN, SSN or CBP-assigned number of the party liable for duties.
- Consignee number: the number of the US party on whose account the goods are shipped.
- Manufacturer or supplier: the last entity that made or assembled the goods, or the supplier of finished goods.
- Ship-to party: the first party scheduled to receive the goods after customs release.
- Country of origin.
- Commodity HTSUS number, at least at the six-digit level.
- Container stuffing location.
- Consolidator, the party that stuffed the container or arranged the stuffing.
The regulation requires that the manufacturer, country of origin and HTS number be linked to each other at the line-item level. That matters for mixed loads. A container with GPU servers assembled in one country, switches made in another and power distribution units from a third needs a separate line for each combination, not one generic "computer equipment" line.
The HTS number has to reach at least six digits, and CBP allows up to ten. Use the same classification logic you will use on the entry. Our article on the HS code for servers explains how servers, GPU accelerators, switches and storage units usually split. Country of origin also needs care for servers: the assembly location is not always the origin CBP will accept, and that difference can change the tariffs on the entry.

What does the timeline look like for an ocean shipment of servers?
Six elements must be filed at least 24 hours before lading at the foreign port. The container stuffing location and the consolidator can follow later, but no later than 24 hours before arrival at the US port. Updates are allowed until the goods enter the limits of a US port.
The table below lays out who does what on a typical sea shipment of servers sold by a non-resident company.
| Step | Deadline under 19 CFR Part 149 | Who usually handles it | What the non-resident seller should provide |
|---|---|---|---|
| Seller, buyer, importer of record number, consignee number | No later than 24 hours before lading at the foreign port | ISF filer: customs broker or IOR acting for the ISF importer | Commercial invoice data and the US numbers of the parties |
| Manufacturer, ship-to party, country of origin, HTS number | 24 hours before lading; may be filed on best available data and updated | ISF filer | Line-level manufacturer, origin and classification for every model |
| Container stuffing location and consolidator | As early as possible, no later than 24 hours before US arrival | ISF filer, with data from the origin forwarder | Address where the servers were stuffed and the stuffing party |
| Updates to any element | Before the goods enter the limits of a US port | ISF filer | Changes to origin, consignee, ship-to or classification |
| Entry and entry summary | On or after arrival, under the importer of record | Licensed customs broker | Final invoice, packing list and supporting documents |
In practice, the 24-hour deadline before lading is earlier than it looks. Forwarders want the ISF confirmation before the container goes to the terminal, and terminals often cut off export cargo a day or more before the vessel loads. For a server order, the data should be ready when the booking is confirmed, not when the truck leaves the factory.
The four elements in the second row can be filed first on the best information you have and updated later, which helps when the final ship-to warehouse is not yet fixed. That flexibility has limits: the first filing still has to be on time, and the update has to happen before the goods enter a US port.

Does a non-resident ISF importer need its own customs bond?
Yes, an ISF importer must have a bond, but it does not always have to be its own. 19 CFR 149.5 accepts a basic importation and entry bond, an ISF bond and a few other bond types, and lets the filing agent post its own bond when the ISF importer has none.
For a foreign company, this rule opens three practical routes. The first is to obtain your own US bond, which also requires a resident agent and a CBP-assigned importer number if you have no IRS number. The second is to file as a single-shipment ISF importer under a dedicated ISF bond arranged through a broker. The third is to let a US-based importer of record and its broker handle the filing under their bond, as part of a full import service.
The bond is not a formality. The basic importation and entry bond conditions in 19 CFR 113.62 include compliance with the ISF rules, and a default makes the principal and surety jointly liable for liquidated damages of 5,000 dollars for each violation. Sureties look at that exposure before they write a bond for a foreign principal, and a claim can raise your premium or end the bond.
The environment for foreign importers has also become stricter. Executive Order 14411 of June 2026 directs CBP to tighten the rules for foreign importers of record, including their use of continuous bonds, so check the current status before you plan a year of shipments around a continuous bond in your own name. Our guide to the customs bond for non-resident importers explains how single and continuous bonds compare.
Who actually transmits the filing, and what paperwork backs it?
The ISF is transmitted electronically by a party that has set up the CBP communication protocol, usually a customs broker or a specialized filer. A foreign company rarely files directly, so the real question is who your filer is and what authority it holds.
Under 19 CFR 149.5, an authorized agent filing for an ISF importer must keep a power of attorney in English until it is revoked, keep revoked powers of attorney and revocation letters for five years, and show them to CBP on request. If you want the ISF and the entry to go in one electronic transmission, which speeds up release, the regulation limits that to an importer filing for itself or a licensed customs broker.
For a non-resident seller, a clean setup usually looks like this. The US buyer or your importer of record appoints one broker as the ISF filer and entry filer for the lane. The origin forwarder sends the stuffing location and consolidator data to that broker for every container. Your export team sends commercial invoice lines with model, manufacturer, origin and HTS number at the time of booking, not at departure.
The weak point is almost always data ownership. When the origin forwarder files the ISF on behalf of a party it has never spoken to, the importer of record number or the consignee number is often missing or wrong. A US filer that also handles the entry sees those inconsistencies before they become a violation.

What happens if the ISF is late, wrong or missing?
A late, inaccurate or missing ISF can lead to liquidated damages of 5,000 dollars per violation against the bond, more inspections and holds on the cargo. For high-value servers, the cost of a held container is often bigger than the claim itself.
The 5,000-dollar figure comes from the bond conditions in 19 CFR 113.62, so it falls on whoever holds the bond used for the filing. CBP can mitigate claims, and a first error with a reasonable explanation is treated differently from repeated late filings, but mitigation is a request, not a right.
The operational cost is harder to plan. A container of AI servers waiting for examination at a US port carries storage charges, delays your installation date and ties up hardware whose value drops every quarter. Inspections can also open crates that were sealed and tested at the factory, which some customers treat as a warranty or chain-of-custody issue. For buyers with project deadlines, a late ISF can turn into a contract dispute even if the claim is mitigated.
Mistakes are also more likely in some patterns we see often in hardware: split shipments where part of an order goes by air and part by sea, consolidated containers with several sellers, re-routed vessels and last-minute changes in the delivery warehouse. Each of these needs a filing update, and each needs one person who owns it.
ISF filing for non-resident importers: how to set it up without a US entity
The simplest route is to work with a US importer of record whose broker files both the ISF and the entry under a bond it already holds. You supply clean line-level data at booking, and the IOR carries the US obligations.
That setup fits companies that ship servers, storage or networking equipment to US customers a few times a year, or that are entering the market and do not want to open a US subsidiary, appoint a resident agent and obtain a bond just to make the first deliveries. It also keeps the advance filing, the customs value, the origin claim and the tariff treatment in the same hands, which matters now that origin and classification decide extra duties on many servers. Our guide to the Importer of Record USA explains the full set of obligations a foreign company takes on when it imports in its own name.
If you ship to the US every week, building your own structure with a bond, a resident agent and a dedicated broker may pay off later. Even then, the ISF data should come from the same master data your export team uses for invoices, so the filing and the entry tell the same story.
Before your next ocean booking, confirm four things: who the ISF importer is under your Incoterm, whose bond covers the filing, who transmits it and when, and whether the manufacturer, origin and HTS number for each model are ready at line level. If any answer is unclear, the container is not ready to load.
If you are planning sea shipments of servers or other high-value hardware and want the ISF, the entry and the bond handled by one accountable party, Comex IOR Services can act as your Importer of Record in the United States. Tell us what you are shipping, from where and on which Incoterm, and we will map the filing flow before the container reaches the port.
Frequently asked questions
Can a foreign company be the ISF importer?
Yes. Under 19 CFR 149.1, the ISF importer is the party causing the goods to arrive in a US port by vessel, such as the owner, purchaser or consignee. A foreign seller shipping on DDP terms is often that party, but it needs a bond and a filer to meet the obligation.
When is the ISF due for an ocean shipment of servers?
Most elements are due no later than 24 hours before the cargo is laden aboard the vessel at the foreign port. The container stuffing location and the consolidator can be sent later, but no later than 24 hours before arrival at the US port.
Do servers shipped by air need an ISF?
No. The Importer Security Filing applies only to cargo arriving by vessel. Air shipments are covered by a separate advance data program, Air Cargo Advance Screening, which carriers and forwarders handle.
What is the penalty for a late or missing ISF?
The bond conditions in 19 CFR 113.62 set liquidated damages of 5,000 dollars for each violation, and CBP can also hold or inspect the cargo. Claims can be mitigated, but the delay to a high-value server shipment is often the larger cost.
Does a non-resident ISF importer need its own customs bond?
It needs bond coverage, but 19 CFR 149.5 allows the filing agent to post its own bond when the ISF importer has none. Many foreign sellers rely on a single-shipment ISF bond or on the bond of a US Importer of Record.
Is the ISF importer the same as the importer of record?
Not necessarily. The ISF importer is responsible for the advance filing, while the importer of record is liable for duties and the entry. The importer of record number is one of the ten ISF data elements, so both parties must be known before the vessel loads.



