# How to create IVI XML: schema, mapping and validation

IVI means Initial Vehicle Information. To create IVI XML, map controlled vehicle data to the destination's message specification and serialize it as XML. Select the accepted schema and messagebook first; do not assume every EU or UK channel accepts an identical file.

[Check unsigned XML](https://signecoc.com/sign#signing-workspace) [Pricing](https://signecoc.com/pricing) 

## Map fields before generating XML

Create a mapping sheet with the source field, XML element, data type, unit, allowed values and applicability condition. Check VIN, approval references and repeated groups against the source record. Use an XML library to preserve namespaces and escaping; validate against the selected XSD and applicable business rules. Correct and re-export before signing. Keep schema version and validation evidence with each export.

## Before you continue

- Obtain the target XSD, messagebook and release notes.

- Check required fields, enumerations and conditional groups.

- Validate the unsigned export, then follow the required signing process.

## Can I rename Excel to XML or copy a sample file?

No. Renaming a file does not create the required structure. A sample can help understand the format, but vehicle-specific values and applicable rules still need review. SignECOC checks prepared XML; it does not generate it.

## Official references

- [EUCARIS — IVI](https://www.eucaris.net/services/ivi/)

- [EUCARIS — Implementation of IVI](https://www.eucaris.net/kb/implementation-of-ivi/)

- [VCA — Electronic Certificates of Conformity](https://www.vehicle-certification-agency.gov.uk/electronic-certificates-of-conformity-ecocs/)

Reviewed: October 19, 2026

[About us](https://signecoc.com/about) 

## Choose your XML step

### [Check unsigned XML](https://signecoc.com/sign#signing-workspace)

Not checked yet? Start with the manufacturer’s unsigned IVI XML and review the precheck result before signing.

### [Sign prepared XML](https://signecoc.com/sign#signing-workspace)

Ready to sign? Use the unsigned IVI XML and your organisation’s certificate after resolving blocking precheck messages.

### [Check and submit signed XML](https://signecoc.com/sign#signed-xml-submission)

Already signed? Keep the original signed XML intact. Check its signature and use the submission area without signing it again.

€0.99 per vehicle covers one IVI XML signature and one supported submission attempt. Review pricing and payment availability before continuing. [Pricing](https://signecoc.com/pricing) 

Need to create the XML or manage type approvals? Prepare your manufacturer data in Electronic COC Platform, then bring the exported IVI XML to SignECOC for checking, signing and supported submission. [Electronic COC Platform](https://electroniccoc.eu/) 

## Related guides

### [What is an eCoC? Electronic Certificate of Conformity explained](https://signecoc.com/what-is-ecoc)

Understand eCoC, paper CoC, IVI XML and vehicle registration. Find the right next step for preparing, checking and signing vehicle conformity data.

### [How to create an eCoC: from manufacturer data to submission](https://signecoc.com/how-to-create-ecoc)

Plan eCoC creation from type approval and vehicle records through IVI XML export, validation, signing and submission.

### [EUCARIS, eCoC and vehicle registration: how they connect](https://signecoc.com/eucaris-ecoc-registration)

Understand EUCARIS IVI exchange, national access points, eCoC submission and the separate national registration process.

### [IVI XML validation errors: causes and fixes](https://signecoc.com/ivi-xml-validation-errors)

Troubleshoot IVI XML precheck errors: UTF-8, file structure, XSD, ICM and vehicle fields. Find the next step for each message before eCoC signing.

### [IVI 2.0 XML validation before eCoC signing](https://signecoc.com/validate-ivi-xml)

Check manufacturer-prepared IVI XML before signing. Understand schema checks, validation messages and the difference between a precheck and authority acceptance.

### [Validate signed eCoC XML before submission](https://signecoc.com/validate-signed-xml)

Check an existing eCoC XML signature before sending. Review signature structure, certificate information and cryptographic validation in SignECOC.

### [Submit an already signed eCoC XML](https://signecoc.com/submit-signed-xml)

Send existing signed IVI XML through a supported channel. Check your file, account access and destination, then track the submission result.

### [Prepare for UK VCA eCoC submission](https://signecoc.com/vca-ecoc-submission)

Plan a UK eCoC submission using the correct IVI XML and authorised channel. Check VCA documentation and SignECOC channel availability.

### [Prepare eCoC XML for the RDW submission route](https://signecoc.com/rdw-ecoc-submission)

Understand the preparation for RDW eCoC delivery: manufacturer access, IVI XML, signature checks and the distinction between test and production.

[SignECOC - How to create IVI XML: schema, mapping and validation](https://signecoc.com/how-to-create-ivi-xml)
