Manifest Filing Knowledge Company News Industry Updates Bonds FAQ US FMC Bonds Knowledge Insurance Knowledge
ICS2 IT Service Provider or In-House System: Which Model Should a Foreign NVOCC Choose?
Direct Answer
A foreign NVOCC should consider an ICS2 IT Service Provider when it needs faster setup, lower technical burden, filing support, and a managed connection to ICS2.
A foreign NVOCC should consider an in-house ICS2 system when it has high EU shipment volume, structured internal data, technical resources, testing capability, and a long-term plan to control ENS filing directly.
The European Commission states that economic operators can meet ICS2 ENS filing obligations either by developing their own IT system or by using the services of an IT Service Provider. It also states that economic operators connecting directly to ICS2 through the Shared Trader Interface must complete mandatory self-conformance testing before going live.
Why This Is a Service Decision
ICS2 filing is both a compliance process and a system process.
The company must decide whether it wants to:
- Use a provider’s existing filing capability
- Develop and maintain its own system
- Use the Shared Trader Portal for lower-volume filing
- Connect through the Shared Trader Interface
- Build internal data validation
- Manage self-conformance testing
- Handle notifications and referrals internally
- Integrate ICS2 with its own operating system
This is not only an IT decision. It affects compliance, operations, cost, customer service, and scalability.
Option 1: Use an IT Service Provider
An IT Service Provider may be the practical choice for many foreign NVOCCs and freight forwarders.
This option may be suitable when:
- The company is new to ICS2.
- EU shipment volume is still moderate.
- Internal IT resources are limited.
- The company wants faster setup.
- The company needs filing support.
- The company wants to avoid building and testing its own system.
- The company needs help with data validation and exception handling.
- The company wants to focus on operations rather than system maintenance.
An ITSP model can reduce technical complexity, but the company should still define data responsibility clearly.
Option 2: Build an In-House ICS2 System
An in-house system may be suitable for larger or more system-driven NVOCCs.
This option may fit companies that:
- Have high EU route shipment volume
- Already run a TMS or operating platform
- Have structured shipment data
- Have internal IT resources
- Can complete testing and implementation
- Need API-style integration
- Want stronger data control
- Want long-term scalability
- Want to build direct ENS filing capability as part of a global compliance system
An in-house system can provide more control, but it requires technical investment and ongoing maintenance.
Option 3: Use the Shared Trader Portal
The European Commission states that ENS filings can be submitted through the Shared Trader Portal, and the sender must be registered in the national or central UUM&DS system to access and connect to the portal.
This may be suitable for lower-volume users or companies that are not ready for system-to-system integration.
However, portal use may be less efficient for high-volume filing or complex multi-branch operations.
Comparison Table
| Decision Point | IT Service Provider | In-House System | Shared Trader Portal |
|---|---|---|---|
| Best for | Fast setup and managed support | High-volume and system-driven operations | Lower-volume filing |
| Technical burden | Lower | Higher | Moderate |
| Testing responsibility | Provider may support | Company must manage | Portal access setup needed |
| Data control | Shared with provider | Stronger internal control | Manual or portal-based control |
| Scalability | Depends on provider | High if built well | Limited for high volume |
| Setup speed | Usually faster | Slower | Moderate |
| Internal IT need | Lower | High | Lower than direct system |
| Best use case | Most first-stage NVOCCs | Large operators | Occasional or lower-volume filers |
Decision Factor 1: Filing Volume
Volume is the first filter.
If the company handles only occasional EU-bound shipments, a portal or provider model may be enough.
If the company handles recurring EU route shipments, an ITSP may provide a balance of efficiency and support.
If the company handles high-volume filing across multiple branches, an in-house system may be worth reviewing.
Decision Factor 2: Internal IT Capability
An in-house system requires more than an idea.
The company needs:
- Technical development resources
- ICS2 message knowledge
- Testing capability
- System maintenance
- Error handling
- Notification management
- Security controls
- Business continuity planning
- Ongoing version and requirement updates
If the company lacks these resources, an ITSP model is usually safer.
Decision Factor 3: Data Control
Some NVOCCs want maximum control over house-level data.
An in-house system may provide stronger control.
However, an ITSP may also provide acceptable control if the contract, user permissions, data privacy policy, and account structure are clear.
Before choosing a provider, ask how data is stored, separated, accessed, and used.
Decision Factor 4: Testing and Go-Live Readiness
Direct connection to ICS2 requires mandatory self-conformance testing before go-live.
A company choosing an in-house system should be ready for:
- Test planning
- Message validation
- Error resolution
- Staff training
- Go-live coordination
- Support after launch
- Business continuity planning
If the company wants to avoid this technical burden, ITSP support may be more practical.
Decision Factor 5: Referral and Notification Handling
ICS2 risk analysis may generate referrals requesting additional information, screening, or other actions. Those referrals must be answered before risk assessment can resume.
The selected filing model should define:
- Who receives notifications
- Who monitors referrals
- Who contacts customers
- Who submits responses
- Who stores response records
- Who escalates unresolved cases
A filing system is not complete unless exception handling is operationally clear.
Service Decision Table
| Company Situation | Recommended Model |
| Low EU shipment volume | Shared Trader Portal or ITSP |
| First-time ICS2 user | ITSP |
| No internal IT team | ITSP |
| Medium recurring volume | ITSP or structured portal workflow |
| High volume and internal system maturity | In-house system review |
| Strong privacy and data control needs | ITSP with clear controls or in-house system |
| Need quick launch | ITSP |
| Need long-term global filing platform | In-house system may be worth reviewing |
| Complex multiple filing workflow | ITSP or in-house system with strong process |
Questions to Ask Before Choosing
- How many ICS2 filings do we expect monthly?
- Do we control house-level data?
- Do we need multiple filing support?
- Do we have an EORI number where needed?
- Do we already have UUM&DS access?
- Do we have internal IT resources?
- Can we complete self-conformance testing?
- Do we need portal, ITSP, or direct system connection?
- Who manages referrals and notifications?
- How is data privacy handled?
- Do we need multi-branch user permissions?
- What happens during system unavailability?
Common Mistakes
Mistake 1: Building In-House Too Early
An in-house system may be unnecessary if volume is low and requirements are still evolving internally.
Mistake 2: Choosing an ITSP Without Defining Data Responsibility
The provider may support filing, but the NVOCC still needs accurate source data and clear internal ownership.
Mistake 3: Ignoring Self-Conformance Testing
Direct system connection requires testing before go-live.
Mistake 4: Treating Portal Access as a Full Operating Workflow
Portal access may allow submission, but internal data collection, validation, and response handling still need procedures.
Mistake 5: Ignoring Referral Handling
ICS2 is not only submission. Risk analysis responses and follow-up actions must be managed.
FAQ
Can an economic operator use an IT Service Provider for ICS2?
Yes. The European Commission states that economic operators can use an IT Service Provider to meet ICS2 ENS filing obligations.
Can a company build its own ICS2 system?
Yes. Economic operators may develop their own IT system, but direct connection through the Shared Trader Interface requires mandatory self-conformance testing before go-live.
Is the Shared Trader Portal enough?
It may be enough for lower-volume users, but high-volume or complex NVOCC operations may need ITSP or system-to-system solutions.
Which model is best for a first-time foreign NVOCC?
An ITSP model is usually more practical because it reduces technical burden and helps the company start with a managed workflow.
Does the filing system replace data validation?
No. The system supports submission, but the company still needs accurate and complete data before filing.
Final Takeaway
The best ICS2 filing model depends on volume, system capability, data control, testing readiness, referral handling, and long-term EU route strategy.
Use an IT Service Provider if speed, support, and lower technical burden matter most.
Build an in-house system only when volume, resources, and system maturity justify it.
Use the Shared Trader Portal when filing needs are limited and manageable.
Navigator International supports logistics companies with ICS2 ENS filing coordination, ITSP-based filing support, house-level data review, multiple filing workflow support, data validation, and related EU manifest filing compliance services.
