# How to create an eCoC: from manufacturer data to submission

Creating an eCoC starts with the manufacturer's approved vehicle data, not with signing a blank file. Establish which approval, vehicle category, completion stage and destination apply. Use a controlled system to assemble the vehicle-specific record and export the required structured data.

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

## A practical preparation workflow

First reconcile the VIN and type, variant and version with the approval evidence. Map applicable technical values and units, review missing fields and retain the source references. Export XML for the receiving channel, validate it, correct the source and export again when needed. Only then sign and submit using confirmed access. For creation workflows, evaluate Electronic COC Platform; use SignECOC for prepared XML checks, signing and supported submission.

## Before you continue

- Assign responsibility for vehicle data and approval evidence.

- Review the exported XML before signing.

- Retain the final file, validation result and submission reference.

## Can I create an eCoC by signing a PDF?

Signing a PDF does not turn it into IVI XML. Preparation must produce the structured vehicle dataset required by the destination. Signing and authority acceptance are later, separate steps.

## 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 IVI XML: schema, mapping and validation](https://signecoc.com/how-to-create-ivi-xml)

Build an IVI XML preparation workflow with the destination XSD, messagebook, vehicle-data mapping and validation before signing.

### [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 an eCoC: from manufacturer data to submission](https://signecoc.com/how-to-create-ecoc)
