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.

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 fieldWhat to check next
Signed XML verifiedThe signed XML passed the IVI root and XMLDSig verification checks.
Signed XML validation failedThe 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 unavailableThe 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 fieldWhat to check next
XMLDSig SignatureNo XML signature was found. Use the signing workspace for unsigned IVI XML.
XMLDSig Signature × 1The XML must contain exactly one XMLDSig Signature element. Check how the signed file was generated; do not add or remove signatures manually.
InitialVehicleInformation / SignatureThe 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.
X509CertificateThe 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 failedThe 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.

Choose your XML step

Check unsigned XML

Not checked yet? Start with the manufacturer’s unsigned IVI XML and review the precheck result before signing.

Sign prepared XML

Ready to sign? Use the unsigned IVI XML and your organisation’s certificate after resolving blocking precheck messages.

Check and submit signed XML

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

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