UK eCoC in Practice: IVI XML, XAdES Signatures and the VCA Submission Routes
The IVI XML format
UK eCoCs build on the Initial Vehicle Information (IVI) file created for the EU eCoC system. The VCA has confirmed the UK XML file will sit very close to the EU IVI template, with small additions for GB-specific sections — for instance using g11 or n11 as approval authority codes, plus extra fields for GB regulatory references.
IVI files have to be in Extensible Markup Language (XML) — not PDF, not Word, nor anything else. XML is the chosen format because eCoCs are structured regulatory data that the VCA and other authorities need to pull out, validate and store automatically.
The IVI schema: what an eCoC contains
The IVI 2.0 schema holds hundreds of technical data fields, spanning:
Vehicle identity
VIN, type approval number, approval authority code, variant and version, and manufacturer details
Technical data
Masses, dimensions, axle configurations, engine specifications, emissions class and fuel type
Compliance data
Component type approvals, regulatory references, and stage-specific data for multi-stage builds
XAdES digital signatures
Every eCoC has to bear a digital signature that vouches for its authenticity and data integrity. The UK adopts the same standard as the EU — XAdES (XML Advanced Electronic Signatures), as set out in ETSI EN 319 132 and in line with the eIDAS Regulation.
The signature types allowed are:
- Advanced Electronic Signatures (AdES) — the baseline requirement
- Advanced Electronic Seals (AdESeal) — for signing at organisation level
- Qualified variants (QES, QESeal) — optional, but accepted
XML is sensitive to formatting
After an XML file has been digitally signed, any alteration at all — even a stray space or line break — will break the signature. It's a frequent cause of submission failures. Sign files as the last step before submission and leave them untouched thereafter.
XSD schema validation
Ahead of submission, IVI XML files are checked against the XSD (XML Schema Definition) to confirm their structure and content are correct. This automated step picks up issues like missing required fields, wrong data types and invalid values before the file ever reaches the VCA.
Validating up front is vital — files that fail the XSD check are rejected and have to be corrected and resubmitted.
The VCA submission routes
VCA eCoC Portal
A web-based interface for uploading IVI XML files by hand. A good fit for lower-volume manufacturers, or anyone in the early days of implementation.
API (system-to-system)
Automated transmission through the VCA API. It lets you integrate directly with production systems, ERP platforms and eCoC management software for high-volume workflows.
eCoC EU² takes on the technical complexity
eCoC EU² software hides the technical requirements away, so your team doesn't have to build XML generation, XAdES signing or VCA API integration in-house: