Questions Exporters and Verifiers Actually Ask

The Carbon Border Adjustment Mechanism (EU Regulation 2023/956) applies a carbon price to certain goods imported into the EU — currently iron and steel, aluminium, cement, fertilisers, hydrogen, and electricity. If you export any of these goods, or products made primarily from them, into the EU, your buyer's declarant needs your installation's verified embedded emissions data — whether you're based in India or anywhere else.

SEE is the direct and indirect greenhouse gas emissions attributable to one tonne of a specific good, calculated per the EU's own Annex IV methodology. It includes your installation's own process emissions, plus — where your good was made using a precursor material — that precursor's own embedded emissions, added in recursively through however many supplier tiers exist.

Often, yes. If a good you produce is itself made from a "precursor" listed under the regulation's Annex II, that precursor's embedded emissions are added into your good's SEE. This is why EnaQt CBAM Verify tracks Purchased Precursors as their own structured data — supplier by supplier, tier by tier, each linked to the specific good it feeds into — instead of a manual, once-a-year spreadsheet exercise.

The EU allows default values to fill genuine gaps — but by regulation, no more than 20% of a complex good's total embedded emissions can come from default-value estimates. The rest has to be real, sourced, verifiable data. EnaQt tracks how much of a product's emissions are default-sourced against that cap, so you can see the exposure before a verifier does.

Direct emissions come from your installation's own production processes — combustion, chemical reactions. Indirect emissions come from the electricity you consume, calculated using the specific or country-level emission factor for the grid it came from. Both count toward SEE, but the source data and default treatments differ.

Yes — the EU requires embedded emissions reported under CBAM's definitive regime to be verified by an accredited body following ISO 14064-3's stages: risk assessment, sampling, findings, and a formal opinion. EnaQt CBAM Verify runs that entire workflow in-platform, rather than as an offline process reconstructed after the fact.

It's the operator-to-importer handoff document — the structured, verified record of your installation's emissions data for a reporting period, which your EU buyer's declarant needs to file their own annual CBAM declaration. EnaQt CBAM Verify generates it automatically from your monthly activity data, not assembled by hand the week it's due.

EnaQt CBAM Verify is a multi-tenant platform — a company can register multiple installations, each with its own data, reporting periods, and role-based access (admin, editor, viewer, verifier), scoped so people only see what they need to.

Access is role-based and scoped per installation. Company admins manage who has access; editors can enter and change data; viewers get read-only access; and an invited verifier gets scoped access to run their verification workflow — nothing more.

Yes. Any accredited verification body — including one you already work with — can be invited by email as a "verifier" role, independent of the one-company-per-user restriction that applies to regular users, since a verifier legitimately needs access across multiple client companies.

That's common, and it's exactly the gap EnaQt Audit Comply exists to help close — on the supplier's own side, not yours. If your precursor supplier already holds an Environmental Clearance or CFE/CFO for India's Environment Audit Rules, 2025, and manages that through EnaQt Audit Comply, their record-keeping is already installation-anchored — which gives them a shorter path onto CBAM Verify when you or your buyer's verifier needs their emissions data. It's a separate platform for their separate obligation, not an automatic feed into yours.

No, and we wouldn't claim it should. A platform can't answer "what does this specific ambiguous clause mean for my operation" the way a person who tracks the regulation for a living can. EnaQt CBAM Verify is the system of record; genuinely ambiguous regulatory judgment calls are still a job for people — which is also why we offer Environmental Audit and Legal & Regulatory Advisory Services alongside the platform.

No — EnaQt CBAM Verify is built for any non-EU exporter of CBAM-covered goods, wherever you're producing from. Indian exporters make up a large share of our current focus, given the volume of MSME exporters navigating this for the first time, but the platform itself isn't India-specific.

The transitional period required quarterly reporting with no financial obligation. The definitive regime introduces the actual carbon-price obligation via certificates purchased by the declarant, phased in through the CBAM factor — 97.5% of embedded emissions require certificates in 2026, declining gradually toward 2034. Your job as the operator stays the same either way: produce verifiable, audit-ready emissions data.

Register your installation, capture your goods and production processes, and start entering monthly activity data — source streams, indirect emissions, purchased precursors, process inputs and outputs. If you're not yet sure where you stand, start with the CBAM Exposure Calculator instead.

A company admin invites you by email as a "verifier" role on their installation. Once accepted, that access carries across every client installation that invites you — no separate login to manage per engagement.

Run the ISO 14064-3 workflow directly: set up the engagement, complete risk assessment, define your sample, log findings, and issue a formal opinion. You can also view and export the Monitoring Plan, and see evidence attached to the specific figures it supports.

Not yet. Today, full change-history visibility is available to company admins internally, not to an invited verifier. That's a real gap on our roadmap — we'd rather tell you that directly than let you find out on a call.

No, and it isn't meant to. What changes is what the site visit is for — confirming what's real on the ground, rather than being the first time you're seeing the data at all.

Purchased Precursors are tracked supplier by supplier, tier by tier, each linked to the good it feeds into. Where a precursor supplier is several tiers upstream and separately manages India's Environment Audit Rules, 2025 through EnaQt Audit Comply, that's a distinct account and platform — not an automatic feed into the exporter's CBAM Verify data — but it means the supplier's own records are already installation-anchored rather than ad hoc, which shortens how far you have to reach to reconstruct their numbers.

Data capture and calculation follow the CBAM Regulation's own Annex IV methodology and the EU MRR-aligned approach, with production-route classifications matching Annex I categories. The verification workflow itself follows ISO 14064-3's stages directly, not a generic audit-management template.

Yes — the verifier role is explicitly exempt from the one-company-per-user restriction that applies to regular platform users, since verification bodies legitimately work across many clients at once.

Findings are logged directly in the platform against the engagement, marked material or not against your stated materiality threshold, and tracked to resolution — open, corrected, uncorrected, or accepted by the client — as part of the same record, not a side email thread.