Which eCoC date applies: 5 July or 29 November?
Understand the eCoC dates for EU legislation, Dutch registration and UK VCA submission. Check vehicle production date, approval scheme and destination.
Manufacturer readiness
Which NAP can your manufacturing team use?
Choose a receiving route that supports your manufacturer and vehicle scope, then complete its onboarding. A National Access Point provides the entry into the EU exchange; software access alone does not establish permission to submit.
01
Choose a NAP, then confirm access
EUCARIS explains that a manufacturer may choose a National Access Point in a Member State. Not every Member State must offer its own manufacturer-facing point. Confirm which service can accept your organisation and the records you intend to send.
02
Check an available route against your requirements
RDW states that its NAP is available for connection. Use the operator’s current onboarding process to confirm the manufacturer identity, test arrangements, applicable IVI profile, certificate requirements and production access. Availability is not evidence that a particular manufacturer has already been approved.
03
Make every submission traceable
Keep the signed file version and request reference with the receiving system’s response. Design the correction process before production rollout, including who investigates a rejection and when a record may be sent again.
- Confirm the receiving endpoint and manufacturer account.
- Test a valid record and a deliberately invalid sample.
- Distinguish transport receipt from validation and acceptance.
- Reconcile an uncertain timeout before repeating a transmission.
04
Keep the UK route separate
VCA provides a UK submission service with its own portal and API. Plan UK delivery and evidence separately from an EU NAP route, using the current VCA requirements for your approval scheme.
Questions and answers
Must we use a NAP in our home Member State?
The EUCARIS implementation guidance describes a manufacturer’s choice of NAP. The chosen operator’s access, testing and submission requirements still have to be met.
Does an HTTP success prove that the eCoC was accepted?
No. Interpret the receiving system’s documented response and retain the outcome for the exact submitted version. A transport-level success does not establish all later checks.
Official references
Reviewed . Requirements are defined by the linked authorities and service documentation.
- EUCARIS: implementation of IVI
Manufacturer submission choices, the IVI exchange model and the Article 37 timetable.
- RDW: digital CoC requirements
Dutch registration scope, production dates, national small series, IVI 2.0 and electronic seals.
- VCA: electronic Certificates of Conformity
UK guidance updated 2 October 2026: vehicle scope, approval schemes and submission arrangements.
Continue through the eCoC workflow
What is the right eCoC route for small-series manufacturers?
Separate EU small series, national small series and GB medium series before planning eCoC. Match approval scheme, destination and production workflow.
Which electronic seal does your eCoC workflow need?
Plan an eCoC electronic seal around the receiving authority’s requirements, authorised entity, certificate, XML format and tested signing workflow.
eCoC software for vehicle manufacturers
Manage vehicle data, IVI 2.0 XML validation, signing and submission preparation in one eCoC workflow. Explore the platform and request a manufacturer demo.
Review your route with one representative vehicle
Bring your approval scheme, vehicle category and target market. We will map the data, validation, signing and submission steps in a workflow demonstration.
Request a workflow demo