Manage UK eCoC, VCA electronic CoC, IVI 2.0 XML generation, XMLDSig signing workflows and UK vehicle compliance processes from one specialist platform.
Frequently asked questions
What is a UK electronic Certificate of Conformity?
A UK electronic Certificate of Conformity, often shortened to UK eCoC, is the digital form of conformity information that links a vehicle to its approved type, variant, version and technical configuration. Instead of treating the Certificate of Conformity as a paper document created at the end of production, an eCoC treats the certificate as structured data that can be generated, validated, signed and exchanged electronically. For manufacturers, this changes the operating model. Vehicle data, approval references, compliance checks and release evidence must be controlled before the final certificate package is created.
What is VCA in the UK eCoC context?
VCA is the UK Vehicle Certification Agency. In the UK vehicle approval environment, VCA is an important approval authority and source of guidance for manufacturers preparing electronic Certificate of Conformity processes. A manufacturer-side platform such as Electronic COC does not replace VCA or make authority decisions. Its role is to help teams keep approval references, vehicle data, IVI XML preparation, validation evidence and signing workflows organized before information is submitted through the relevant authority, portal, API or operational route.
What is IVI 2.0?
IVI 2.0 refers to structured Initial Vehicle Information used in modern electronic vehicle information exchange. For eCoC work, IVI 2.0 matters because it moves certificate-related information away from manually assembled documents and toward a structured XML data model. That model can carry vehicle identification details, approval information, technical attributes, manufacturer information, multi-stage references and release context in a machine-readable form. The business challenge is not only creating XML. It is keeping the source data complete, consistent and reviewable.
Is XMLDSig mandatory for every UK eCoC workflow?
Signing requirements depend on the applicable authority process, implementation route and regulatory context. XMLDSig is the common XML signature standard used when an XML document must carry digital signature evidence. For a manufacturer, the practical point is to prepare signing workflows early. The team should know which records are complete, who can approve release, which electronic seal or signing method applies, how signed files are archived and how corrections are handled after a signed XML package has been produced.
What is an eIDAS electronic seal?
An eIDAS electronic seal is a trust-service mechanism used by a legal entity to support authenticity and integrity for electronic data. In eCoC workflows, the seal is relevant because a certificate package may need to prove that it was issued by the correct organization and has not been altered after signing. Qualified and advanced electronic seals have different assurance levels and operational requirements. Electronic COC helps teams coordinate the workflow around signing readiness, but the trust-service relationship and legal acceptance requirements must be handled through the appropriate providers and authority rules.
What is the difference between a qualified and an advanced electronic seal?
An advanced electronic seal is designed to be linked to the creator, capable of identifying the creator and connected to the sealed data so changes can be detected. A qualified electronic seal adds a higher assurance level because it is created using a qualified seal creation device and supported by a qualified trust service provider under the eIDAS framework. In eCoC operations, the distinction matters because manufacturers must align signing workflows, provider setup, seal ownership and audit records with the level expected by the receiving process.
Can body builders and converters issue eCoCs?
Body builders, converters and other multi-stage vehicle manufacturers may have certificate responsibilities depending on their approval role, vehicle stage and regulatory position. The operational challenge is that a later-stage eCoC often depends on previous-stage approvals and inherited data. Electronic COC is designed to support this kind of manufacturer-side data control by keeping stage references, approval context, inherited values, version history and final-stage release checks visible in one workflow. It does not decide whether a specific organization is legally allowed to issue a certificate.
How are multi-stage vehicles handled in an eCoC process?
Multi-stage vehicles require careful handling because the final vehicle record may depend on data from an incomplete vehicle, a previous-stage manufacturer and one or more completion or conversion stages. The eCoC workflow needs to preserve previous-stage references, approval numbers, variant/version relationships and technical changes introduced at each stage. A good workflow should show which values are inherited, which values changed, which approval reference applies and which team owns the release review before an IVI XML or signed certificate package is generated.
What information is required for an eCoC?
The exact data set depends on the vehicle category, approval context and applicable certificate model, but manufacturer-side eCoC preparation usually involves vehicle identification, manufacturer identity, type approval references, variant and version data, production or completion information, technical attributes, emissions or mass data where relevant, stage information for multi-stage vehicles and release metadata. The data must be complete enough to support validation, IVI XML generation, signing workflows and later audit review.
How does IVI XML work in practice?
In practice, IVI XML is generated from structured source data rather than typed manually line by line. The manufacturer needs controlled records for approval data, vehicle attributes, stage references and release status. The XML generation step should therefore be the result of a reviewed data workflow. Validation checks should identify missing, inconsistent or incorrectly formatted information before the XML file is signed or submitted. This reduces late corrections and makes the certificate process easier to audit.
How are corrections managed after an eCoC record is created?
Corrections should be handled through a controlled change process. The team should know what changed, who approved the correction, whether the change affects the IVI XML output, whether a previous signed file must be superseded and whether a new release record is needed. For compliance managers, the important point is traceability. A correction should not become an undocumented overwrite of certificate data. It should remain connected to the vehicle record, approval context and audit trail.
Why is vehicle type approval important for UK eCoC?
Vehicle type approval is the legal and technical context that gives meaning to certificate data. An eCoC is not just a list of vehicle attributes. It connects a specific vehicle to an approved type, variant, version and manufacturer responsibility. If the approval reference is wrong or if variant/version information does not match the vehicle configuration, the certificate process can create compliance risk. That is why Electronic COC treats approval references as operational data that must stay visible during preparation and release.
Does Electronic COC integrate directly with VCA?
This page does not claim any unsupported direct VCA integration status. Electronic COC is positioned as a manufacturer-side compliance and eCoC preparation platform. It helps teams prepare vehicle data, approval references, IVI XML generation, validation workflows, signing readiness and audit evidence. Any portal, API or official submission path should be confirmed against the applicable VCA process, customer setup and agreed implementation scope.
How does ERP integration fit into UK eCoC work?
ERP integration can reduce duplicate entry when vehicle, production or configuration data already exists in internal systems. However, ERP data usually needs mapping, review and exception handling before it becomes certificate output. A practical UK eCoC rollout often starts with a controlled scope, confirms the data model, identifies validation gaps and then connects ERP or API flows where the source data is reliable enough. Integration should support compliance control, not bypass it.
Why should manufacturers start UK eCoC readiness before production pressure begins?
UK eCoC readiness requires more than a final export button. Teams need time to align approval references, vehicle data ownership, IVI XML structure, validation rules, signing responsibility, correction handling and audit evidence. If those decisions are delayed until the first live certificate run, the project can become a reactive technical exercise. Starting earlier lets homologation, compliance, IT and operations teams define the workflow before deadlines, volume and customer commitments create pressure.