Emission Factor Matching: Why Carbon Accounting Needs AI
'Diesel' on an invoice can hit five different NGA factors, and the wrong one is an audit finding, not a rounding error. Here is how 5-tier matching lands each line item on a factor you can defend, where it still fails, and why it matters more than extraction.
Try a simple test. Take a single fuel docket - "DIESEL 87.3L" printed on a fading thermal receipt - and ask several different carbon accounting tools to calculate the emissions. There is a fair chance you get different numbers, and not every tool will tell you which emission factor it actually used.
The math itself is trivially simple. Activity data times emission factor equals emissions. Everyone who's done this for more than a week knows the formula. But the formula isn't the problem. Emission factor matching is the problem - figuring out which of the many NGA factors (and thousands more across global databases) applies to this specific line item, in this specific context.
That diesel docket? It could be transport fuel for a fleet vehicle (2.7 kg CO2-e per litre, NGA Factors 2025 Table 9). Or it could be stationary energy for an on-site generator (69.9 kg CO2-e per GJ, Table 8 - which you'd need to convert from litres using the energy content of 38.6 GJ per kilolitre). Same word on the receipt. Different table. Different factor. Different answer. And if you're reporting under NGER, applying Table 9 when you should've used Table 8 is an audit finding. Not a rounding error - an audit finding.
The BCG GAMMA survey found companies estimate a 30-40% error rate in their emissions calculations. We'd bet most of that gap comes from factor selection, not from reading the wrong number off a document. You can extract "87.3 litres" perfectly and still get the emissions wrong by a factor of two if the system picks the wrong factor.
The matching problem is harder than the extraction problem
We've written about how our 7-phase AI pipeline extracts data from utility bills. Extraction gets a lot of attention because it's visible - document in, numbers out, satisfying before-and-after. But extraction is the easier half.
Once you've pulled "87.3 litres diesel" from a receipt, you need to answer a chain of questions that a human analyst does instinctively but software struggles with. Is this transport fuel or stationary fuel? What vehicle or equipment consumed it? Which NGA table applies? Was it standard diesel or a biodiesel blend? What's the reporting period and which year's emission factors should I use?
Electricity is its own minefield. You extract 25,000 kWh from a bill. Fine. But the Scope 2 emission factor depends on which state the site is in. Victoria's factor is 0.78 kg CO2-e per kWh. Tasmania's is 0.20. That's not a small difference - it's a 75% gap from the same consumption figure. If you don't know the site location (or the system assigns the wrong state), you can be off by almost four times.
And then there's the really hard category. A line item that reads "$15,000 - IT consulting services." That's not a physical activity. It's a spend figure. It needs a spend-based emission factor in kgCO2e per AUD, not an activity-based one in kgCO2e per kWh or per litre. The factor depends on the industry sector code of the service provider. Spend-based factors are already 30-90% less precise than activity-based ones - but picking the wrong sector makes it even worse.
This is the problem that AI actually needs to solve. Not reading numbers off documents. Matching those numbers to the right factor.
What five tiers give you that a single lookup cannot
We didn't arrive at five tiers because it sounded good in a product spec. We arrived at five tiers because a single matching approach fails too often on real-world data.
Our material library holds pre-loaded NGA factors from DCCEEW and a construction EPD factor library. Every extracted line item runs through the tiers in order. The first tier that returns a high-confidence match wins.
Tier 1 is a direct match. The extracted material name or code maps exactly to an entry in the library. "Grid electricity - NSW" hits the NGA Table 1 factor for NSW at 0.64 kg CO2-e/kWh. This is fast and dead accurate when it works. It often doesn't work on real documents, because real documents don't say "Grid electricity - NSW." They say "Supply charges - Ausgrid network" or just "Electricity" with no state identifier.
Tier 2 is an alias match. This is where things get interesting. When a reviewer corrects a match, or assigns a material to a line that did not match, the system saves the line text as an alias on that material for the organisation (accepting a match that was already right adds nothing). So once a reviewer has mapped "Origin Energy supply charges" to grid electricity in NSW, the next time that phrase appears, Tier 2 catches it instantly. Each correction fills a gap specific to that organisation's retailers and invoice formats. Aliases stay inside the organisation, with no cross-tenant learning, and are capped at 500 per material.
The later tiers loosen the match step by step. They catch naming variations and OCR errors, such as "Diesl" from a damaged receipt standing in for "Diesel", or "Natural Gas - Reticulated" for "Natural gas" in the library. Looser matching also generates more false positives, which is why it sits behind the more precise tiers.
Monetary line items need particular care. "$45,000 catering services" needs a kgCO2e/AUD factor for food services, not a kgCO2e per meal factor that would require a unit the document doesn't contain, and spend-based records are floored to low data quality so nobody mistakes them for activity data.
Every match gets a confidence score. Below the threshold, the system sends it to human review instead of silently applying a factor that might be wrong. That threshold matters more than most people think.
A worked example: what actually happens when you upload a diesel receipt
Here's an illustrative scenario. A construction company's fuel docket reads:
FUEL 142.6L ULP - $248.92 BP EASTLINK 18/01/2026 14:37
Phase 3 of the pipeline extracts: quantity = 142.6, unit = litres, material = "ULP", cost = $248.92, site context = BP Eastlink (Victoria).
The matching engine starts working.
Tier 1: Looks for "ULP" as a direct material name. No exact match - the library has "Petrol - gasoline for use as a transport fuel" from the NGA Factors workbook, not "ULP."
Tier 2: Checks aliases. A reviewer previously corrected "ULP" to the petrol transport factor, so it is saved as an alias. Match found. Confidence: 0.95. Factor applied: approximately 2.3 kg CO2-e per litre (NGA Factors 2025, transport petrol, Scope 1).
The system applies the factor: 142.6L x 2.3 kg CO2-e/L = approximately 328 kg CO2-e.
If there had been no alias? A later, looser tier might still have reached the petrol factor at lower confidence, and if confidence fell below the threshold, the line would have gone to a reviewer.
Now change the scenario. Same 142.6 litres, but the docket says "DIESEL" and the site is a mine site with both haul trucks (transport) and generators (stationary). Tier 2 aliases might map it to transport diesel. But if the fuel at this site goes into generators, it should be stationary diesel instead. Same word, different factor, different emissions. Aliases are saved per organisation, not per site, so where the same fuel serves different purposes at different locations, a reviewer's judgement on site context still matters.
Where the system still breaks
We're not going to pretend this is solved. It isn't.
Novel materials with no close match. Take invoices for "hydrotreated vegetable oil" (HVO100 renewable diesel). If the library has no specific factor, a loose match might land on a biodiesel blend factor. That isn't wrong, exactly, but it isn't right either - HVO has different lifecycle emissions characteristics. A human has to research it and select the appropriate factor, and the correction is saved as an alias. But that first instance? It needs a person.
Confidence scores aren't certainty scores. A match returned at 0.92 confidence feels reassuring. But a 0.92 match can still be wrong - typically where a line item is ambiguous between two plausible factors. "Gas" could be natural gas (stationary energy) or LPG (bottled gas). Context usually resolves it, but not always. High confidence means the system is fairly sure. It doesn't mean the system is right.
Aliases depend on humans actually reviewing. The alias system only helps if people correct wrong matches when they see them. If a user accepts every suggestion without checking, wrong matches stay wrong, and a careless correction is saved as an alias that repeats. We send low-confidence items to review, but we can't force people to pay attention. The alias library is only as good as the care reviewers put into their corrections.
Spend-based matching is inherently imprecise. When an invoice line is "$12,500 - professional services" and the matcher selects a spend-based factor for "professional, scientific and technical services," that factor is a sector average. It doesn't know whether those services came from a one-person home office or a firm running data centres. Spend-based factors can differ from activity-based results by a factor of two, and that's before considering which sector code was chosen. We're honest about this: spend-based matching is a starting point. It gets you into the right order of magnitude. It doesn't get you audit-grade precision.
Why this matters for NGER and ASRS compliance
The Clean Energy Regulator doesn't just check whether you reported emissions. It checks whether you applied the right methodology. Under NGER, diesel used for transport and diesel used for stationary energy are reported under different provisions of the NGER Measurement Determination, with different emission factors from different NGA tables. Apply the wrong one and your NGER submission has a methodological error - the kind the ANAO found in 72% of the 545 reports it audited.
Under ASRS, the stakes rise again. ASSA 5010 phases in assurance requirements progressively - limited assurance on Scope 1 and 2 from Year 1, expanding to reasonable assurance by Year 4. When an auditor reviews your Scope 1 emissions, they won't just check that you multiplied correctly. Expect them to trace the emission factor back to the NGA Factors workbook and test whether you selected the right factor for the right application. An audit trail that shows which factor was applied and why is no longer optional - it's what separates an assurable disclosure from a guess.
This is where the 5-tier system earns its complexity. Each record keeps the factor applied and its version, the verbatim line text it came from, and typed audit events on the ledger write. If an auditor asks "why did you apply transport diesel instead of stationary diesel to this receipt?", the answer can point to the source line and the reviewer correction behind the match.
That level of traceability is what turns emission factor matching from a hidden assumption into a documented, auditable decision.
The difference between matching and guessing
Most carbon accounting tools treat factor selection as a configuration step. You set up your emission factors once - diesel is 2.7, electricity is the national average, natural gas is 51.53 - and then apply them to everything. That works until it doesn't. Until you have a Victorian site and a Tasmanian site on the same electricity factor. Until diesel is going into both trucks and generators. Until an invoice shows up with a line item nobody anticipated.
The shift from configuration to matching is fundamental. Configuration assumes you know all the answers upfront. Matching assumes you don't - and builds a system that looks for the right answer for each line item, saves reviewer corrections as aliases, and records why each factor was applied.
We built Carbonly's material library around NGA factors because the Australian context demands specificity. A factor set built around US EPA data will not, on its own, separate natural gas reported in GJ from natural gas reported in cubic metres under NGA. Nor will it carry WA's separate electricity grids (SWIS and NWIS) with different emission factors, or the AR5-to-AR6 GWP difference between NGER and AASB S2.
We're not sure we've got every edge case covered yet. New material names keep turning up on invoices. A refrigerant blend like R-454B is a good example: if the library has no factor for it, someone has to look up the GWP, create the material entry, and let the alias take it from there.
That's the honest reality. Emission factor matching isn't a solved problem. It's a problem that gets less wrong over time, as reviewer corrections build up the alias library. The gap between "less wrong over time" and "perfect from day one" is where most of the real work in carbon accounting happens.
Pick any invoice from your last NGER submission and trace the emission factor back to the NGA workbook. If you can't explain which table it came from and why - not the number, the why - that's your starting point.
If you want to see how your own invoice lines match, and which ones would go to review, email hello@carbonly.ai.
Related Reading: