UK VCA eCoC compliance for vehicle manufacturers
Clear UK resource for VCA eCoC preparation, UK Certificate of Conformity data, IVI 2.0, IVI XML, XMLDSig, eIDAS seals and multi-stage vehicle workflows.
Who this UK eCoC page is for
A UK eCoC process is not just a replacement for a paper Certificate of Conformity. The practical task is to connect a vehicle to the correct approval reference, variant, version and technical data, then keep the XML, validation result, signing state and correction history explainable. ElectronicCoC is relevant where a manufacturer needs one controlled workflow for those steps instead of a document assembled from emails and spreadsheets. For a UK team, the important test is whether the certificate can be explained from the vehicle file without asking several departments to reconstruct the data trail. If the production record, approval file and final XML do not agree, the problem is a governance issue rather than a formatting issue. A practical UK eCoC workflow therefore needs clear source ownership, review states and correction rules before any submission route is considered.
IVI XML, signatures and corrections
IVI 2.0 gives structure to vehicle data, but XML alone does not prove that the data is correct. A reliable UK workflow separates source-data review, IVI XML generation, validation, digital signature preparation and final release. If a value changes after release, the team should create a controlled correction with a new version, not silently overwrite the record. Digital signing should come after that review, not before it. A signed XML file may prove integrity, but it does not fix a weak vehicle record. The release workflow should make the validation result, signing decision and archive version easy to find. That is the difference between an eCoC platform and a file exporter.
- Generate IVI XML from reviewed vehicle records.
- Validate mandatory fields and approval relationships before signing.
- Use XMLDSig and eIDAS concepts as part of a controlled trust workflow.
- Keep superseded XML files and correction reasons visible.
A practical UK preparation path
The best first step is a limited pilot with real vehicle data. Choose one approval family or one multi-stage scenario, map the source systems and define who owns each critical field before automation is expanded. A small pilot is usually enough to expose the real gaps. Use actual vehicles, not sample rows, and include at least one correction so the team can test whether the new version, old XML, approval context and audit evidence remain connected.
- Map UK approval references and vehicle categories.
- Define field ownership across homologation, production, quality and IT.
- Run validation before generating signed XML.
- Document correction, archive and release rules.
Built for
- Vehicle manufacturers
- Converters and body builders
- Homologation teams
- Compliance and technical managers
VCA and UK type approval context
VCA eCoC planning should start with the approval data, not the final file. Teams need to know which authority reference applies, which vehicle categories are in scope, how M, N or O category data is maintained and where multi-stage information enters the record. This page does not claim an unsupported integration status; it focuses on the manufacturer-side preparation layer. This also affects manufacturers that sell similar vehicles into EU and UK channels. The same VIN and technical attributes may sit close to each other, but market references, approval status and release evidence still need their own controls. Keeping those distinctions visible reduces the risk of treating a UK Certificate of Conformity as a copied EU output.
Frequently asked questions
What is a UK electronic Certificate of Conformity?
It is a manufacturer-controlled electronic record that connects a specific vehicle to the correct approval reference, technical configuration and release evidence. It should be treated as structured compliance data, not only as a digital document.
What role does VCA play?
VCA is the UK authority context manufacturers must consider for UK eCoC planning. ElectronicCoC supports manufacturer-side data preparation and workflow control; it does not replace VCA or a technical service.
What is IVI 2.0?
IVI 2.0 is a structured vehicle-information model used in electronic vehicle data exchange. It helps organise VIN, approval, technical and multi-stage data in XML.
Is XMLDSig enough on its own?
No. XMLDSig helps protect the integrity of signed XML, but the source data must be reviewed and validated before signing.
How are corrections handled?
Corrections should create a traceable new version showing what changed, why it changed, who approved it and whether XML or signing evidence was regenerated.
Can body builders use eCoC workflows?
Yes, when their approval role and process require controlled final-stage data. The workflow should preserve previous-stage references and changed values.
What data is usually needed?
Typical data includes VIN, manufacturer details, approval reference, extension, type, variant, version, masses, dimensions, bodywork, propulsion, emissions where relevant and multi-stage references.
Canonical page