KBA plans IVI 2.x testing for October 2026 and live operation from 5 November. See how manufacturers can prepare eCoC data, signing and delivery.
KBA IVI 2.0 transition: prepare your eCoC process now
KBA plans to open its IVI 2.x test environment in October 2026 and begin live operation on 5 November 2026. Manufacturers intending to use the German National Access Point should prepare the complete eCoC workflow now: vehicle data, IVI 2.0 validation, electronic signing, delivery and response handling.
KBA's information to IVI process participants dated 16 September 2026 sets out an operational timetable and several important processing rules. The dates remain subject to later KBA updates, so teams should treat them as a release plan to verify, not as an unconditional guarantee.
KBA IVI 2.0 timetable
- October 2026: the IVI 2.x test environment is expected to open; KBA has not yet stated an exact day.
- 5 November 2026: live use, access for German registration authorities and KBA routing through EUCARIS are planned to begin.
- 29 November 2026: KBA plans to close the legacy InterIVI-CoC interface that receives CoC and national data in one record.
This operational schedule is separate from the legal baseline. Article 37 of Regulation (EU) 2018/858 requires manufacturers, from 5 July 2026, to make the certificate of conformity available to the whole-vehicle type-approval authority as structured electronic data. EUCARIS describes IVI 2.0 as the common exchange format and explains that a national authority must complete testing before going live.
What manufacturers should prepare before testing
A successful test is not merely a valid XML file. The manufacturer needs a repeatable process that connects trusted source data, approval context, IVI 2.0 generation, validation, the authorised electronic signature or seal, the manufacturer-specific KBA connection and the response returned after submission.
- Vehicle data: identify missing, inconsistent or wrongly formatted values before XML generation.
- IVI 2.0 validation: test representative records for each relevant vehicle category and approval profile.
- Signing: confirm the authorised signatory or seal owner, certificate suitability and operational responsibility.
- KBA onboarding: confirm the manufacturer's mandate, test credentials, endpoints and release conditions directly with KBA.
- Operations: define who reviews acceptance, errors, corrections and resubmissions.
Why correction handling matters
KBA states that IVI 2.x records cannot be deleted by KBA after submission because they are distributed to participating countries through EUCARIS before being stored in the German system. An incorrect record must therefore be addressed with a correction record. That makes pre-submission control and post-submission response tracking part of the same compliance process.
Test cases should include more than a successful first submission. Teams should also exercise validation failures, authority errors, correction records, repeated delivery and the evidence retained for each outcome.
National data must follow the IVI-CoC record
KBA reminds participants that German national data may only be sent after the related IVI-CoC record. KBA recommends a one-day interval as the safer operating sequence. The exact waiting rule and continuation criteria should be reconfirmed against the latest KBA technical instructions before production use.
How Digital CoC supports KBA readiness
Digital CoC brings eCoC creation, IVI 2.0 validation, electronic signing, manufacturer-specific KBA or RDW NAP delivery and response tracking into one controlled workflow. Manufacturer authorisation, authority onboarding and final acceptance remain with the responsible parties; platform validation is preparation evidence, not authority acceptance.
Starting with real sample records now allows teams to spend the KBA test window on end-to-end scenarios instead of basic data cleanup. A focused readiness review should cover the source data, XML rules, signing model, connection responsibilities and correction workflow.
Frequently asked questions
When will KBA's IVI 2.x test environment open?
KBA currently plans to open it in October 2026. The exact day was not stated in the 16 September information.
When is KBA live operation planned?
KBA plans live operation, registration-authority access and EUCARIS routing from 5 November 2026.
Can KBA delete an incorrect IVI 2.x submission?
According to KBA's information, no. The record is distributed through EUCARIS before KBA stores it, so the error must be addressed with a correction record.
Does Digital CoC replace KBA authorisation?
No. Digital CoC supports preparation, validation, signing, delivery and tracking. Manufacturer mandate, onboarding and authority acceptance remain separate controls.
Official references
KBA-specific dates and processing rules in this article are based on KBA's information to IVI process participants dated 16 September 2026. Verify later KBA notices before making production decisions.