EUCARIS and NAP delivery: what a manufacturer must distinguish
EUCARIS describes a vehicle-information exchange environment, while national access arrangements and competent authorities govern the route relevant to a given market. A manufacturer's internal eCoC preparation, an XML validation pass and an official delivery acknowledgement are three different states. This guide maps the handoffs without claiming that Digital CoC is the official receiving system.
1. Define the destination
Record the intended market, competent authority, applicable IVI message/schema version and route for the approved vehicle category. Do not infer the route from a generic EU label. Ask who is permitted to submit and what evidence the receiving system returns.
2. Keep responsibilities visible
The manufacturer owns the correctness of the vehicle record and the preparation of its electronic CoC. The approval or access environment sets submission and onboarding requirements. Digital CoC can organize preparation and status, but official acceptance must be evidenced by the responsible external system.
3. Handle corrections as new controlled events
A changed vehicle fact or approval reference requires review of the candidate already prepared. Link each submission attempt and response to the exact file revision. A transport-level success only says an endpoint received a request; it does not prove content acceptance.
EU and UK are separate implementation contexts
EUCARIS documents IVI implementation choices. UK VCA publishes its own IVI XSD, supplementary requirements and portal/API guidance. Check the current receiving documentation and onboarding status for each destination before planning a live handoff.
Separate preparation from official delivery
A manufacturer prepares and checks the vehicle record and applicable IVI candidate. The competent authority or national access arrangement determines the accepted route and onboarding requirements. EUCARIS describes national access point and international exchange options, including retrieval and notification patterns; it does not make one universal submission endpoint available to every manufacturer.
A practical handoff sheet should name the intended market, receiving route, applicable message/schema version, authorized submitter, signing or sealing requirement, response owner and retry procedure. For a fictitious correction, retain the previous candidate and the new revision, then link any acknowledgement or rejection to the exact submitted version. Never equate a local HTTP success with authority acceptance.
UK VCA operates a separate eCoC service and publishes UK-specific IVI requirements and portal/API guidance. Confirm UK scope and timing on VCA's live page before using an EU process plan for UK submissions.