Getting started
How CBAM Compliance works, from your first plant model to a filed declaration.
- Start here — the 5-minute path
- Your workflow, step by step (every role)
- Why the numbers are trustworthy
- Filling data without mistakes
Start here — the 5-minute path
The shortest route from zero to a submitted declaration.
The platform follows one simple flow: model your plant, let the engine calculate, plan ahead, then declare. You never do the maths by hand — the engine is the single source of every figure.
- Build your plant in the Balance Twin (guided Go → 1 → 2 → 3 → Done editor). Pick your sector and production route, then fill the amber fields.
- Open the Calculator to see engine-certified emissions and liability for what you modelled.
- Use Forecasting to project cost over the phase-in years and compare price scenarios.
- Track what you must hold and surrender in Certificates and the Compliance calendar.
- Export the official QReport XML from Reports and submit it in the CBAM Registry.
Note: Not sure a value is right? Every input with a '?' has a contextual tip, and amber fields mean 'please confirm' — not 'error'.
Your workflow, step by step (every role)
The order of work for importers, suppliers, verifiers and administrators.
Pick your role in the bar under the header ('I am …'); the step bar then highlights where you are and links the next step. The role only arranges the menu — it never grants access.
EU importer / broker / consultant:
- Company & EORI (/declarant): authorised-declarant status, EORI and country — used on every report.
- Bring in imports (/customs-import): upload the customs or ERP Excel; every row is calculated by the engine, and unclear rows are reported, never guessed.
- Supplier data (/enterprise/suppliers): invite suppliers for actual emissions or a Balance Twin plant model; they can pass precursor requests on to their own suppliers.
- Review & verify (/verification): check supplier figures and evidence, and give your accredited verifier read-only access (/enterprise/verifiers).
- Declare & certificates (/certificates): add batches to the annual declaration, clear the pre-filing check, approve, buy certificates, then file; the Watchdog keeps checking afterwards.
- Plan costs (/forecasting): project certificate costs for the coming years.
Non-EU producer / supplier:
- Model your plant (/twin): build it in the Balance Twin, submit it for review, download the PDF and XML.
- Answer a data request (/supplier-portal): open the invitation link your EU buyer sent.
- Your buyers' cost (/calculate): default values against your own data.
Accredited verifier: Your clients (/auditor) for submissions, evidence and audit bundles; Method & guides (/help). Administrator: Readiness check (/setup), Settings (/settings), Reference data (/admin/default-values).
Why the numbers are trustworthy
Every figure comes from the engine — never from AI or a guess.
One rule governs the whole product: emissions and liability numbers come only from the calculation engine. The AI assistant explains and guides, but it is blocked from stating a figure — it routes you to the calculator instead.
This means what you see on screen is identical to what gets exported in your official XML. There is no second, hidden number.
Filling data without mistakes
How the guardrails and amber guidance keep your data clean.
The editor protects you in three layers, so a layman can fill it with confidence:
- Structure guardrails: you can only connect steps in ways that are physically valid for your route. Invalid connections are refused on the canvas and again when you save.
- Plausibility bands: each value shows an expected range. A figure far outside it turns amber with a hint — advisory only, it never changes your number.
- Unit checks: the app flags likely kg-vs-tonne slips (a common, costly error) before they reach the engine.
- Amber means 'confirm', not 'wrong'. If your value is genuinely correct, keep it.
- Enter mass in tonnes unless a field says otherwise.