Physical and financial electricity contracts face different CBAM evidence rules

Corporate procurement of renewable electricity increasingly uses physical power purchase agreements, virtual PPAs and Guarantees of Origin. The three instruments can support decarbonisation strategies, but they do not provide equivalent evidence for EU Carbon Border Adjustment Mechanism (CBAM) treatment of imported electricity. They also confer different contractual and economic rights for buyers and sellers.

Physical PPAs require CBAM-relevant delivery evidence

A physical power purchase agreement sets out contractual arrangements for electricity delivery, but the contract itself does not qualify a megawatt-hour for actual-emissions treatment under CBAM. The CBAM-relevant criteria also require an eligible generating installation, relevant network evidence, firm nominations linked to production within the same hour and verification. Without these elements, the documentation linked to the agreement may not meet the requirements.

An agreement that references a wind farm can be insufficient where settlement is based on a regional trading hub. In such cases, the qualifying physical arrangements needed for CBAM treatment are absent even if the contract is tied to renewable generation.

Virtual PPAs provide price exposure without physical delivery proof

A virtual PPA typically involves financial settlements between a renewable generator and a corporate buyer. The structure can hedge price exposure or support investment in a new renewable energy project while the buyer purchases physical electricity from the market. This separation allows corporate buyers to manage financial risk while sourcing electricity through market mechanisms.

Under CBAM rules for actual-emissions treatment of a specific electricity import into the EU, a virtual PPA does not function as the required physical-delivery agreement. Matching annual contract volumes in megawatt-hours against an import portfolio does not convert a financial arrangement into evidence of qualifying physical delivery.

Guarantees of Origin certify renewable attributes, not border nominations

A Guarantee of Origin certifies an attribute of renewable electricity generation and can be used to support electricity disclosure and renewable-energy claims, subject to applicable registry and disclosure requirements. However, a certificate does not by itself establish which electricity was nominated for delivery across an EU border. GoO documentation may complement a wider evidence file, but it does not replace CBAM physical criteria.

Certificates also need controls to prevent the same attribute from being sold or claimed more than once. This management requirement applies even when certificates are retired for a European corporate buyer.

Attribute ownership issues affect Serbia and Montenegro generators

The distinctions between physical delivery evidence, financial arrangements and GoO attributes have commercial implications for independent power producers in Serbia and Montenegro. A renewable developer may sell physical electricity under an offtake agreement to one trading company while selling Guarantees of Origin to another buyer. Such arrangements can be permissible depending on applicable schemes and contractual terms.

These structures affect revenue composition and raise questions about ownership of renewable attributes. Contracts marketing electricity as low-carbon or CBAM-qualified are expected to specify whether the buyer receives renewable certificates, physical delivery rights, actual-emissions evidence or combinations of these products.

Renewable procurement claims do not automatically reduce CBAM liabilities

Corporate purchasers are also required to separate renewable procurement claims from emissions legally attributed to imported electricity under CBAM. Buying renewable certificates for European offices does not necessarily change embedded emissions attributed under CBAM to electricity imported from a non-EU system. The emissions attribution depends on the applicable CBAM framework rather than on certificate-based claims alone.

A steel or aluminium purchaser with a renewable PPA cannot automatically claim lower CBAM liabilities on imported products. Sector-specific rules governing direct and indirect embedded emissions must be assessed independently from the electricity procurement arrangement used by the purchaser.

Contracts can separate delivery rights, certificate schedules and carbon evidence

Energy contracts can include multiple commercial products by specifying electricity volumes, generation sources, delivery arrangements, nominations and rights related to carbon-related evidence. A separate certificate schedule can define registry details, certificate vintage, transfer terms, retirement steps, cancellation processes and controls against duplicate claims. Financial agreements used to hedge electricity prices should remain distinct from documentation intended to demonstrate physical delivery.

Bundled offerings are therefore expected to distinguish rights tied to electricity delivery, renewable attributes and emissions evidence rather than treating them as one undefined green megawatt-hour. This separation supports clarity over which documentation is relevant for each compliance purpose.

EU–Energy Community recognition proposal targets certificate recognition

The distinction between renewable certificates and CBAM qualification could become more significant if broader mutual recognition of renewable certificates is developed between the EU and the Energy Community. A September 2026 proposal identified as COM(2026) 464 envisages a new recognition framework. As described in the source material, it had not yet become an operative replacement for existing CBAM qualification requirements.

For renewable developers and electricity traders, commercial arrangements are therefore expected to preserve separate auditable rights associated with physical electricity, financial settlements, renewable attributes and emissions evidence. This includes ensuring that each component remains traceable under its relevant documentation pathway.

error: Content is protected !!
Scroll to Top