29 November 2026 is the operational readiness date for electronic Certificates of Conformity for many manufacturers of M, N and O category vehicles. Authority guidance moved the earlier 5 July 2026 transition to 29 November. The additional time should be used to test data mapping, validation, signing, submission and rejection handling—not to postpone the project.
An eCoC is structured, machine-readable vehicle and approval data; it is not a scanned paper certificate. Start with our eCoC explainer and review the Electronic COC Platform for implementation options.
What changes on 29 November 2026?
The Swedish Transport Agency states that the provision planned for 5 July has been postponed to 29 November 2026. The UK VCA also identifies 29 November as the mandatory submission date for newly manufactured M, N and O vehicles under relevant GB and UKNI schemes. Scope and exemptions still depend on the market and approval scheme.
Operational implication: a manufacturer must have the data model, authority route, permissions, digital signature and correction workflow working before the first mandatory production record is created.
Which vehicles are in scope?
M, N and O categories are central to the current EU and UK eCoC programmes, but category alone is not enough. Approval scheme, complete or incomplete status, multistage manufacture, series type and granting authority all affect the decision. VCA guidance, for example, distinguishes national small series exemptions from GB medium series and UKNI EU small series obligations.
Why this is not only an IT project
An XML file may pass its XSD and still contain the wrong approval, variant, version or technical value. Homologation, production, quality and IT teams therefore need a shared control model.
| Workstream | Key question | Required output |
|---|---|---|
| Scope | Which category, scheme and build stage applies? | Vehicle-family scope matrix |
| Data | Where does each IVI field originate? | Source and ownership map |
| Validation | Which XSD, business and homologation rules apply? | Version-controlled rule set |
| Trust | Who signs with which authority? | Certificate and permission procedure |
| Submission | Which NAP, portal or API is correct? | Tested authority route |
| Operations | How are rejects and resubmissions recorded? | Auditable event history |
An eight-step readiness plan
- Inventory categories, approvals, markets, stages and production volume.
- Map ERP, PLM, production and homologation data to IVI 2.0.
- Assign owners for VIN, type–variant–version and technical values.
- Select manual, file import, API or a hybrid operating model.
- Apply structural, business-rule and homologation-source validation; see our IVI 2.0 validation guide.
- Establish signature, certificate lifecycle and access controls.
- Test success, rejection, correction and version resubmission.
- Freeze cut-over responsibilities, fallback and first-week monitoring.
Are EUCARIS/NAP and VCA the same route?
No. EU exchanges may use EUCARIS through a selected National Access Point. This is not a generic EUCARIS account open to any company. VCA operates a separate UK portal and API and explicitly states that the UK system is not linked to EUCARIS. See the end-to-end submission guide.
How the Electronic COC Platform helps
The Electronic COC Platform supports controlled data preparation, rule validation, version management, signing workflows and traceable submission results. Anemon Engineering combines the platform with homologation expertise so that the project improves the underlying approval data rather than merely producing XML.
Measure your readiness. Share your vehicle categories, granting authorities, target markets and monthly CoC volume through our eCoC assessment form to discuss an appropriate pilot.
Where does delay create real cost?
The expensive failure is rarely an inability to create an XML file. It is usually a mismatch between approval and ERP data, different owners using different values, signing authority being defined too late, or NAP acceptance testing being omitted from the programme. If these gaps surface near the mandatory date, shipment and registration planning may be affected.
Readiness should therefore be demonstrated by taking a real representative vehicle record from source through validation, signature, test submission and closed response. Management reporting should expose uncovered vehicle families, unowned fields, unresolved rule failures, pending authority access and certificate expiry—not only a project-completion percentage.
Selecting a starting model
| Manufacturer profile | Practical start | Main control |
|---|---|---|
| Low volume, few configurations | Controlled entry or validated template | Segregation of duties and review |
| Medium volume, stable ERP data | File transfer with exception handling | Mapping and version control |
| High volume, many variants | API automation and rule engine | Preventing bad master data from scaling |
| Multistage manufacturer | Stage-specific data and permissions | Previous-stage source and change boundary |
The objective is not maximum automation on day one. Prove a representative workflow first, then scale it without losing approval traceability.
eCoC transition and manufacturer readiness — Explore Electronic COC to plan eCoC readiness as one controlled operating workflow.
Frequently asked questions
Has 5 July 2026 disappeared?
It remains the original regulatory reference, while current authority implementation guidance moves operational readiness to 29 November. Confirm the position with your own granting authority.
Does paper end in every case?
No universal statement is safe. Transitional records, exemptions, earlier manufacture and authority requests may require different handling.
Is XSD validation sufficient?
No. It checks structure, not whether the data matches the approved type and the individual vehicle.
Can an existing ERP be connected?
Yes. File or API integration can be assessed after the source model and data quality are understood.
Which official sources should be followed?
Monitor the Swedish Transport Agency, the VCA eCoC guidance, EU legislation and the instructions of your granting authority and NAP.
Summary
The 29 November 2026 transition is not a simple replacement of paper with a digital copy. Manufacturers need a controlled chain that produces vehicle-level IVI data, validates it, signs it, submits it through the correct authority route and records the response. Anemon Engineering and the Electronic COC Platform help design that chain around the manufacturer's approvals, markets and production volume.
