Germany's Kraftfahrt-Bundesamt (KBA), the federal authority for vehicle type approval, has written to IVI participants setting out a firm rollout schedule for version 2.0. It is the first time an EU national authority has published a plan this detailed for reaching 29 November 2026, rather than simply pointing back at the regulation's own deadline. Note that this concerns Germany's EU scheme specifically, separate from the UK's own VCA eCoC system, though many manufacturers will be running both in parallel.
What KBA actually announced
- Test operation. Test intake of version 2.x datasets is due to start in October 2026 only, a month ahead of the production go-live.
- Certificate validation. KBA points manufacturers to the European Commission's DSS webapp demo, where a signing certificate can be uploaded and checked for eIDAS conformity before production begins.
- Production go-live. Unchanged: 5 November 2026.
- Old interface switched off. InterIVI-CoC, the existing channel that combines CoC and national data in one dataset, is switched off on 29 November 2026, alongside the end of the so-called Gentlemen's Agreement.
- Access for registration authorities. Registration authorities will also be able to query IVI-CoC 2.0 records from 5 November 2026, once EUCARIS forwarding is switched on.
- No more deletions. From version 2.x onwards, KBA will no longer be able to delete submitted IVI-CoC records, since they are distributed to other EU member states over EUCARIS before KBA itself stores them. The only remedy for a mistake will be a separate correction dataset.
- Submission order. National data may only be sent once the IVI-CoC record has been transmitted. KBA recommends allowing a full day, to be safe.
The biggest operational change
Until now, an error in a submitted record could simply be deleted and resubmitted. From version 2.x, the only route is a correction record, so internal processes need to be rebuilt around corrections rather than delete-and-resend.
Why this is a signal for all of Europe, not just Germany
Germany operates its own National Access Point (NAP) rather than waiting on the shared EU EUCARIS build, which puts it ahead of most other member states on IVI 2.0 (we cover 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 ahead of national data, come directly from the architecture set out in Regulation (EU) 2018/858 and are meant to apply across every member state. Germany's timeline gives an early look at how those rules will work in practice.
What this means in practice for manufacturers
- If you sell into the German market, treat October 2026 as your test window and run your own integration test within it, ahead of production.
- Check your signing certificate against the European Commission's DSS tool now, rather than discovering an eIDAS problem just before 5 November.
- Build your process around corrections, not delete-and-resend. This is not a German quirk, it is how IVI 2.0 is designed to work everywhere.
- Leave a gap between sending the eCoC and sending national data, at least a day, rather than submitting both together.
How CoCDesk handles this
- National data is only sent once the eCoC has been confirmed, with no need to track the order by hand.
- A full audit trail means correcting a record never means deleting it.
- The signing certificate is checked against eIDAS ahead of every submission, not after a NAP rejects it.
Source: Kraftfahrt-Bundesamt (KBA), Abteilung Typgenehmigung, notice to IVI process participants, September 2026.
Ready to meet the UK eCoC deadline?
Book a free demo and see how COCDESK can have your eCoC process production-ready before the VCA mandate takes effect.