KBA IVI 2.0 Transition Is Approaching: Prepare Your eCoC Process Now

KBA's information to IVI process participants dated 16 September 2026 sets out a concrete transition window for Germany's IVI 2.x route. The authority plans to make a test environment available in October 2026 and to begin live use on 5 November 2026. For manufacturers, the practical message is straightforward: the time to prepare vehicle data, signing and operational follow-up is before the test window opens.

An electronic Certificate of Conformity is not complete when a document is merely generated. The vehicle record must be structured correctly, validated against the applicable IVI 2.0 rules, signed or sealed through an appropriate process, submitted through the manufacturer's authorised national route and monitored until a response is received. Electronic COC Platform brings those steps together so teams can manage the path from source vehicle data to the authority response in one controlled workflow.

The dates manufacturers should put on their transition plan

KBA's current schedule identifies three operational milestones. The exact opening day for the test environment has not yet been announced, and the dates remain subject to later KBA updates.

• October 2026: KBA expects to open its test environment for IVI 2.x data submissions.
• 5 November 2026: live operation, access by German registration authorities to IVI 2.0 records, and forwarding through KBA to EUCARIS are planned to begin.
• 29 November 2026: KBA plans to close the legacy InterIVI-CoC interface that accepts CoC and German national data in one record.

This short interval matters. Mapping source fields, creating representative test records, preparing certificates and agreeing who handles failed responses can take longer than the technical upload itself. Teams that complete those foundations now can use the test period for realistic submission, correction and recovery scenarios rather than basic data cleanup.

Turn source vehicle data into submission-ready eCoC records

The first readiness question is whether the approved vehicle truth can be represented reliably in the required XML structure. A missing value, an invalid code or a field derived from the wrong approval reference may result in a rejected record or require a correction after submission. This is why IVI XML preparation for manufacturers must start with field ownership and approval traceability, not simply with file generation.

Electronic COC Platform uses manufacturer vehicle data to create electronic conformity records and validate them against the applicable IVI 2.0 rules before submission. Teams can see which records are ready, which need review and which contain issues that should be resolved. Platform validation is a preparation control; formal acceptance remains an authority decision and is confirmed only by the response returned after submission.

Manage electronic signing, delivery and responses as one flow

KBA also calls attention to checking whether certificates satisfy the relevant eIDAS requirements. A technically correct vehicle record still needs an appropriate electronic signature or seal process and a valid manufacturer-specific authority connection. Those elements should be tested together, because the operational chain is only as strong as its certificate, authentication and response-handling steps.

Electronic COC Platform combines eCoC creation, IVI 2.0 validation and electronic signing with submission through the manufacturer's own KBA or RDW NAP connection to EUCARIS. It also tracks responses so accepted records, failed records and records that require another action remain visible. Use of either route depends on the manufacturer's authorisation, certificates and connection conditions; software capability alone is not authority approval.

If your team is still deciding how the national route fits into the wider exchange model, our guide to EUCARIS National Access Points for eCoC explains the relationship between the manufacturer, the NAP and EUCARIS.

Corrections must be designed into the process

A particularly important point in KBA's notice is that an IVI 2.x record cannot simply be deleted by KBA after submission. KBA explains that the record is distributed through EUCARIS to participating countries before it is stored in the KBA system. An error must therefore be addressed by sending a correction record.

For manufacturers, this increases the value of pre-submission controls and post-submission visibility. The first test cases should include not only a successful record but also a rejected message, a data correction and a safe resubmission. A clear audit trail should show what changed, why it changed and which response closed the case.

Send German national data in the correct sequence

KBA states that German national data must follow the related IVI-CoC record and recommends sending it one day later for a safe process. That sequencing rule should be reflected in the operating model rather than left to individual memory. Teams need to know whether the IVI-CoC has been sent, which response has arrived and whether the national-data step is now eligible to continue.

The legacy InterIVI-CoC interface handled CoC and national data together. Its planned closure makes the separation and correlation of these steps more visible. Waiting times, identifiers and continuation conditions should be confirmed against the latest KBA technical documentation and the rules deployed in the relevant environment.

A practical readiness checklist before October

• Vehicle data: identify the approved sources for every required eCoC field and resolve gaps.
• IVI 2.0 records: prepare representative examples for vehicle types, stages and edge cases.
• Electronic signing: verify certificate suitability, ownership, validity and the signing or sealing flow.
• Authority connection: confirm the manufacturer's KBA or RDW authorisation, credentials and test scope.
• Operations: assign owners for responses, corrections, resubmissions and German national-data sequencing.

The legal and network context is available from Regulation (EU) 2018/858 and the official EUCARIS IVI implementation guidance. KBA's type-approval area remains the official public starting point for German authority information. The specific dates above are based on KBA's 16 September 2026 information to IVI process participants and should be checked against any later KBA notice before a production decision.

Prepare for the KBA transition with Electronic COC Platform

Electronic COC Platform helps manufacturers create, validate and electronically sign IVI 2.0 eCoC records, submit them through their manufacturer-specific KBA or RDW NAP connection to EUCARIS, and follow acceptance or error responses. To assess your current readiness with representative vehicle data, contact our team and plan the test scope before the KBA environment opens.