eCoC XML signing and submission
Bring the IVI eCoC XML prepared by your organisation or its software provider. Check the file, sign it with a certificate controlled by your organisation and submit through a supported EU or UK channel. Already signed? Use the signed XML submission area.
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 SignerUpload your IVI XML
Choose your file to reveal the next steps in order.
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
From IVI XML to eCoC submission in one workflow
Follow a clear sequence of checks, signing and submission steps.
Upload
Upload an IVI eCoC XML file prepared by the manufacturer.
Validate
Run automated XML and IVI checks before submission.
Sign
Sign the XML using your own signing certificate.
Submit
Send through a supported EU NAP or UK channel.
Track
Review validation results, submission status and processing responses.
Prepare your eCoC for electronic delivery
Check the IVI XML, apply the required signature and prepare submission through the appropriate channel in one workspace.
IVI XML validation
Check structure, formatting and required XML elements before submission.
Submission prechecks
Identify common validation issues before sending. These checks do not replace an authority’s acceptance decision.
Local certificate signing
With the Local Signer app, private keys stay on your device while the XML is signed.
Submission routing
Send validated eCoC XML through supported electronic channels.
Result tracking
Review validation results, submission status and processing responses.
Developer API
Integrate eCoC signing and submission workflows into manufacturer systems.
Bring separate eCoC tasks into one workflow
Without SignECOC
- Manual XML checks
- Separate signing tools
- Unclear submission status
- Different procedures for each channel
- Limited traceability
With SignECOC
- One upload workflow
- Automated validation
- Local certificate signing
- Supported EU and UK channels
- Clear status and result tracking
Electronic Certificate of Conformity (eCoC) workflows
In this workflow, electronic Certificates of Conformity are handled as structured IVI XML messages. Preparing the XML is only the first step: manufacturers must also check it, sign it and use the appropriate submission channel.
SignECOC brings IVI XML validation, electronic signing and submission preparation together for manufacturers, homologation departments, compliance teams and software providers.
IVI XML validation and eCoC signing
Check your IVI XML before signing and submission. Sign with a manufacturer-controlled certificate using the Local Signer app or a temporary encrypted session with your PFX/P12 file.
The signing workflow supports XMLDSig and XAdES. Certificate suitability depends on the selected channel and its requirements. With local signing, private keys stay on the manufacturer’s device.
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
eCoC XML guides
What is an eCoC? Electronic Certificate of Conformity explained
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
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
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
Understand EUCARIS IVI exchange, national access points, eCoC submission and the separate national registration process.
IVI XML validation errors: causes and fixes
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
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
Check an existing eCoC XML signature before sending. Review signature structure, certificate information and cryptographic validation in SignECOC.
Submit an already signed eCoC 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
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
Understand the preparation for RDW eCoC delivery: manufacturer access, IVI XML, signature checks and the distinction between test and production.