# Validate signed eCoC XML before submission

An XML file containing a Signature element is not automatically a valid signed eCoC. Use the signed-file workflow to inspect the file, then sign in for the available server-side signature checks. Read any warnings before submission.

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

## Keep the signed file intact

Changing signed vehicle data can invalidate the signature. Use the original signed output and check the reported signature profile, certificate information and cryptographic result. Structural checks alone do not establish cryptographic validity. If data needs correction, return to the source system and produce a newly signed file.

## Signature validation

- Message or field: Signed XML verified — What to check next: The signed XML passed the IVI root and XMLDSig verification checks.
- Message or field: Signed XML validation failed — What to check next: The signed XML did not pass validation and cannot be submitted yet. Review the validation details. If corrections change the XML, sign the corrected file again before uploading it.
- Message or field: Status unavailable — What to check next: The signature check returned no recognised result. Submission is paused. Run the check again; if the problem continues, contact support.

## XMLDSig and XAdES

If you need support, describe the step and share the error code or a non-sensitive field name. Do not paste XML, vehicle identifiers, certificate files, passwords or PINs into the contact form.

- Message or field: XMLDSig Signature — What to check next: No XML signature was found. Use the signing workspace for unsigned IVI XML.
- Message or field: XMLDSig Signature × 1 — What to check next: The XML must contain exactly one XMLDSig Signature element. Check how the signed file was generated; do not add or remove signatures manually.
- Message or field: InitialVehicleInformation / Signature — What to check next: The signature is nested inside another XML element. Generate the signed XML again with the Signature element directly under InitialVehicleInformation; do not move an existing signature manually.
- Message or field: X509Certificate — What to check next: The certificate embedded in the signed XML could not be read. Check the signing certificate and generate the signed file again. Do not edit the embedded certificate manually.
- Message or field: Reference URI="" — What to check next: The signature does not reference the complete XML document. Check the signing settings and generate the signed file again; do not edit an existing signature manually.
- Message or field: Cryptographic verification failed — What to check next: The signature could not be verified against the XML content and its certificate. Do not submit this file. Check the original document and signing settings, then generate a new signed file without editing it afterwards.

## Before you continue

- Keep an unchanged copy of the signed XML.

- Review certificate, reference and signature-position messages.

- Resolve a failed signature check before attempting submission.

## Does SignECOC sign an already signed file again?

The signed-file submission flow is intended to check and send an existing signed file. It does not require a second signing step. Submission still depends on account permissions, credits and channel availability.

## Official references

- [EReg — IVI](https://www.ereg-association.eu/topic-groups/topic-group-xii)

Reviewed: October 2, 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.

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

### [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 - Validate signed eCoC XML before submission](https://signecoc.com/validate-signed-xml)
