ISF Coordination in U.S. Route Service: Should a Foreign NVOCC Include It?

Direct Answer

A foreign NVOCC should consider including ISF coordination in its U.S. route service scope if customers expect integrated U.S. import support, if the company already manages AMS or HBL data, or if shipment delays often occur because importer, broker, and NVOCC data are not aligned.

However, ISF coordination should not be presented as the same thing as FMC qualification or AMS filing.

CBP explains that Importer Security Filing, commonly known as ISF or 10+2, is required for U.S.-bound ocean vessel shipments, and ISF importers or their agents must provide required data elements no later than 24 hours before the cargo is laden aboard the vessel destined to the United States.

Why This Is a Service Decision

A foreign NVOCC may not be the importer.

But it often controls or receives key shipment information, including:

• HBL number
• Shipper information
• Consignee information
• Notify party information
• Cargo description
• Container information
• Vessel and voyage details
• Loading port
• Destination information
• AMS-related data

Because ISF and AMS data must be consistent in practical operations, customers may expect the NVOCC to help coordinate information even if the importer or customs broker is responsible for filing.

Option 1: Include ISF Coordination

ISF coordination may be useful when the NVOCC wants to provide a more complete U.S. route service experience.

It may fit companies that:

• Serve many U.S. import customers
• Handle recurring U.S.-bound shipments
• Already coordinate AMS filing
• Issue their own HBL
• Work with customs brokers
• Serve importers who need data reminders
• Want fewer document mismatch problems
• Want better customer retention
• Want to provide one-window U.S. route support

This does not mean the NVOCC becomes the importer. It means the NVOCC helps coordinate data flow.

Option 2: Keep ISF Outside the Service Scope

This may be better when:

• Customers already have their own customs brokers
• Shipment volume is low
• The NVOCC only provides basic freight forwarding support
• The company does not handle importer-side data
• Internal staff cannot monitor ISF deadlines
• The company does not want additional filing-related responsibility
• The service scope is limited to FMC, bond, tariff, and AMS setup

This option is simpler, but the company should still explain what is excluded.

Decision Table

What ISF Coordination Should Include

A practical ISF coordination scope may include:

• Explaining required timing to customers
• Collecting data early
• Coordinating HBL number consistency
• Reminding importer or broker of cut-off
• Checking AMS and ISF data alignment
• Confirming who files ISF
• Confirming who handles amendments
• Storing communication records
• Escalating missing data before loading
• Separating AMS responsibility from ISF responsibility

The scope should be written clearly. “ISF support” should not be vague.

What ISF Coordination Should Not Mean

ISF coordination should not automatically mean:

• The NVOCC is the importer
• The NVOCC replaces the customs broker
• The NVOCC files every ISF directly
• FMC qualification includes ISF filing
• AMS filing and ISF filing are the same
• Cargo insurance is included
• Customs entry service is included

Under 19 CFR § 149.2, the ISF Importer or authorized agent must submit the required filing through a CBP-approved electronic interchange system within the required time.

Authorized Agent and Bond Considerations

If the company moves beyond coordination and becomes involved in actual ISF transmission, eligibility and bond requirements should be reviewed.

19 CFR § 149.5 addresses eligibility to file an Importer Security Filing and authorized agents. It also states that the ISF Importer must possess an appropriate bond, including options such as a basic importation and entry bond, basic custodial bond, international carrier bond, foreign trade zone operator bond, or importer security filing bond.

This is why ISF support should be scoped carefully. Coordination, filing support, and direct filing are not the same service.

Service Scope Questions to Ask

Before including ISF support, ask:

1. Are our customers asking for ISF assistance?
2. Do we issue the HBL?
3. Do we control AMS-related data?
4. Who is the ISF Importer?
5. Who is the customs broker?
6. Who will file ISF?
7. Who will handle amendments?
8. What data must we collect from customers?
9. What is our internal cut-off time?
10. Do we have a filing provider?
11. Is ISF included in the service fee or charged separately?
12. How do we limit confusion between AMS and ISF?

If these questions are unclear, start with ISF coordination instead of direct ISF filing.

Common Mistakes

Mistake 1: Confusing AMS and ISF

AMS and ISF are related in U.S.-bound ocean shipping, but they are different requirements with different responsible parties.

Mistake 2: Promising ISF Filing Without Defining Responsibility

The company should clarify whether it provides coordination, filing submission, or only data support.

Mistake 3: Waiting for Importer Data Too Late

ISF timing requires early data collection.

Mistake 4: Ignoring HBL Number Consistency

AMS and ISF data should be coordinated so that bill information can match correctly.

Mistake 5: Treating ISF as Part of FMC Qualification

FMC qualification does not automatically include ISF service.

FAQ

Should every foreign NVOCC include ISF coordination?

No. It depends on customer needs, shipment volume, data control, internal capability, and the company’s U.S. route service model.

Is ISF the same as AMS?

No. AMS is cargo manifest-related filing, while ISF is Importer Security Filing for U.S.-bound ocean cargo.

Who is responsible for ISF?

The ISF Importer or authorized agent is responsible for submitting the required filing through a CBP-approved system.

Can an NVOCC help with ISF?

Yes, an NVOCC may coordinate data, remind customers, align AMS and HBL information, or work with filing providers, depending on service scope.

Should ISF be included in an FMC service package?

Not automatically. It should be included only when the company’s U.S. route service model requires importer-side data coordination or filing support.

Final Takeaway

ISF coordination can improve U.S. route service quality, but it should be defined carefully.

A foreign NVOCC should include ISF coordination when customers need integrated U.S. import support and the company can manage data timing, broker communication, and AMS-ISF alignment.

If customers already manage ISF through their own customs brokers, the NVOCC may only need to provide timely and accurate shipment data.

Navigator International supports logistics companies with FMC qualification application, NVOCC bond handling, FMC filing coordination, SCAC code application, C3 bond handling, CBP filing, AMS account opening, independent ISF capability support, and related U.S. shipping compliance services.