In India, and in most other CBAM-exposed manufacturing geographies, an Environmental Clearance or a Consent for Establishment/Operation isn't issued to "the exporter." It's issued to a specific installation — a mine, an ore-processing plant, a smelter, a fastener unit's own upstream steel supplier. The company whose name is on the CBAM declaration is often several tiers removed from the company whose name is on the permit.
A finished-goods exporter buys semi-fabricated steel or aluminium from a domestic supplier, who bought it from a primary producer, who sourced ore or alumina from a processing operation several steps further back. Under the EU's own methodology, a precursor's embedded emissions travel with it into the final good's number — and if that precursor was itself made from another precursor, the calculation recurses again, tier after tier, until there's no precursor left to trace. The exporter's own factory gate is rarely where the story starts.
That creates a specific, recurring problem for verification: the installation holding the primary environmental and emissions data isn't always the one you're engaged to audit, and it isn't always the one that thinks of itself as "in CBAM's scope" at all — because from where they sit, they're just complying with India's own Environment Audit Rules, 2025. They're not exporting anything to the EU. They just happen to sit inside the supply chain of someone who is.
EnaQt CBAM Verify is built for the exporter's side of this: goods, production processes, and — critically — Purchased Precursors tracked supplier by supplier, tier by tier, each one linked to the specific good it feeds into and to the supplier installation that produced it. It's the structured alternative to a single spreadsheet column labeled "inputs."
EnaQt Audit Comply is built for the other side — the installation that holds the actual Green Approval, the Environmental Clearance, the CFE/CFO, the EPR obligation, several tiers up the chain, with no export order of its own. Most of the installations on Audit Comply aren't exporters at all; they're domestic industrial sites managing their own Environment Audit Rules compliance, Green Credit claims, and BRSR disclosures.
The two platforms share the same installation-anchored data model and the same tamper-evident audit trail. That doesn't mean data flows automatically between two companies' accounts today — it means that when a supplier several tiers upstream is already on Audit Comply, the path onto CBAM Verify when a buyer or a verifier finally asks for their emissions data is shorter than building a reporting system from a blank page. The record-keeping discipline is already in place; only the CBAM-specific reporting layer is new.
What this means for an engagement: when both the installation you're verifying and its key precursor suppliers are on EnaQt platforms, you're not reconciling three different spreadsheet conventions from three different companies. You're reading the same kind of installation-anchored record at every tier — each one independently auditable, each one traceable back to a specific supplier and a specific evidence attachment.
If a precursor supplier several tiers up isn't yet on either platform, the practical question worth asking early in an engagement is simple: does this installation already hold an Environmental Clearance or CFE/CFO for its own domestic obligations? If it does, that's usually the fastest signal that real, auditable activity data already exists somewhere in that company — even if it's not yet organized for a CBAM-specific handoff. Environment Audit Rules compliance and CBAM verification are asking a version of the same underlying question: can this installation prove what it actually did, not just what it's permitted to do.
Whether you're reviewing an exporter's Summary Communication or trying to reach a precursor supplier several tiers upstream, we'd rather walk you through it directly.
Talk to Us For EU Verifiers & Importers