Renewable electricity has typically been sold using a producer-trader-buyer structure supported by guarantees of origin. Under the European Union’s Carbon Border Adjustment Mechanism (CBAM), that arrangement is not sufficient when an authorised CBAM declarant uses actual embedded emissions for imported electricity. The change requires 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 developed a green electricity monitoring, reporting and verification dashboard to manage this obligation for solar, wind and battery energy storage projects.
The dashboard is intended to determine whether each claimed megawatt-hour can be reproduced from original source evidence. It also aims to ensure that the evidence passes required eligibility tests and can be defended during accredited verification. Rather than operating as a document register, it is designed as a controlled management system for the underlying regulatory and operational requirements. The focus is on reconstructability of claimed volumes from contracts, meters, operational records and transmission evidence.
Eligibility conditions for actual-emissions claims on imported electricity
Electricity under CBAM uses default emission factors as 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. These criteria apply to the claimed volume covered by an eligible import period.
The first criterion requires coverage by a power purchase agreement between the authorised CBAM declarant and a producer in a third country. The second requires either direct connection of the generating installation to the EU transmission system or demonstration of no physical network congestion along the relevant route at the time of export. The third sets an emissions threshold: the installation must emit no more than 550 grams of fossil-origin CO2 per kilowatt-hour. The fourth requires firm nomination across relevant interconnection capacity with production and nomination referring to the same period of no more than one hour.
The fifth criterion requires certification by an accredited verifier receiving at least monthly interim reports. The criteria are not weighted, so failure of any single condition can return the electricity to the default-value route. Clarion.Engineer’s 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, along with responsible party, required evidence, reporting period, latest review date and corrective action.
A demonstration baseline shows two out of five gates passed, two at risk and one blocked. These figures are described as illustrative rather than representing performance of a specific plant. The system is intended to expose readiness before unsupported actual values reach the importer or verifier. A low emission factor alone does not establish that imported electricity originated from the installation during the claimed hour.
From document storage to controlled evidence architecture
Some companies initially respond to reporting obligations by creating shared folders for contracts, meter files, guarantees of origin and emissions calculations in spreadsheets. This approach may store evidence but does not establish relationships between evidence elements required for verification tracing. A verifier must trace a reported quantity through the data flow, identify its origin, understand transformations and determine who reviewed it. The dashboard is structured to support that traceability.
The MRV model is organised into three layers of controlled truth. The first layer is fixed installation truth covering legal identity of operator, generating installation details, ownership structure, geographical location, technology and installed capacity. It also includes connection point information such as single-line diagram inputs, metering boundary and hierarchy of measurement devices to define where the CBAM boundary begins and ends.
The second layer is hourly operational truth linking revenue meters, SCADA and power plant controller data with production schedules and balancing records. It connects grid imports, auxiliary consumption, curtailment, outages, interconnector nominations and settlement information for each hour. Where battery storage exists, it also includes charging sources, state of charge, losses, discharging volumes and source-attribution ledgers.
The third layer is assurance and handover truth containing monitoring plan content, control descriptions and data-quality checks. It also includes management approvals, monthly evidence packs, findings, corrective actions and verifier requests plus declarant-specific reporting outputs. The current model contains 71 structured inputs across these layers with assigned definitions covering format, unit, owner, source system, reporting frequency, approval requirement and evidence reference.
The input definitions are intended to reduce ambiguity when engineering, trading, finance, sustainability and legal 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 or contract-covered volume. Under CBAM these quantities cannot be treated as interchangeable within verification evidence chains.
Technology-specific operational controls for solar PV and wind generation
The dashboard follows each claimed megawatt-hour through six controlled handovers described as asset truth through contractual truth additions. The first handover establishes asset truth including installation identity, technical boundary and connection architecture. The second establishes hourly truth through meters, SCADA data sources including power plant controller inputs and time synchronisation requirements.
The third handover adds contractual truth including PPA coverage and declarant identity elements used in claim formation. Subsequent stages are described in terms of eligibility reconstruction needs across contracts, meters and grid nominations with verifier evidence support for each hour.
Solar photovoltaic installations require operational reconciliation between inverter output-related measures and exported electricity at connection points. The dashboard addresses relationships among inverter output reporting versus transformer losses outcomes versus auxiliary consumption plus clipping and curtailment effects alongside grid imports at the point-of-connection meter. It records curtailment instructions and plant availability while also capturing imported electricity consumed by the installation.
The solar module also checks whether PPA volumes used in claimed CBAM quantities align with gross generation or net eligible export definitions used in claim eligibility determination. For wind farms the control structure starts at turbine level through collection systems transformers and revenue meter references used for settlement alignment. 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 through collection-system losses transformer losses outage records dispatch instructions and alignment among turbine controllers power plant controller SCADA records and settlement systems. Missing turbine data or unexplained adjustments are treated as exceptions rather than being absorbed into monthly totals without traceable explanation.
BESS attribution ledger requirements within CBAM eligibility chains
Battery energy storage introduces attribution complexity because it shifts electricity in time while adding conversion losses rather than creating new renewable megawatt-hours by itself. If charging comes from both a renewable installation and the grid then discharged quantities cannot automatically be classified as renewable or linked directly to an original power purchase agreement without additional attribution controls.
The dashboard maintains a separate battery ledger for every reporting interval covering opening state of charge renewable charging grid or mixed-source charging charging losses standing losses discharge closing state of charge plus any quantity previously claimed before storage entry. A conservative control limits eligible battery discharge so it cannot exceed eligible charge after losses and prior claims.
A megawatt-hour claimed before entering storage cannot be claimed again after discharge within the same controlled chain logic described in the model requirements. This requires distinct metering or reliable source flags for different charging streams including cases where batteries share connections with solar or wind generation facilities.
The system must demonstrate whether battery charging occurred directly from the renewable facility from grid sources or from mixed sources while establishing loss treatment rules that prevent double counting across generator ledgers and battery ledgers simultaneously within claim formation logic.
Monthly close process D+10 evidence packs for verification readiness
The dashboard operates using a monthly close process rather than assembling information retrospectively at year end. In this model D denotes reporting cut-off date normally the final day of the month with subsequent milestones measured in working days after D.
At D+1 source data are frozen including meter SCADA power plant controller energy-management system schedule transmission files and settlement files secured in 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 completes where eligible quantity per interval is constrained by available generation contractual volume nominated capacity import quantity plus other applicable limits; unsupported quantities are excluded rather than carried into claims. At D+7 an evidence pack undergoes four-eyes review where data owners confirm source records control owners review exceptions and management assesses open findings or changes to monitoring system design elements.
By D+10 a monthly interim evidence pack is issued containing controlled hourly ledger reconciliation exception report supporting documents management approval plus evidence required for verifier review under actual-emissions route needs described in guidance context within the model narrative.
Verification planning aligned with CBAM guidance process steps
The dashboard changes how producers interact with accredited verifiers by aligning preparation work ahead of formal verification issuance. Verification is described as extending beyond inspection of completed spreadsheets into pre-contract stage activities strategic risk analysis verification planning process analysis site visits findings independent review and issuance of a verification report under European Commission 2026 guidance referenced within the model description.
A well-structured dashboard mirrors this process using a control register showing addressed risks versus open risks plus an evidence index enabling traceability from sampled megawatt-hours back to original meter SCADA record contractual entitlement and nomination inputs used in eligibility tests. A change log explains modifications to meters software calculation rules plus responsible personnel involved in controlled adjustments while a findings register separates errors non-conformities from improvement actions.
This approach reduces verification friction while maintaining verifier independence because pre-verification is management preparation testing whether systems can support claims before independent assessment occurs by accredited verifiers who still issue formal conclusions based on independent evaluation requirements described in guidance context within the model narrative.
Cross-functional delivery via WP-00 to WP-09 work packages
Implementation is organised through 10 work packages numbered WP-00 to WP-09 with governance pathway installation boundary definition and data architecture established in early work packages. A second group completes physical-delivery PPA grid-route evidence technology-specific controls plus monthly close operations aligned with MRV processing needs described in the model requirements.
The final group covers representative-month testing remediation steps plus accredited handover activities required for verification readiness under actual-emissions route conditions described earlier in eligibility criteria sections. The work breakdown is described as cross-functional because engineering defines plant boundary technical data while metering operations manage source systems commercial teams hold PPA buyer information trading scheduling teams control nominations finance compliance manage quantities declarations.
The dashboard assigns each control a responsible owner evidence source frequency approval level readiness status while dependencies are made visible so management can see that verification cannot begin effectively until monitoring boundary source hierarchy and physical-delivery route stabilise within controlled evidence architecture requirements described earlier.
A representative-month exercise is identified as pivotal where one reporting month runs through full process from source freeze through evidence pack creation plus pre-verification review to reveal whether design works under operating conditions including missing data curtailment outages storage activity settlement differences described as part of operational testing scope within this implementation approach.
Elevated by CBAM.Clarion.Engineer