EU eCoC · legal duties in force

eCoC compliance and automation for Chinese automakers

Connect vehicle and approval data, IVI 2.0 validation, electronic signing, EU NAP / UK VCA submission, and a VIN-level evidence chain.

2026-07-05 · in force

Article 37 structured electronic CoC duties

No later than 2026-11-29

Coordinated operational transition, not a uniform legal postponement

See the automation flow

Official status · verified 2026-07-30

Separate legal dates, operating status, and national rules

Plan by vehicle category, production date, approval authority, and registration country instead of relying on a single EU-wide countdown.

EU legal milestone

2026-07-05

The Article 37 milestone for structured electronic CoCs and member-state exchange capability remains unchanged.

EUR-Lex

Operational transition

No later than 2026-11-29

A coordinated transition followed the 168th working group. Ready countries may switch earlier; this did not amend the legal date.

RAR official notice

Ireland is operational

Automatic VIN retrieval

Revenue can retrieve applicable new M and N vehicle records through EUCARIS; IVI 2.0 becomes the sole accepted route on November 30.

Irish Revenue

From compliance document to production data flow

Make every VIN validatable, deliverable, and traceable

Automation is not just faster XML generation. It must control versions, errors, signing authority, external receipts, and later corrections at production scale.

Vehicle and approval data
Connect WVTA, vehicle configuration, PLM / MES, and VIN data while retaining field provenance and template revisions.
01
Layered IVI 2.0 validation
Run XSD, ICM, cross-field, and internal business checks without presenting technical acceptance as substantive compliance.
02
Controlled electronic signing
Set the signer, certificate type, XML profile, key controls, and trust validation against the selected NAP's current requirements.
03
Separate EU and UK delivery
Use an available NAP for the EUCARIS exchange path and operate the UK VCA Portal / API as a separate route.
04
Receipts, corrections, and evidence
Link original XML, hashes, receipts, retries, business versions, and correction approvals to each VIN for CoP review.
05

Four implementation workstreams

Put regulatory scope, data engineering, trust services, and external connectivity into one testable delivery chain.

Regulatory scope and route

Confirm vehicle categories, approval paths, production dates, target markets, and paper transition boundaries in an implementation matrix.

IVI data and signing

Deliver mapping, version control, XSD / ICM prechecks, and XML signing aligned with the selected NAP's requirements.

NAP / VCA integration

Support EU NAP onboarding, testing, and receipt handling while building the UK VCA route independently.

CoP evidence and operations

Establish VIN status, corrections, certificate lifecycle, incident handling, and independently exportable evidence.

See the full service scope

From scope confirmation to first-batch evidence

Each stage is governed by verifiable outputs and external gates, not fixed week counts that hide NAP onboarding and data-readiness uncertainty.

Scope and evidence baseline

Vehicle · approval · market

Map categories, WVTA, approval authorities, production dates, registration markets, and current CoC data sources.

Sample and access validation

XML · signing · credentials

Use redacted test VINs to lock versions, test negative cases, validate signatures, and start NAP / VCA access.

Production release and operations

Receipt · correction · audit

Validate first submissions, downstream VIN retrieval, recovery, certificate rotation, and evidence export.

Who this is for

M, N, and O vehicle manufacturers within Regulation 2018/858
EU representatives, approval teams, and European business units
Cross-functional CoC, PLM / MES, quality, and digital transformation teams
Exporters building separate EU NAP and UK VCA delivery routes

Confirm applicability before choosing systems, signing, and connectivity.

We first confirm vehicle scope, approval path, target markets, and available data, then define a testable validation scope.

FAQ

Frequently asked questions

How is an eCoC different from a traditional CoC?

An eCoC is a structured electronic CoC exchanged as XML and IVI messages, not a scan of a paper document. It must remain traceable to the vehicle, approval, signing evidence, and submission receipts.

What do July 5 and November 29, 2026 mean?

July 5 is the legal Article 37 milestone. November 29 is the latest boundary of a coordinated operational transition. Countries may switch earlier and do not apply identical vehicle scopes or dates.

Is a paper CoC still required after an eCoC is provided?

Article 36(2) removes the general duty to accompany the vehicle with a paper CoC once a compliant eCoC has been provided. National transitions, small-series routes, and special authority requests still require separate checks.

Must a manufacturer integrate with every sales-country NAP?

The rules allow delivery through any EU NAP to the authority granting the whole-vehicle type approval. You must still verify downstream VIN retrieval and registration; NAP acceptance does not mean automatic registration across Europe.

Do all NAPs mandate QES, QeSeal, or one XAdES profile?

No. Implementing rules set electronic-signing and security baselines, while signer type, certificate registration, and XML profile depend on the selected NAP's current documentation and test results.

Does the UK use the EUCARIS NAP route?

No. The UK VCA runs a separate Portal / API. GB, UKNI, and EU type approvals used in Northern Ireland also require route-specific analysis; one submission cannot cover both EU and UK systems.

Validate the full eCoC chain with real test VINs