ESG Reporting Moved From 'Nice-to-Have' to Mandatory in 2026—But Nobody Told Small Businesses How to Track Scope 1, 2, and 3 Emissions in Their Accounting System

General
1

Been diving into the ESG reporting landscape this quarter and honestly? It’s getting real for businesses of all sizes—faster than most people expected.

The Regulatory Reality Check

Here’s what changed in 2026:

  • California SB 253 now requires companies with over $1 billion in annual revenue to report Scope 1 and 2 greenhouse gas emissions (starting with 2025 data, filed in 2026). Scope 3 reporting follows in 2027.
  • EU CSRD expanded to listed SMEs as of January 2026, though there’s an opt-out until January 2028. The “double materiality” requirement means you report BOTH how sustainability risks affect your company AND how your company impacts society.
  • The SEC climate disclosure rule remains in legal limbo after the administration change, but Large Accelerated Filers were originally facing March 2026 compliance deadlines.

“But Fred, I’m not a $1 billion company!” I hear you. Neither am I. But here’s the thing: supply chain pressure flows downhill. Your biggest client’s biggest client is probably subject to Scope 3 requirements—and Scope 3 means their supply chain emissions, which includes you.

The Small Business Tracking Gap

I started looking at how small businesses and solo practitioners are supposed to track this stuff, and found a massive gap:

  • Specialized carbon accounting software (Persefoni, Sweep, Greenly) costs €3,000-€80,000/year. That’s absurd for a 10-person company.
  • SME-focused tools like Normative offer free carbon calculators, but they’re simplistic—no integration with your actual financial records.
  • Spreadsheets are what most small businesses default to. Error-prone, manual, and exactly the kind of “we’ll figure it out later” approach that creates compliance nightmares.

The Beancount Opportunity

This is where my brain went immediately: can we track environmental metrics alongside financial data in Beancount?

The concept would be extending your chart of accounts with metadata:

2026-04-01 * "Pacific Gas & Electric" "Monthly electricity"
  Expenses:Utilities:Electricity    450.00 USD
  Assets:Checking
  ; kwh: 2800
  ; co2_kg: 560
  ; scope: 2
  ; source: "EPA eGRID 2025 CAMX subregion"

2026-04-02 * "United Airlines" "SFO to ORD business trip"
  Expenses:Travel:Flights    1200.00 USD
  Assets:Credit-Card:Amex
  ; miles: 1846
  ; co2_kg: 428
  ; scope: 3
  ; calculation: "DEFRA 2025 domestic flight factor"

Then you could query it:

SELECT account, sum(number(co2_kg)) as total_emissions, sum(position) as cost
  WHERE scope = "2"
  GROUP BY account

Over time your Beancount ledger becomes a unified financial AND environmental record.

Where I’m Stuck

I’ve been prototyping this for my personal ledger (tracking my household carbon footprint alongside FIRE metrics—because what’s the point of financial independence if the planet’s on fire, right?). But I’ve hit several questions:

  1. Emission factor databases are a mess. EPA publishes eGRID for electricity, DEFRA has transport factors, but there’s no single source. And factors change annually. Should we build a Beancount plugin that auto-looks up emission factors?

  2. Metadata vs. dedicated accounts. Is metadata the right approach, or should CO2 be tracked as its own “currency”? Like 500 CO2_KG as a posting? That would enable balance assertions and proper accounting of emissions.

  3. Scope 3 is basically impossible for small businesses. Your suppliers’ emissions, your customers’ usage of your product, employee commutes… the data just doesn’t exist at small scale. Is approximate good enough?

  4. Who needs this NOW vs. someday? Am I overengineering my personal ledger, or am I building skills that will be mandatory for businesses within 2-3 years?

Questions for the Community

  • Does anyone track non-financial metrics (carbon, water, waste) alongside financial data in Beancount? What metadata schema do you use?
  • Is the “Beancount as unified financial + environmental ledger” concept viable, or should these be separate systems?
  • For CPA/bookkeeper folks: Are your clients asking about ESG tracking yet? Or is this still “big company problems” in your world?
  • Plugin idea: A Beancount plugin that reads expense transactions, matches them against emission factor databases (EPA, DEFRA), and auto-generates CO2 metadata. Would you use this? Would you help build it?

I’m genuinely curious whether this is just me being a data nerd, or whether there’s a real community need here.