CarbonComply

How it works

Data in. The right number out. Nothing files without a record.

Four steps, in a fixed order — data has to exist before it's calculated, calculated before it's filed, filed before it's audited. Here's what actually happens at each one.
Book a compliance assessment
  1. 01

    Data in

    Plant data, however you already keep it.

  2. 02

    Calculation engine

    The right methodology per sector, per regulation.

  3. 03

    Filing

    Output in the shape the regulator expects.

  4. 04

    Audit trail

    Every step hash-chained, immutable, verifiable.

Step 01

Data in

Production volumes, fuel and energy consumption, and purchased electricity — from whichever system you already use to track them:

  • CSV or Excel upload, for plants that track this in spreadsheets today.
  • Direct Tally or SAP connectors, for plants where it already lives in an ERP.
  • AI extraction from invoices and utility bills, for the data that only exists on paper.

The point is not to make you change how you keep records before you can start — it's to get what you already have into one place.

Step 02

Calculation engine

One data set, run through the methodology for your sector and regulation — the engine knows a tonne of clinker is calculated differently from a tonne of primary aluminium, and that CBAM's embedded-emissions method isn't CCTS's GEI method, even when they're both drawing on the same plant.

That means the same underlying numbers produce both a CBAM-compliant embedded-emissions figure and a CCTS GEI figure — you enter your plant data once, not twice.

Where supplier-verified data exists, it's used in place of EU default values automatically — see the CBAM page for how that data gets collected.

Step 03

Filing

Output in the shape the regulator actually asks for — a CBAM report your importer can file through the EU's registry, or CCTS compliance output in BEE's format. Not a generic sustainability PDF you'd still have to translate into a filing yourself.

If you're obligated under both regimes, both filings come off the same underlying calculation, so the numbers can't quietly drift apart between them.

Step 04

Audit trail

Every event — a data upload, a supplier declaration, a recalculation, a filing — is written into a hash chain: each entry's hash is derived from the entry before it, so nothing can be quietly edited or deleted after the fact. Corrections are recorded as new entries, not overwrites.

Your verifier doesn't get a PDF export of your evidence — they get read-only access to the actual chain, and can independently confirm it hasn't been tampered with.

Want to see it against your own data?

Bring a real month of production and utility data and we'll walk through what the engine actually produces.

Book a compliance assessment