Electricity traded across multiple borders in the Western Balkans remains subject to the European Union’s Carbon Border Adjustment Mechanism (CBAM) based on origin and import status, rather than on the route taken through regional markets. Utilities, traders, customs teams, transmission system operators and EU electricity importers are told that distinguishing transit from import is necessary to determine whether a carbon liability arises and which emissions factor applies. The European Commission’s CBAM guidance separates electricity originating in the EU, third-country electricity moving through the Union under a transit procedure, and electricity produced outside the EU that is later imported for consumption within the bloc.
The distinctions are relevant for trading arrangements involving Serbia, Montenegro, Bosnia and Herzegovina, North Macedonia and Albania, where commercial transactions and physical electricity flows can pass through several jurisdictions before reaching their final destination. The Commission’s Q&A outlines three electricity-flow scenarios that determine whether CBAM applies. These scenarios also explain why border crossings, commercial resale or temporary passage through EU territory do not automatically determine the carbon treatment of an electricity transaction.
Three CBAM treatments for cross-border electricity flows
Under the Commission’s Q&A, electricity generated within the EU keeps its EU origin for CBAM purposes if it leaves the Union and then returns. In that case, the electricity is not subject to CBAM when it re-enters. This treatment depends on the electricity being EU-originated before leaving.
A separate approach applies to third-country electricity that enters the EU under a Union transit procedure and then continues to another third country. Because the electricity is not released for free circulation in the EU, the transit movement does not trigger CBAM. The guidance links this outcome to the transit procedure status rather than to the fact of crossing EU territory.
CBAM applies when electricity is produced in one third country, routed through another third country, and then imported and consumed within the EU. Where default emissions factors are used, the applicable factor is tied to the country of production rather than automatically to the last trading hub or transit country. The Commission’s guidance therefore distinguishes production location from subsequent trading or transit points.
Seller identity does not determine physical origin
For regional traders, the distinction between electricity origin and the identity of the seller is highlighted as a key point. Purchasing power through a neighbouring market with a lower emissions intensity does not automatically change the emissions factor applicable to power generated elsewhere. The guidance also states that pricing should not assume that movement through EU territory under a qualifying transit arrangement creates a final CBAM obligation.
The supporting records are expected to separate commercial counterparties from the physical and regulatory characteristics of each flow. Contracts, schedules, customs documentation, transmission system operator records and generation data should show where electricity was produced, which borders it crossed and where it was ultimately released for free circulation. This documentation requirement applies regardless of how many parties participate in regional trading.
Where installation-specific actual emissions are claimed, CBAM conditionality still has to be met. Transit arrangements do not remove those requirements or replace evidence linking the generating installation to the imported volume claimed under actual emissions. The guidance therefore treats transit as insufficient by itself for meeting installation-level evidence expectations.
Origin errors and their effect on transaction pricing
Incorrect origin treatment can affect a transaction before electricity is scheduled. A trader may overprice a transit position by including a CBAM cost that does not arise, or underprice an import by applying an emissions factor associated with the last trading hub instead of using the producing country factor. The impact depends on which default factor applies, the relevant certificate price and what commercial margin is available to absorb additional costs.
The Commission’s guidance notes that as carbon-related expenses become more significant, inaccurate assumptions about origin and import status can influence both deal approval and contractual pricing. For cases using actual emissions claims, it says commercial assessment should compare certificate exposure under the applicable default factor with exposure calculated using verified installation-specific emissions values. The difference should be evaluated against costs for scheduling, data retention, verification and contractual administration.
If expected benefits do not cover those additional costs, maintaining a bespoke evidence chain may not be commercially justified. The guidance also indicates that companies should distinguish legal eligibility of a claim from its economic value when deciding how to document origin and emissions information.
Scheduling, customs records and compliance evidence requirements
The guidance calls for metering, scheduling and contractual information to be maintained as a connected evidence set. It states that accurate generation data alone cannot support a valid CBAM claim if timestamps, interconnector nominations, route information or allocations to the buyer do not reconcile with other records. This requirement links operational data quality with compliance outcomes.
Monthly exception reporting is described as a way to identify missing hours, route changes, curtailment and balancing corrections before they become year-end verification findings. The objective is described as preserving an auditable account of electricity generated, scheduled, transported and imported rather than relying on retrospective reconstruction. The same approach is intended to support consistent evidence across reporting periods.
The compliance file must also identify the authorised CBAM declarant. It should distinguish transit status of a movement from the final import event used for CBAM purposes. Where actual emissions are used, installation-specific conditions need documentation alongside records establishing origin and route.
Regional routes into Italy and across Central Europe
The issue is described as relevant to Montenegro’s electricity links between Balkan generation and Italy. It also covers Serbian trading routes into Hungary, Romania and Croatia. Regional market integration can increase intermediary transactions, making it more important to distinguish contractual resale, physical transit and final EU import.
The guidance says trading companies can incorporate these distinctions into route-specific compliance procedures. For each recurring route, companies should identify country of production, applicable transit arrangements, final EU import point, responsible authorised declarant, default-factor fallback and supporting information needed for any actual-emissions claim. Embedding these elements into transaction approval is described as a way to prevent incorrect carbon-cost assumptions entering commercial offers and settlement arrangements.
Linking trade operations with finance in CBAM files
A robust implementation should allow underlying records to explain a transaction’s CBAM treatment both to a verifier and to a commercial manager. Compliance information should connect with purchasing decisions, production records, customs handling and finance rather than operate as a separate reporting process. Documented assumptions and fallback procedures are also described as helping companies handle changes in suppliers, routes or prices without rebuilding calculations from scratch.
For electricity traded across the Western Balkans, decisive questions are where power was produced, how it moved through the electricity system and whether it was ultimately imported into the EU. The guidance states that an invoice chain alone cannot establish which CBAM treatment applies. Instead it points back to origin determination and import status supported by operational scheduling records and customs documentation.
