Persefoni vs Watershed

Requirement evaluated: The platform must calculate a full Scope 1, 2, and 3 greenhouse-gas inventory aligned to the GHG Protocol, explicitly covering the hard Scope 3 categories (purchased goods and services, upstream and downstream transportation, use of sold products, investments, and employee commute) without requiring manual spreadsheet assembly. Each category calculation must identify whether the underlying activity data is primary (supplier-measured) or estimated (spend-based or average-data method), with that distinction surfaced in the output.

For a publicly traded company replacing a consultant-built spreadsheet with an auditable inventory, Persefoni's integrated Emissions Calculation Engine ingests activity and spend data and calculates a full Scope 1, 2, and 3 inventory without manual spreadsheet assembly. <cite index="12-1">The engine is aligned with both the Greenhouse Gas Protocol and the Partnership for Carbon Accounting Financials (PCAF), leverages a global set of out-of-the-box emission factors, and allows creation of custom emission factors unique to the business.</cite> All 15 GHG Protocol Scope 3 categories are pre-built into the platform. …

Limitations: The AI-powered natural language emission factor mapping for spend files (which would further automate Category 1 spend-based calculations) is <cite index="5d7bd313-950f-48fb-a5d5-95d0b52d1bf9">labeled 'Coming Soon'</cite>, so buyers relying on automated spend-file-to-emission-factor mapping at scale today will need to …

Requirement evaluated: The platform must calculate a full Scope 1, 2, and 3 greenhouse-gas inventory aligned to the GHG Protocol, explicitly covering the hard Scope 3 categories (purchased goods and services, upstream and downstream transportation, use of sold products, investments, and employee commute) without requiring manual spreadsheet assembly. Each category calculation must identify whether the underlying activity data is primary (supplier-measured) or estimated (spend-based or average-data method), with that distinction surfaced in the output.

Watershed directly addresses the buyer's need to replace an annual consultant-built spreadsheet with a continuously auditable, automated GHG inventory. The platform ingests activity and spend data from utility bills, ERP systems, travel tools, and supplier surveys via APIs and AI-driven PDF ingestion, then automatically applies emission factors to calculate Scope 1, 2, and all 15 Scope 3 categories aligned to the GHG Protocol. For Scope 3 calculation, Watershed uses its proprietary CEDA database (60,000 geographically-differentiated spend-based emission factors across 400 industries and 148 countries) …

Limitations: For the hardest downstream Scope 3 categories (notably use of sold products, Category 12), spend-based databases do not yet provide methodology coverage, so calculations rely on activity-based data (units sold, energy use per unit) …

Requirement evaluated: The platform must maintain a complete, immutable audit trail covering every data input, emission factor selection, calculation step, methodology change, and user action, sufficient to support third-party limited assurance engagements without supplemental documentation from the buyer. The audit trail must be exportable in a format that an external assurance provider can independently review, directly addressing the buyer's stated problem that the current spreadsheet is not auditable.

For a publicly traded company replacing an un-auditable consultant spreadsheet, Persefoni's Footprint Ledger is the core mechanism. The platform's named 'Activity & audit logs' feature records every data addition, modification, and deletion alongside the identity of the user who made the change, directly addressing the buyer's stated problem of non-auditable spreadsheet processes. …

Limitations: Persefoni's public documentation describes the audit log in terms of user-stamped add/modify/delete events and per-calculation factor visibility, but does not publicly document cryptographic immutability (e.g., hash-chaining or write-protected append-only storage) …

Requirement evaluated: The platform must maintain a complete, immutable audit trail covering every data input, emission factor selection, calculation step, methodology change, and user action, sufficient to support third-party limited assurance engagements without supplemental documentation from the buyer. The audit trail must be exportable in a format that an external assurance provider can independently review, directly addressing the buyer's stated problem that the current spreadsheet is not auditable.

For a publicly traded company replacing an unauditable spreadsheet, Watershed maintains complete audit trails for all carbon data, recording how every emissions figure was calculated and which emission factors were applied. The mechanism has two layers: first, the platform's data lineage engine traces each calculation from raw activity data input through emission factor selection to final output, making the chain inspectable within the platform; second, external auditors can be granted direct read access to view data lineage, inspect supporting evidence, review calculation chains, and verify audit trails without relying on supplemental buyer documentation (Watershed CSRD blog, watershed.com/ …

Limitations: The technical architecture of the audit log (for example, whether entries are cryptographically hashed or append-only at the database level) is not publicly documented, so a buyer requiring the highest-evidence immutability guarantees for a reasonable-assurance engagement should ask Watershed to demonstrate the specifi …

Requirement evaluated: The platform must support science-based or internally defined decarbonization target setting, allow the buyer to track actual emissions trajectories against those targets by scope and business unit, and model abatement scenarios. This capability must be connected to the same verified inventory data used for external disclosure, so that target progress reporting is consistent with the publicly disclosed figures required under the SEC and CSRD regimes.

For a publicly traded company needing target progress to reconcile exactly with SEC and CSRD disclosed figures, Persefoni addresses this through two connected components that both draw from the same Footprint Ledger inventory. First, the 'Reduce Footprint' feature, embedded in the core Climate Management and Accounting Platform (CMAP), lets users model percent-reduction scenarios across Scopes 1, 2, and 3 individually, visualize year-over-year progress against a target reduction goal, and identify which footprint sources offer the greatest abatement opportunity. …

Limitations: Publicly available documentation for CTM and Reduce Footprint describes tracking against a 'corporate target' and scope-level decomposition, but does not explicitly confirm that sub-targets can be configured at the business-unit or subsidiary hierarchy level and rolled up to the consolidated group total; buyers with ES …

Requirement evaluated: The platform must support science-based or internally defined decarbonization target setting, allow the buyer to track actual emissions trajectories against those targets by scope and business unit, and model abatement scenarios. This capability must be connected to the same verified inventory data used for external disclosure, so that target progress reporting is consistent with the publicly disclosed figures required under the SEC and CSRD regimes.

For a publicly traded company needing auditable target progress that is numerically consistent with SEC and CSRD disclosures, Watershed operates through a single verified inventory that feeds both its decarbonization planning tools and its external disclosure workflows. On the measurement side, Watershed produces a scope 1/2/3 inventory with complete audit trails and 150+ error checks; on the strategy side, the platform's dedicated 'Act' module lets teams model SBTi-aligned targets, compare abatement scenarios (clean power procurement, supply chain switching, cloud optimization, and other levers), and track actual emissions trajectories against those targets. …

Limitations: Public documentation confirms scope-level and category-level target tracking but does not fully detail how sub-targets decompose to individual business units or legal entities and roll up to a consolidated group target; buyers with complex multi-subsidiary structures under ESRS E1 should verify this hierarchy in a demo …

Requirement evaluated: The platform must ingest activity and spend data from at least four named source systems: utility bills, ERP spend exports, corporate travel systems, and supplier survey responses. Each data connection must maintain a documented lineage record showing the source, ingestion timestamp, and transformation applied, replacing the current consultant-built annual spreadsheet with a continuously updatable data pipeline.

For a publicly traded company replacing a consultant-built spreadsheet with a continuously auditable pipeline, Persefoni's Integration Hub provides named connectors to each of the four required source types: 9,000+ utility providers for Scope 1/2 consumption data, SAP Concur and Navan/TripActions for corporate travel activity, NetSuite and SAP Ariba/Coupa for ERP spend exports, and the Scope 3 Data Exchange module for supplier survey responses. Once connections are authenticated, the platform automatically extracts activity data on a configurable cadence and calculates footprints. …

Limitations: The documented audit log captures user-action timestamps and per-calculation factor transparency, but available public documentation does not explicitly confirm that connector-level ingestion events are stamped and stored as individual provenance records per raw activity row (versus per-import batch or per-user action) …

Requirement evaluated: The platform must ingest activity and spend data from at least four named source systems: utility bills, ERP spend exports, corporate travel systems, and supplier survey responses. Each data connection must maintain a documented lineage record showing the source, ingestion timestamp, and transformation applied, replacing the current consultant-built annual spreadsheet with a continuously updatable data pipeline.

For a publicly traded company replacing a consultant-built annual spreadsheet, Watershed provides a multi-source data ingestion pipeline that covers all four source types the buyer requires. For utility bills, <cite index="14-4,14-5">facility-related emissions data arrives in non-standardized PDFs; Watershed addresses this with an AI-powered utility bill ingestion tool that automatically extracts and validates emissions data from PDFs with audit-ready transparency.</cite> For ERP spend and travel systems, <cite index="4-7,4-8">Watershed connects with ERP systems like SAP and Oracle for procurement and spend data, and with travel booking tools like Concur and Navan to capture trip-level activ …

Limitations: Available documentation confirms lineage tracking at the transformation and calculation level and describes it as covering "every step of the data transformation process," but does not explicitly specify whether per-record ingestion timestamps (as distinct from per-batch or per-session metadata) …

Requirement evaluated: The platform must include a supplier data collection module that enables the buyer to send data requests to suppliers, receive primary emissions data or product-level carbon footprints directly into the platform, and distinguish that primary data from spend-based estimates in Scope 3 Category 1 and other relevant categories. This replaces ad hoc supplier survey management and is required to improve data quality for the hard Scope 3 categories beyond the spend-based default.

For a publicly traded company moving off a consultant spreadsheet and toward assurance-grade Scope 3 reporting, Persefoni addresses this requirement through two integrated, natively built components: the Scope 3 Data Exchange module and Persefoni Pro. The buyer's sustainability team initiates the workflow inside the platform by sending auditable data requests to suppliers; suppliers do not need to be existing Persefoni customers, and those who have never calculated a footprint can respond by creating a free Persefoni Pro account to measure and share their own emissions. …

Limitations: Published documentation describes requests as 'auditable' and the workflow as replacing spend-based estimates, but granular technical detail on exactly how the platform tags incoming supplier responses as 'primary data' versus retained spend-based estimates in the calculation engine (the precise provenance distinction …

Requirement evaluated: The platform must include a supplier data collection module that enables the buyer to send data requests to suppliers, receive primary emissions data or product-level carbon footprints directly into the platform, and distinguish that primary data from spend-based estimates in Scope 3 Category 1 and other relevant categories. This replaces ad hoc supplier survey management and is required to improve data quality for the hard Scope 3 categories beyond the spend-based default.

For a publicly traded company replacing a consultant-built spreadsheet with auditable Scope 3 data, Watershed's Supply Chain module addresses this requirement end to end. The platform includes built-in supplier portals and workflows that allow the buyer to send data requests directly to vendors and track responses at scale, replacing ad hoc email-based survey management. …

Limitations: Public documentation describes the supplier portal, data request workflows, and primary-data-to-EF transformation at the product marketing level; granular configuration details (e.g., exact campaign-builder UI, structured PCF upload schemas aligned to PACT Pathfinder, or per-category response-tracking dashboards) …