The large enterprise carbon accounting tools are excellent products built for a specific buyer: a global company with a dedicated sustainability team, a seven-figure software budget, and 18 months to onboard. Watershed, Persefoni, and similar platforms serve that buyer well. But most of the companies now facing mandatory disclosure under CSRD, the SEC climate rule, or customer pressure from large-enterprise supply chains are not that buyer. They are 75-person manufacturers, 300-person logistics operators, 150-person professional services firms. They have one sustainability manager, or a finance controller who inherited the project, and zero appetite to spend more on software than they spend on accounting.
We built Emitpulse because we spent time inside that gap and saw how bad the options were. You either pay for a platform designed for a company 10x your size, or you do everything in spreadsheets, or you hire a consultant for a one-time report that is out of date before the ink dries. None of those work if you have an annual filing obligation.
What "Disclosure Mandate" Actually Means for a Mid-Market Company
The CSRD's scope under the Large Undertakings definition captures EU companies meeting two of three thresholds: more than 250 employees, more than EUR 50 million in net turnover, or more than EUR 25 million in total assets. That encompasses a large number of companies that would not typically describe themselves as "enterprise." The first wave of filers (large public-interest entities) reported for financial year 2024. The second wave, capturing large undertakings not previously covered, applies to financial year 2025. If you are a 300-person manufacturing company with EUR 60 million in turnover and a German or French subsidiary, you may already be in scope.
The SEC climate disclosure rule, following litigation delays and rule revisions, requires Scope 1 and Scope 2 emissions disclosure from larger reporting companies and accelerated filers, with Scope 3 remaining voluntary. But the supply chain pressure mechanism is often more immediate than the direct regulatory trigger: large US-listed companies now disclosing Scope 3 Category 1 (purchased goods and services) will request supplier emissions data. If you sell to those companies, they will ask.
The Complexity Mismatch
Enterprise carbon accounting platforms are built around the assumption of high data complexity: hundreds of facilities, dozens of ERP integrations, multi-country grid factors, complex internal carbon pricing, financed emissions calculations under PCAF. That complexity is real at Fortune 500 scale, but it is overkill for most mid-market companies whose Scope 1 and 2 footprint fits on a single page.
A mid-market manufacturer in the US Midwest typically has: a handful of owned or leased facilities with known electricity and gas consumption, a fleet of vehicles for which they can get fuel purchase records, and business travel that shows up on credit card statements. Their Scope 3 obligations, at least in year one, are likely categories 1 (purchased goods and services) and 7 (employee commuting) as required disclosures under CSRD, and possibly category 11 (use of sold products) if they sell physical goods into regulated supply chains. That is a tractable dataset, not a six-month implementation project.
We are not saying simple automatically means fast. Getting clean fuel consumption data from a fleet of 40 vehicles, matching it to vehicle records, and applying the right DEFRA or EPA emission factors per vehicle type takes real work. But it is work you can do with a properly designed interface and a pre-built emissions factor library, not a bespoke consulting engagement.
The Spreadsheet Problem and Why It Gets Worse Under Audit
The spreadsheet approach works for year one. A finance controller who understands the GHG Protocol can build a defensible model, pull consumption data from utility bills and fuel records, apply published factors, and produce a number. We have seen it done well. The problems start in year two.
First, year-over-year comparability: if the factor library used in year one was DEFRA 2022 and you update to DEFRA 2024 in year two, your baseline changes. The GHG Protocol's Corporate Standard requires you to recalculate historical years when a significant emission factor update occurs. In a spreadsheet, that is manual and error-prone. In a versioned carbon ledger, it is a factor update operation with a clear audit trail.
Second, audit readiness: the CSRD requires third-party limited assurance on climate disclosures from financial year 2025, with reasonable assurance phased in from 2028. Limited assurance under ISAE 3000 means an external verifier will trace reported figures back to source data. "Here is the spreadsheet" does not satisfy that requirement. They need to see which factor version was applied to which consumption figure and when that calculation was made.
A mid-size distribution company we worked with early on had done three years of voluntary reporting in spreadsheets. When they faced their first limited assurance review, the verifier spent more time reconstructing methodology documentation than on the actual data. The reported figures were fine. The audit trail was not. That is a fixable problem, but it takes two to three cycles to rebuild properly.
What a Realistic First-Year Setup Looks Like
For a company starting from scratch with a CSRD filing obligation for financial year 2025, a realistic setup has three phases.
Phase one is data inventory, running through the first two months. You identify every data source that feeds into Scope 1, 2, and the Scope 3 categories in your materiality boundary. Utility bills, fuel purchase records, fleet management system exports, business travel booking system reports, spend data from accounts payable for purchased goods. You do not need all of it clean immediately. You need to know what exists and where.
Phase two is baseline calculation, running through months three and four. You load the data, apply emissions factors from a maintained library (DEFRA, EPA eGRID, IPCC AR6 for refrigerants), and produce a first-pass inventory. This is where you find the gaps: a subsidiary whose electricity consumption was not reported, a refrigerant top-up event that nobody logged, business travel that was expensed outside the standard system.
Phase three is documentation and assurance prep. Every calculation needs a methodology note. Every factor needs a source reference and version date. If you have market-based Scope 2 claims from RECs or Guarantees of Origin, the retirement certificates need to be attached to the relevant calculation entries. The output is not just a number but an auditor-ready package.
Choosing a Tool That Fits the Work
When evaluating software, the question to ask is not "does it cover all 15 Scope 3 categories" but "does it match the complexity of my actual inventory and produce audit-ready output." A tool that costs $800 per month and gets you through your CSRD ESRS E1 filing with clean documentation is more valuable than a platform that costs $50,000 per year and requires a six-month implementation before you can run a single report.
The practical checklist for a mid-market buyer: pre-built emissions factor libraries that update with each DEFRA and EPA eGRID release; clear factor versioning so you can see what was applied to every calculation; dual Scope 2 reporting (market-based and location-based as separate ledger rows); CSRD ESRS E1 report output that maps to the actual disclosure requirements, not a generic PDF export; and some form of audit trail that shows the chain from source data to reported figure. Supplier data request functionality matters if you have meaningful Scope 3 Category 1 exposure, but it is not the first thing to optimize for.
The entry point does not have to be the full suite. Start with Scope 1 and 2, establish a clean baseline, and expand to Scope 3 categories as your filing obligations and data availability mature. The important thing is that the foundation is auditable from day one, not retrofitted after an assurance provider asks uncomfortable questions about your spreadsheet formula structure.