For auditors & accountants

Carbon data that survives assurance

Every number in a GreenKPO report is backed by an immutable audit trail. Not a PDF. Not a spreadsheet. A timestamped, tamper-evident evidence chain — from data entry to signed report.

ISO audit provenCSRD ESRS E1 alignedGHG Protocol methodologyPowered by KPOTrust

The problem

Most carbon reports can't survive scrutiny

When an auditor asks 'show me the source data behind this figure' — most carbon tools produce a spreadsheet. GreenKPO produces an evidence chain.

Typical carbon tool

  • Report is a PDF with no traceable source data
  • Data entered manually into spreadsheets
  • No record of who changed what or when
  • Vendor data collected via email, stored nowhere
  • Assurance requires rebuilding the data trail

GreenKPO

  • Every figure linked to its source record
  • Immutable field-level change log on every entry
  • Timestamped, user-attributed, tamper-evident
  • Vendor data captured via structured survey portal
  • Evidence ready before the auditor asks

How it works

The audit evidence chain

Five stages. Each one produces structured, timestamped evidence that flows automatically into the report.

  1. 1

    Data collection — structured, not free-form

    Employee survey, IT survey, financial ledger upload, and vendor portal survey capture activity data in defined fields with validation rules. No manual re-entry. No spreadsheet hand-offs.

    Each submission timestamped and user-attributed on save
  2. 2

    Calculation — approved methodology, traceable factors

    Emissions calculations use DEFRA and GHG Protocol approved factors. Every calculation is logged — the factor used, the version, the date applied. If a factor is updated, the change is recorded.

    Methodology details available on the KPOData platform per calculation
  3. 3

    KPOTrust audit trail — immutable field changes

    Every change to every field is written to the KPOTrust immutable log — trigger type, previous value, new value, status, user, timestamp. Records cannot be altered or deleted. Same infrastructure that passed an ISO audit for Standard Chartered, Siemens, and Wood PLC.

    Append-only log — no edit, no delete, full history preserved
  4. 4

    Report generation — figures linked to source

    Every figure in the GHG Carbon Planning Report maps to a token pulled directly from platform data. There is no manual step between data and report. The report is a structured output of the evidence, not a separate document.

    Token mapping available for auditor review per report section
  5. 5

    Assurance-ready export — give auditors what they need

    Auditors receive a structured evidence pack: the report, the KPOTrust change log, the source survey data, and the calculation methodology reference. Everything needed to sign off limited or reasonable assurance under CSRD.

    Structured export — no manual assembly required

Proven in production

Audit-ready at enterprise scale

The KPOTrust infrastructure underpinning GreenKPO has already been used as audit evidence by enterprise clients in regulated industries.

80+Legal entities managed in a single instance
150KUsers on the platform across enterprise clients
ISOAudit passed using platform change-control as evidence

Financial services

Standard Chartered and Muzinich.

Industrial enterprise

Siemens Healthineers and Wood PLC, 60 and 80+ entities.

ISO audit evidence

Platform change-control used as primary audit evidence.

Multi-jurisdiction

Ireland, UK, France, Singapore. CSRD, GHG Protocol, DEFRA.

Common questions

Common questions

What level of assurance does GreenKPO support?

The platform is designed to support limited assurance (required from 2025 under CSRD) and is being built toward reasonable assurance (required from 2028). The KPOTrust audit trail provides the evidence layer that makes both levels achievable without manual data reconstruction.

Can we access the audit trail directly as assurance providers?

Yes. The KPOTrust audit log is exportable as a structured evidence pack. We can scope auditor access to the relevant reporting period and entity boundary.

How is vendor-reported Scope 3 data validated?

Vendor data is collected via a structured portal survey with field-level validation — not email or spreadsheet. Each submission is timestamped and attributed. The data quality split (measured vs estimated) is surfaced in the report and the evidence pack.

What happens if a client corrects a figure after submission?

Every correction is written to the KPOTrust immutable log with the previous value, new value, user, and timestamp preserved. The audit trail shows the full history — not just the current state.

Ready to see the evidence chain?

Book a technical walkthrough for your assurance team.

Book a walkthrough
Check Your Carbon Readiness