The question keeps coming up in every board meeting: “Where exactly does our carbon data come from?” The honest answer, in most mid-market industrial companies, is this: from a spreadsheet fed manually twice a year, from PDF invoices nobody can find when the auditor calls.
Yet the data you need to calculate your Scope 1, 2 and 3 emissions already exists in your ERP. It is not labelled “carbon”, but it is there: energy invoices in the procurement module, fuel consumption in asset management, purchased quantities by supplier in the supply chain. The problem is not missing data — it is the missing link between that data and an emission factor reference database.
This guide explains how to activate that link, module by module, following the GHG Protocol Corporate Standard — the global benchmark for corporate carbon accounting.
Carbon Accounting and ERP: Why the Data Is Already There
The GHG Protocol in 3 Scopes: What Your ERP Already Knows (and What It Doesn’t Yet)
The GHG Protocol Corporate Standard, published by the WRI (World Resources Institute) and the WBCSD, defines three emission boundaries for a company:
- Scope 1: Direct emissions from sources owned or controlled by the organisation (boilers, fleet vehicles, industrial processes, refrigerant gases).
- Scope 2: Indirect emissions from purchased and consumed energy: electricity, steam, heat, and cooling.
- Scope 3: All other indirect emissions upstream and downstream in the value chain (purchased goods and services, freight transport, use of sold products, end-of-life treatment, employee commuting, etc.).
What your ERP already handles natively: Scope 1 (via asset management and industrial consumption records) and Scope 2 (via energy procurement). What it does not yet know: how to map those data points to an emission factor (in kgCO2e per kWh, per litre, per km) to produce a result in tonnes of CO2 equivalent.
For Scope 3, the challenge runs deeper: the ERP holds the volumes (quantities purchased, distances transported, supplier spend) but not the unit carbon footprints. Those footprints must be imported from reference databases such as ecoinvent (the leading academic and industry standard), DEFRA (UK government factors), or the EPA Emission Factors Hub (US).
Why Connect Carbon Accounting to Your ERP Rather Than a Standalone Tool
The tempting path is to deploy a dedicated ESG platform, fed by a monthly ERP export. That approach works for a first disclosure report — not for sustainable, operational carbon accounting.
Three decisive arguments for native ERP integration:
- Auditability: every ESG data point must be traceable back to its source invoice or production order. An ERP provides that audit trail; a third-party tool fed by CSV export does not.
- Frequency: real-time (or monthly) emissions tracking requires a continuous data feed. A quarterly export to a standalone tool cannot detect a drift mid-year.
- Maintenance cost: two parallel data repositories means twice the divergence risk and twice the manual reconciliation effort.
Scope 1 in the ERP: Direct Emissions
Natural Gas, Fuel Oil, Refrigerants: How Asset and Energy Modules Track Consumption
Scope 1 is the easiest to integrate because it maps to measurable, invoiced physical flows. In an industrial ERP, the relevant data sources are:
- Asset management module (EAM/CMMS): gas and fuel meter readings by asset, maintenance work orders with associated consumption.
- Procurement module: supplier energy invoice lines (natural gas, heating oil, propane) with volumes in m³ or litres.
- Inventory module: consumption of combustible raw materials (coke, coal, biomass).
For refrigerant gases — often invisible in standard management systems — the maintenance module is the only reliable source: every top-up intervention must generate a work order recording the recharged volume in kg, the refrigerant type (R410A, R32, HFO), and the associated GWP (global warming potential).
The integration key: create an “emission factor” field in the ERP linked to each energy or fluid type, then automatically calculate the result in tCO2e from the volume consumed.
Vehicle Fleets: The ERP as the Single Source of Mileage Truth
For company fleets integrated into the ERP (via a transport or expense management module), mileage data forms the basis of Scope 1 calculations. The calculation method: mileage × emission factor by vehicle type (petrol, diesel, electric, hybrid) and category (passenger car, light van, HGV).
Vehicle emission factors are available from DEFRA for UK and international scope, and from the EPA for North American operations.
Scope 2 in the ERP: Purchased Electricity and Heat
Integrating Energy Bills and Emission Factors (Market vs. Location-Based)
Scope 2 emissions calculations rely on two official methods defined by the GHG Protocol:
- Location-based method: apply the average emission factor of the national electricity grid to the kWh consumed. The UK grid factor (around 175 gCO2e/kWh in 2024 per DEFRA) differs significantly from Germany’s or France’s, making the choice of location relevant.
- Market-based method: apply the specific emission factor of the energy contract subscribed, particularly if the company holds renewable energy certificates (RECs or GOs) or a Power Purchase Agreement (PPA).
The ERP must store, for each site and meter, the kWh consumed per period, the contract type (standard grid, GO/REC, PPA), and the applicable emission factor. This configuration is typically handled in the site management module or in the management accounting layer by cost centre.
The Green Energy Contract Complexity: Handling It in the Procurement Module
Renewable energy certificates and PPAs create an accounting complexity: the electricity physically consumed still comes from the grid, but the “label” contract allows the company to claim zero emissions under the market-based method. This distinction must be traceable in the ERP to be defensible in an audit.
In practice: the procurement module must distinguish standard “energy” invoice lines from associated “renewable energy certificate” lines, and the Scope 2 calculation must be able to produce both methods in parallel. The CSRD and the GHG Protocol both require publication of both figures.
Scope 3 in the ERP: The Indirect Emissions Challenge
According to CDP’s 2024 data, corporate supply chain emissions are on average 26 times higher than their direct operational emissions (Scopes 1 and 2). For a mid-market industrial company, Scope 3 represents the bulk of total carbon footprint, with “purchased goods and services” (category 1) typically the largest single contributor.
Category 1 (Procurement): Enriching Item and Supplier Records with Emission Factors
The most operational approach to calculating Scope 3 category 1 in the ERP is to enrich the item and supplier master data with unit emission factors. Two levels of granularity are available:
- Factor by spend category: assign an average emission factor (in kgCO2e/£ or kgCO2e/kg) to each procurement family, sourced from DEFRA or ecoinvent. This is the “spend-based” method — quick to deploy, lower precision.
- Supplier-specific factor: the supplier discloses its product-level carbon footprint and the company integrates that factor into the ERP supplier record. This is the “supplier-specific” method — more accurate but requires supply chain engagement.
A key point on “double counting”: Scope 3 category 1 emissions for a buyer correspond to the Scopes 1 and 2 of their supplier. This overlap is intentional under the GHG Protocol and is not an error, but it must be documented to avoid misinterpreting sector-level aggregates.
Transport and Logistics Categories: Integrating TMS and ERP for Freight Emissions
Freight transport (category 4, upstream, and category 9, downstream) is a significant source for industrial distributors. The calculation relies on: distance × weight transported × emission factor by mode (truck, rail, air, maritime).
If the company operates a TMS (transport management system) connected to the ERP, transport data is already structured. Emission factor enrichment can be done via DEFRA freight factors for international transport or via the SmartFreight GLEC Framework for multimodal logistics.
Without a TMS, carrier invoice lines in the procurement module form the calculation base — provided the transport mode and weight are captured on each line.
Category 11 (Use of Sold Products): Simulation in the Sales Module
For manufacturers whose products consume energy during use (electrical equipment, vehicles, heating systems), category 11 of Scope 3 can exceed in volume all other categories combined.
The ERP’s sales module holds volumes sold by product reference. To calculate use-phase emissions, you need to model the annual energy consumption per unit sold (in kWh or litres) and the average product lifespan, then apply the relevant emission factors.
This simulation must be versioned annually because electricity grid emission factors evolve over time.
Market Solutions: Native Modules vs. Dedicated Tools
SAP Sustainability Footprint Management: Strengths and Limits
SAP has offered a dedicated solution since 2022 — SAP Sustainability Footprint Management — designed to calculate carbon footprint at product and company level by leveraging SAP S/4HANA data. Q1 2026 updates notably improved transport calculations and the allocation between Scope 3.1 and 3.2 for purchased goods.
Strengths: native integration with the SAP ecosystem, GHG Protocol and PACT V3 compliance, real-time calculations, built-in audit trail. Limits: significant additional licensing costs, most relevant for large enterprises and mid-market companies already on S/4HANA, non-trivial configuration curve.
Microsoft Sustainability Manager (Integrated with Dynamics 365): Relevance for Mid-Market
Microsoft Sustainability Manager is integrated into the Dynamics 365 and Cloud for Sustainability platform. The 2025–2026 versions include product carbon footprinting via bills of materials, emission allocation by organisational unit, reporting period locking, and electricity grid mix tracking.
For a company running Dynamics 365 Business Central or Finance, this is the most natural option to avoid an external ESG silo. Functional maturity is lower than SAP SFM for complex industrial scenarios, but it covers the majority of needs for mid-market services or distribution companies.
Middleware Alternatives and Dedicated Tools
For mid-market companies whose ERP does not offer a mature native sustainability module, dedicated tools act as middleware:
- Watershed: focused on automating data collection via API and standard ERP connectors, strong on Scope 3 supply chain. Widely adopted by US and UK mid-market manufacturers.
- Plan A: European provider (Berlin), strong on CSRD/ESRS compliance, good functionality-to-price ratio for companies with 200–2,000 employees.
- Persefoni: cloud platform oriented towards financial emissions (investments, loans), used by financial groups and their industrial subsidiaries.
The choice between a native module and a dedicated tool depends primarily on integration depth: if you need a native audit trail and real-time ERP data updates, the native module is the right call. If you have heterogeneous sources (ERP + spreadsheets + supplier CSVs), a middleware may be more flexible in the short term.
Implementing Carbon Accounting in the ERP: A 4-Phase Plan
Phase 1: Map the Existing Data Flows in Your ERP
Before any configuration, document precisely what data exists in your ERP, its quality, and its granularity. Key questions: are energy consumptions recorded per site or globally? Are raw material purchases distinguished by type in the chart of accounts or in the item master? Are fleet mileages tracked directly or only as euro reimbursements?
This mapping typically takes two to four weeks with an ERP functional consultant and a carbon expert. It determines the realistic scope for version 1 of your ERP carbon accounting.
Phase 2: Enrich Master Data (Items, Suppliers, Sites) with Emission Factors
This is the longest data work stream. It involves adding emission factor fields (in kgCO2e per unit) to purchased items, energy types, vehicles, and production sites in the ERP.
DEFRA’s emission conversion factors are the starting point for UK and internationally-oriented companies. Regularly updated, they cover hundreds of material, energy, and service categories. For specific supply chain footprints, ecoinvent provides the granularity needed for high-stakes Scope 3 disclosures.
Phase 3: Automate Collection and Calculations (API Connectors, Batch)
Once master data is enriched, emission calculations must run automatically at every relevant transaction (receipt of an energy invoice, validation of a supplier purchase order, closure of a production order). This is the role of calculation rules configured in the sustainability module or in a middleware connected to the ERP.
The end goal: produce a monthly emissions dashboard by scope, by site, by procurement family — with no manual intervention, and a traceable link back to the source transaction.
Phase 4: Validate and Audit (Alignment with CSRD and Independent Experts)
The first version of calculations must be reviewed by an external carbon expert before being incorporated into an official CSRD report. Key checkpoints: boundary consistency (justified and documented exclusions), emission factor sources (date, version, reference database), treatment of biogenic emissions, and compliance with the chosen GHG Protocol method (location-based or market-based for Scope 2).
For companies subject to CSRD, the report will be audited by an independent assurance provider. The ERP audit trail is a strong argument: every figure must trace back to a transaction, not a spreadsheet.
What the ERP Changes in Carbon Reporting
The ERP does not simplify carbon accounting — it makes it sustainable over time. Without it, data collection remains manual, fragmented, and unaudited. With it, carbon accounting becomes a management process like financial accounting: structured, traceable, and actionable for decision-making (supplier substitution, fleet electrification, energy contract renegotiation).
What the ERP does not change: the intrinsic complexity of Scope 3, particularly the dependency on supplier data. A perfectly configured ERP with poor emission factors produces a poor carbon balance. Data quality at the input remains the number-one limiting factor.
To go further, read our complete guide to CSRD and sustainability reporting in the ERP and our article on the EU Carbon Border Adjustment Mechanism (CBAM) and ERP compliance obligations.
