ICS2 EORI and UUM&DS Access: What Should a Foreign NVOCC Decide Before Filing?

Direct Answer

A foreign NVOCC should review its EORI and UUM&DS access model before starting ICS2 ENS filing.

If the company wants to submit ENS filings through the Shared Trader Portal or connect directly to ICS2, it should understand whether it needs its own EORI, UUM&DS access, system roles, certificates, and testing process.

If the company uses an IT Service Provider, the provider may act as the technical Sender, but the economic operator may still remain the Declarant for the ENS filing.

The European Commission states that economic operators connecting to ICS2 must obtain an EORI number from an EU Member State customs authority, develop the necessary IT and business processes, and complete mandatory self-conformance testing where applicable. It also states that ENS filings can be submitted through the Shared Trader Portal and that access requires registration in the national or central UUM&DS system.

Why This Is a Service Decision

Many foreign NVOCCs first ask:

“Can we file ICS2?”

A better question is:

“Which access model should we use, and who is responsible for each role?”

ICS2 access may involve:

• EORI number
• UUM&DS access
• Shared Trader Portal
• Shared Trader Interface
• IT Service Provider
• Sender role
• Declarant role
• Digital certificates
• Self-conformance testing
• ENS data responsibility
• Referral response workflow

If these are not clarified before filing, the company may choose a service model that does not match its operational capacity.

Option 1: Use the Company’s Own Access

A foreign NVOCC may consider using its own access when it wants stronger filing control.

This may involve using the Shared Trader Portal or connecting directly through the Shared Trader Interface, depending on the company’s technical capability and filing volume.

This option may be suitable when:

• The company has recurring EU-bound shipments
• The company controls house-level data
• The company wants direct visibility over ENS filings
• The company has internal compliance staff
• The company has technical support
• The company can manage UUM&DS access
• The company can handle certificates and testing
• The company wants long-term filing independence

The European Commission states that economic operators may develop their own IT system and connect directly to ICS2 via the Shared Trader Interface, but mandatory self-conformance testing must be completed before go-live.

Option 2: Use an IT Service Provider

An IT Service Provider model may be more practical for many foreign NVOCCs.

This option may be suitable when:

• The company is new to ICS2
• Internal IT resources are limited
• EU shipment volume is still moderate
• The company needs faster setup
• The company wants managed filing support
• The company does not want to build its own system
• The company needs help with data validation and exception handling
• The company wants to focus on operations instead of system maintenance

The European Commission states that economic operators can meet ICS2 ENS data filing obligations either by developing their own IT system or by using the services of an IT Service Provider.

Sender Role vs. Declarant Role

This distinction is important.

The European Commission FAQ explains that the Sender is the system actor that technically constructs and exchanges messages with the Shared Trader Interface. It also explains that when an economic operator uses an IT Service Provider, the ITSP holds the Sender role and registers a certificate with its own EORI number, while the economic operator still holds the Declarant role and should use its own EORI number for the ENS filing.

In practical terms, using an ITSP does not mean the NVOCC can ignore its own filing identity or data responsibility.

The provider may handle technical exchange, but the NVOCC still needs accurate business data and clear internal ownership.

Option 3: Use Shared Trader Portal for Lower-Volume Filing

The Shared Trader Portal may be suitable for lower-volume users or companies that do not need full system-to-system integration.

This model may fit companies that:

• File occasionally
• Do not have internal IT resources
• Need portal-based access
• Want manual control over filing
• Have manageable shipment volume
• Can train staff for portal use
• Do not need API-style integration

However, portal use still requires access preparation and process control. It does not remove the need for accurate ENS data, response handling, and internal responsibility.

Decision Table

Factor 1: Filing Volume

Filing volume is the first decision point.

Low-volume filers may not need direct technical connection.

Medium-volume filers may benefit from ITSP support.

High-volume NVOCCs may review whether direct connection or a deeper system integration is worth the investment.

Factor 2: Internal IT Capability

Direct access requires more than filing knowledge.

The company may need to manage:

• System access
• Certificates
• Message exchange
• Testing
• User roles
• Error handling
• Security settings
• System maintenance
• Business continuity

If the company cannot support these items, an ITSP model may be more practical.

Factor 3: Data Responsibility

Even if a provider handles technical filing, the NVOCC still needs to control the source data.

The company should decide who verifies:

• Shipper information
• Consignee information
• Goods description
• HS code
• Transport document number
• Routing information
• EORI details
• House-level data
• Linking data
• Amendments and corrections

Technology can transmit data, but the company must still make sure the data is accurate and complete.

Factor 4: Access and Role Management

The access model should define:

• Who is the Sender
• Who is the Declarant
• Which EORI is used
• Who manages certificates
• Who receives notifications
• Who responds to customs referrals
• Who keeps filing records
• Who handles system incidents

If these roles are unclear, the company may face operational confusion after go-live.

Factor 5: Future Growth

A company may start with an ITSP or portal model and later review direct connection when EU volume grows.

This staged approach can work well.

The key is to choose a service model that fits today’s volume but does not block tomorrow’s growth.

Service Decision Checklist

Before choosing an ICS2 access model, ask:

1. Do we have an EORI number?
2. Do we need UUM&DS access?
3. Will we use the Shared Trader Portal?
4. Will we use an IT Service Provider?
5. Will we build our own system?
6. Who is the Sender?
7. Who is the Declarant?
8. Which EORI will be used for ENS filing?
9. Who manages digital certificates?
10. Who handles testing and go-live?
11. Who receives ICS2 notifications?
12. Who responds to referrals or filing errors?
13. Who stores ENS records?
14. Can this model support future volume growth?

Common Mistakes

Mistake 1: Treating ITSP Support as Full Responsibility Transfer

An ITSP may act as technical Sender, but the economic operator may still remain responsible for its ENS filing identity and business data.

Mistake 2: Ignoring EORI Preparation

ICS2 access and filing identity should be reviewed early.

Mistake 3: Choosing Direct Connection Without Testing Capacity

Direct connection requires technical readiness and mandatory self-conformance testing.

Mistake 4: Using the Portal Without a Workflow

Portal access is not enough. The company still needs data collection, validation, notification handling, and record storage.

Mistake 5: Not Defining Who Handles Referrals

ICS2 may generate risk-mitigating referrals. The filing model should define who responds.

FAQ

Does a foreign NVOCC need an EORI for ICS2?

If the company is acting as an economic operator in the ICS2 filing process, EORI and filing identity should be reviewed. The European Commission states that economic operators connecting to ICS2 must obtain an EORI number from an EU Member State customs authority.

Can an IT Service Provider file ICS2 ENS on behalf of a company?

Yes. The European Commission states that economic operators may use an IT Service Provider to meet ICS2 ENS filing obligations.

Does using an ITSP mean the company does not need its own EORI?

Not necessarily. The European Commission FAQ explains that when an economic operator uses ITSP services, the ITSP holds the Sender role, while the economic operator still holds the Declarant role and should use its own EORI number for the ENS filing.

Is the Shared Trader Portal enough for every NVOCC?

No. It may work for lower-volume filing, but high-volume or complex operations may need ITSP support or direct system integration.

What is the safest model for a first-time foreign NVOCC?

For many first-time filers, an ITSP-supported model is more practical because it reduces technical burden while allowing the company to build internal ICS2 experience.

Final Takeaway

ICS2 filing starts before data submission.

A foreign NVOCC should first decide how EORI, UUM&DS access, Sender role, Declarant role, portal use, ITSP support, and internal responsibility will work together.

The right access model should match filing volume, technical capability, data control, referral response needs, and long-term EU route strategy.

Navigator International supports logistics companies with ICS2 ENS filing coordination, EORI and access model review, ITSP-based filing support, house-level data review, multiple filing workflow support, data validation, and related EU manifest filing compliance services.