How to Improve Emissions Data Accounting for Your Company

Last updated: May 29, 2026. Emissions data accounting is the operating system behind a credible greenhouse gas inventory. The hard part is usually not the final calculation formula. It is getting the boundary, source data, evidence, emission factors, assumptions, review process, and annual refresh workflow under control.

Short answer: improve emissions data accounting by treating greenhouse gas data like finance data. Define what the inventory covers, assign data owners, collect activity data before estimating, keep evidence for every material input, track emission factor versions, document assumptions, review year-on-year movements, and build a repeatable process for Scope 1, Scope 2, and relevant Scope 3 emissions.

Why emissions data accounting often breaks

Many companies begin with a spreadsheet, a reporting deadline, and a list of requested numbers. That can work for a first estimate, but it often creates problems when the same numbers need to be reused for a customer request, sustainability report, CDP response, investor questionnaire, reduction target, or assurance process.

The common failure points are practical:

the organizational boundary is unclear;
facility, finance, procurement, HR, travel, and operations teams use different datasets;
activity data is mixed with estimates without labeling which is which;
emission factors are copied forward without version control;
Scope 3 categories are calculated from spend data even when better supplier or activity data is available;
supporting evidence is missing when someone asks how the number was produced; and
the next reporting cycle starts from scratch because no one documented the process.

Good emissions data accounting fixes those issues before the numbers are published.

Start with the reporting use case

Before improving the data system, clarify what the emissions data needs to support. The answer changes the level of detail required.

A company may be preparing emissions data for:

a company-level greenhouse gas inventory;
a sustainability report or regulatory disclosure;
a customer supplier request;
a CDP, EcoVadis, or procurement portal response;
a Microsoft, Salesforce, Amazon, Google, Cisco, HP, Dell, or other buyer request;
a service-level or contract-level emissions calculation;
a product carbon footprint;
a reduction target or transition plan; or
independent assurance or verification.

A simple internal footprint may tolerate more estimates than an assured disclosure or a customer-facing service-level calculation. A buyer request may also ask for specific supporting documentation, not just a total tCO2e number. Read the request first, then design the data process around the output.

Use the GHG Protocol as the accounting backbone

The Greenhouse Gas Protocol is the main global reference point for corporate greenhouse gas accounting. For most companies, the practical starting point is the Corporate Accounting and Reporting Standard, supported by the Scope 2 Guidance and the Corporate Value Chain (Scope 3) Standard.

The GHG Protocol logic is simple but strict enough to matter. A company should define organizational and operational boundaries, separate Scope 1, Scope 2, and Scope 3 emissions, use appropriate activity data and emission factors, and apply the accounting principles of relevance, completeness, consistency, transparency, and accuracy.

For background, see Keslio's GHG Protocol guide and its guide to Scope 1, Scope 2, and Scope 3 emissions.

1. Build a clear data map

A data map turns emissions accounting from a one-off calculation into a managed workflow. For each emissions source, record:

scope and category;
business unit, site, legal entity, or service line;
data owner;
source system or record type;
unit of measure;
reporting frequency;
supporting evidence required;
emission factor source;
calculation method; and
review owner.

For Scope 1, this might include fuel invoices, fleet records, generator logs, refrigerant service reports, or process data. For Scope 2, it usually includes electricity bills, meter readings, landlord data, renewable electricity contracts, and certificate evidence. For Scope 3, it may include procurement exports, supplier emissions data, logistics records, travel data, waste records, employee commuting assumptions, or product-use data.

2. Assign data owners before the deadline

Emissions data usually sits outside the sustainability team. Finance may own spend data. Facilities may own electricity and gas bills. Operations may own fleet and generator fuel. HR may own headcount and commuting assumptions. Procurement may own supplier data. Travel platforms may own business travel. IT may own cloud or equipment records.

Assigning owners early prevents a reporting scramble. Each owner should know which data is needed, what period it covers, what format is expected, and what evidence must be retained. If the company reports annually, make the process repeatable by keeping a simple data request list for each owner.

3. Collect activity data before relying on estimates

The quality of an emissions inventory depends heavily on the quality of the underlying activity data. In many cases, activity data is stronger than spend-based estimates because it reflects what actually happened: kWh of electricity, litres of fuel, kilograms of refrigerant, kilometres travelled, tonnes of waste, or units shipped.

Spend-based estimates can still be useful, especially for early Scope 3 screening or when better data is unavailable. But the calculation should label where spend data is used, which currency and year it reflects, which emission factor source was applied, and whether inflation, exchange rates, or category mapping affected the result.

A useful hierarchy is:

measured data from meters, invoices, or operational systems;
supplier-specific emissions or activity data;
activity data combined with reliable emission factors;
modeled or estimated activity data; and
spend-based estimates where no better data is available.

4. Rate data quality, not just data completeness

A dataset can be complete and still weak. For example, a full procurement export may cover every supplier payment, but it may not classify emissions-intensive suppliers accurately. A travel export may include every flight, but miss cabin class or distance assumptions. A utility file may cover all invoices, but use billing periods that do not match the reporting year.

For material emissions sources, rate data quality using a simple scale. Consider:

whether the data is primary or estimated;
whether the data covers the correct reporting period;
whether units are clear and convertible;
whether the activity category is specific enough;
whether supplier-specific data is available;
whether assumptions are documented; and
whether evidence can be traced back to the source.

This helps the company prioritize improvements. The goal is not perfect data everywhere. The goal is better data for the sources that drive the footprint or matter most to the reporting use case.

5. Control emission factors and unit conversions

Emission factors are often where hidden errors enter the calculation. A company should record the factor source, factor year, geography, unit, greenhouse gases included, and whether the factor is location-based, market-based, spend-based, supplier-specific, or activity-based.

Common control checks include:

matching fuel types and units correctly;
converting litres, gallons, kilograms, tonnes, miles, kilometres, kWh, MWh, and currency consistently;
separating kg CO2e from tCO2e;
using the right country or grid factor for electricity;
tracking renewable electricity instruments separately from standard electricity use;
recording global warming potential assumptions where relevant; and
not mixing old and new factor versions without explanation.

Even when the calculation is outsourced or software-supported, the company should still understand which factor library is being used and how it maps to the company's activity data.

6. Treat Scope 3 as a staged data-improvement project

Scope 3 is usually the hardest part of emissions data accounting because it depends on suppliers, customers, employees, logistics providers, travel platforms, landlords, product assumptions, and procurement categories. Trying to perfect every Scope 3 category in the first year can waste time and still produce weak numbers.

A better approach is staged:

screen all 15 Scope 3 categories for relevance;
identify which categories are likely material;
use spend or activity estimates for an initial baseline where needed;
prioritize better data for the largest or most decision-useful categories;
request supplier-specific data only where it will materially improve the inventory;
document exclusions and data gaps; and
improve the method year by year.

For suppliers responding to customer requests, this can cut both ways. Your customer may be asking you for emissions data because your company sits inside their Scope 3 inventory. If the request is buyer-specific, Keslio's supplier request support can help interpret what data is actually needed.

7. Keep an evidence file for every reporting year

An evidence file is the difference between a number and a defensible number. Keep one folder or repository for each reporting year with:

the final calculation workbook or export;
raw data files received from each owner;
utility bills, fuel invoices, travel reports, waste reports, and supplier submissions;
emission factor sources and versions;
boundary decisions;
methodology notes;
assumptions and exclusions;
quality checks and reviewer comments;
change logs from prior years; and
copies of any customer or reporting-framework requirements used to scope the work.

If independent assurance or verification is required, the assurance provider will usually need traceable evidence. Consultant support, calculation support, and internal review are useful, but they are not the same as independent assurance.

8. Run review checks before publishing numbers

Before sharing emissions data externally, review it like a management number. Useful checks include:

Does the reporting period match the stated period?
Are all material sites, entities, and operations included or clearly excluded?
Do Scope 1, Scope 2, and Scope 3 totals add correctly?
Are location-based and market-based Scope 2 figures clearly labeled?
Are tCO2e and kg CO2e used consistently?
Do year-on-year changes make sense?
Are large variances explained by business changes, data changes, or factor changes?
Are estimates marked as estimates?
Can each material number be traced back to evidence?
Does the methodology match the customer, regulatory, or reporting use case?

Variance checks are especially important. If emissions fall by 40 percent, the company should know whether that reflects real operational change, better data, a missing site, a factor update, or a calculation error.

9. Make annual refreshes easier

Good emissions data accounting should get easier after the first cycle. Keep a standing calendar for data requests, owner reminders, calculation review, management sign-off, and publication. Update the data map each year rather than rebuilding it.

For annual refreshes, document:

changes in business structure, sites, or operations;
changes in reporting boundary;
new or removed emissions sources;
changes in data quality;
updated emission factors;
methodology changes; and
whether prior-year figures need restatement.

This creates a cleaner audit trail and makes the numbers more useful for reduction planning.

What customer requests change

A customer request can make emissions data accounting more specific. Instead of asking for a broad company footprint, the buyer may ask for:

company-level Scope 1 and Scope 2 emissions;
Scope 3 categories linked to purchased goods and services;
service-level or contract-level emissions;
renewable electricity evidence;
supplier-specific emission factors;
methodology documentation;
portal-ready responses;
a consultant letter; or
independent assurance.

Those are different response paths. A service-level request needs allocation logic. A consultant-letter route needs documented consultant support. Independent assurance needs an appropriate independent provider. A portal response may need short, exact answers rather than a long report. The first step is to review the wording of the request before calculating.

For more on customer-driven reporting, see Keslio's guide to what suppliers should prepare for sustainability reporting.

Common mistakes to avoid

Starting calculations before defining the boundary.
Collecting totals without keeping source evidence.
Using spend estimates when actual activity data is available.
Applying one generic emission factor to unlike activities.
Mixing location-based and market-based Scope 2 figures.
Ignoring refrigerants, leased sites, remote work, logistics, or waste because ownership is unclear.
Changing methods each year without documenting why.
Treating software output as final without reviewing the mapping and assumptions.
Assuming customer requests only require company-level emissions.
Describing calculation support as assurance.

How Keslio can help

Keslio helps companies build practical GHG emissions calculations, emissions data maps, evidence files, Scope 3 screens, methodology notes, customer-ready responses, and annual refresh workflows. The work is designed for teams that need credible emissions data without turning every request into a broad ESG project.

If your company has received a buyer request, Keslio can also help through supplier request support: reviewing the request wording, confirming the likely response path, preparing the data checklist, organizing the evidence, and supporting a customer-ready submission.

Need help improving emissions data accounting?

If your team is trying to clean up emissions data, prepare a first GHG inventory, respond to a customer request, or make annual refreshes easier, Keslio can help define the right scope, calculate the emissions, and document the methodology clearly.