Renewable electricity has typically been traded through a structure in which the producer supplies power, a trader manages scheduling and balancing, and the buyer receives contractual volumes supported by guarantees of origin. Under the EU Carbon Border Adjustment Mechanism (CBAM), this approach is not sufficient when an authorised CBAM declarant seeks to use actual embedded emissions for imported electricity. In that case, the claim requires more than attribute documentation.
A CBAM actual-emissions claim depends on an auditable chain linking a named generating installation, a physical power purchase agreement, hourly production, transmission capacity nominations, network conditions, an identified EU declarant and an accredited verifier. Clarion.Engineer has developed a green electricity monitoring, reporting and verification dashboard intended to convert regulatory and operational requirements into a controlled management system for solar, wind and battery energy storage projects. The dashboard is designed to test whether each claimed megawatt-hour can be reconstructed from source evidence and defended during accredited verification.
Eligibility conditions for using actual emissions in CBAM electricity
Electricity is treated differently from many other CBAM goods because default emission factors are the standard route. Installation-specific actual emissions may be used only when cumulative conditions are satisfied. For electricity imported into the EU, European Commission definitive-period guidance identifies five cumulative criteria.
The claimed volume must be covered by a power purchase agreement between the authorised CBAM declarant and a producer in a third country. The generating installation must be directly connected to the EU transmission system or there must have been no physical network congestion along the relevant route at the time of export. The installation must emit no more than 550 grams of fossil-origin CO2 per kilowatt-hour.
The claimed electricity must also be firmly nominated across relevant interconnection capacity, with production and nomination referring to the same period of no more than one hour. Finally, fulfilment must be certified by an accredited verifier receiving at least monthly interim reports. The guidance indicates that the criteria are not weighted.
Passing four out of five does not create an 80 per cent-compliant claim, and failure of a single condition can return the electricity to the default-value route. The dashboard therefore starts with an eligibility gateway rather than an emissions calculation. It records each legal test status as passed, at risk, blocked or not assessed.
The demonstration baseline described for the framework shows two of five gates passed, two at risk and one blocked. The figures are presented as illustrative of how readiness is exposed before unsupported actual values reach an importer or verifier. The dashboard is intended to address cases where low direct operating emissions do not automatically establish eligibility for installation-specific treatment during a claimed hour.
From document storage to controlled evidence architecture
The dashboard approach responds to how companies often manage new obligations by creating shared folders for contracts, meter files, guarantees of origin and emissions calculations in spreadsheets. While such storage may hold documents, it does not establish relationships between evidence elements required for verification tracing. A verifier needs to trace reported quantities through data flows and identify origins, transformations and reviewers.
Clarion.Engineer’s model organises MRV into three layers described as controlled truth. The first layer is fixed installation truth covering operator identity, generating installation details, ownership structure, geographical location, technology and installed capacity. It also includes connection point information, single-line diagram references, metering boundary definitions and hierarchy of measurement devices.
The second layer is hourly operational truth connecting revenue meters, SCADA systems and power plant controller data with production schedules and balancing records. It also covers grid imports, auxiliary consumption, curtailment instructions, outages, interconnector nominations and settlement information. For battery storage installations, it additionally includes charging sources, state of charge values, losses, discharging volumes and source-attribution ledgers.
The third layer is assurance and handover truth containing monitoring plans, control descriptions and data-quality checks. It includes management approvals, monthly evidence packs, findings and corrective actions as well as verifier requests and declarant-specific reporting outputs. The current model includes 71 structured inputs across these layers with defined ownership, source systems and evidence references.
The dashboard assigns definitions to each input to reduce ambiguity when different teams use different names for the same quantity. A single field such as “eligible exported electricity” can otherwise refer to gross generation, net generation, metered export, nominated export or settled export depending on context. Under CBAM requirements described in the model, these quantities are not treated as interchangeable.
Six handovers used to test whether claims can survive
The dashboard follows each claimed megawatt-hour through six controlled handovers described in the framework. The first establishes asset truth including installation identity, technical boundary and connection architecture. The second establishes hourly truth using meters, SCADA data, power plant controller records and time synchronisation.
The third adds contractual truth including the power purchase agreement and declarant identity as part of linking entitlement to claimed quantities. Subsequent handovers are described as continuing this chain through operational reconciliation and assurance steps required for verification readiness. The model’s stated purpose is to determine whether claims remain defensible after each stage of evidence linkage.
Solar PV controls versus wind controls
The legal gateway is described as common across renewable technologies within the eligibility framework while supporting operational evidence differs by technology type. For solar photovoltaic installations, the main issue identified is defining relationships between inverter output, transformer losses, auxiliary consumption, clipping effects, curtailment actions and grid imports relative to the point-of-connection meter. The framework notes that reported inverter production can exceed exported electricity measured through revenue metering.
The dashboard reconciles inverter-level data to transformer values and revenue-meter readings while recording curtailment instructions and plant availability information. It also captures auxiliary loads and any imported electricity consumed by the installation during relevant periods. It further checks whether power purchase agreement volumes and claimed CBAM quantities are based on gross generation or net eligible export.
For wind farms, control structures are described as beginning at turbine level through collection systems, transformers and revenue meters. Turbine SCADA totals may differ from settlement quantities due to electrical losses, availability exclusions, timestamp differences or data substitutions. The wind module tests turbine completeness along with collection-system losses and transformer losses.
The framework describes checks including outage records alignment among turbine controllers, power plant controller data and SCADA records as well as settlement systems inputs. Missing turbine data or unexplained adjustments are treated as exceptions rather than being absorbed into monthly totals without explanation. Both solar PV and wind configurations ultimately reconcile to an hourly physical-delivery chain that links production timing with nomination capacity allocations.
Guarantees of origin do not replace CBAM eligibility tests
The model states that guarantees of origin remain useful for ownership identification and traceability but do not replace the five CBAM eligibility tests required for using actual embedded emissions. A certificate attached to electricity can demonstrate an attribute but cannot by itself prove physical power purchase agreement structure or absence of congestion along a route at export time. It also cannot independently establish cross-border nomination details or accredited verification outcomes for the relevant claim.
BESS attribution ledger for charging sources and losses
Battery energy storage is described as creating a distinct attribution problem because it shifts electricity in time while introducing conversion losses. The framework states that a battery does not create a new renewable megawatt-hour; instead it changes when energy is delivered relative to when it was charged. If charging occurs from both a renewable installation and the grid then discharged quantity cannot automatically be classified as renewable or linked solely to an original power purchase agreement.
The dashboard therefore maintains a separate battery ledger for every reporting interval covering opening state of charge values, renewable charging amounts or mixed-source charging indicators and associated charging losses plus standing losses. It also records discharge volumes together with closing state of charge values and any quantity previously claimed before storage entry.
A conservative control is described: eligible battery discharge cannot exceed eligible charge after losses and prior claims. The framework states that megawatt-hours claimed before entering storage cannot be claimed again after discharge within CBAM evidence logic described in the model. Distinct metering or reliable source flags are required for different charging streams when batteries share connections with solar or wind assets.
The model also states that even correctly attributed discharge remains subject to broader CBAM gateway requirements including contractual coverage route evidence hourly nomination capacity alignment and verifier review steps described elsewhere in the framework. Storage changes production-to-delivery timing but does not remove physical traceability obligations required for eligibility determination.
Monthly close timetable: D+1 through D+10
The dashboard operates through a monthly close rather than assembling evidence retrospectively at year end in the model description provided. In this timeline framework D represents the reporting cut-off date normally set as the final day of the month while subsequent milestones are measured in working days rather than calendar days alone.
At D+1 source data are frozen with meter readings SCADA outputs power plant controller data energy-management system inputs schedule files transmission files and settlement files secured in their original form to prevent uncontrolled changes after reporting begins. By D+3 generation imports exports storage quantities and settlement quantities are reconciled with gaps duplicates timestamp differences and unexplained losses entered into an exception register.
At D+5 hourly matching is completed where eligible quantity per interval is constrained by available generation contractual volume nominated capacity import quantity and other applicable limits; unsupported quantities are excluded rather than carried into claims. At D+7 evidence packs undergo a four-eyes review with data owners confirming source records control owners reviewing exceptions and management assessing open findings or monitoring system changes.
By D+10 a monthly interim evidence pack is issued containing controlled hourly ledgers reconciliation exception reports supporting documents management approval and evidence required for verifier review steps described in the framework. The timetable is presented as an operational design choice rather than a statutory deadline because it supports monthly interim reports needed for actual-emissions routes while discrepancies remain correctable during accessible periods.
Verification process aligned with Commission guidance
The framework describes verification as starting before an accredited verifier arrives rather than being limited to inspection of completed spreadsheets. It references European Commission 2026 guidance describing a process extending from pre-contract stages through strategic risk analysis verification planning process analysis site visits findings independent review and issuance of verification reports. It also emphasises testing data flows control activities treatment of data gaps and assessment of monitoring plans.
A well-structured dashboard mirrors this process using elements such as a control register showing which risks have been addressed versus those remaining open alongside an evidence index enabling tracing from sampled megawatt-hours back to original meter SCADA record contractual entitlement and nomination details. A change log explains modifications to meters software calculation rules or responsible personnel while findings registers separate errors non-conformities from improvement actions.
This approach reduces verification friction without compromising verifier independence because pre-verification is management preparation testing whether producer systems can support claims while accredited verifiers still conduct independent assessments before issuing formal conclusions described in Commission guidance referenced by the framework.
Implementation via work packages WP-00 to WP-09
Implementation is organised into 10 work packages, numbered WP-00 through WP-09 as described in the model outline provided. The first group establishes governance CBAM pathway installation boundary definitions and data architecture foundations within project scope definitions used for MRV operations.
The second group completes physical-delivery PPA arrangements grid-route evidence technology-specific controls plus monthly close procedures aligned with operational timelines used for reporting freezes reconciliation matching review steps described earlier in the framework narrative provided here.
The final group covers representative-month testing remediation activities plus accredited handover steps required before verification readiness can be assessed within this MRV structure description. Engineering teams manage plant boundaries technical data metering operations manage source systems commercial teams hold PPA documentation trading scheduling teams control nominations while finance compliance teams manage quantities declarations; verifiers require evidence from all functions but cannot create missing evidence on behalf of project participants within this model description.
Elevated by CBAM.Clarion.Engineer