UK IVI output
Use the UK IVI XSD, including applicable GB and UKNI approval values. An EU XML file needs a UK-specific review before submission.
Bring UK IVI XML preparation, electronic signing and submission review into your manufacturer process. eCoC EU supports UK VCA workflow planning and delivery within an agreed scope, with UK account and testing requirements treated separately from EUCARIS.
Use the UK IVI XSD, including applicable GB and UKNI approval values. An EU XML file needs a UK-specific review before submission.
VCA offers portal and API submission. Access belongs to the manufacturer account and its authorised users; a shared third-party account for multiple manufacturers is not permitted.
API onboarding includes a successful test before production access. Treat test credentials and production release as separate steps.
VCA's guidance, updated 28 August 2026, sets 29 November 2026 for newly manufactured vehicles in the specified M, N and O approval schemes. Exemptions include national small-series schemes. Check the official guidance for your exact category and approval.
For your implementation review, identify who prepares vehicle data, who authorises release and who will handle returned errors. These responsibilities matter whether the team uploads files through a portal or uses an API.
A low-volume team may need a controlled way to prepare and review files, with a named person handling submission. A repeat-production program may need integration work connecting its existing data source with certificate preparation. Describe the actual volume and data flow before choosing the automation scope.
API data access is a different service from full ERP automation. The proposal should say which inputs are mapped, which actions remain with your team and how exceptions are reviewed. Evaluate one representative record before extending to more vehicle families.
Walk through a complete record and a record that requires correction. Ask the implementation team to explain where the operator sees the issue, which value should be reviewed and how the next submission is linked to the work already done.
Keep the generated output, signing outcome and submission response distinguishable in your acceptance checklist. A product demonstration explains the workflow; only the agreed route-specific testing establishes readiness for your production use.
Yes. Specify your UK vehicle program and current preparation process so the review can focus on UK IVI output and VCA workflow requirements.
Your vehicle category, approval scheme, approximate volume, current data source and whether you want operator-led preparation or an integration discussion.
No. Software scope, manufacturer access and authority testing are separate parts of the implementation. The proposal should make each responsibility explicit.
Source checked on . Consult the latest authority guidance for your implementation.
Use these resources to prepare your implementation discussion.
See the vehicle-data-to-submission workflow.
Understand the roles and route-specific trust requirements.
Separate included access from additional implementation work.
Set out vehicle volume, template and integration needs.