Short answer for investors

Romanian power-market rules matter because licensing scope, aggregation logic and balancing exposure can reshape how a project earns and how investors value it.

Why this matters in practice

Practical legal guidance on Romania's licensing boundaries between trading and system-grade aggregation.

Practical legal guidance on Romania's licensing boundaries between trading and system-grade aggregation.

A market distinction that looks subtle - until it breaks a business model

Romania separates market-facing trading from system-facing aggregation through licensing scope, market rules and TSO validation.

Across Europe, Virtual Power Plants have become a familiar concept. Batteries, renewables and flexible demand are bundled together, optimised through software, and presented to markets as a single, intelligent resource. In many jurisdictions, that model extends naturally into short-term wholesale markets.

It is therefore unsurprising that companies entering Romania often assume the same logic applies.

The problem is that Romania's market design draws a line in a different place - and that line is legal, operational and enforceable.

In Romania, trading electricity and aggregating flexibility are not just different commercial strategies. They are different legal functions, governed by different rules, validated by different authorities, and carrying very different risk profiles.

Failing to understand that distinction does not just create theoretical exposure. It can derail market access, trigger regulatory scrutiny, and undermine bankability.

Trading and aggregation: similar tools, different legal meanings

From the outside, modern trading desks and aggregators often look alike. Both use advanced algorithms, forecast prices, optimise portfolios and control dispatch schedules. This visual similarity is precisely where confusion begins.

Under Romanian law, however, the distinction does not turn on technology. It turns on where responsibility and control sit.

Trading, in legal terms, is a market-facing activity. A trader participates in organised markets, submits bids and offers, settles transactions and manages imbalances, either directly or through a balance responsible party (PRE/BRP). Trading may involve assets owned by third parties, and it may involve sophisticated optimisation, but it remains anchored in market participation.

Aggregation, by contrast, is not defined by commercial convenience. In Romania, aggregation is treated as a system-facing function. It involves the pooling of multiple assets into a resource that can be activated, measured and enforced at system level. That difference matters because system-level actions affect frequency, congestion and security of supply - responsibilities that sit squarely with the Transmission System Operator.

This is why the Romanian framework does not treat aggregation as "trading plus software". It treats it as a different activity altogether.

The three gates every business model must pass

A useful way to understand Romania's market architecture is to think in terms of three regulatory gates.

The first gate is licensing. Any activity must fit within the scope of an ANRE licence and the rights expressly granted under that licence. Trading, supply, production and aggregation are not interchangeable labels; they carry different regulatory expectations.

The second gate is market access. Participation in Day-Ahead and Intraday markets is governed by OPCOM rules and conventions. These instruments determine how participants may trade, including whether they do so individually or through recognised forms of aggregate market participation.

The third gate is system operation. Anything that affects balancing, dispatch or real-time system behaviour falls under Transelectrica's authority. This is where aggregation, in its legally meaningful sense, is validated - through technical integration, testing and confirmation of capability.

A participant may pass the first two gates and still fail the third. That is not a loophole. It is by design.

What trading on DAM and ID really allows

Romania's Day-Ahead and Intraday markets are participant-centric. Orders are submitted by participants, cleared by the market operator, and settled under EU market coupling rules. Even where OPCOM rules recognise aggregate market participation, the market continues to see a single contractual counterparty, with a single balance responsibility.

This matters because market aggregation is not the same as system aggregation.

Market-level aggregate participation allows a participant to represent multiple assets commercially. It does not create a system-recognised unit, does not confer dispatch authority, and does not involve validation by the TSO. The market clears trades; it does not supervise how a portfolio behaves in real time.

In other words, DAM and ID remain trading markets - even where aggregation is used as a commercial interface.

Where aggregation truly begins in Romania

The point at which aggregation becomes legally meaningful in Romania is not in OPCOM documentation. It is in Transelectrica's operational framework, specifically the procedure for confirmation of aggregation capability.

That procedure is not optional, and it is not cosmetic. It requires the aggregator to demonstrate technical architecture, real-time communication, SCADA/EMS integration, performance testing and compliance under TSO command. Only once these steps are completed do aggregated units exist as recognised system resources.

This is why aggregation in Romania is, today, inseparable from the balancing market. That is where flexibility becomes system-relevant, and that is where the law insists on technical validation.

Why labels do not save you

One of the most common mistakes in this space is assuming that contractual language or marketing terminology can redefine regulatory reality.

They cannot.

Romanian regulators and the TSO apply a substance-over-form approach. If a company pools assets, centrally controls them, and presents itself as a single flexible resource capable of system response, it will be assessed as an aggregator - regardless of whether it calls itself a trader.

That assessment has consequences. Without the right licence scope and without TSO validation, the activity becomes exposed: to enforcement, to access refusal, and to adverse conclusions in financing and M&A due diligence.

Why investors and banks care so much

From a financing perspective, the distinction between trading and aggregation is not semantic. It goes directly to risk allocation.

Trading risk is familiar: market exposure, credit risk, imbalance settlement. Aggregation introduces additional layers: system integration risk, performance risk, regulatory dependency and enforcement risk. Lenders and investors will always ask whether the activity being financed is actually permitted, validated and enforceable under the applicable framework.

When the answer is unclear, capital becomes expensive - or unavailable.

Clarity beats optimism

Romania's power markets are not hostile to innovation. They are, however, legally conservative where system security is concerned.

Trading and aggregation coexist, but they do so under different rules, with different authorities and different consequences. Understanding where one ends and the other begins is not just good compliance practice. It is a prerequisite for building a business model that survives regulatory scrutiny and attracts capital.

In Romania, aggregation is not trading with better software.
It is a different activity, at a different gate, with different obligations.

Ignoring that reality is not bold. It is risky.

Contact

Horia Grigorescu

+40 744 310 710

If you are entering the Romanian power markets and need a clean map of what is permitted on DAM/ID vs. what requires separate aggregation qualification and balancing integration, share a short summary of your model and target assets.

×

Grigorescu & Partners

Get our insights. No spam

Short, practical notes on energy regulation, project bankability, corporate work and tax disputes - written from mandates, not theory.

Don't show again (30 days)