Prepare your eCoC NAP submission workflow

A National Access Point is a manufacturer-facing entry route for electronic CoC data. EUCARIS explains that Member States do not all need to operate their own NAP: an authority may also receive IVI information through international exchange. The destination registration country therefore does not automatically mean a separate manufacturer integration.

Confirm the selected access point, supported message version, authentication method and current onboarding instructions before planning delivery. A general statement that a platform supports EUCARIS does not establish your manufacturer's access or acceptance.

1. Identify the vehicle category, approval context and intended route.
2. Complete the manufacturer registration and arrange the credentials required by that route.
3. Prepare a representative vehicle record and validate the applicable IVI XML.
4. Apply the agreed electronic signing or sealing process after the data checks.
5. Test submission and retain both the payload reference and the authority response.
6. Assign an owner to rejected records and follow the documented correction procedure.

A request leaving your system is an event, not proof that the certificate was accepted. Design the rollout review around the response that the receiving service actually returns. The Submission Center provides the operational place to follow records; the route-specific response remains the evidence for the next action.

For repeated failures, classify the problem first: vehicle data, XML structure, signing, authentication or receiving-service response. This keeps the correction with the responsible team and avoids recreating an otherwise valid vehicle record.

Prepare your intended access point, approval and vehicle scope, expected volume, data sources and the people responsible for signing and submission. Use a representative scenario for the initial discussion; exchange confidential records and credentials only through an agreed onboarding channel.

The review should produce a written map of prerequisites, supported operations, testing responsibilities and response handling. Add further routes only after the first scoped workflow is understood.

NAP submission questions