Climate Data Hub
The hard part of corporate emissions reporting is coverage: every line of spend needs an emission factor. This is the ledger that gets a year of ERP spend fully mapped.
What the reporting actually needs
A science-based target commits an organisation to a number it has to defend. The hard part isn't the calculation. It's that every line of spend has to map to an emission factor, the factor that applied at the time, and any line that doesn't map is a hole in the disclosure.
The Climate Data Hub is the central ledger and dashboard that closes those holes: around half a million rows of annual ERP data, processed end to end into a model that reporting and assurance both work from.
Getting to full coverage
The dataset reaches 100% emission-factor coverage through a set of temporal logic rules instead of hand-mapping the long tail. Factors are time-dependent: a category's factor changes between reporting years, so the rules select the one in force for each transaction's date rather than the current one. Get that wrong and prior years get quietly restated. Power BI Dataflows carry the transformation, keeping the logic in one governed place instead of duplicated across report files, and ERP integration supplies the procurement spend the model is built on.
Why it is a ledger
It's a ledger, not a dashboard, because assurance asks how a figure was arrived at, and a number you can't trace back to the transactions behind it isn't defensible. The model keeps the line-level detail underneath the aggregate.
- Role
- Data pipeline and model design
- Status
- In production, ongoing
- Scale
- ~0.5M rows of ERP data annually
- Coverage
- 100% emission-factor mapping
- Stack
- Power BI Dataflows, DAX, ERP integration, GHG Protocol