KBA 即將轉換至 IVI 2.0：現在開始準備 eCoC 流程
KBA 於 2026 年 9 月 16 日發布的資訊說明了轉換至 IVI 2.x 的規劃。車輛與型式核准資料、簽署、傳送、回應和更正必須形成一個受控流程。
KBA 轉換的重要日期
- 2026 年 10 月：預計開放測試環境，確切日期尚未公布。
- 2026 年 11 月 5 日：預計開始正式運作、登記機關存取及 KBA 向 EUCARIS 轉送。
- 2026 年 11 月 29 日：預計關閉舊 InterIVI-CoC 介面。
以上為規劃日期。測試或正式運作前，請確認 KBA 最新技術公告。
測試前準備車輛資料
VIN、型式核准、延伸、變型、版本與技術值必須來自可信來源。Electronic COC 支援準備與驗證，但不保證主管機關接受。
透過更正紀錄處理錯誤
已傳送的 IVI 2.x 紀錄不能直接刪除。應測試回應、更正、重新傳送及版本間可追溯的關聯。
依正確順序傳送國家資料
國家資料應在相關 IVI-CoC 紀錄之後傳送。KBA 建議間隔一天。
Readiness checklist
- KBA / market context: KBA-connected eCoC and IVI XML readiness
- Vehicle and approval scope: vehicle manufacturers preparing EU eCoC records, IVI XML, signatures and release evidence
- IVI 2.0 XML data structure and validation preparation
- eIDAS / qualified electronic seal readiness where signing is required
- Delivery route: KBA/NAP-related delivery preparation and manufacturer-side workflow control
- Internal ownership for missing data, exceptions and release evidence
Useful public references
- KBA CoC data and vehicle type data: KBA-connected eCoC and IVI XML readiness
- EUCARIS IVI: IVI 2.0 and vehicle information exchange context
- eIDAS Regulation: Trust-service and electronic-signature context
- Regulation (EU) 2018/858: EU vehicle type-approval framework context
與 Electronic COC 一起檢視車輛資料、簽署路徑、獲授權的 KBA 或 NAP 連線及測試情境。
/zh-tw/platform /zh-tw/contact
常见问题
Is this page for Germany vehicle owners ordering a COC?
No. Electronic COC is focused on manufacturer-side eCoC preparation, workflow control, IVI XML readiness and release coordination.
Does Germany eCoC work require a country-specific workflow?
The certificate data model is connected to the wider EU eCoC and IVI context, but Germany planning should still account for local authority, portal, API, NAP or delivery expectations.
How does Electronic COC help with KBA readiness?
It gives manufacturer teams a controlled workspace for records, approval context, missing-data review, XML preparation, signing coordination and delivery-readiness tracking.