# IVI XML validation errors: causes and fixes

A failed IVI XML precheck needs a specific diagnosis. Start with the message shown in SignECOC, identify the affected field or file requirement, and correct the export in the system that created it.

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

## Find the cause before exporting again

Keep the original file. Read the error code, rule and XML path where available. The tables below explain what each result means and where to investigate. SignECOC checks your file; it does not generate or repair manufacturer data.

## File checks before validation

- Message or field: UTF-8 — What to check next: This file could not be read as UTF-8 XML. Export the unsigned IVI XML again from your source system using UTF-8 encoding, then upload the new file. Renaming the file does not change its encoding.
- Message or field: Empty file or over 5 MB — What to check next: The XML file is empty or exceeds the allowed size. Choose a valid file within the upload limit.
- Message or field: XML cannot be read — What to check next: The file could not be parsed as XML. Export it again from the source system and upload the new file. If a signature is required, sign the newly exported file; do not edit an already signed file manually.
- Message or field: InitialVehicleInformation — What to check next: This file is not an IVI XML document with the required InitialVehicleInformation root element. Upload the correct IVI file.
- Message or field: DTD / ENTITY / xml-stylesheet — What to check next: DTD, entity declarations and XML stylesheet instructions are not allowed. Correct the source XML before uploading. If the file is already signed, generate a new signature after correcting it.
- Message or field: XMLDSig Signature — What to check next: This XML already contains an XMLDSig signature. Use the signed XML submission area instead.

## Read XSD, ICM and service results

- Message or field: XSD — What to check next: If the result reports an XSD issue, inspect the named element, its position and expected value format against the schema for your destination. Correct the export in your source system; changing a filename does not change the XML structure.
- Message or field: ICM — What to check next: An ICM message concerns a business-rule check. Read the rule name and affected field together, then compare the value with the vehicle and type-approval records. Do not invent a replacement value merely to clear the message.
- Message or field: XSD_ICM — What to check next: This label identifies schema and business-rule checks; read the pass/fail result and messages as well. SignECOC’s unsigned-file precheck does not validate the digital signature. Passing it does not prove authority acceptance or vehicle registration.
- Message or field: Validation service unavailable — What to check next: The validation service is currently unavailable. Your XML has not been confirmed valid or invalid. Try again later or contact support.

## Locate the reported vehicle field

Use the element name or XPath in the returned message to locate the field. The suggestions below explain where to verify a value; the provider’s original rule and message determine the reported issue.

- Message or field: VehicleIdentificationNumber — What to check next: Check the vehicle identification number (VIN) against the manufacturer’s vehicle record and the reported validation requirement.
- Message or field: TypeApprovalNumber — What to check next: Check the type-approval number against the vehicle’s applicable approval document and the reported validation requirement.
- Message or field: Type / Variant / Version — What to check next: Check the vehicle’s type, variant and version together against its applicable approval records. Confirm that the combination matches this vehicle before changing a value.
- Message or field: IviReferenceId — What to check next: Check the IVI reference in the document header against the reference assigned to this document. Review the provider’s reported requirement before changing it.

## Example: the wrong root element

```
HTTP 400
code: invalid_ivi_root
rootName: VehicleInformation
requiredRoot: InitialVehicleInformation
```

This synthetic example contains no vehicle data and is not an IVI template. The selected document has a different root name. Choose the manufacturer’s correct IVI export and run the checks again. Renaming the root alone does not supply missing vehicle data or make the document schema-valid.

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.

## Examples: validation results

```
POST /api/validation/eucaris

HTTP 200
{"validation":{"status":"passed","isValid":true,"validationLevel":"XSD_ICM","signatureValidated":false,"messages":[]}}

HTTP 200
{"validation":{"status":"failed","isValid":false,"validationLevel":"XSD"}}

HTTP 502
{"code":"eucaris_validation_unavailable"}
```

Synthetic, shortened responses from POST /api/validation/eucaris are shown below. A passed precheck does not verify a signature or establish authority acceptance. HTTP 502 with eucaris_validation_unavailable means no usable validation result was obtained; it does not mean the file is invalid.

## Before you continue

- Match the XML schema to the intended destination.

- Correct the source record, export again and repeat the check.

- Sign only after resolving blocking validation messages.

## Does a service error mean my XML is invalid?

No. If the validation service cannot return a usable result, the file’s validity is undetermined. Retry later; if the problem persists, contact support with the error code and time.

## Official references

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

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

Reviewed: September 30, 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 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 - IVI XML validation errors: causes and fixes](https://signecoc.com/ivi-xml-validation-errors)
