Charge point operators that operate public charge points are required to report on a specific data set as stated by AFIR. In this article, you will learn what National Access Points are, what NAP reporting is, and how to comply with AFIR article 20.
Since April 14, 2025, every charge point operator (CPO) managing publicly accessible charging infrastructure in the EU must report detailed charging station data to their country's National Access Point (NAP).
This requirement, mandated by Article 20 of the Alternative Fuels Infrastructure Regulation (AFIR), represents a shift in how charging data is shared across Europe.
The Commission can issue recommendations to Member States to ensure compliance, and non-compliance may result in fines. Yet many CPOs are still navigating the technical complexities of multi-country NAP integrations, evolving data standards, and an upcoming 2026 deadline (see further in the blog) that will add another layer of requirements.
This guide explains everything you need to know about NAP reporting: what data you must share, the technical requirements, key deadlines, including the critical DATEX II mandate, and how to approach compliance efficiently.
What is AFIR Article 20 and what is NAP reporting?
The Alternative Fuels Infrastructure Regulation (AFIR) is the EU's framework for accelerating the deployment of alternative fuel infrastructure, including EV charging stations. As part of the broader 'Fit for 55' climate strategy, AFIR establishes mandatory targets and standards to ensure charging infrastructure is accessible, transparent, and interoperable across all member states.
Article 20 requires CPOs operating public or semi-public charge points to make both static and dynamic charging data available through their country's National Access Point (NAP).
Each EU member state operates its own NAP—a centralised platform that collects and publishes charging infrastructure data.
These NAP platforms serve multiple purposes as they:
- help EV drivers find available chargers,
- enable authorities to monitor infrastructure deployment, and
- support eMSPs (e-Mobility Service Providers) in delivering seamless charging experiences.
The core principle is transparency and accessibility. By making this data freely available in a standardised format, AFIR aims to eliminate fragmentation in the European charging landscape and create a truly interoperable network where drivers can charge anywhere without friction.
Importantly, while AFIR is an EU regulation, similar reporting frameworks exist in the UK (under PCPR - Public Charge Point Regulations), Switzerland (Road Traffic Act), and Norway (Nobil). For CPOs operating across multiple European markets, this means navigating several parallel compliance obligations.
What data must be reported under Art. 20 AFIR?
AFIR distinguishes between two types of data, each with different update requirements and use cases.
Static data
Static data describes the fundamental characteristics of your charging infrastructure. This information changes infrequently—typically only when you modify your station setup, pricing structure, or operational parameters. According to AFIR, static data must be updated within 24 hours of any change.
Required static data includes:
- Geographic location.
- Number of connectors.
- Number of parking spaces for people with disabilities.
- Contact information of the owner and operator.
- Opening hours.
- ID codes, at least of the recharging point operator.
- Type of connector.
- Type of current (AC/DC).
- Maximum power output (kW) of the charging station.
- Maximum power output (kW) of the charging point.
- Vehicle type compatibility.
Dynamic data
Dynamic data reflects the real-time status of your charging infrastructure. This information changes continuously as drivers plug in, sessions complete, and chargers experience operational issues. AFIR mandates that dynamic data is updated within one minute of any status change—a requirement that necessitates automated, always-on data feeds.
Required dynamic data includes:
- Operational status (operational/out of order).
- Availability (in use/not in use).
- Ad hoc price.
- Electricity supplied is 100% renewable (yes/no).
The one-minute update requirement for dynamic data is particularly significant. It effectively requires real-time integration between your CPMS (Charge Point Management System) and your NAP reporting mechanism—manual updates are not feasible.
Key NAP reporting deadlines you need to know
Understanding the timeline for NAP reporting compliance is crucial, especially with an important upcoming deadline that will affect all CPOs.
April 14, 2025 – NAP data sharing mandatory (NOW ACTIVE)
Obviously, this deadline has already passed. As of mid-April 2025, all CPOs operating publicly accessible charging infrastructure in the EU were required to begin sharing both static and dynamic data through their country's NAP.
The data can be provided in various formats depending on each member state's technical specifications. Many NAPs accept the OCPI (Open Charge Point Interface) protocol, particularly version 2.3.0, which was the first OCPI version specifically designed to align with AFIR requirements.
April 14, 2026 – DATEX II standard becomes mandatory (NOW ACTIVE)
This is the critical upcoming deadline that many CPOs haven't yet prepared for. Starting April 14, 2026, all charging infrastructure data submitted to NAPs must be provided in DATEX II format.
DATEX II is a European standard (CEN/TS 16157) originally developed for exchanging road traffic and travel information. It provides a common, machine-readable data model that ensures consistency and interoperability across national borders. While many NAPs currently accept data in OCPI or other formats, this flexibility ends in April 2026.
The shift to DATEX II represents more than just a technical format change. It's about creating a truly harmonised data ecosystem where information flows seamlessly between national systems, eventually feeding into a central European access point.
For CPOs, this means either:
- implementing DATEX II data transformation in your own systems;
- working with a CPMS provider or roaming platform that handles DATEX II conversion; or
- partnering with a service provider that manages NAP reporting entirely on your behalf.
The complexity here shouldn't be underestimated. DATEX II has its own schema requirements, validation rules, and country-specific implementation profiles. Getting this wrong can result in data rejection, compliance gaps, and potential penalties.
Why NAP reporting is complex
While the principle sounds straightforward, the practical implementation of NAP reporting presents several challenges.
Differing international requirements and tools
Each EU member state operates its own NAP with different technical architectures, API specifications, and data validation rules. Germany's Mobilithek works differently from the Netherlands' NDW or France's transport.data.gouv.fr. If you operate across multiple countries, you're managing multiple integrations, each with its own requirements.
Evolving NAP requirements
NAP requirements continue to evolve. The April 2026 shift to mandatory DATEX II is one example. This creates ongoing maintenance—someone needs to monitor regulatory changes, understand new technical requirements, and update data feeds accordingly.
How to simplify NAP reporting
For CPOs using GreenFlux's Managed Roaming service, NAP reporting is available as an add-on that handles the entire compliance process on your behalf.
We extract the required static and dynamic data from your charging infrastructure, transform it into the appropriate formats for each country's NAP (including DATEX II), and maintain ongoing data feeds that meet all update requirements. You don't need to integrate with NAPs directly, implement data transformations, or monitor regulatory changes.
Our service covers all EU member states plus the UK, Switzerland, and Norway. When you expand into new markets, NAP compliance comes automatically—no additional integration work needed. We monitor regulatory changes across all covered countries with our integration partners and update our systems when requirements change, so you stay compliant without allocating resources to track updates.
This means:
- No extra tech stack.
- No new vendor relationships to manage.
- No operational overhead.
You stay fully compliant with AFIR Article 20, DATEX II requirements, and country-specific NAP regulations while focusing on operating your charging network and serving your customers.
Getting started
NAP reporting is available as an opt-in add-on for CPOs using GreenFlux's Managed Roaming service. If you're already a customer, you can add it to your service package. If you're evaluating roaming solutions, we can include NAP compliance from the start.
'Someone needs to monitor regulatory changes, understand new technical requirements, and update data feeds accordingly.'
What are the benefits of our NAP reporting service? This service is designed for CPOs who:
- operate publicly accessible charging infrastructure across Europe;
- want to avoid the technical complexity of managing NAP integrations directly, and
- prefer a consolidated approach where roaming and compliance reporting are handled together.
Ready to simplify your NAP compliance?
With the DATEX II mandate approaching in April 2026, now is the time to ensure your NAP reporting is handled efficiently. Contact us to learn how GreenFlux's Managed Roaming with NAP reporting can keep you compliant across all European markets—without the technical complexity.
