Digital and paper CoC may run together
Prepared markets such as the Netherlands and Germany can accept digital eCoC, while France, Italy, Poland, and other markets may still need paper CoC during preparation.
Updated May 2026
The practical deadline changed, but the operating work did not
The latest eCoC conversation is not only about a date. It is about uneven member-state readiness, access-point choice, certificate requirements, and keeping paper CoC available where the destination market still relies on it.
- Jul 5, 2026The original date remains in Regulation (EU) 2018/858.
- Jul 1, 2026RDW connection changes are treated separately from the eCoC 2.0 transition window.
- Nov 29, 2026eCoC 2.0 is treated as optional before this transition date in the current operating arrangement.
NAP choice is flexible
A manufacturer does not need to submit through its home country or type-approval country. A German type approval can use the Dutch RDW NAP when that access point is the better operational route.
Regulatory baseline
EU eCoC is structured vehicle data, not a PDF replacement
Buyer decisions
What OEM teams need to decide before eCoC production
The eCoC decision is operational as much as it is legal. Manufacturers need a data route, a certificate route, an access-point route, and a fallback route.
- 1
eCoC is not just a PDF replacement
The operating model includes structured IVI XML, VIN data, manufacturer legal names, a QTSP certificate path, XAdES or XMLDSIG signing, NAP submission, EUCARIS retrieval, and archive evidence.
- 2
Member-state readiness is not symmetrical
One manufacturer selling across Europe may need digital eCoC for prepared markets and paper CoC for markets that are still preparing their retrieval or registration process.
- 3
Certificate setup can become the long pole
The certificate needs to come from a QTSP on the EU Trust List, include digital signature and non-repudiation key usage, and match the manufacturer name in type approval.
Readiness checkpoint
Need to validate your eCoC route?
Use one vehicle line, target member states, and certificate status to check the NAP, QTSP, and paper fallback path before production planning.
Operating definition
What makes an EU eCoC operation credible?
A credible eCoC operation connects four layers: vehicle data, certificate trust, NAP submission, and evidence retention. The manufacturer still needs destination-market instructions and paper fallback where digital retrieval is not ready.
Data route
Prepare IVI 2.0 XML, VIN-level data, type approval fields, schema checks, and ICM data quality validation.
Trust route
Use an EU Trust List QTSP certificate with the required key usage and manufacturer name alignment.
Access-point route
Choose a NAP such as RDW when it gives better readiness, endpoint access, and testing support.
Fallback route
Keep paper CoC available during the transition for destination countries that cannot retrieve or accept digital eCoC yet.
Route decision
Choose the eCoC operating route before choosing the signing vendor
The right vendor conversation starts after the manufacturer has mapped NAP selection, certificate validation, data quality checks, and paper CoC fallback.
| Route | Typical use | What to confirm | eSign.AI role |
|---|---|---|---|
| NAP selection | Submit eCoC through a prepared access point, even when the type approval country is different. | Endpoint, test window, public certificate exchange, production submission rules, and destination retrieval readiness. | Prepare signed XML packages, batch status, callback records, and archive return around the selected NAP flow. |
| Certificate validation | Sign eCoC with a certificate accepted under the EU trust framework. | QTSP status, certificate chain, revocation status, key usage, manufacturer name match, and seal policy. | Route XAdES or XMLDSIG signing through a controlled certificate path and keep validation evidence. |
| Data quality check | Validate IVI XML and vehicle data before submission to reduce rejected batches. | IVI 2.0 XML mapping, VIN data, type approval fields, sample validation, and ICM checks. | Validate batches before submission and return per-file success or failure records. |
| Paper CoC fallback | Support markets where paper remains required during the transition. | Destination country readiness, registration-team instructions, archive policy, and duplicate handling. | Keep signed XML evidence, VIN records, and paper duplicate operations aligned. |
Route
NAP selection
Typical use
Submit eCoC through a prepared access point, even when the type approval country is different.
What to confirm
Endpoint, test window, public certificate exchange, production submission rules, and destination retrieval readiness.
eSign.AI role
Prepare signed XML packages, batch status, callback records, and archive return around the selected NAP flow.
Route
Certificate validation
Typical use
Sign eCoC with a certificate accepted under the EU trust framework.
What to confirm
QTSP status, certificate chain, revocation status, key usage, manufacturer name match, and seal policy.
eSign.AI role
Route XAdES or XMLDSIG signing through a controlled certificate path and keep validation evidence.
Route
Data quality check
Typical use
Validate IVI XML and vehicle data before submission to reduce rejected batches.
What to confirm
IVI 2.0 XML mapping, VIN data, type approval fields, sample validation, and ICM checks.
eSign.AI role
Validate batches before submission and return per-file success or failure records.
Route
Paper CoC fallback
Typical use
Support markets where paper remains required during the transition.
What to confirm
Destination country readiness, registration-team instructions, archive policy, and duplicate handling.
eSign.AI role
Keep signed XML evidence, VIN records, and paper duplicate operations aligned.
Submission workflow
One NAP can serve more than one destination market
Cross-border submission is possible, but retrieval remains the gating issue. If the destination country has no EUCARIS retrieval point, the registration flow may still require paper CoC.
- 1
Request access
Send the request to the NAP operator, obtain the endpoint, and confirm the testing path.
- 2
Provide certificates
Provide public certificate material and align signing plus transport certificate requirements.
- 3
Validate data
Run signature checks, certificate trust-chain checks, revocation checks, and ICM data quality validation.
- 4
Retain evidence
Return signed records, validation results, certificate evidence, and status callbacks to homologation or archive systems.
eSign.AI workflow
Turn eCoC preparation into a controlled signing operation
eSign.AI sits between OEM systems, QTSP certificate routes, and NAP submission preparation. The goal is predictable batch operation rather than one-off XML signing.
XAdES and XMLDSIG signing
Support recommended XAdES signing paths and XMLDSIG where required, with certificate, timestamp, revocation, and validation evidence captured for each signed XML file.
Batch XML operations
Process eCoC XML batches with schema checks, business-field checks, per-VIN status, retry handling, and result manifests for operations teams.
System callback and archive
Return signed records, validation results, certificate evidence, and status callbacks to homologation, ERP, DMS, or vehicle archive systems.
Country readiness
Country readiness changes the practical workflow
Digital eCoC acceptance and paper CoC fallback need to be planned by destination market during the transition.
| Market group | Examples | What it means | What to confirm |
|---|---|---|---|
| Prepared NAP markets | Netherlands RDW, Germany | Digital eCoC acceptance and access-point readiness are stronger starting points for production testing. | Confirm endpoint, public key exchange, XAdES support, test procedure, and production volume expectations. |
| Markets still preparing | France, Italy, Poland | Digital eCoC planning can continue, but paper CoC may still be needed for registration workflows. | Confirm whether the destination country can retrieve eCoC data through EUCARIS before replacing paper. |
| Unclear readiness | Spain | Avoid assuming that digital eCoC acceptance is ready for all production vehicles. | Check destination-country instructions and keep paper CoC fallback available. |
Market group
Prepared NAP markets
Examples
Netherlands RDW, Germany
What it means
Digital eCoC acceptance and access-point readiness are stronger starting points for production testing.
What to confirm
Confirm endpoint, public key exchange, XAdES support, test procedure, and production volume expectations.
Market group
Markets still preparing
Examples
France, Italy, Poland
What it means
Digital eCoC planning can continue, but paper CoC may still be needed for registration workflows.
What to confirm
Confirm whether the destination country can retrieve eCoC data through EUCARIS before replacing paper.
Market group
Unclear readiness
Examples
Spain
What it means
Avoid assuming that digital eCoC acceptance is ready for all production vehicles.
What to confirm
Check destination-country instructions and keep paper CoC fallback available.
FAQ
EU eCoC questions from OEM teams
eCoC readiness review
Plan EU eCoC around NAP readiness, certificate trust, and paper fallback
Bring one vehicle line, sample IVI XML, manufacturer legal names, certificate status, target member states, and current CoC workflow into a readiness conversation.
