Energy data access regulation in Ukraine: existing rights, practical implementation and EDDIE UA proposals
Зміст статті / On this page (20)
- Why this is about more than building another API
- Four different kinds of statements on this page
- Electricity Market Law 2019-VIII and the statutory commercial metering administrator
- What Law 4834-IX changed on 7 April 2026
- Commercial Metering Code 311: the rules that already exist
- Who is responsible: AKO, PPKO, DSO, BRP, aggregator and customer
- Metering points and EIC: why an identifier is not a password
- An end-to-end case: independent aggregator working with an external BRP
- The actual November 2026 draft amendment to the Metering Code
- Why the NCRECP meeting of 24 November 2026 is important
- Six targeted improvements proposed by EDDIE UA
- Why historical metering data must not be confused with device control
- European comparison: reference requirements, not direct Ukrainian legal rules
- Where should amendments be made: Law, Code or existing AKO procedures?
- Central API, technical federation or multiple statutory administrators?
- Twelve proposed acceptance tests for an interoperable access framework
- Economic and regulatory impact evidence
- What EDDIE UA should do after 24 November 2026
- Conclusion: preserve authoritative metering, improve the right to use data
- Primary sources and related research
Why this is about more than building another API
Ukraine's electricity consumers increasingly operate solar PV, energy storage, EV chargers, heat pumps, industrial refrigeration and other flexible resources. These assets can potentially shift consumption, reduce peaks and provide market services. But deciding what equipment to install, what load can actually move and whether a service will produce positive net value depends on trustworthy data.
A cold-storage operator, for example, may want two competing aggregators to evaluate its electricity history before considering battery storage. Both service providers require the same correctly scoped, quality-labelled historical intervals. The customer should not have to switch supplier or balancing arrangements, disclose its corporate password or give either candidate unrestricted access to every metering point. Conversely, the provider cannot receive confidential readings merely because it knows the customer's EIC.
The regulatory challenge is to make lawful, non-discriminatory information access operational and verifiable, without weakening commercial metering integrity or transferring statutory functions by software design. A missing API URL in our research is not proof that no authorised access procedure exists. The general duty to provide access in a statute is likewise not proof that every user-facing process is already implemented.
Four different kinds of statements on this page
Law in force means legislation or a regulatory decision that has legally entered into effect for a given purpose and date. Current consolidated wording and transitional clauses matter.
Regulatory draft means proposed text published for approval, consultation or adoption. A draft may guide planning but does not acquire statutory force merely because it is public.
EDDIE UA proposal means a possible technical or procedural improvement suggested for discussion. It is not a binding duty or an approved Ukrenergo operation.
Tested research software means code that passed a defined synthetic test in a stated environment. A successful test cannot issue a legal permission, certify security or establish that official market data can be retrieved.
Every significant recommendation should be read in light of the distinction. Future policy updates must retain a dated version history rather than silently replacing old drafts.
Electricity Market Law 2019-VIII and the statutory commercial metering administrator
Ukraine's Electricity Market Law No. 2019-VIII establishes the institutional structure. Article 53 addresses the commercial metering administrator (AKO) and its functions. The statutory function is assigned to the transmission system operator; in the relevant Ukrainian context, that involves NPC Ukrenergo.
Commercial metering supports the reliable determination of electricity produced, consumed, transmitted, distributed, imported and exported for market settlement and other authorised purposes. Metering service providers (PPKO), metering points (TKO), measurement validation and correction procedures all have roles in this system. An external technical node does not become a second statutory AKO simply by serving an API response.
EDDIE UA therefore does not propose several conflicting official settlement records. It explores information-access interoperability while preserving the legal responsibility of competent parties. Whether an independent company can lawfully operate a particular access or permission service is an institutional question requiring specific analysis, not an automatic consequence of a distributed architecture.
What Law 4834-IX changed on 7 April 2026
Law No. 4834-IX, which entered into force in April 2026 subject to its transitional provisions, materially changes the problem statement. It is no longer appropriate to say that Ukrainian law entirely lacks a basic non-discriminatory access principle.
Article 53(6), as amended, provides for non-discriminatory access by legally eligible parties to customer information through the AKO in accordance with the Commercial Metering Code, including data relevant to changing supplier or aggregator and demand response. The regulator monitors implementation of the relevant measures. Eligible parties still need a proper legal entitlement; a metering-point identifier alone is not sufficient.
Article 74(9–10) adds organisational and technical oversight of non-discriminatory access and the principle of clear and equal conditions, with the required data protections. The framework already acknowledges access neutrality and monitoring. Our research should therefore concentrate on how these obligations are implemented and independently evidenced.
Article 74-1 addresses smart metering deployment, minimum requirements and consumer access. Among its important provisions is the right of a consumer to receive its own commercial metering data without charge and to share those data with other persons in accordance with data-protection requirements. This must not be misrepresented as a promise that any new smart meter will be installed free of charge: the law also addresses economic feasibility and disclosure of installation or upgrade costs.
The implication is straightforward: EDDIE UA should focus on identity, legal representation, relationship to a metering point, allowed purpose and scope, documented requests, refusal and appeal, withdrawal, audit, interoperability and fair competition. Legal applicability and individual commencement dates should be checked against the official consolidated text before formal submissions.
Commercial Metering Code 311: the rules that already exist
The Commercial Metering Code, NCRECP Resolution No. 311 of 14 March 2018, is a core implementing instrument. It has been amended repeatedly, including by Resolutions No. 841 of 2 June 2026 and No. 1358 of 11 August 2026. The applicable consolidated version must be established before any clause-by-clause legal submission.
Under the project's existing verification register, Code paragraph 2.2.2 already includes authorised access to reference data for appropriate parties and the technical ability to receive, preserve and transmit relevant metering data to legally entitled recipients with protection in place. Section IV addresses the metering-point register and EIC. Section IX addresses data integrity, confidentiality, quality, validation and corrections.
The law and Code may specify the function without prescribing a particular programming library or web route. Relevant operational details may already exist in separate AKO procedures. It would be careless to demand a new duty before obtaining and comparing the current approved procedures, technical contracts and published documentation.
Who is responsible: AKO, PPKO, DSO, BRP, aggregator and customer
The commercial metering administrator (AKO) performs the functions assigned by law and the Code. A private data-access gateway cannot assume those statutory powers through an informal agreement.
Metering service providers (PPKO) perform the metering activities for which they are lawfully responsible, which may include collecting, preparing or transmitting measurement information according to applicable arrangements. A software integrator is not automatically a registered PPKO.
Distribution system operators (DSOs) have separate grid, metering-related and contractual responsibilities, depending on the point. The transmission operator has its own designated functions. Physical proximity to a meter is not enough to determine every information entitlement.
The balancing responsible party (BRP) has market obligations for imbalance responsibility. A customer's choice to consult a separate independent aggregator does not automatically change its BRP, nor does it automatically grant the aggregator statutory access to all metering records.
An independent aggregator may have a legitimate business reason to evaluate historic consumption and flexibility. Nevertheless, information access, joining an aggregation group, changing balancing relationships, qualifying for market services and issuing device commands are separate procedures.
A customer and its representative must be lawfully entitled to initiate the relevant process. In a business context, company ownership, building tenancy, contractual consumption, current management and a person holding a power of attorney may have different implications across time periods.
This is why entering a company registration number plus an EIC is only the beginning of identity resolution, not proof of entitlement.
Metering points and EIC: why an identifier is not a password
A metering point (TKO) links information to a defined metering arrangement. EIC identifies the relevant energy-market object in the information process, but possession of the code does not prove a legal relationship.
Consider an industrial tenant that occupied a warehouse only from March through August. An unbounded request for the previous year could expose a different company's data. Or consider a consultant who copies the EIC from an electricity bill but has not been authorised by the customer. A secure gateway must not reveal confidential intervals merely because both identifiers are syntactically correct.
The proposed EDDIE UA workflow therefore distinguishes representation, the legal relationship to the point for the requested time, data categories, purpose, recipient, access period and the applicable legal basis. Actual proof sources and procedures must be determined by competent institutions, not invented by the prototype.
An end-to-end case: independent aggregator working with an external BRP
Imagine a food-processing facility that operates refrigeration, rooftop solar and potentially battery storage. It has an existing supplier and BRP but invites a competing aggregator to assess whether demand response would be valuable.
Step 1 – applicant. The company and its authorised representative are verified. Company registration data alone are insufficient.
Step 2 – metering scope. The relevant EIC or metering points are determined, including changes in lawful rights during the requested historical period.
Step 3 – legal entitlement. The lawful basis, purpose, eligible recipient, data categories, historical window and any access to subsequently produced data are established.
Step 4 – authorised information request. The competent service returns appropriately validated intervals with source, unit, quality, versions and corrections.
Step 5 – independent assessment. The aggregator examines peaks, potential flexible loads and possible battery sizing. This analytical work is not equivalent to market qualification or physical control authority.
Step 6 – access lifecycle. Relevant access events are recorded; expiration or withdrawal under the applicable procedure is enforced. Retention and other lawful bases for previously received data are evaluated separately.
Step 7 – any later market decision. If the customer accepts a market offer, aggregator agreements, BRP relations, metering qualifications, imbalance exposure and other obligations must be handled under their own rules. A data permission itself does not change supplier or BRP.
This is a proposed illustrative workflow, not a claim that one official production DataHub interface currently executes the entire sequence. The research question is how to make it repeatable and lawful without privileged integration.
The actual November 2026 draft amendment to the Metering Code
The project's internal REG-006 review examined a supplied 20-page draft of a proposed NCRECP resolution amending Code No. 311: an introductory justification, draft resolution and proposed substantive changes. The reviewed document did not contain the adopted date or number of a final resolution. It must therefore not be presented as an enacted instrument.
Proposed section 1 and definitions address secure exchange, interoperability and near-real-time information. We should not propose these concepts as completely absent from the draft.
Proposed points 2.2.2(24–29) cover non-discriminatory access, neutral conditions, public procedures, monitoring and compatible data formats. Much of the overarching policy principle is already included.
Proposed points 5.14–5.15 address smart meters, local communication and open formats, certain protocol documentation duties, intervals and near-real-time information. The precise availability of technical documentation is limited by the proposed text; this is not a promise of universal public access to every proprietary meter protocol.
Proposed point 9.1.2 concerns lawful bases, requests, permission termination, identification, authorisation and documentation. Some wording around further requests after withdrawal warrants focused legal consideration.
Proposed point 9.1.3 addresses a consumer's own history and transfer to eligible recipients. It should not be described as an entirely new EDDIE UA concept.
Proposed points 9.1.4–9.1.10 cover timestamps, versioning, preservation and correction. The useful contribution is reproducible conformance test data rather than restating the principles.
Proposed points 9.1.11–9.1.13 set out machine-to-machine exchange categories, portal functions, notification, access separation and logs. REG-006 identifies eleven types of M2M process. These are proposed functions, not independently verified production endpoint URLs or a published third-party sandbox.
Proposed points 9.1.14–9.1.15 and 12.2.4–12.2.7 address data quality and disputes, smart meter installation or upgrades, compatibility and disclosure of associated costs.
This overview is based on the user-provided draft as previously analysed in the project and does not replace an independent verbatim comparison with the officially published text. An issue not described in this particular PDF may already be covered by another AKO procedure.
Why the NCRECP meeting of 24 November 2026 is important
The official NCRECP agenda for 24 November 2026 includes item 29: consideration of approving a draft regulatory act proposing amendments to Code No. 311 in implementation of Law No. 4834-IX.
As of the article's date, 21 November 2026, this meeting is still in the future. There is no basis to claim that the draft has been adopted or entered into force. Even if the regulator approves the draft on 24 November, that intermediate step must be distinguished from consultation, adoption of a final resolution, publication and the effective date.
Our next source review should compare the Code in force, the actual published draft at its relevant procedural stage and the final enacted amendment – only if and when the latter exists. The historical record should be dated and retained.
Six targeted improvements proposed by EDDIE UA
Proposal 1 – Make the effect of permission withdrawal unambiguous
The goal is not to invent permission management. The examined draft already addresses it, but the wording on readings entered into DataHub after termination leaves an important question about re-downloading previously existing history after revocation.
The proposed principle is to stop new requests relying solely on the terminated legal basis from the correct effective time, unless the law provides otherwise. This must be distinguished from the legality of already received copies and any separate lawful processing basis. The competent procedure should establish notice, effective time and auditable propagation.
Suggested tests: a permitted read before termination, a new request afterward, an attempted re-download of an old interval, an in-flight request, a separate lawful entitlement and the resulting audit record. Final clause language requires legal review.
Proposal 2 – Publish reproducible access and interoperability scenarios
The draft already addresses public procedures and interfaces, so EDDIE UA does not need to ask for an API in the abstract. It should be possible for an eligible third-party developer to exercise a documented operation with synthetic data, understand its state and denial reasons, identify contract versions and prepare for a supported schema change.
Suggested tests: independent implementations handle the same permitted and denied examples, expired rights, inconsistent scopes, malformed data and incompatible versions. The actual technology and official endpoints must be specified by the competent provider, not invented by Wesfin.
Proposal 3 – Measure equal treatment without disclosing protected profiles
Existing law and the draft establish non-discrimination. We suggest a method to examine whether that principle is realised through onboarding counts, substantiated refusal categories, median and p95 times, withdrawal latency and incident resolution.
Different types of request may have different legal prerequisites and must not be compared indiscriminately. Aggregate reporting needs proper privacy safeguards. No numerical service-level agreement becomes law merely because a researcher suggests it.
Proposal 4 – Document an independent aggregator with an external BRP
This is the core C&I use case: a verified corporate representative, a specific metering point, a legal basis, limited historical data, an unrelated aggregator, the existing supplier and an external BRP.
The relevant authorities should clarify the permitted information flow. Tests should prove that legitimate data access does not change balancing membership or supply relationships, and that an unverified representative cannot receive protected readings. This scenario might be documented in an existing authorised technical procedure.
Proposal 5 – Standard test fixtures for time, quality and revisions
The examined draft already refers to interval boundaries, ISO 8601 and versioning. Rather than duplicating the rule, provide machine-readable cases for 15-minute and other relevant periods, 23-hour and 25-hour daylight-saving days, missing data, estimated/substituted readings and revision history.
Tests must reject interpreting missing as zero, losing the provenance of corrections, swapping import/export direction or double counting a repeated local hour. Actual settlement treatment remains subject to the official Code and related procedures.
Proposal 6 – Neutral conformance for smart-meter local reading
The legislation and draft address smart-meter compatibility with energy management systems. A useful practical step would be agreed read-only local profiles, with time, sample age, direction, units, quality and appropriately secured activation, while protecting metrology and customer privacy.
EDDIE UA does not propose using DataHub as a second-by-second dispatch route for battery PCS, BMS, industrial HVAC or EV chargers. Reading local telemetry and commanding physical equipment are different permissions.
These six items are a consultation agenda, not approved amendments or comments officially filed with NCRECP. Their necessity must be checked against existing AKO rules and the competent authority's mandate.
Why historical metering data must not be confused with device control
An official validated interval supports commercial accounting and lawful information exchange. A local inverter or industrial controller may instead produce second-by-second measurements, SoC, available charging power and operational alarms. Those readings can be provisional and have a different measurement and legal status.
A site controller such as Wesfin Edge must respect hardware protections, BMS safety, grid protection, local reserve rules and customer restrictions regardless of what a cloud optimizer requests. The lawful access to historic EIC data does not permit a cloud service to bypass those limits. DataHub is not the control channel for physical inverter registers.
A credible data platform needs explicit provenance, timestamp, quality and intended use for each class of value. A near-real-time sample is not automatically official settlement data.
European comparison: reference requirements, not direct Ukrainian legal rules
Directive (EU) 2019/944 and Commission Implementing Regulation (EU) 2023/1162 provide useful reference principles for independent aggregation, customer data access, permissions, interoperability and smart-meter information.
A complete implementation mapping distinguishes six procedures: a final customer requesting historic validated readings; an eligible service provider accessing those readings; the service provider terminating its service; the customer revoking an active permission; activation of near-real-time smart-meter access; and subsequent reading by a compatible device. A service terminating and a customer withdrawing permission are not the same process, just as validated history is different from fast local telemetry.
EU law does not itself require several statutory Ukrainian AKOs or a DNS-inspired federation. Its relevance must be analysed through domestic legislation and Ukraine's applicable Energy Community obligations. A research traceability matrix is not legal certification.
Read the EU rule-to-process guide and the separate Horizon Europe EDDIE history.
Where should amendments be made: Law, Code or existing AKO procedures?
The most proportionate approach begins by checking whether the existing rule already permits the intended process.
Level 1 – Current AKO procedures and documentation. If legal entitlement and the required interaction already exist but are difficult to discover or test, publish or clarify the corresponding procedure and conformance examples first. This may be the fastest and least expensive solution.
Level 2 – Commercial Metering Code and NCRECP decisions. If an access lifecycle, accountability duty, monitoring requirement or dispute procedure lacks sufficient normative clarity, targeted amendments may be appropriate within the regulator's mandate. The text must remain technology-neutral and must not compel use of a proprietary Wesfin service.
Level 3 – Related market rules. If the question concerns balancing responsibility, supplier or aggregator status, qualification or settlement, establish which existing market or retail rule applies. Do not silently embed commercial relationship changes in a technical metering-data API.
Level 4 – Primary legislation. Creating a new mandatory institutional status or altering statutory competence may require legislative amendment. That determination must follow an independent legal opinion, not an engineering preference for more nodes.
The default should be to verify the cheapest legally sound route before proposing an extensive reform.
Central API, technical federation or multiple statutory administrators?
Alternative A – the statutory AKO operates an open, well-documented, geographically redundant central interface with standard entitlements. It may already satisfy most goals with simpler accountability and fewer security boundaries.
Alternative B – one statutory AKO plus legally permitted interoperable information-service nodes. Possible gains include reusable local adapters and implementation competition; added obligations include trust directory, certificates, cross-operator audits, recovery and more complex governance.
Alternative C – multiple statutory commercial metering administrators. This would require a fundamentally different legal framework and justification; it is not implied by a technical federation and is not currently recommended.
We should evaluate legality, privacy, resilience, equal access, implementation hours, CAPEX/OPEX and five-year total cost under equivalent workloads. No verified evidence yet justifies promising a fixed percentage saving from federation. See the economic comparison.
Twelve proposed acceptance tests for an interoperable access framework
T01 – Representation. A requester knowing correct company and EIC identifiers but lacking verified authority must not receive confidential readings.
T02 – Scope. A lawful recipient may access the specified metering point and period, not every point or historical interval.
T03 – Neutral third-party onboarding. Two comparably entitled service providers can use the documented process without privileged software configuration.
T04 – External BRP. Reading history cannot by itself switch supplier, BRP, aggregation group or market obligations.
T05 – Revocation. New requests relying solely on an expired or withdrawn basis are rejected, with separately lawful retention considered independently.
T06 – Expiration and replay. Duplicate requests, old permissions and changes in representation do not create unintended new access.
T07 – Correction history. A fabricated 100.0 kWh reading and its later 97.5 kWh correction retain reproducible revision and source records. These are illustrative values, not actual metering data.
T08 – Time and data completeness. Half-open intervals, daylight-saving transitions, missing values, units and import/export directions remain unambiguous.
T09 – Failure of a technical access node. New confidential disclosures do not proceed on the basis of arbitrary stale cached authority.
T10 – Technical authority transfer. Nodes A and B must not both publish contradictory confirmed authority for the same synthetic record; production claims need separate machines, keys and network partition testing.
T11 – Public procedures and appeal. The eligible integrator can find current contracts, schema versions, denial categories and a legitimate appeal route.
T12 – Audit and privacy. Relevant authorised subjects can examine appropriate access history, while outsiders cannot enumerate other customers' readings.
These are EDDIE UA proposed tests, not an approved NCRECP certificate or admission checklist. Some synthetic behaviours have been demonstrated; all twelve have not been independently validated in a production multi-organisation deployment.
Economic and regulatory impact evidence
A proposal should measure both benefit and implementation cost. Useful evidence includes request volumes and recipient categories, engineer-hours per integration, time to verify entitlement, median/p95 access time, denial categories, correction and withdrawal latency, incident rates, security and PKI costs, certificate rotation and ongoing operational expense.
The analysis should include privacy risk, protection cost and the ability to serve smaller customers. Gross revenue for a specific aggregator is not the same as net social benefit from an information platform. The same market service might operate through an improved central API.
Conservative, Base and Optimistic scenarios must have documented assumptions and grounded input prices. In the absence of measured figures, neither artificial savings percentages nor invented regulatory response deadlines should be published.
What EDDIE UA should do after 24 November 2026
Stage A – Verify the regulator's actual decision. Retrieve the official meeting outcome and any approved text; record whether the act is a draft, a final decision or an effective provision. Check consultation deadlines only when formally published.
Stage B – Compare clauses verbatim. For relevant provisions of 2.2.2, 5.14–5.15, 9.1.2–9.1.15 and 12.2.4–12.2.7, maintain an evidence register of current text, published draft, question, proposed wording and rationale. Check whether other AKO instruments already resolve each issue.
Stage C – Consult institutional and market actors. Seek lawful process descriptions from the AKO, PPKO, DSOs, aggregators and BRPs. Do not place real EIC identifiers or confidential customer histories into a public synthetic test.
Stage D – Arrange independent legal and security review. Evaluate competence, data protection, independent access-provider status, conflicts of interest, incident responsibilities and any conditions for a limited lawful pilot.
Stage E – Run conformance and impact tests. Exercise the proposed T01–T12 matrix, compare independent implementations and evaluate A versus B with the same workload and cost assumptions.
Stage F – Submit only an approved proposal. Final comments to a competent authority should have checked exact clause wording, supporting evidence, legal sign-off and project-owner approval. A draft on this website is not an official filing.
Conclusion: preserve authoritative metering, improve the right to use data
EDDIE UA advocates a clear principle: lawfully entitled customers and service providers should understand how to obtain the data they need, how their rights are verified, how an access decision can be challenged, how permissions expire and where a particular reading originated. Neutrality needs measurable evidence; security needs independently tested controls; economic benefits need a real comparator.
We do not propose abolishing the AKO, establishing several contradictory official settlement records, exposing any customer's private history through an EIC-only lookup, or dispatching batteries through DataHub. We are studying how existing access rights can be implemented credibly and whether open standards or appropriately governed technical services would help.
Primary sources and related research
- Electricity Market Law No. 2019-VIII – statutory structure and AKO functions.
- Amending Law No. 4834-IX of 7 April 2026 – non-discriminatory access and smart metering provisions.
- NCRECP Commercial Metering Code No. 311 – implementing legal framework.
- NCRECP Resolution No. 841 of 2 June 2026 – earlier adopted Code amendment.
- NCRECP Resolution No. 1358 of 11 August 2026 – earlier adopted Code amendment.
- Official NCRECP agenda for 24 November 2026, item 29 – scheduled draft approval, not proof of final enactment.
- Directive (EU) 2019/944 – European reference framework.
- Commission Implementing Regulation (EU) 2023/1162 – EU functional and procedural reference model.
- EU procedures, EDDIE UA architecture, practical use cases, questions and answers.
Source limitation: the descriptions of individual November 2026 draft clauses are derived from a user-supplied 20-page draft already analysed in the project's internal REG-006 source register. They are not a newly certified verbatim comparison against a final adopted text. An independent legal review and source update are required after the 24 November procedural event.

