If an eCoC cannot be found by VIN, start with the submitted artifact and the receiving-system result. A file generated in the manufacturer's software may not have been accepted or made available for retrieval. Check vehicle identity, route, manufacturing stage and the service being queried before retrying or creating a correction.
The practical question is where the evidence chain stops. Manufacturers, importers and registration teams often see different parts of that chain. A shared investigation record helps them resolve the missing link without repeatedly exchanging an XML attachment that may never have reached the right system.
What does “eCoC not found” actually establish?
It establishes that a particular lookup did not return the expected record at that time. It does not, on its own, establish a wrong vehicle, invalid XML, an authority outage or an exemption. The EReg NAP FAQ lists possible causes including an eCoC not yet submitted, a rejected delivery unnoticed by the manufacturer and exchange-system downtime.
Record the service name, environment, query time and observed message. Keep full VINs and operational logs within the authorised investigation channel rather than publishing them in an open support discussion.
Use this diagnostic sequence
| Check | Evidence | Owner |
|---|---|---|
| Correct vehicle | VIN on the production record, signed file and lookup request agree. | Vehicle-data owner |
| Actual submission | Operation reference and exact artifact were sent to the intended production route. | Submission operator |
| Receiving result | Acceptance or rejection tied to that artifact, beyond transport success. | Integration or portal owner |
| Correct record and stage | Expected manufacturer, manufacturing stage and revision are identified. | Homologation team |
| Correct retrieval service | The service can retrieve that route's records and is available to that user. | Receiving authority or service operator |
Check identity without changing the VIN
Compare the identifiers at each handover rather than relying on a screenshot of a dashboard row. Revenue specifies a 17-character alphanumeric VIN for the lookup described in its guidance. A transcription error, extra character or query for another production unit can point to a different record.
Do not repair an identity mismatch by silently altering the signed XML. First establish which source is authoritative. If the certificate contains a genuine error, use the submitted eCoC correction process and preserve the prior record.
Generated, transmitted and accepted are different states
Ask for the file, its controlled revision, submission time, receiving route and response. An HTTP success may establish only that a request reached a service. A schema result may establish structure. Neither alone proves the intended authority can retrieve the record.
If a portal rejected the file, work from the actual error and regenerate after correcting the source or mapping. If the outcome is unknown, reconcile it before retrying. Blind resubmission can produce duplicate operations or make later responses harder to interpret.
EU retrieval and UK public access are separate questions
Revenue explains that, for the applicable new M and N vehicles, it retrieves the eCoC through EUCARIS using the VIN. VCA operates a separate service. As checked on 16 October 2026, VCA's guidance still describes the public retrieval service as Phase 2 with launch timing to be confirmed and provides an interim data-request channel.
VCA also says manufacturers can view only their own records through the submission portal. Therefore, inability to find another manufacturer's record in that portal is not proof of a failed submission. Check which service and access rights are relevant. An unavailable public lookup and an unavailable manufacturer submission channel are different operational issues.
Identify the stage in a multi-stage vehicle
One VIN can be associated with information from successive manufacturing stages. Ask whether the registration team expects the base, incomplete or completed vehicle record. Confirm the completing manufacturer and applicable revision. EUCARIS retrieval guidance explicitly accounts for multiple IVI records in multi-stage vehicles.
A base vehicle record cannot be assumed to describe every completed-vehicle characteristic. Conversely, failure to locate the expected completed-stage record does not prove the base manufacturer's submission is missing.
Escalate with a compact evidence package
Send the authorised operator a concise package: vehicle identity, manufacturer and stage, approval context, environment, schema family, submission reference, receiving response and lookup details. State the business impact and the next registration step, while asking a precise question: was this artifact accepted, distributed and available through the queried service?
Keep one owner for follow-up and record the answer. Do not promise a fixed recovery time without the operator's confirmation. Digital CoC can help the manufacturer connect certificate status and evidence history; the NAP delivery workflow should identify where the external operator takes responsibility.