CBAM Intelligence
Qubere resolves embedded emissions, benchmark, certificate price, and phase-in factor for every CN code and origin country from a versioned, checksum-deduped regulatory dataset — and tells you plainly when a number is missing instead of quietly treating it as zero.
The problem
What a trade-compliance lead says about CBAM readiness today:
"Someone copy-pastes default emission values out of a PDF annex once a quarter. Nobody's sure if it's still current."
Stale defaults
"We can't tell which shipments actually have real supplier emissions data versus which ones are silently on the EU default."
Actual vs. default, blurred
"UK CBAM starts in 2027 and we're tracking EU and UK scope in two different documents that never agree."
Two regimes, no single view
How Qubere addresses it
Exposure overview
The overview aggregates every calculation across the account: estimated exposure, embedded emissions, assessed quantity, and countries assessed, split between actual supplier emissions and EU default. Anything incomplete is pulled out of the total and listed separately, with the exact missing input named.
Cost Lens
Enter a CN code and a scenario year; Cost Lens resolves default emissions, benchmark, certificate price, and phase-in factor for every country of origin in one pass — a bulk resolver, not 190 sequential lookups — and paints the world map by estimated cost per tonne. Toggle official certificate price against a scenario price to stress-test a future year.
Quotes
A quote prices a prospective purchase from the emission records you already hold for a supplier: pick the supplier, add the goods and tonnes, choose the year of import and the certificate price, and the cost per item is computed from direct plus indirect emissions and the CBAM factor published for that year. When no factor is published for the year, the item says Not priced — it is never filled with a guess.
Certificate price
The Certificate Price screen shows the published CBAM certificate prices on record: a weekly reference-price chart you can hover for the detail, this week against last week, the latest quarter price, and the year's high and low, each with its source. It is marked as feeding your bill, so you can see which price your costs and quotes are computed from.
Calculator
The Calculator produces a single shipment's CBAM result: Quick (EU default emission method) or Advanced (actual production facility direct/indirect emissions entered by hand), plus an eligible carbon-price-paid-in-country-of-origin deduction against the certificate cost. A Cost Lens country deep-links straight into a pre-filled Advanced calculation.
Regulatory data lifecycle
Every official document — product scope annex, default emission values, benchmark, certificate price, phase-in schedule — is staged, checksum-deduped against anything already imported, and validated before it can ever go active. A live fetcher can pull the latest published document automatically, but it only ever reaches "staged" or "needs review" — never "active" without a person confirming it.
| EU · Default Emission Value | v2026-09 | FETCHED | needs review |
| EU · Benchmark | v2026-Q3 | ACTIVE | validated |
| UK · Product Scope | v2026-08 | VALIDATED | validated |
EU and UK, side by side
UK CBAM (effective 2027) tracks its own product scope, aggregated goods categories, commodity-category mapping, GHG scope, and system boundary — deliberately separate tables and separate applicability logic from EU CBAM, because the regimes genuinely differ on scope and boundary definitions. A jurisdiction toggle switches the whole workspace; nothing is silently shared between them.
Manage workspace
The CBAM menu is organised as four areas: Manage, Analyze, Explore and Reports. It opens on Manage → Imports, where each import line carries its CN code, origin, production facility, emissions basis and customs reference. Suppliers, Production Facilities, Emissions, Benchmarks and Carbon Price Evidence sit one tab away, so the inputs are kept next to the lines that use them.
Annual Declarations and certificates
Qubere applies the definitive-regime rules as separate, checkable steps: declarant authorisation, the 50-tonne threshold ledger, the Article 22 emissions values, the certificate holding requirement and the certificate ledger. Each step names what blocks it, instead of producing a total that looks complete.
Authorisation and penalties
Article 17(7a) provisional decisions are tracked as a lifecycle, and imports that depend on them are held until the decision is recorded. Article 26 penalties are composed from the statutory rule: a minimum of N × P1, a standard amount of minimum × m, with m between 3 and 5 and set by the authority. The authority's multiplier and any reduction decision are recorded as inputs; Qubere never picks them.
Electricity and data provenance
Imported electricity emissions are computed from the quantity in MWh multiplied by an emission factor. If the MWh quantity is missing, the line fails closed with a named error instead of guessing. Emission factors derived from third-party data carry a licence status, and a gate keeps them out of calculations until the licence is cleared.
Objection handling
| "Where do the default emission values actually come from?" | Staged from the official EU Implementing Regulation annexes (or fetched live from the published document), checksum-deduped, validated, and only activated after a human confirms it — every active record carries its regulation reference, version, and effective dates. |
| "Can a bad live fetch push wrong numbers into our cost calculations?" | No. A live fetch can only reach staged or needs-review status. Activation — the only state cost calculations read from — is a separate, manual, audited action every time. |
| "What happens to a shipment when we genuinely don't have a default value yet?" | It's marked incomplete and listed under "assessments requiring attention" with the exact missing input named. It is never counted as €0 exposure in a total. |
| "Is UK CBAM just EU CBAM with a different label?" | No. Separate scope, separate aggregated-goods-category and commodity-category tables, separate GHG-scope and system-boundary definitions, and separate applicability logic — because the two regimes actually differ. |
| "Will Qubere decide our Article 26 penalty for us?" | No. It composes the amount from the statutory rule, but the multiplier and any reduction are decisions by the authority and are recorded as inputs. The Article 26(1) base amount is not loaded yet, so no amount is shown until it is. |
| "Can we use third-party electricity data today?" | Only where the licence is cleared. IEA-derived factors sit behind a licensing gate that is still closed, and electricity lines without MWh fail with a named error. |
The close
A CBAM number you can defend, because every input traces back to a versioned, checksummed, human-activated regulatory record — in both EU and UK.
Next step: bring a real CN code and origin country mix from your book of business. We'll run Cost Lens across it, open the regulatory evidence behind one result, and show exactly what's flagged incomplete and why.
Full detail: apps/custom/src/modules/cbam/README.md