eCoC in Practice: IVI XML, XAdES Signatures and the Routes into the NAP
The IVI XML format
eCoCs rest on the Initial Vehicle Information (IVI) file created for the EU eCoC system. The IVI 2.0 XML file conforms to the harmonised EU IVI template, with each EU Member State applying its own approval authority code (for instance e1 for Germany or e2 for France) plus country-specific regulatory references where they apply.
IVI files have to be in Extensible Markup Language (XML) — not PDF, not Word, no other format. XML is the choice because eCoCs are structured regulatory data that the NAP and other authorities need to extract, validate and store automatically.
The IVI schema: what an eCoC holds
The IVI 2.0 schema spans hundreds of technical data fields, covering:
Vehicle identity
VIN, type approval number, approval authority code, variant and version, and manufacturer details
Technical data
Masses, dimensions, axle configurations, engine specifications, emissions class and fuel type
Compliance data
Component type approvals, regulatory references, and stage-specific data for multi-stage builds
XAdES digital signatures
Every eCoC has to bear a digital signature that guarantees authenticity and data integrity. The EU mandates a single standard for this: XAdES (XML Advanced Electronic Signatures), defined in ETSI EN 319 132 and aligned with the eIDAS Regulation.
The signature types allowed are:
- Advanced Electronic Signatures (AdES) — the baseline requirement
- Advanced Electronic Seals (AdESeal) — used for organisation-level signing
- Qualified variants (QES, QESeal) — optional, but still accepted
XML is sensitive to formatting
After an XML file has been digitally signed, any edit at all — even a single space or line break — invalidates the signature. This trips up submissions regularly. The file must be signed as the very last step before submission, with nothing altered afterwards.
XSD schema validation
Ahead of submission, IVI XML files are validated against the XSD (XML Schema Definition) to confirm that their structure and content are sound. This automated check picks up problems such as missing mandatory fields, wrong data types and invalid values before the file ever reaches the NAP.
Validating before submission is essential — any file that fails the XSD check is rejected and must be corrected and resubmitted.
Routes for submitting to the NAP
The NAP eCoC portal
A web interface for uploading IVI XML files by hand. A fit for manufacturers with smaller volumes, or those still early in their rollout.
The API (system-to-system)
Automated delivery over the NAP API. It supports direct integration with production systems, ERP platforms and eCoC management software for high-volume operations.
eCoC EU² takes on the technical complexity
The eCoC EU² software hides the technical requirements away, so your team never has to build XML generation, XAdES signing or NAP API integration in-house:
Ready for the EU eCoC rollout?
Book a free demo and see how eCoC EU² can have your eCoC process production-ready across every EU Member State.