Why Your General Ledger Is the Best Emissions Data Source You Are Ignoring

There is a strange industry pattern where carbon accounting is treated as a separate discipline from financial accounting. Consultants build models in isolated workbooks. Sustainability teams collect data through email chains. Nobody consults the general ledger, even though it contains the highest-fidelity record of company activity anywhere in the business.

That gap is not a technical necessity. It is a legacy of how the field grew up. Closing it is the largest single efficiency gain available to a mid-market company. Here is why.

What does the general ledger actually contain that emissions accounting needs?

Emissions inventories need three things: activity data, a source for that data that is complete, and an audit trail. The general ledger provides all three for the majority of Scope 3 categories.

• Activity data. Every invoice paid, every vendor charged, every service consumed. That is the definition of activity for spend-based emissions.
• Completeness. The ledger has to balance. If a dollar left the company, it is in the ledger. Emissions inventories, by contrast, are famously incomplete when built ad hoc.
• Audit trail. Every ledger entry ties to a source document, an approval, and a posting date. That is exactly what emissions assurance requires.

Compared to the alternative (surveying department heads, requesting spreadsheets from suppliers, reconstructing activity from memory), the ledger is a substantially better data source for the categories it covers.

How does GL account to emission factor mapping actually work?

Published emission factor datasets are organized by sector code. EPA USEEIO uses NAICS codes. Exiobase uses its own sector taxonomy. DEFRA uses UK sector categories. Each has 300 to 500 categories.

Your chart of accounts typically has 40 to 100 expense accounts. Mapping is a one-time exercise.

Once the mapping table exists, every future transaction posted to that account inherits the factor. New accounts require one mapping decision. This is not a heavy ongoing burden.

What is the accounting analogy that makes this click?

Think of emissions accounting as running a parallel ledger in the same accounting system.

• Your financial ledger tracks dollars in and out per transaction.
• Your emissions ledger tracks tCO2e per transaction.
• Both use the same source documents.
• Both need to reconcile at close.
• Both are subject to assurance review.

The methodology, the controls, the audit trail: they are the same discipline applied to a different unit. Once you frame it this way, the arguments for keeping sustainability data in a separate spreadsheet system stop making sense.

What categories cannot be built from ledger data?

Ledger data does not cover everything. Four categories need supplementary sources.

• Scope 1 fuel combustion. You need volumes (gallons, therms), not dollars. Utility bills provide this; the ledger only shows the invoice amount.
• Scope 2 electricity. kWh is the unit, from utility bills. Ledger amount alone would use a spend-based factor and miss the grid regionality.
• Employee commuting. Never appears in the ledger. Requires a survey or transit card data.
• Use of sold products (Category 11). Requires product engineering data, not spend.

For everything else, the ledger is either the primary source or a strong cross-check.

How do you handle transactions that map to multiple factors?

Some accounts hold heterogeneous spend. A generic "office expenses" account might include furniture, cleaning services, and coffee. Two approaches work.

• Blended factor. Compute a weighted average factor based on historical composition of the account. Use it going forward. Revisit annually.
• Vendor-level override. For material vendors within a mixed account, map at the vendor level rather than the account level. Requires slightly more setup but improves accuracy.

Neither approach is more correct than the other; the choice depends on how much material spend passes through mixed accounts and how much precision you need.

What is the audit trail benefit of ledger-based emissions?

When an assurance reviewer samples ten Scope 3 line items and asks how you got the numbers, the ledger-based answer is:

1. Here is the ledger transaction (invoice number, vendor, amount, date, posting user, approval workflow).
2. Here is the account it was posted to.
3. Here is the mapping from that account to a USEEIO sector code (documented in the methodology appendix, version-controlled).
4. Here is the emission factor value (USEEIO 2022 revision A, sector 541800, factor 0.412 kg CO2e per dollar).
5. Here is the calculation (amount times factor equals tCO2e).

That trail is walkable in ten minutes. The alternative (spreadsheet-based emissions with typed numbers) can consume weeks in assurance response.

What emission factor dataset should you use with the ledger?

Choose based on geography and industry.

• US-based, general purpose. EPA USEEIO. Free, updated regularly, aligns with NAICS codes that map cleanly to standard US charts of accounts.
• UK-based. DEFRA GHG Conversion Factors. Widely used in UK reporting.
• Global or multi-country. Exiobase for multi-regional coverage. Ecoinvent for higher resolution (paid).
• Sector-specific overlays. For financial services, PCAF factors. For real estate, CRREM. For agriculture, sector-specific datasets exist.

Pick one primary dataset. Document the version in your methodology. Only change when the assurance provider asks or when a factor material to your report is updated by the source.

What breaks this workflow?

Three failure modes.

• Aggressive account consolidation. If your COA has only 10 accounts, you cannot map to sector-level factors with any granularity. Fix by adding subaccounts or using vendor-level overrides on the largest categories.
• Manual journal entries without vendor detail. Bulk journal entries that lump multiple activities into one line lose the vendor context. Require vendor-level detail on entries above a materiality threshold.
• Multi-entity consolidation gaps. If subsidiaries use different charts of accounts and you consolidate for financial statements but not for emissions, you introduce a boundary mismatch. Consolidate emissions using the same logic as the financial roll-up.

All three are fixable. None require re-architecting the accounting system.

The mistake to avoid

The assumption that carbon accounting is a separate discipline from financial accounting is where the industry has been quietly overspending for a decade. The ledger is the highest-fidelity, most complete, most auditable record your company produces. Using it as the backbone of Scope 3 is not a shortcut; it is closer to the standard than most consultant-led approaches. The teams that get this right treat emissions as another dimension on the same transaction, not as a parallel data collection exercise. Everything else follows from that reframe.