Serbian Exporters Face Risks from Combining CBAM, Scope 2 and Product Carbon Data

Serbian manufacturers exporting to the European Union must distinguish between CBAM embedded emissions, corporate Scope 2 electricity emissions and product carbon footprints, as each framework applies different accounting boundaries, calculation rules and verification requirements. Although the figures may relate to the same physical production process, using them interchangeably can lead to inaccurate regulatory reporting and inconsistent information for customers.

A single carbon figure may simplify management dashboards, customer disclosures and investment presentations, but it cannot represent every reporting obligation. Manufacturers need a shared evidence base supported by separate calculation methodologies, clearly defined boundaries and consistent reporting labels.

CBAM Calculations Follow Product-Specific Regulatory Boundaries

The Carbon Border Adjustment Mechanism (CBAM) operates as a customs-linked regulatory framework covering specified CN codes. Its calculations follow prescribed production boundaries, rules for direct and indirect emissions, precursor treatment and verification requirements.

A manufacturing facility may produce several goods, while only some fall within CBAM’s scope. Consequently, the calculation must begin with the covered product and its production route rather than the company’s entire operational footprint.

Different emissions figures for the same physical production can therefore be legitimate when calculated under CBAM, corporate Scope 2 and product-footprint methodologies. The principal control risk arises when these figures are combined or presented without explaining their differences.

Scope 2 and Product Footprints Apply Different Accounting Rules

Corporate Scope 2 reporting measures emissions associated with purchased electricity, steam, heat and cooling consumed by the reporting organisation. Depending on the applicable reporting framework and available contractual instruments, companies may disclose both location-based and market-based results.

These figures support corporate emissions targets but cannot automatically be transferred into CBAM reporting fields. The two frameworks differ in their boundaries and eligibility criteria, meaning that a valid corporate calculation does not necessarily satisfy the requirements for a regulatory declaration.

Product carbon footprints introduce additional considerations. A cradle-to-gate calculation can cover upstream raw materials, transport, purchased energy and manufacturing activities under a defined lifecycle methodology. Activities outside a CBAM production boundary may still be relevant to a customer’s product assessment. A finished component that is not itself covered by CBAM can nevertheless contribute embedded emissions from steel, aluminium and factory energy to a buyer’s product footprint.

Purchased Heat and Renewable Electricity Require Separate Treatment

Purchased heat demonstrates why automated data mapping can produce incorrect results. It may be included in a company’s Scope 2 inventory, while the CBAM methodology can classify measurable heat differently within an installation’s direct-emissions calculation.

Software that automatically categorises every Scope 2 input as a CBAM indirect emission may generate a consistent-looking report without correctly reflecting the applicable methodology.

Renewable electricity presents a similar challenge. A guarantee of origin may support a corporate market-based emissions claim when the relevant criteria are satisfied. A CBAM claim based on actual emissions values may require a different evidence chain, including physical electricity delivery or a qualifying power purchase agreement (PPA), time matching and verified data from the generating installation. Product-footprint standards may apply another set of requirements. Although the electricity consumption may involve the same megawatt-hour, the accounting treatment depends on the reporting framework.

Shared Carbon Data Require Separate Calculation Modules

A controlled reporting system should collect common evidence once and apply distinct calculation rules for each reporting purpose. The shared evidence layer can include meter records, energy contracts, production volumes, material genealogy and supplier data.

Separate calculation modules then apply the relevant boundaries, emissions factors and allocation rules. A reconciliation report explains the differences between the resulting figures rather than forcing methodologies to produce a single number. This approach also improves investment assessment. If renewable electricity procurement reduces a company’s corporate Scope 2 figure but does not change the current CBAM result for a particular aluminium product, management can still assess the project’s customer or strategic value without presenting it as a regulatory emissions saving.

Similarly, improved precursor data may lower reported CBAM embedded emissions without changing physical production. Keeping the accounts separate allows management to distinguish an improvement in emissions information from an actual operational reduction.

EU Customers Need Consistent and Reconciled Carbon Disclosures

European Union customers may request several emissions figures from the same Serbian supplier. Procurement teams may require product carbon footprints, customs teams may need CBAM information, and sustainability departments may request Scope 1 and Scope 2 disclosures.

Suppliers that can explain the relationships between these figures provide a clearer basis for customer assessments than manufacturers that submit the same emissions intensity under different reporting labels. For Serbian exporters, maintaining separate carbon accounts helps protect against misrepresentation, verification findings and poorly informed investment decisions. A robust reporting system should identify the common evidence base, specify the methodology used for each figure and explain precisely what the results represent.

Reconciliation and Governance Strengthen Carbon Reporting Controls

Management dashboards can make differences between the reporting frameworks easier to understand through a reconciliation waterfall. This starts with physical site emissions before identifying corporate Scope 2 treatment, product-allocation adjustments and CBAM-specific exclusions or precursor additions.

The resulting presentation shows executives not only the three figures but also the reasons they differ. This reduces the risk of treating the lowest reported value as the universally applicable result.

The same process supports external communication. When a customer asks why a CBAM figure is higher or lower than a supplier’s published product footprint, the manufacturer can provide a methodology-based explanation rather than issuing a corrective response. Consistent reporting labels help prevent discrepancies in carbon data from undermining commercial trust.

Governance responsibilities should reflect the separation of the accounts. Finance may oversee corporate inventory consolidation, the export or tax function may coordinate CBAM information, and product teams may manage customer-facing footprints. A central carbon-data owner can maintain common source records and ensure that the different functions use consistent meter data, emissions factors and supplier information.

This structure also improves auditability by limiting the effects of methodology changes. Updates to product-footprint guidance need not require changes to the CBAM calculation system, while revisions to a CBAM default value should not automatically alter the corporate inventory. A shared evidence base combined with modular calculations requires a more structured initial design but makes carbon reporting easier to control across repeated reporting cycles.

Elevated by CBAM.Clarion.Engineer