Electronic COC Platform · IVI 2.0

eCoC software for vehicle manufacturers

Built for second-stage and multi-stage manufacturers, including ambulance and wheelchair-accessible vehicle (WAV) converters.

Request a workflow demo
How to generate eCoC XML

Learn how to generate eCoC XML and review XSD and ICM validation results.

  1. 01

    Follow one vehicle from its source data and approval references.

  2. 02

    Generate XML and inspect XSD / ICM validation findings.

  3. 03

    Review the seal arrangement and the exact file released for signing.

  4. 04

    Trace the NAP response and the next action for a rejected record.

The video shows XML preparation. Signing and NAP delivery are reviewed against your provider and destination; a demo is not authority acceptance.

Electronic COC

What will you see in the demo?

  • Follow one vehicle from its source data and approval references.
  • Generate XML and inspect XSD / ICM validation findings.
  • Review the seal arrangement and the exact file released for signing.
  • Trace the NAP response and the next action for a rejected record.

Request a workflow demo

Your information will only be used to respond to your operational eCoC request.

PDF · English

NAP / eCoC readiness checklist

Enter your email to unlock the PDF. This request does not subscribe you to a newsletter.

Your information will only be used to respond to your operational eCoC request.

From a vehicle record to an electronic Certificate of Conformity

An eCoC project starts with the actual vehicle and its approval context. A VIN alone is not enough: the team also needs the relevant type, variant, version, technical values and production information. Organise these inputs before deciding how the XML will be generated or where it will be delivered.

  • Identify the vehicle and the applicable approval reference.
  • Review missing or inconsistent data before XML preparation.
  • Keep release approval, signing and the receiving authority’s response as separate steps.

Give each team a clear handover

Use the platform discussion to map who owns each decision. Production supplies vehicle-specific values; homologation reviews approval-related content; the responsible entity authorises release; integration teams coordinate connected systems. The useful result is a repeatable process with visible exceptions, not another spreadsheet that only one person understands.

  • Data owners: resolve the source of a missing value.
  • Reviewers: confirm which certificate version is ready for signing.
  • Release teams: reconcile the signed file with the submission outcome.

Evaluate the software with one representative vehicle

A focused demonstration should follow one record all the way through the proposed workflow. Include an incomplete input and a corrected version, as well as a successful path. This shows how the implementation will deal with daily production work. An ERP or API connection is scoped against your source system and target interface; it should be verified with a sample exchange before rollout.

  • Vehicle category, production volume and approval scheme.
  • A sanitised source-data sample and the team’s current CoC process.
  • Target market, signing arrangement and required delivery route.

Start with an implementation scope you can verify

Choose one production line, vehicle category or issuing entity for the initial scope. Agree which data is imported, which checks block release, who resolves an exception and what evidence is retained. Expand after those handovers have been demonstrated. Authority onboarding and trust-service arrangements remain specific to the manufacturer and destination.

Frequently asked questions

Is this eCoC software for vehicle owners?

The platform is for vehicle manufacturers and authorised teams managing certificate production. Vehicle owners seeking a replacement CoC should contact their manufacturer or its authorised representative.

Can we use existing ERP and production data?

Existing data can form the basis of the implementation. The first step is to assess available fields, identifiers, export or API access and update responsibilities. The agreed connection and mapping need verification with your own sample data.

What should we bring to an eCoC software demo?

Bring your vehicle categories, target markets, approximate certificate volume and a sanitised example of the source data. Include the current signing and submission arrangements so the demonstration can follow your actual handovers.

Coordinate XML, signing and delivery preparation more clearly

EReg: IVI 2.0 guidelinesEUCARIS: implementation of IVI