When smart‑meter data is unavailable, there can be several underlying causes. Examples include communication issues, local meter faults, planned work in the network, or a meter that has been declared technically not readable. In many cases, suppliers could not distinguish between these situations based on the responses they received from the metering chain.
This lack of transparency leads to several challenges:
Billing processes need to cope with incomplete or missing data and resort to estimates.
Customer portals and apps show empty graphs or generic “no data” messages, which can persist for some time.
Customer service has limited information about whether a meter issue is known to the grid operator and whether any remedial action is planned.
Other topics, such as TS025 (about the functioning of P4 message exchange), already address related aspects of non‑readable meters. TS055 adds a specific focus on structured fault and status information.
TS055 is part of the Dutch May 2026 sector release (previously “Allocatie 2.0 Tranche 4”). Within this release, TS055 concerns the exposure of connection and fault information via APIs. For suppliers, the new element is the availability of smart‑meter fault information; the connection‑information component is more relevant to other roles and is not in scope for this release.
TS055's new API It makes smart‑meter fault information available in a standardised way to relevant market parties, including suppliers. In addition to that, the TS055 API makes the following possible:
Querying whether a particular meter or connection has an active fault.
Receiving information about the type of fault and when it started.
Seeing in which phase of the grid operator’s process the issue currently is (for example, identified, under investigation, scheduled for field work).
This information is intended to be used in automated processes on the supplier side, such as billing exception handling, customer‑service support, and information shown in portals and apps.
The May 2026 sector release combines several topics (including TS023/TS060, TS039, TS040, TS041, TS046, and TS055) that together modernise allocation and metering processes and expand the use of APIs in the metering chain.
For TS055, the sector has defined:
A detailed planning for specification, implementation, and testing.
An early testing phase (the “kopgroeptest”) with a small number of market parties.
A subsequent general acceptance test (GAT) period, in which all parties validate their implementations before go‑live.
The lead-group test (kopgroeptest) allows the sector to verify that the TS055 API behaves as intended in real‑world scenarios before it becomes broadly available.
On the supplier side, Eneve and one of our customers, Zonneplan, participated in the TS055 kopgroeptest. In this context, Eneve implemented the TS055 fault‑information API and used it in end‑to‑end tests for the Supplier market role.
The main activities in this early test included:
Implementing TS055 according to the sector’s business requirements and technical specifications.
Executing scenarios in which Zonneplan requested fault information for meters with different status situations.
Comparing responses from the TS055 API with expectations from the topic documentation and reporting deviations or ambiguities.
The tests have been successfully completed. As a result, Eneve is prepared to use the TS055 API once it is available in sector test and production environments.
Once TS055 is live and supported in supplier systems, several practical improvements become possible.
1. More context for “no data” situations
When meter data is missing, suppliers can use the TS055 API to check whether there is an active fault and, if so, what type of fault and since when. This allows internal users (for example, customer‑service staff) and external users (end customers via portals) to see a more specific explanation rather than a generic “data unavailable” message.
2. Better informed billing logic
Information on the nature and duration of a fault helps suppliers select appropriate estimation or fallback methods when meter data is missing. For example, a short‑lived communication issue may be handled differently than a long‑running technical fault in a meter that cannot be resolved quickly.
3. Support for customer communication
By integrating TS055 into billing and customer‑facing systems, suppliers can more accurately inform customers about known meter issues, whether the grid operator is working on them, and what the expected impact on consumption graphs or invoices might be.
Eneve is an example of a supplier‑side system that integrates TS055 and makes the information available both in internal screens (such as connection detail views) and through passthrough APIs for portals and apps.
https://energiedatawijzer.nl/onderwerpen/voorbereiden-op-de-aankomende-release/mei-release-2026/