Germany's Kraftfahrt-Bundesamt (KBA), the federal authority responsible for vehicle type approval, sent IVI participants a notice with a concrete rollout schedule for version 2.0. It is the first time an EU national authority has published a technical plan this detailed for reaching 29 November 2026, rather than a general reference to the regulation's deadline.
What KBA actually announced
- Test operation. Test intake of version 2.x datasets is expected to start only in October 2026, a month before production go-live.
- Certificate validation. KBA points to the European Commission's DSS webapp demo, where a signing certificate can be uploaded and checked for eIDAS conformity ahead of production.
- Production go-live. Unchanged, 5 November 2026.
- Old interface switched off. InterIVI-CoC, the existing channel that bundled CoC and national data in one dataset, is deactivated on 29 November 2026, together with the end of the so-called Gentlemen's Agreement.
- Access for registration authorities. Registration authorities can start querying IVI-CoC 2.0 records from 5 November 2026 too, alongside activation of EUCARIS forwarding.
- No more deletions. From version 2.x, KBA will no longer be able to delete submitted IVI-CoC records, because they are distributed to other EU member states over EUCARIS before KBA itself stores them. The only way to fix a mistake will be a separate correction dataset.
- Submission order. National data can only be sent after the IVI-CoC record has been transmitted. KBA recommends waiting a full day, to be safe.
The biggest operational change
Until now, a mistake in a submitted record could be deleted and resubmitted. From version 2.x, the only path is a correction record, so internal processes need to be built around corrections rather than delete-and-resend.
Why this is a signal for all of Europe, not just Germany
Germany runs its own National Access Point (NAP) instead of waiting on the shared EU EUCARIS build, which makes it the most advanced market for IVI 2.0 today (we covered this in our EU & UK NAP readiness tracker). The mechanisms KBA is now testing, EUCARIS forwarding, the end of record deletion, and the forced sequencing of CoC before national data, come straight from the architecture described in Regulation (EU) 2018/858 and are meant to apply across every member state. Germany's timeline shows how those rules will actually work.
What this means in practice for manufacturers
- If you sell into the German market, treat October 2026 as a test window and plan your own integration test inside it, before production starts.
- Validate your signing certificate against the European Commission's DSS tool now, instead of finding an eIDAS problem right before 5 November.
- Design your process around corrections, not delete-and-resend. This is not a German-specific requirement, it is how IVI 2.0 is meant to work everywhere.
- Build in a gap between sending the eCoC and sending national data, at least a day, rather than submitting both at once.
How CoCDesk handles this
- National data is sent only after the eCoC has been confirmed, with no manual tracking of order.
- A full audit trail means correcting a record never requires deleting it.
- The signing certificate is checked against eIDAS before every submission, not after a NAP rejects it.
Source: Kraftfahrt-Bundesamt (KBA), Abteilung Typgenehmigung, notice to IVI process participants, September 2026.
Ready for the EU eCoC rollout?
Book a free demo and see how COCDESK can have your eCoC process production-ready across every EU Member State.