Smart ways to collect emissions data
Collecting emissions data is where most carbon programmes stall. The calculations are well understood; getting accurate activity data from dozens of sites, systems and suppliers every month is the hard part. Here are the smart ways to collect emissions data — from utility bills and meter readings to ERP batch runs and supplier portals — and how to keep quality high as volume grows.
Start from activities, not scopes
Asking a site manager which scope a diesel invoice belongs to slows everything down and invites mistakes. A better approach is guided entry by activity: the person records what happened — fuel bought, electricity used, a flight taken — and the system assigns the scope and GHG Protocol category automatically. In EKOTRACE, Capture › Add data works this way, with units converted and the right versioned emission factor applied. Scope becomes a tag, not a maze. See how this builds a full Scope 1, 2 and 3 inventory.
Bills and meter readings, with evidence attached
Utility bills are still the backbone of Scope 1 and 2 data. Two details make a big difference:
- Attach the evidence. Upload the bill or a photo of the meter with each entry, so a reviewer or verifier can see the source.
- Split periods properly. Bills rarely match calendar months. An entry that covers, say, 14 March to 16 April should be split across both months automatically so monthly dashboards stay accurate.
Meter readings can be entered as opening and closing values, letting the system work out consumption and flag a reading that goes backwards.
Business travel from airport codes
Flights are a common source of error. Instead of asking people to estimate distances, enter the departure and arrival airports. The system can calculate the great-circle distance with a standard uplift, decide whether the flight is domestic, short-haul or long-haul, apply the cabin class and handle returns and multiple travellers. Hotel nights, rail and taxis follow the same pattern.
Templates for bulk upload
When a site already keeps data in Excel, retyping it wastes time. Structured CSV or Excel templates let teams upload many lines at once. The upload should validate units, sites and dates before anything is saved, and show exactly which rows failed and why.
ERP and finance systems: batch runs
For larger organisations, fuel purchases, fleet cards, purchased goods and travel spend already live in ERP or expense systems. Scheduled batch runs can bring that data in automatically. Three controls make batch imports trustworthy:
- Reconciliation — totals received are compared with totals in the source system.
- A transfer log — every run is recorded with what was received, excluded and created.
- Retry and alerts — failed runs are flagged and can be retried without duplicating data.
Field app, QR codes and surveys
Some data is best captured where it happens: a generator log, a refrigerant top-up, a waste collection. QR codes on site let staff open the right form on a phone. Short surveys work well for things like employee commuting, where you need a sample rather than an invoice.
Suppliers report directly
For Scope 3, the most accurate data comes from suppliers themselves. A supplier portal lets them sign in with an e-mail and access code and report emissions, targets or product footprints directly — no spreadsheets passed around by e-mail.
Quality checks before approval
More data means more chance of error. Every entry, whatever its source, should be tested before it counts. EKOTRACE compares each entry with the six-month history for the same item at the same site and flags anything outside a set range (±35% by default). Flagged entries go to a reviewer; clean ones can be approved in bulk with "Approve all without warnings". A different person from the one who entered the data must approve it.
Keep collection on a calendar
A Collection calendar sets due dates per site and owner, sends reminders before the deadline and escalates afterwards. Data progress shows every facility and month as approved, in review, partial or missing, so gaps are visible early rather than at year end.
Record data type and quality as you go
Not every figure is equally reliable. Mark each entry as actual, estimated or proxy, and record which meter or asset it came from. That small step pays off at reporting time: data quality summaries, uncertainty notes and assurance sampling all depend on it. It also shows where to invest next — sites still running on estimates are the obvious candidates for better metering or an ERP integration.
What is next: reading bills automatically
Automatic reading of scanned bills (OCR) is on our roadmap. As with every other source, extracted values will go through the same checks and human approval before they count.
Frequently asked questions
Which method should we start with?
Guided entry and templates for sites; batch runs once volumes justify the integration effort.
Can different sites use different methods?
Yes. All routes land in the same ledger and pass the same checks.