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 electronic seal does your eCoC workflow need?
Confirm the receiving authority’s requirements before choosing a certificate or signing service. The authorised entity, seal level, supported file format and operational controls must work together.
01
Do not assume a qualified seal is always mandatory
RDW’s current guidance specifies at least an advanced electronic seal under eIDAS; it permits a qualified seal but does not require one. Check the conditions for your receiving route instead of treating the strongest certificate label as a universal rule.
02
Confirm the entity and the signing arrangement
Record whose identity the certificate represents and who can authorise use. Ask the receiving operator and trust-service provider to confirm the required seal level, certificate profile, signed payload and supported XML packaging before purchase or implementation.
03
Sign the reviewed version and preserve its evidence
The file released by the manufacturer must be the file used in the signing and delivery process. Establish controls for corrections after signing, certificate expiry, access changes and recovery from service failures.
- Identify the entity, authorised operators and certificate owner.
- Verify the exact XML and signing format with the receiver.
- Test a signed sample through the agreed validation route.
- Retain the signed version and its submission response.
04
Include signing in the implementation demonstration
Use one representative vehicle to show how source data reaches the reviewed file and how that version is handed to signing. The provider arrangement and receiving interface need their own verification. Electronic COC does not issue trust-service certificates or replace the receiving authority’s checks.
Questions and answers
Should we buy a Qualified Electronic Seal immediately?
First confirm the receiver’s requirements and the provider’s support for the actual payload and workflow. A qualified certificate alone does not prove that the receiving system will accept the submitted file.
Does a signed XML file guarantee acceptance?
No. Data quality, the required structure, signing conditions and the receiving system’s checks are separate parts of the process. Retain and review the actual submission outcome.
Official references
Reviewed . Requirements are defined by the linked authorities and service documentation.
- RDW: digital CoC requirements
Dutch registration scope, production dates, national small series, IVI 2.0 and electronic seals.
- EUCARIS: implementation of IVI
Manufacturer submission choices, the IVI exchange model and the Article 37 timetable.
Continue through the eCoC workflow
Which NAP can your manufacturing team use?
Choose an eCoC National Access Point and plan manufacturer onboarding, validation, signing, submission responses and corrections. Keep UK VCA delivery separate.
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.
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