Custom EDSN integration for market messages
Suppliers, grid operators, metering responsible parties and other market parties in the Dutch energy market exchange their data via the central systems that EDSN manages on behalf of the joint grid operators, such as the Central Connections Register. Anyone taking part has to show that their own system exchanges correct and complete information with those central systems. Appfront builds the integration into your own software and guides you through testing and qualification.
What is an EDSN integration for market messages?
An EDSN integration for market messages lets your own system exchange data with the central systems of the energy market. EDSN manages those systems on behalf of the joint grid operators. The Central Connections Register (C-AR) holds the data on all electricity and gas connections in the Netherlands, including the supplier, the balance responsible party and the metering responsible party for each connection; according to EDSN, it is the basis for switching supplier and moving home. C-ARM processes allocation, reconciliation and metering data, and through the Meter Data Register, suppliers and other service providers can request meter readings and consumption at the end customer's request. EDSN reports that in 2025 more than nine billion messages were exchanged between roughly 440 market parties.
Only a recognised market party can access the central applications. Since the Energy Act (Energiewet) came into force on 1 January 2026, Het Normo manages participation in the data exchange. According to the ACM (the Dutch Authority for Consumers and Markets), Het Normo acts as the data exchange entity and sets the conditions for participation, while EDSN still operates the central systems. According to Partners in Energie, the portal of the regional grid operators and EDSN, joining takes five steps: registering with Het Normo using eHerkenning, connecting your own system to the central systems, testing and qualification, formal completion with a market role confirmation, and entry to the market. During qualification, you demonstrate in the test environment that your system exchanges correct and complete information.
We build custom software because the part on your side of the connection, the decentral system, has to fit your own processes: your customer records, invoicing, metering data or flexibility services. The integration creates the messages your role requires, processes what comes in and handles confirmations and rejections, so that a connection never silently stays in the wrong status. Every message is logged, so if a grid operator asks a question you can show what was sent and when. In the first step, we work with you to establish which processes and messages apply to your market role, and what is needed for qualification.
Your role
The messages your market role requires.
Qualified
Tested in the test environment.
Traceable
Every message recorded.
How we build your EDSN integration for market messages
We start with your market role and your processes: which data you receive and send, which systems it sits in and where work is still done by hand. Then, for each process, we define which messages your system has to create and process, and what happens in the event of a rejection. We first build the process that matters most for your role, such as switching supplier or metering data, and test it in the test environment. This prepares the qualification that you carry out yourself with EDSN. The remaining processes follow. If the agreements in the sector change, we update the integration.
What you exchange and why.
Create, process, reject.
Proven in the test environment.
Monitoring, and maintenance when new agreements apply.
What an EDSN integration for market messages actually does
The components below appear in almost every integration with the central systems. Which ones you need depends on your market role and on what your current software already does.
Messages
Create and process per process.
Statuses
Connections in the correct status.
Rejections
Errors visible and resolved.
Measurement data
Meter readings and consumption processed.
Test environment
Ready for qualification.
Log
Every message traceable.
Who we build an EDSN integration for market messages for
The integration is intended for parties that take part in the data exchange in the energy market themselves, or are about to, and that do not get their message traffic entirely from an off-the-shelf package.
Energy suppliers
Switching, moving, metering data.
Service providers
Metering data with customer mandate.
Flexibility parties
Congestion and balancing services.
Software builders
Your package on the central systems.
Technology and integrations
This page is about the message traffic between market parties and the central systems of the energy market. If you only want to look up connection details via the public search function, see the EAN codebook integration. For software for an energy cooperative, there is building energy cooperative software, and for flexibility and congestion, the OSCP integration. Registering with Het Normo requires eHerkenning; read more in the eHerkenning integration. You can read about our approach at custom software development.
Why choose Appfront for your EDSN integration for market messages?
A switch that stalls because a rejection went unnoticed, meter data entered by hand, or a qualification that has to be redone because a process doesn't work properly: all of these cost a market party customers and time. That's what we build on: messages recorded per process, rejections you can see, and an integration proven in the test environment.
Process by process
Messages that fit your role.
Visible
Rejections reported immediately.
Proven
Tested before go-live.
Security and privacy in an EDSN integration for market messages
The message traffic contains data about connections, contracts and consumption, and this can often be traced back to individuals. According to EDSN, suppliers process personal data only with the end customer's consent, and EDSN itself acts as a processor on behalf of the grid operators. The integration uses only the data your processes need, with a dedicated account that has exactly the permissions required, and records every message with its time and result.
The integration runs in a European data centre or in your own environment, with encrypted connections and storage. Certificates and access credentials for the central systems are kept secure and are not visible to staff. We agree with you in advance who may send messages and who may only view them.
Frequently asked questions about an EDSN integration for market messages
Questions that energy suppliers, service providers and software vendors in the energy market ask before getting started.
Energie Data Services Nederland is the collaboration platform of the Dutch grid operators. It manages the IT infrastructure and data services that market parties use to handle their processes in the energy market, such as the Central Connection Register (C-AR) and the processing of allocation, reconciliation and meter data.
The Central Connection Register (Centraal Aansluitingenregister) holds the details of all electricity and gas connections in the Netherlands, including who the supplier, balance responsible party and metering responsible party are. According to EDSN, it is the basis for switching and moving processes.
Only recognised market parties. Since the Energy Act (Energiewet) came into force, Het Normo manages participation in the data exchange. You register there with eHerkenning, after which your system is connected and you go through testing and qualification.
During the qualification, a new party demonstrates in the test environment that its own system exchanges correct and complete information with EDSN's central systems. It also checks that you have sufficient knowledge of the processes in the energy market.
The Berichtenbox from Partners in Energie is intended for questions, notifications and requests to grid operators that don't go through automated message traffic. An integration deals with that automated traffic itself.
Not just like that. According to EDSN, changes always go through the grid operator, or through the energy supplier with the end customer's consent. The integration sends the messages your role is allowed to send in a process and handles the responses.
For market parties that want to connect their message traffic to their own processes, new parties that need to qualify, and software vendors that want to support the energy market in their package. If your standard package covers all the processes for your role, you usually don't need a custom integration.
Connecting your system to energy market messaging?
Tell us which market role you have and which systems you work with. We'll show you how an integration handles your message traffic.