eCoC 2.0 の移行期限は 2026 年 11 月 29 日まで延長: 中国 OEM が今すべきこと

EU の eCoC 2.0 移行期間は延長されましたが, 導入を先送りする理由にはなりません。

According to the May 2026 RDW Initial Vehicle Information Newsletter, the European Commission has enabled a transitional period for eCoC version 2.0 until November 29, 2026. Until that date, paper CoC remains mandatory, and eCoC 1.x or 2.0 is not mandatory.

For Chinese OEMs exporting to Europe, this update changes the implementation schedule but not the compliance direction. eCoC 2.0 still requires an eIDAS-compatible company electronic seal, IVI 2.0 XML data preparation, XAdES signing, and connection readiness with RDW and EUCARIS-related flows.

The newsletter also confirms IVI 2.0 schema updates. TyreTypeCode has been extended, and MechanicalCouplingCanBeFittedTable now includes MechanicalCouplingCanBeFittedApprovalMark and MechanicalCouplingCanBeFittedApprovalNumber. This shows that the key challenge is not only digital signing, but also vehicle data governance, field mapping, validation, and continuous standard updates.

Small-series rules also need attention. National small-series vehicles may be exempt where a national approval authority grants a derogation. However, eCoC is still required for M, N, and O category vehicles with European whole-vehicle type approval, including European small-series approval.

RDW has separately postponed the mandatory switch to its new connection to July 1, 2026. This is not the same as the November 29 eCoC 2.0 transition. It is a RDW connection upgrade intended to support more manufacturers and larger CoC volumes. RDW now supports XAdES signing, and EUCARIS NAP software will also support XAdES.

eSign.ai's eight-phase roadmap therefore remains relevant: project initiation, vendor selection, contract execution, eSeal application, IVI 2.0 XML preparation, API integration, compliance validation, RDW/EUCARIS readiness, and production operation before November 29.

The practical message is simple: do not wait until autumn. QTSP eSeal onboarding, XML field mapping, sample validation, and API integration should begin in parallel. The transition window should be used to move from emergency compliance to stable batch operation.

This 日本語 version preserves official technical terms for accuracy. It is for reference only and does not constitute legal advice.