An EU-valid eCoC file must not be assumed valid for UK VCA submission. UK IVI follows the EU IVI 2.0 structure but adds GB and UKNI approval options. The file must conform to VCA's UK XSD and enter the separate UK service. Manufacturers can reuse controlled source data, but should generate and validate the output for its actual destination.
This distinction affects OEMs, trailer manufacturers and body builders supplying both markets. Copying a finished XML file and changing a country code by hand creates a weak link between approval evidence, generated output and the document that is signed.
EU and UK requirements side by side
| Decision | EU context | UK VCA context |
|---|---|---|
| Schema | Applicable EU IVI package and receiving-route instructions | UK IVI XSD published by VCA |
| Approval authority options | Applicable EU approval codes | Additional g11 and n11 options for GB and UKNI information |
| Approval scheme values | Applicable EU enumerations | Additional GB and UKNI scheme options, including GBMED and UKNIESS |
| Representative information | Applicable EU approval context | VCA supplementary instructions for GB or EU/NI representatives |
| Submission | Selected NAP and EUCARIS exchange arrangements | Manufacturer VCA portal or API account |
| Acceptance evidence | Result associated with the EU submission | Result associated with the separate UK submission |
Understand the UK additions before mapping
VCA lists additions to restricted-value fields, including TypeApprovalCountryCode and TypeApprovalTypeCode. The authority-code choices include g11 and n11; the scheme options distinguish GB unlimited series, medium series, national small series and the corresponding UKNI contexts. These values are not interchangeable labels for the same approval.
VCA also publishes an eco-innovation option and guidance for EU-named elements retained in the UK structure. For example, the representative group needs the relevant GB-based or EU/NI-based representative according to the approval. Read the published guidance with the XSD rather than inferring meaning solely from an element's name.
Reuse source facts, not an unreviewed certificate
A sound design separates the manufacturer record from destination mapping. Maintain VIN, approval references, type/variant/version and applicable technical values in controlled sources. Then select the approval context and mapping appropriate to the output. Some facts may be shared; others need different approved references or applicability decisions.
Keep a mapping register with source, owner, revision, destination field and transformation. A GB approval code should not be inserted into an EU-only enumeration simply because it resembles an EU code. Equally, changing the authority code does not turn an EU approval into a GB approval.
Test the two outputs as separate artifacts
Use one representative vehicle configuration to exercise both mappings. Preserve each candidate with its schema package, source revision and intended destination. Review vehicle facts as well as XSD results. A schema pass cannot establish that the approval reference belongs to that configuration.
- Generate the EU candidate against the selected EU package.
- Generate the UK candidate against VCA's UK package.
- Introduce a UK-specific approval value and verify the expected schema behaviour.
- Review the representative and approval references in each candidate.
- Sign or seal the correct finalized candidate and retain its separate submission result.
These are recommended pilot checks, not claims that a particular authority will accept every synthetic test. Our IVI XML validation guide explains the distinction between structural validation and a manufacturer's factual review.
Keep EUCARIS and VCA connections distinct
VCA explicitly states that the UK system is not linked to EUCARIS. A successful UK submission does not place the record into the EU exchange network. Likewise, a NAP acknowledgement is not proof of UK submission. Name the route on each operation and make the response owner visible.
The VCA portal offers file upload and the API supports automated exchange. Production API access follows the required test process. Manufacturer account ownership remains important: VCA does not permit a third-party account to submit for multiple manufacturers. Integration support and the legal entity's account are different responsibilities.
Plan corrections and multi-stage work from the start
If a shared source value changes, determine which outputs are affected and regenerate only through the reviewed mappings. Preserve earlier submitted artifacts. An EU correction and a UK revision need their own route-specific handling; do not copy a successful status between them.
For multi-stage vehicles, obtain the actual earlier-stage data and use the applicable stage instructions. VCA's guidance explains that builders complete mandatory or applicable sections for their stage rather than assuming all previous-stage information must be consolidated into every field.
Digital CoC can organize the controlled vehicle record and the UK preparation workflow alongside EU-facing operations. Bring both approval contexts to a demonstration so the mapping, signing responsibilities and actual access arrangements can be reviewed with a real example.