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-cn/platform /zh-cn/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.