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 | What to check next |
|---|---|
| Signed XML verified | The signed XML passed the IVI root and XMLDSig verification checks. |
| Signed XML validation failed | 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. |
| Status unavailable | 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 | What to check next |
|---|---|
| XMLDSig Signature | No XML signature was found. Use the signing workspace for unsigned IVI XML. |
| XMLDSig Signature × 1 | The XML must contain exactly one XMLDSig Signature element. Check how the signed file was generated; do not add or remove signatures manually. |
| InitialVehicleInformation / Signature | 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. |
| X509Certificate | 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. |
| Reference URI="" | 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. |
| Cryptographic verification failed | 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.