How it works
Fixed order
Data in. The right number out. Nothing files without a record.
Step 01
Data in
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.
However you keep it
No system migration required before you can start.
Step 02
Calculation engine
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.
Sector × regulation
A tonne of clinker is not calculated like a tonne of primary aluminium.
Step 03
Filing
Filing
For CBAM, a report your importer can file through the EU's registry. For CCTS, BEE's Form A — the performance assessment itself, generated from the same calculation, with the evidence pack behind it.
A CCTS filing needs Form B as well: your accredited verifier's certificate. We render it from the verification the agency actually recorded, and won't produce it before that exists — because under §5(1) a Form A without a Form B isn't a filing.
If you're obligated under both regimes, both come off the same underlying calculation, so the numbers can't quietly drift apart between them.
The artefact
Not a sustainability PDF you'd still have to translate.
Step 04
Audit trail
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.
Your auditor 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.
Hash-chained
Corrections are new entries, never overwrites.
Access
Who gets what
Not one login for everyone.
Each participant gets access scoped to their job, rather than a shared spreadsheet with everyone's edits in it.
Your auditor
Their own login, read-only, straight into the hash-chained evidence trail — not a PDF export you have to keep re-sending every time they ask a question.
Your accredited verifier (ACVA)
Scoped to the appointment you make, for the compliance cycle you make it for — and closed to your own staff, because §5 assigns the opinion to them and not to you. Their site visit, their findings and their opinion are recorded as they happen, and Form B is rendered from that record rather than retyped from it.
Offset and aggregator data
A separate field-data surface for aggregator organisations feeding offset-project data — energy, industry, agriculture, waste, forestry — into the same credit pipeline as your compliance filings, not a parallel system that doesn't talk to it.
Your own systems
A public API for teams who want production and utility data flowing in directly, instead of a person re-keying it through the UI every month.
Scoped per role
A filing touches more people than whoever hits submit.
Next
Your own data
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