VCA eCoC submission: a manufacturer readiness checklist
A UK submission project needs a defined vehicle scope, a controlled UK IVI candidate and an accountable manufacturer team. Prepare those together. An XML file, an account and an integration are separate deliverables, and none is a substitute for a recorded receiving-system outcome.
Confirm the current UK requirements
VCA's guidance applies mandatory eCoC submission from 29 November 2026 to newly manufactured M, N and O vehicles under the stated GB and UKNI schemes. GB medium series and UKNI EU small series are included; national small series are exempt. Check your exact scheme on the official page.
VCA provides portal and API routes. Submissions must conform to its UK IVI XSD and include a digital signature. API production access follows successful testing. Manufacturer account ownership matters: a third-party account cannot submit on behalf of multiple manufacturers. The UK service is not connected to EUCARIS and does not act as an EU NAP.
Assign owners before the first test
Name the manufacturer account owner, vehicle-data owner, homologation reviewer, integration contact and person who will handle rejected records. Put the escalation contact beside each responsibility. An external supplier can assist with implementation while the manufacturer retains the responsibilities applicable to its submission account and vehicle data.
Assemble one reviewable test package
- A representative vehicle record with its approval scheme and source revision.
- The UK schema package and guidance revision chosen for the test.
- The generated candidate, validation result and signing evidence.
- The selected test environment and authorized account context.
- The receiving response and a named owner for any correction.
For a portal-led process, rehearse how the operator selects the file and reconciles the result with the vehicle register. For an API-led process, rehearse error handling, delayed responses and candidate revision changes. Choose the route around daily volume, available support and exception handling, rather than automation for its own sake.
Rehearse a correction
Use a synthetic test in which the team discovers a source discrepancy before release. Stop the candidate, correct the owned source, regenerate and retain the earlier attempt. Then test how the implementation associates the later receiving response with the revised file. Agree the actual correction and versioning rules with the destination documentation; do not invent a local numbering convention and assume the receiver interprets it the same way.
Decide what is ready for production
Use an acceptance sheet listing evidence, reviewer and unresolved issue for each step. Account setup, successful test transmission, data review, signed-file verification and receiving acceptance should have separate entries. Keep a named operational contact and a written response to failed submissions before increasing volume. A general statement that the integration works is too vague for the team handling tomorrow's vehicles.
Where can Digital CoC help?
Discuss the preparation and tracking work around your representative vehicle. Confirm the UK-specific mapping, signing arrangement and external submission scope before the pilot. Use VCA's current publications as the authority for UK requirements and access instructions.