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.
UK submission planning
Prepare your UK vehicle data, XML review, signing and submission handover around the VCA’s current instructions. Electronic COC helps manufacturer teams define that workflow and its implementation scope. The manufacturer’s VCA account, integration tests and receiving outcomes must be verified for the actual project.
VCA’s guidance covers newly manufactured M, N and O vehicles from 29 November 2026 under the relevant GB and UKNI schemes. National small-series approvals are exempt; GB medium series and UKNI EU small series are included. Record the scheme and manufacture date for each workflow before selecting the delivery route.
The UK service uses a UK-adapted IVI 2.0 schema. Phase 1 launched on 17 June 2026. Submissions use the portal or API; production API access requires successful testing first. VCA prohibits third-party accounts submitting for multiple manufacturers. Confirm the current schema and account instructions in the official guidance linked below.
Use one representative vehicle to define the work before scaling up. The data team should be able to identify the inputs, the reviewer should know which version is ready and the operator should be able to find the submission result. This checklist is a project planning aid, not a statement that your account or integration has already been accepted.
VCA instructs manufacturers to apply digital signatures using the same method as for their EU counterparts. Confirm the intended file and signing arrangement against VCA’s current instructions. Retain the submitted XML version, the signing result and the portal or API outcome together. An upload or HTTP success alone does not establish the receiving outcome; investigate an unclear status before resubmitting.
VCA guidance: security, authenticity and submission of eCoC data
Agree who investigates a rejected file and who can authorise a corrected release. Include a missing-data example, a corrected record and a repeat-attempt scenario in the demonstration. Set a clear handover between the manufacturer’s operational team and the integration team so that an unclear response does not lead to uncontrolled resubmission.
No. VCA states that its UK system is not connected to EUCARIS. Plan the UK route separately from EU NAP delivery.
Assess the portal and API against your volume, source system and support capacity. Confirm account access and test prerequisites before deciding the production operating procedure.
No. This page describes preparation and project scoping. Approval of account access and the outcome of an actual submission come from VCA’s process and must be evidenced for your implementation.
Bring the approval scheme, vehicle categories, planned volume, source-data format, signing arrangement and current VCA account status. Use sanitised examples for an initial discussion.
Reviewed . Requirements are defined by the linked authorities and service documentation.
Official UK scope, dates, XML specifications, portal and API guidance; page updated 28 August 2026.
Manage vehicle data, IVI 2.0 XML validation, signing and submission preparation in one eCoC workflow. Explore the platform and request a manufacturer demo.
Plan IVI 2.0 XML validation around schema checks, vehicle data review and release decisions. Identify what must be corrected before signing and submission.
Connect eCoC XML signing to the reviewed vehicle record. Scope certificate ownership, signing API handovers, validation and submission evidence.
Share your approval scheme, source system and preferred submission method. We can scope the XML, signing and delivery handovers for your team.
Request a workflow demo