For vehicle manufacturers, homologation teams and production operations in Europe and the United Kingdom.
If an eCoC has been submitted but cannot be found by VIN, establish the last confirmed processing stage before sending it again. A file export, a transport receipt, acceptance by the receiving system and successful downstream retrieval are separate observations. Match each observation to the same vehicle, certificate version and destination.
The useful question for a manufacturer is: which party can prove what happened to this exact record? The following diagnostic sequence is a suggested operating method. It helps a homologation or production team collect a complete case for its NAP operator, authority or implementation partner.
The EReg manufacturer Q&A identifies missing submission, rejected delivery and EUCARIS downtime as possible reasons why a record cannot be found. Its discussion also separates the manufacturer’s delivery from subsequent distribution and registration. These are useful investigation branches; they are not proof of the cause in a particular case.
First record whether the vehicle was sent through an EU NAP or the UK VCA service. Confirm the environment, manufacturer account, approval scheme and build stage. A successful result in a test environment cannot establish the presence of an official production record. A screenshot without these details is weak evidence for an escalation.
| Last confirmed stage | Check next | Suggested owner |
|---|---|---|
| XML generated internally | Find the actual dispatch event, destination and submitted file digest. An export is not a dispatch receipt. | Manufacturer operations |
| Request transmitted | Locate the documented receiver response and interpret its status. Record an unresolved timeout as uncertain. | Integration team |
| Receiver reports rejection | Preserve the response, identify the responsible source value and prepare the documented correction route. | Data owner and reviewer |
| Receiver reports acceptance | Check which record version was accepted and ask the operator to trace onward processing where relevant. | NAP or receiving-system support |
| Record available to one authorised service | Compare the retrieval route, destination country, build stage and identifiers used by the failing service. | Registration liaison |
| Conflicting results for the same VIN | Reconcile timestamps and versions before changing or repeating the record. | Manufacturer incident owner |
Compare the VIN in the production record, the signed XML and the retrieval request character by character. Copy it from a controlled source rather than from a photograph or a retyped email. If a third party reports the problem, ask which system they searched and when; the words ‘not found’ alone do not identify a failed exchange.
For a multi-stage vehicle, identify the manufacturer and completion stage of the missing certificate. A previous-stage record and a final-stage record can concern the same physical vehicle while answering different approval questions. Preserve the approval reference and stage with the support case instead of relying on VIN alone.
Keep the certificate’s business version separate from the IVI schema revision and the local file name. Renaming a file does not create a correction. Before issuing a changed version, establish whether the earlier submission was accepted and apply the receiver’s documented versioning and correction process. Review the related multi-stage data handover guide where more than one manufacturer is involved.
VCA’s guidance states that the UK service is separate from EUCARIS. It also distinguishes the manufacturer submission portal from the planned public retrieval service. Follow the access route currently documented by VCA; failure to find a record through an unrelated service does not establish a rejected UK submission.
For EU delivery, identify the actual NAP operator and the authority or registration service trying to retrieve the data. Obtain the relevant response or trace through the authorised support channel. Do not treat a commercial VIN lookup site as an authoritative test of the whole eCoC exchange.
Illustrative scenario: a manufacturer’s system records ‘sent’ at 09:10. A registration contact reports a missing VIN at 10:00. The dispatch log contains a transport success but no retained acceptance result. The team should first retrieve or reconcile the receiver’s outcome. It should not change the vehicle data merely to produce another file.
If reconciliation shows rejection, the data owner can address the stated cause and a reviewer can authorise the next release. If it shows acceptance, the case moves to onward availability and retrieval. If the outcome remains unknown, retain that uncertainty and escalate it with the request reference. The purpose of this example is to avoid turning an observation gap into contradictory certificate records.
Use the receiver’s secure support route for XML files or identifiers. Regulation (EU) 2024/1061 requires traceability of exchanged messages in the EU NAP framework. A manufacturer-side evidence record should make those traces easier to reconcile, without claiming that the manufacturer controls the entire registration process.
Track unresolved outcomes separately from rejected records. Give each case an owner and a next action. When the receiver confirms the outcome, close the gap between the operational dashboard and the evidence retained against the certificate. Review repeated causes with the source-data team rather than treating every missing VIN as a new integration incident.
For an implementation discussion, bring one anonymised example of the dispatch, response and retrieval problem. Electronic COC can be assessed against the preparation, review and evidence handovers your team needs. Start with the manufacturer delivery workflow, or discuss your operating case. For a service outage affecting many records, use the separate NAP outage recovery plan.
An HTTP success describes a transport interaction. Interpret the receiving system’s documented outcome for the submitted version and establish downstream availability separately. Keep each result with the vehicle record.
First determine whether the previous attempt was rejected, accepted or unresolved. Reconcile an uncertain outcome through the receiver’s documented mechanism before repeating the transmission or creating a correction.
The UK VCA service is separate from EUCARIS. Use the currently documented UK access and support route for UK records, and the appropriate EU route for EU records.
Supply the VIN, manufacturer, approval and build stage, environment, destination, timestamps, submitted version, request reference, receiver response and the service reporting the missing record. Use the authorised secure support channel.
Reviewed on 16 October 2026. Authority statements below are distinguished from our suggested operating controls. Receiving-system instructions and the applicable approval scheme govern the actual submission.
Continue with Electronic COC articles that connect eCoC readiness, manufacturer rollout and certificate release control.
Prepare eCoC operations for NAP outages: preserve signed records, reconcile uncertain submissions and test an authorised alternative route. EU and UK guidance.
What manufacturers should prepare for Netherlands NAP and RDW-facing eCoC data workflows, including structured vehicle data, validation and delivery evidence.
A practical 2026 guide to UK VCA eCoC readiness, portal/API submission planning, IVI XML preparation, signing controls and multi-stage vehicle data.