KBA IVI 2.0 Transition: Prepare Your eCoC Process for November 2026

KBA's information dated 16 September 2026 sets out an important transition window for IVI 2.x. The test environment is expected during October 2026, live use is planned from 5 November 2026, and the legacy InterIVI-CoC interface is planned to close on 29 November 2026. The exact test-opening day had not yet been stated in the information available for this article.

For manufacturers, the practical task is wider than generating an XML file. Vehicle data, approval context, IVI 2.0 validation, eIDAS signing or sealing, the applicable KBA or NAP route, acknowledgements and correction records all need to work as one controlled process. Dates and operating details remain subject to later KBA updates.

The KBA IVI 2.0 dates manufacturers should track

October 2026 is the expected window for the IVI 2.x test environment. Manufacturers should enter that window with representative records, known data owners and signing preparation already in place, so testing can focus on real submission and correction scenarios rather than basic data discovery.

Live use, access for registration authorities and routing through KBA to EUCARIS are planned from 5 November 2026. The legacy InterIVI-CoC interface, which combines CoC and national data, is planned to close on 29 November 2026. Treat these as planning dates and confirm them against KBA's latest technical communication before production activity.

Turn vehicle data into submission-ready eCoC records

A successful transition starts with source data. VIN, approval number, extension, variant, version and technical values should be mapped to an accountable source and reviewed before the IVI 2.0 record is released. A technically well-formed message can still be wrong when the underlying vehicle or approval context is wrong.

Electronic COC helps manufacturer teams create structured eCoC records, review missing information and run IVI 2.0 validation before the applicable external delivery step. Platform validation improves readiness; it is not a guarantee of KBA, EUCARIS, NAP or registration-authority acceptance.

Coordinate electronic signing and delivery evidence

KBA's information also draws attention to the eIDAS suitability of certificates. Manufacturers should confirm certificate ownership, signing authority, validity, trust chain and operational access before testing. Electronic COC supports signing-readiness and evidence coordination but does not act as a certificate authority, qualified trust service provider or governmental authority.

The applicable KBA or RDW/NAP route depends on manufacturer authorization and authority-specific onboarding. Electronic COC can keep the record, validation state, signature status, delivery response and next action visible in one workflow when the required customer connection is authorized and configured.

Plan correction records, not deletion

A key operational point in KBA's communication is that an IVI 2.x record cannot simply be deleted by KBA after submission. The information is distributed through EUCARIS before storage in the KBA context, so an error must be handled with a correction record.

Testing should therefore include more than a successful first message. Teams should deliberately test an invalid record, interpret the response, correct the source data, issue the appropriate correction and preserve the relationship between the original and replacement evidence.

Send national data in the right order

KBA states that national data should follow the related IVI-CoC record and recommends sending it one day later for a safe operating sequence. This makes correlation, status tracking and retry control essential, especially when production volumes increase.

The waiting period and continuation rules should be confirmed against the latest KBA technical guidance. A manufacturer workflow should show which IVI-CoC record was sent, which response was received, whether the required interval has passed and whether the national-data step is permitted to continue.

KBA IVI 2.0 readiness checklist

• Prepare representative vehicle and type-approval records before the test environment opens.
• Validate IVI 2.0 structure and business rules against the current applicable package.
• Confirm eIDAS certificate suitability, signing authority and operational access.
• Document the authorized KBA or RDW/NAP delivery route for the manufacturer.
• Test acknowledgements, errors, corrections, retries and archive evidence.
• Keep IVI-CoC and national-data sequencing visible and configurable.
• Reconfirm dates and technical rules against KBA's latest communication before going live.

Where Electronic COC fits

Electronic COC brings eCoC record preparation, IVI 2.0 validation, signing-readiness coordination and delivery-response tracking into one manufacturer-side workflow. It supports readiness and controlled operations; authority authorization, legal responsibility and final acceptance remain with the manufacturer and the relevant external parties.

Use the related resource at /germany-kba-ecoc-ivi-xml/, review the platform overview at /platform, or contact Electronic COC at /contact with the process, vehicle category and current blocker your team wants to control first.