Secure signing workspace 

# Sign your prepared eCoC XML

Start with the unsigned IVI eCoC XML prepared by your organisation or its software provider. Check it, sign with your organisation’s certificate and continue to a supported submission channel.

Certificate control Private keys and token PINs remain under manufacturer control. 

Before signing, have your organisation’s certificate ready: use the Local Signer with a supported token or a temporary encrypted PFX/P12 session. The certificate must suit the destination. SignECOC does not issue certificates. Submission also requires an authorised account, available credits and a configured channel.

[Local Signer](https://signecoc.com/download-local-signer) 

Drop your IVI eCoC XML here  One manufacturer-prepared IVI XML file, up to 5 MB 

Waiting for an XML file  Upload an IVI eCoC XML file prepared by the manufacturer. 

- Upload

- Precheck

- Sign

- Credit

- Submit

- Result

## Need a signing certificate for eCoC?

Get guidance on qualified electronic seals under eIDAS for eCoC XML signing. A suitable certificate identifies your organisation when signing IVI XML before submission.

Certificate validity  Choose a validity period offered by the provider 

eIDAS trust services  Guidance on suitable trust service providers 

Qualified electronic seal  An electronic seal for your organisation 

Application support  Remote guidance during the application 

Availability and suitability depend on your organisation, the provider and the selected signing channel. 

Choose the right signing setup for your organisation. [Request certificate support](https://signecoc.com/support) 

## Already have a signed eCoC XML?

Upload your signed IVI XML for validation and submission through a supported EU NAP or UK channel. No new signature is needed.

- Submit without signing again

- One credit per submission attempt

- Server-side signature checks before submission

Upload signed XML  Signed IVI eCoC XML, up to 5 MB 

Submission channel 

Result email 

Waiting for signed XML  Upload signed IVI XML to check the existing signature and prepare submission. 

Credits required for submission  Each submission attempt for an already signed XML uses one credit. If you have no credits available, buy credits before submitting. 

## 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/) 

## [eCoC XML guides](https://signecoc.com/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.

### [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.

[eCoC XML Signing and Submission | SignECOC](https://signecoc.com/sign)
