EUCARIS/NAP eCoC submission is the controlled process by which a manufacturer makes signed IVI data available through an accepted National Access Point. It is not a single public EUCARIS account that any company can open. The route depends on the granting authority, market, NAP onboarding, manufacturer permissions and integration method.
For data creation see the IVI 2.0 guide; for timing see the 29 November readiness guide.
What do IVI, EUCARIS and NAP mean?
- IVI is the structured conformity data model.
- EUCARIS supports secure exchange of vehicle and driver information between authorised parties, including the relevant eCoC use case.
- NAP is the national access route through which the manufacturer or authorised representative connects to the exchange process.
End-to-end submission flow
- Freeze the VIN and configuration event.
- Create IVI data from approval, ERP and production sources.
- Validate XSD, cross-field rules and homologation truth.
- Assign a traceable version.
- Apply the required digital signature or seal.
- Route to the correct NAP, portal or API.
- Record transport and authentication responses.
- Associate acceptance, warning or rejection with VIN and version.
- Correct the source, preserve the old version and resubmit.
- Retain file hash, signer, timestamp, target and response as an audit trail.
EUCARIS/NAP versus VCA
| Area | EU / EUCARIS–NAP | UK / VCA |
|---|---|---|
| Infrastructure | EUCARIS ecosystem through the selected NAP | VCA's own eCoC service |
| Connection | NAP-specific model | VCA portal or API |
| Format | EU IVI/XSD plus NAP guidance | EU-based UK IVI plus VCA rules |
| Access | Manufacturer/representation and NAP procedure | Manufacturer or authorised representative account |
| Key fact | No universal public EUCARIS account | VCA states its system is not linked to EUCARIS |
KBA or RDW EU routes and the VCA portal/API must therefore be treated as separate integration targets.
Questions when selecting a NAP
- Does the route fit the granting authority and target markets?
- How are manufacturer and authorised representative roles accepted?
- Are portal, batch and API options available?
- Which test evidence is required before production?
- Which signature, certificate and key-storage rules apply?
- How are response codes and resubmissions documented?
- What service levels, maintenance windows and support apply?
Why signing is a separate workstream
The legal entity, authorised user or service, private-key custody, certificate renewal and post-signature integrity must be controlled. A temporary test method may not satisfy production security and continuity requirements.
Rejection management
Separate connection/authentication, XML/XSD and data/business-rule failures. A homologation-scope problem cannot be solved by merely changing the field format. Every correction needs a source, owner and preserved audit trail.
Multi-route operation with Electronic COC Platform
The Electronic COC Platform lets a manufacturer manage different approval and market routes on a shared data and audit layer, applying destination-specific schemas and profiles while retaining VIN-level version and response history.
Choose the right route. Provide your granting authority, markets, categories and monthly eCoC volume through our route assessment form to request a demonstration.
Evidence required before production
One accepted test file is useful but is not sufficient evidence of operational readiness. The manufacturer should exercise acceptance, schema rejection, business-rule rejection, authorisation failure, correction and resubmission end to end. Timeouts, destination outage and certificate renewal also belong in the operating procedure.
| Evidence | What it proves | Owner |
|---|---|---|
| NAP/VCA acceptance | File and connection profile work at destination | Integration |
| Homologation validation report | Data is grounded in valid approval scope | Homologation |
| Signature verification | Integrity and signing authority | Security / authorised signer |
| Reject and correction record | Failure is traceable to its source | Operations |
| Recovery procedure | Records survive an interruption | IT and continuity |
Separating operational responsibility
Homologation owns content and approval scope; IT owns transfer, authentication and monitoring; security owns keys and certificates; operations owns queues and timely closure of rejects. Allowing one person to change, approve and submit records without independent control creates avoidable risk, particularly at volume.
A good platform does not remove these responsibilities. It makes them visible through roles, event history and recorded reasons for change.
EUCARIS/NAP and VCA eCoC process management — Explore Electronic COC for controlled management of multiple submission routes.
Frequently asked questions
Can any manufacturer open a direct EUCARIS account?
Access is established under the selected NAP, approval relationship and authorisation procedure.
Is VCA a EUCARIS NAP?
No. VCA explicitly states that the UK service is not linked to EUCARIS.
Portal or API?
A portal may fit low volume; an API usually fits sustained volume. Data quality and exception handling are as important as volume.
Official sources?
Use EUCARIS IVI guidance, Implementing Regulation (EU) 2024/1061, VCA guidance and the current documents of the selected NAP.
Summary
eCoC submission is more than an upload screen. A manufacturer must create and sign the correct IVI record, route it through an authorised NAP or the separate VCA service, classify technical and business responses, version corrections and retain an auditable event history. EUCARIS/NAP and the UK VCA route are distinct.
