Carbon accounting that starts with the bills you already have.
Upload a utility bill, a fuel statement or a freight note. NetZero SME extracts the consumption, applies the official emission factor for your grid and year, and builds a GHG Protocol inventory you can hand to a bank, a buyer or an EU customs declaration.
The demo workspace is a Selangor aluminium extruder with two years of operating data and twelve months of CBAM declarations already in it.
Built for three kinds of buyer
Export manufacturers
Embedded emissions per tonne of finished product, split into the direct and indirect intensities an EU CBAM declaration asks for.
Service providers & tech vendors
Corporate Scope 1, 2 and 3 for the European and US enterprise clients auditing your supply chain โ office energy, cloud hosting and travel.
Domestic SMEs
The disclosure a sustainability-linked loan or a PLC tender actually requires, produced from the bills you already receive.
From a PDF to a disclosure
- 1
Drop in a bill
TNB, SESB, Sarawak Energy, SP Group, Air Selangor, a Shell fleet statement or a freight note. A consolidated SP bill is decomposed into separate electricity, gas and water records.
- 2
The engine does the arithmetic
Units are normalised, the right regional grid factor is resolved for the year of consumption, and Scopes 1, 2 and 3 are assigned per the GHG Protocol.
- 3
A human verifies
Every draft lands in a review queue beside the source document. Nothing enters the inventory โ or any disclosure โ until someone approves it.
- 4
Export the disclosure
Bursa Malaysia, SGX Core ESG, EU CBAM or CSRD/ESRS E1 โ generated from the verified figures, with the factor and authority behind every number.
What makes the numbers defensible
- Every record stores the factor value, the issuing authority and the year it was applied โ so a figure can still be explained a year later, even after the factor is revised.
- Edits to a verified figure send it back for re-approval instead of quietly changing a number an auditor already signed off.
- The audit trail is append-only at the database level: the application role holds no UPDATE or DELETE grant on it.
- Tenant isolation is enforced by Postgres row-level security, not by a WHERE clause someone might forget.
- Market-based Scope 2 is reported alongside location-based, never instead of it.