PRE, BRP and Aggregation in Romania: Legal Differences for Investors

PRE/BRP is financial responsibility. Aggregation is system-level control. Confusing them creates real risk.

Why imbalance responsibility is not control - and never has been

1. A persistent misconception with real regulatory consequences

In Romanian market practice, a familiar argument surfaces whenever participants try to stretch the boundaries of what is lawfully permitted:

"We are PRE / BRP, therefore we can centralise volumes and operate assets together."

It sounds plausible. It is also legally wrong.

Becoming a Party Responsible for Balancing (PRE/BRP) is essential for participating in electricity markets. But PRE status is not a shortcut to aggregation, not a licence to pool assets operationally, and not a substitute for the regulatory and technical framework that governs aggregation in Romania.

The confusion is understandable. PREs sit close to balancing. Aggregation also sits close to balancing. But proximity is not equivalence.

This article explains, in clear and practical terms:

• why PRE is a responsibility mechanism, not a control mechanism;
• why delegation of balancing responsibility is not aggregation;
• and why conflating the two creates compliance, enforcement and bankability risk.

2. What PRE is meant to do under EU and Romanian law

At EU level, the balancing framework is built on a straightforward principle:

every market participant must be financially responsible for the imbalances it causes, either directly or through a designated balance responsible party.

This principle is codified in Regulation (EU) 2019/943, which allows a participant to:

• remain responsible for its own imbalances; or
• delegate that responsibility to a BRP / PRE.

Romanian law implements this framework through:

• Transelectrica's balancing rules and procedures;
• the PRE registration and onboarding process administered by the TSO.

The key legal insight is simple but decisive:

PRE status answers only one question: who pays for imbalances?

It does not answer:

• who controls assets,
• who decides dispatch,
• who aggregates flexibility,
• or who interacts with the system as a unified operational resource.

Those questions belong to a different legal layer.

3. What PRE actually is in practice

From both a legal and operational perspective, PRE status is a financial and settlement construct.

A PRE undertakes to:

• assume financial responsibility for deviations between scheduled and actual injections or withdrawals;
• post collateral and guarantees to Transelectrica;
• receive imbalance settlements;
• manage data flows relating to schedules and measured values.

PRE responsibility may cover:

• the PRE's own portfolio; or
• multiple third-party participants, through delegation agreements.

What matters is where PRE sits in the process.

PRE operates downstream of market and operational decisions. It does not sit upstream of dispatch.

Concretely, a PRE:

• does not decide how assets are dispatched;
• does not command technical resources;
• does not issue operational instructions;
• does not perform system-facing control.

Financial responsibility, even when aggregated across many participants, does not transform into operational authority.

4. Delegation of balancing responsibility is not aggregation

This distinction is the one that most often gets blurred in practice.

4.1 What delegation actually transfers

When a producer, consumer or trader delegates balancing responsibility to a PRE:

• the PRE becomes financially responsible for imbalances;
• the delegating party retains operational autonomy, control over its assets, and responsibility for compliance with market and technical rules.

In legal terms, delegation is a risk transfer, not a control transfer.

Nothing in the delegation mechanism:

• centralises dispatch,
• pools operational control,
• or creates a combined system resource.

4.2 What aggregation legally requires

Aggregation, as recognised in Romania, requires something fundamentally different.

It involves:

• central operational control over multiple assets;
• pooled response to market or system signals;
• technical validation by the TSO;
• performance accountability at aggregated-unit level.

These elements are not incidental. They are what make aggregation system-relevant.

They are also entirely absent from the PRE framework.

No step in the PRE onboarding process:

• tests dispatch capability,
• validates EMS/SCADA integration,
• confirms aggregated responsiveness,
• authorises pooled operational representation.

That absence is not accidental.

5. What the PRE registration process proves - by omission

Transelectrica's PRE registration materials are instructive precisely because of what they require - and what they do not.

To become a PRE, an entity must:

• hold a valid ANRE licence (production, supply or trading);
• obtain an EIC code;
• provide guarantees;
• sign the balancing responsibility convention;
• conclude measurement and data aggregation conventions for settlement purposes.

What is notably missing:

• aggregation capability confirmation (TEL-07);
• operational testing of pooled assets;
• formation of aggregated dispatchable units (UD/CD/ISD);
• system-facing control obligations.

Legal conclusion: If PRE status were intended to function as a gateway to aggregation, these elements would be unavoidable. They are not there.

6. Why PRE cannot be used as an aggregation "workaround"

In practice, some market actors attempt to rely on PRE status to justify:

• centralised optimisation of multiple assets;
• coordinated dispatch decisions;
• VPP-like behaviour without formal aggregation approval.

From a legal standpoint, this is dangerous territory.

If a PRE:

• exercises real-time control over multiple third-party assets;
• pools them operationally;
• presents itself commercially or operationally as a single flexible resource,

then the activity is likely to be classified as aggregation in substance, regardless of contractual labels.

PRE status does not provide legal shelter against that requalification.

7. PRE vs aggregation: the functional divide

This comparison explains why the two roles are complementary, but never interchangeable.

8. Why investors and lenders care

From an investment perspective, misuse of PRE status is an immediate red flag.

In due diligence, the questions are predictable:

• Is aggregation actually being performed?
• If yes, where is the aggregation licence scope?
• Where is the Transelectrica TEL-07 confirmation?
• How is system compliance ensured?

If the answer is simply "we are PRE", the analysis does not end - it begins.

Projects that rely on PRE status as a proxy for aggregation routinely encounter:

• regulatory pushback,
• operational friction with the TSO,
• failure to qualify for balancing services,
• weakened creditworthiness.

9. Responsibility is not authority

Romania's electricity market design is consistent and deliberate.

PRE status allocates financial responsibility, not operational authority.

It determines:

• who settles imbalances,
• who posts collateral,
• who bears financial consequences.

It does not determine:

• who controls assets,
• who aggregates flexibility,
• who interacts with the system as a unified operational resource.

Understanding this distinction is not a technicality. It is essential for lawful market entry, sustainable business models and bankable investment structures.

Contact

Horia Grigorescu

+40 744 310 710

If you are structuring a trading desk, a PRE setup, or a VPP strategy in Romania and want a clean legal map of what is allowed, what requires TSO validation, and where bankability risks appear, send us 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.