Serbian industrial companies preparing carbon emissions declarations need data systems that balance regulatory requirements, operational monitoring and long-term evidence retention. The choice between 15-minute readings, hourly records and monthly electricity bills depends on the intended claim, with each data type serving a different purpose in measurement, reporting and verification (MRV).
For specific actual indirect electricity calculations under the EU Carbon Border Adjustment Mechanism (CBAM), Commission guidance points to reconciling electricity generation and consumption within periods of one hour or less. Fifteen-minute collection can provide greater detail where meters and energy-management systems support it, but it should be treated as an engineering choice rather than a universal legal requirement.
Monthly invoices remain important for financial reconciliation because they provide settled electricity quantities and help confirm total site imports. They cannot establish hourly matching between renewable generation and consumption or identify when the two diverged. Factories therefore need to retain both interval-level records for evidence and operations, and invoices for settlement control.
Time Synchronisation and Data Quality
A reliable MRV architecture must ensure that electricity meters, generators and factory systems use consistent timestamps. Storing records in Coordinated Universal Time (UTC) while displaying local time for operators can help manage discrepancies caused by daylight-saving transitions, when local clocks may contain duplicate or missing hours.
Automated controls should identify missing intervals, duplicate records, meter resets and implausible readings. Where the applicable methodology permits estimates for short gaps, the original missing-data event should remain visible. Unrecorded interpolation makes it difficult for verifiers to distinguish measured values from assumptions.
The same principles apply to data resolution. Factories should establish a formal policy identifying which meters retain 15-minute, hourly, shift-level or monthly records and explaining why each interval is appropriate. This limits uncontrolled data growth while making clear which sources can support claims requiring more precise matching.
Production Data and Operational Benefits
Electricity records must be compatible with production information. High-frequency power readings have limited value for product-level allocation if the factory records output only monthly and cannot establish which product was manufactured during a given period.
Continuous production facilities may be able to use daily or shift-level records, while batch manufacturers may need order-level information. The appropriate resolution depends on how energy consumption must be allocated to the products covered by the reporting exercise.
More detailed electricity profiles can also support peak-demand analysis, identification of equipment running during breaks, battery-cycle monitoring and scheduling flexible loads around renewable generation. These operational benefits may justify 15-minute data collection even where hourly aggregation is sufficient for the regulatory calculation.
Retention, Security and Data Storage
Industrial data historians may compress or overwrite high-frequency records after a set period. Serbian exporters should review retention settings before evidence is lost, since monthly totals cannot reliably reconstruct historical interval readings. This is particularly relevant for 2026, when verified actual data will support the first annual CBAM declarations in 2027. Companies need to ensure that records remain available for the reporting and verification process.
Data storage can be organised in tiers. Raw high-frequency operational readings can remain in existing historians, while validated 15-minute or hourly series and essential metadata are archived for reporting. This preserves auditability without requiring every control-system tag to be copied into the carbon platform.
Cybersecurity and storage costs should remain proportionate to the reporting purpose. Carbon accounting does not require every machine to be connected to the internet. Read-only data extraction, secure gateways and controlled databases can provide the necessary information without unnecessarily increasing risks to operational technology.
Formal Policies and Automated Validation
Factories can automate completeness, range, sign, unit and continuity checks to identify anomalies before monthly close. Human reviewers can then concentrate on exceptions instead of manually checking thousands of readings. The data-resolution policy should also document whether each interval supports a regulatory requirement, an engineering application or both. This rationale helps prevent later IT cost reductions from compressing or deleting records that appear redundant but remain essential for verification.
A documented policy also makes future upgrades easier by showing which meters already provide the required detail and which need new instrumentation or changes to retention settings. For Serbian exporters, collecting suitable interval data, preserving the original records and aggregating them only through controlled calculations establishes the basis for credible annual declarations.
Elevated by CBAM.Clarion.Engineer
