Back to blog
Tracker
14 July 2026

EU & UK eCoC readiness tracker: which National Access Points are live — and who actually runs them

EU & UK eCoC readiness tracker: which National Access Points are live — and who actually runs them

Living document — last updated 14 July 2026. 27 EU Member States + United Kingdom. Statuses change quickly in the run-up to the deadline: always confirm the current position with the relevant national authority before relying on it for a registration. Corrections welcome at kontakt@cocdesk.com.

No single EU-wide switch

From 29 November 2026, electronic Certificates of Conformity (eCoC, IVI 2.0 XML) become the mandatory way to make conformity data available for newly manufactured M, N and O category vehicles across the EU — and, on a parallel timeline, in the UK. But each Member State designates its own National Access Point (NAP), on its own timeline, and the UK runs a separate system entirely. EUCARIS has confirmed there is no central public registry of readiness.

That leaves manufacturers and distributors with a practical problem: which markets can actually receive a signed eCoC today, and which still require paper? This page tracks that — and, just as importantly, who the eCoC-responsible authority actually is in each market.

3

Live

2

Piloting

7

Preparing

16

Unconfirmed

First, a trap to avoid: three different authorities

Under Implementing Regulation (EU) 2021/133 (and its assimilated UK equivalent), three roles are involved — and they are frequently not the same organisation:

  • Type-approval authority — issues approvals and, in most countries, hosts the national CoC database.
  • Registration authority — registers the vehicle and receives the eCoC at the point of registration.
  • NAP operator — runs the eCoC data exchange and connects to EUCARIS (whose central hub is operated by RDW, Netherlands). The UK's VCA is the exception: it runs a standalone system outside EUCARIS.

The eCoC-responsible body is usually the type-approval / CoC-database authority — not the registration office. Clean single-body cases where all three coincide: Netherlands (RDW) and Germany (KBA).

Explore the map

Every tracked jurisdiction is coloured by readiness. Click a country to see its NAP and the latest updates. The full table below is generated from the same data.

LivePilotingPreparingUnconfirmed

Hover to highlight, click a country for details. 🇬🇧 UK runs a standalone system outside EUCARIS.

JurisdictionNAP / responsible authorityStatusConf.Updates
🇮🇪IrelandThe Revenue CommissionersNSAI = type approvalLiveHigh
  • All new vehicles presented for registration are legally required to have an e-CoC (national requirement since 2016).
  • From 5 July 2026, manufacturers generate, digitally sign and transmit e-CoCs via EUCARIS in IVI 2.0 format; Revenue retrieves them automatically by VIN.
  • Until 29 Nov 2026, earlier e-CoC formats or paper certificates remain acceptable; from 30 Nov 2026, only IVI 2.0 e-CoCs are accepted.
  • Applies to categories M and N only. Applicants enter the 17-character VIN or upload the eCoC XML via myAccount/ROS before the NCTS appointment.
🇳🇱NetherlandsRDWType approval + registration + EUCARIS operator + NAP in one bodyLiveHigh
  • eCoC/CoC database operational since 2016 — the most advanced NAP.
  • Runs the shared manufacturer test NAP (ecoc2help@rdw.nl).
  • One of 3 subscriber states receiving every eCoC submitted to any NAP.
🇬🇧United KingdomVCAVehicle Certification Agency — standalone system, not a EUCARIS NAPLiveHigh
  • Phase 1 submission portal + API live since 17 June 2026.
  • Mandatory 29 Nov 2026 for GB & UKNI schemes; signed UK IVI 2.0 XML, batches up to 100 files.
  • No EUCARIS interconnection — a UK submission has no effect in the EU and vice-versa.
  • Phase 2 (public VIN lookup) pending.
🇩🇪GermanyKBAKraftfahrt-BundesamtPilotingHigh
  • Named lead NAP; hosts the CoC database and runs Germany's EUCARIS node.
  • Early eCoC data already received.
  • One of 3 subscriber states receiving every eCoC.
  • Plan against Germany regardless of the transition.
🇵🇱PolandCOI / CEPiKTDT = type approvalPilotingHigh
  • NAP up and in the integration-testing / onboarding phase (COI briefing, 10 June 2026).
  • Producers request access certificates via OWoC and submit a PKCS#10 CSR to COI.
  • Integration tests required before production submissions.
🇫🇮FinlandTraficomRegistration + type approval in one agencyPreparingHigh
  • Confirmed (DGEC FAQ) to run its own NAP.
  • Digital-certificate e-service already live.
🇫🇷FranceUTAC-OTCANTS/SIV = downstream registration onlyPreparingHigh
  • DGEC FAQ (18 May 2026): test environment installed July 2026 for manufacturer trials.
  • NAP not connected to EUCARIS until Q4 2026.
  • One of 3 subscriber states receiving every eCoC.
  • Likely a 29 Nov backstop for live registrations — keep paper until then.
🇮🇹ItalyMIT – Motorizzazione CivileCED (Divisione 7) = likely NAP owner — inference, not announcedPreparingMedium
  • Listed in the DGEC FAQ as planning a NAP — no rollout confirmation since.
  • Circolare 22215/2023 frames 5 July only as a manufacturer option to drop paper; the Nuovo Processo Immatricolativo is still “programmato.”
  • The CED (Divisione 7) already runs Italy's EUCARIS contact point — the near-certain NAP owner, but that is inference.
  • Circolare 17287 (6 July 2026 — the day after the original deadline) reformed registration with no mention of eCoC, EUCARIS, NAP or the NPI.
  • No Italian source acknowledges the 29 Nov transition date.
🇱🇺LuxembourgSNCASNCH = type approvalPreparingMedium
  • Confirmed (DGEC FAQ) to run its own NAP — upgraded from unconfirmed.
  • SNCT (roadworthiness testing) is a different body — not the eCoC authority.
🇵🇹PortugalIMTType approval + registration in one bodyPreparingHigh
  • Live online CoC-submission platform (chnac.imt-ip.pt).
  • NAP-operator status not separately confirmed.
🇷🇴RomaniaRARDRPCIV = registrationPreparingHigh
  • NAP in development, targeted around September 2026.
  • Will generate, validate and upload eCoC-IVI 2.0 to EUCARIS.
🇸🇪SwedenTransportstyrelsenSwedish Transport AgencyPreparingHigh
  • Building an eCoC/IVI database.
  • Will NOT run its own NAP — manufacturers must route via another Member State's NAP.
🇦🇹AustriaBMIMIGenehmigungsdatenbank (central approval database)UnconfirmedMedium
  • The eCoC-responsible body is the central approval database — not a registration office.
  • Registration runs via insurers.
🇧🇪BelgiumFPS MobilityDIV = registration directorate within itUnconfirmedMedium
  • EReg Topic Group XII participant.
  • Production status unconfirmed.
🇧🇬BulgariaIA “Automobile Administration”КАТ / MoI = registrationUnconfirmedMedium
  • NAP status unknown.
🇭🇷CroatiaCVHCentar za vozila HrvatskeUnconfirmedHigh
  • Confirmed (DGEC FAQ) it will NOT run its own NAP — routes via another Member State.
  • CVH coordinates registration + homologation; MUP holds the central register.
🇨🇾CyprusRTDRoad Transport DepartmentUnconfirmedHigh
  • Registration + type approval in one department.
  • NAP status unknown.
🇨🇿Czech RepublicMinistry of TransportUnconfirmedLow
  • “Own NAP” not verified — Czechia isn't in EReg Topic Group XII and was historically only “interested.”
  • May rely on another Member State's NAP.
🇩🇰DenmarkMotorstyrelsenFærdselsstyrelsen = type approvalUnconfirmedMedium
  • eCoC NAP operator not published.
🇪🇪EstoniaTranspordiametRegistration + type approval in one bodyUnconfirmedHigh
  • Digital registration fully live.
  • eCoC NAP status unknown.
🇬🇷GreeceMin. of Infrastructure & TransportRegional transport directoratesUnconfirmedMedium
  • Registration is decentralised to regional directorates; no single acronym.
  • NAP status unknown.
🇭🇺HungaryKAVBM / Nyilvántartó = registrationUnconfirmedMedium
  • KAV is the type-approval authority.
  • NAP status unknown.
🇱🇻LatviaCSDDRegistration + type approval in one bodyUnconfirmedHigh
  • NAP status unknown.
🇱🇹LithuaniaRegitraLTSA = type approvalUnconfirmedHigh
  • Confirmed (DGEC FAQ) it will NOT run its own NAP — routes via another Member State.
  • Regitra receives the eCoC at registration.
🇲🇹MaltaTransport MaltaUnconfirmedMedium
  • National land-transport authority.
  • NAP status unknown.
🇸🇰SlovakiaŠDÚMoI Police = registrationUnconfirmedMedium
  • State Transport Authority (Ministry of Transport) on the approval side.
  • NAP status unknown.
🇸🇮SloveniaMinistry of InfrastructureUpravna enota = registrationUnconfirmedMedium
  • Registration via Administrative Units.
  • NAP status unknown.
🇪🇸SpainDGTNAP operator unpublishedUnconfirmedMedium
  • Closest official statement: Orden PJC/528/2026 (BOE, 29 May 2026) makes the electronic ITV card mandatory for M/N/O and L.
  • The future e-ITV data format — to be set by a DGT resolution — “will be coherent, for M, N and O vehicles, with the eCoC data established in Reg (EU) 2021/133.” That is the only regulatory hook to eCoC.
  • No NAP operator or EUCARIS eCoC connection announced; absent from Italy's 16-country EUCARIS list.
  • Likely a 29 Nov backstop.

Compiled from primary sources (national authorities, Légifrance, the French DGEC FAQ of 18 May 2026, MIT, the VCA, EUCARIS/EReg, Regulations (EU) 2018/858 and 2021/133), verified to mid-July 2026.

The "subscriber state" mechanic

Only Germany, France and the Netherlands subscribe to receive every eCoC submitted to any NAP. Everyone else — authorities and the public — retrieves an eCoC on demand by VIN through a public web interface. There is no automatic routing to your "intended market": the tag exists in IVI 2.0 but is not mandatory, and EUCARIS does not auto-transfer on it. The UK sits outside this entirely — a UK submission stays in the VCA system.

Markets in focus

🇬🇧 United Kingdom

Ahead of every EU market on availability — the VCA portal and API have been live since 17 June 2026. But it is a closed loop: no EUCARIS interconnection, so a UK submission has no effect in the EU and vice-versa. Mandatory 29 November 2026 for GB & UKNI schemes; signed UK IVI 2.0 XML.

🇳🇱 Netherlands & 🇩🇪 Germany

The two most advanced EUCARIS markets, and the two clean single-body cases. RDW has received eCoC data since 2016 and operates the EUCARIS hub; KBA is a named lead NAP with early eCoC data. If you sell into either, treat eCoC capability as a hard requirement now.

🇫🇷 France

The clearest legal architecture — the arrêté of 12 November 2019 tasks UTAC-OTC (not ANTS/SIV) with receiving, checking and storing the eCoC. But per the official DGEC FAQ, the NAP is test-only from July 2026 and won't connect to EUCARIS until Q4 2026. Keep paper until then.

🇪🇸 Spain & 🇮🇹 Italy

Both look like 29 November backstop cases. Spain's only regulatory hook is Orden PJC/528/2026 (BOE, 29 May 2026), which mandates the electronic ITV card and says the future e-ITV format will be "coherent" with eCoC data under Reg 2021/133 — no NAP or EUCARIS connection announced. Italy has kept a conspicuous official silence even after 5 July: the CED (Divisione 7), which already runs Italy's EUCARIS contact point, is the near-certain NAP owner, but that is inference — and MIT's circolare 17287 of 6 July 2026 reformed registration with no mention of eCoC at all. For both, keep issuing paper until the authority confirms otherwise.

The three scenarios you'll face in parallel

1. Live NAP

NL, DE (and the standalone UK). Submit the eCoC digitally; a national paper copy may still be required in parallel.

2. No live NAP, EUCARIS retrieval

Submit through another country's NAP (e.g. RDW) and the destination retrieves via EUCARIS. Sweden, Lithuania and Croatia explicitly rely on this.

3. No NAP, no retrieval

A paper CoC is still required; a digital submission has no legal effect there yet. The default for every "Unconfirmed" market.

What this means for importers and registration agents

  • Map each market to its scenario and its correct authority — don't assume the registration office is the eCoC NAP.
  • Plan a dual regime through 29 November 2026 — paper and digital in parallel; paper doesn't disappear on any single date.
  • Digitally supplied CoCs for vehicles built after the deadline must be eIDAS-signed IVI 2.0 XML — legacy 1.x files must be converted; the paper transition does not authorise unsigned XML.
  • Selling into both the UK and the EU? Submit to the VCA and to the relevant EU NAP separately — there is no interconnection between them.
  • Get your QTSP signing certificate now — it must be from a provider on the EU Trusted List, accepted across all NAPs. It's the longest-lead item.

Methodology & sources

Statuses are compiled from publicly available primary sources and verified to mid-July 2026: Regulations (EU) 2018/858 (Art. 37) and 2021/133 with secure-exchange rules 2024/1061; the French DGEC's Electronic Certificates of Conformity — answers to manufacturers' questions (18 May 2026); the VCA's eCoC guidance; EUCARIS IVI service documentation and EReg Topic Group XII / IVI-NAP guidance; and national authority publications (RDW, KBA, VCA, UTAC-OTC, RAR, IMT, COI/CEPiK, Traficom, Transportstyrelsen, DGT, MIT and others as cited per row).

This is not legal advice and readiness can change without notice — verify with the relevant authority before acting. We revise this page as new information is confirmed; the date at the top reflects the latest revision.

Ready in each market the day it goes live

CoCDesk generates signed, schema-valid IVI 2.0 eCoCs and submits them to the UK's VCA portal and API — and to every EU National Access Point. One pipeline, every jurisdiction.

Book a demo

Ready to meet the UK eCoC deadline?

Book a free demo and see how COCDESK can have your eCoC process production-ready before the VCA mandate takes effect.

Comprehensive eCoC document management system for UK vehicle manufacturers. Full VCA compliance for the November 2026 eCoC mandate.

Barnab Limited

Company number: 15559009

41a St. Stephens Terrace, London, England, SW8 1DL

© 2026 COCDesk. All rights reserved.