Factory Evidence &
CBAM Export Pack
Prepare installation-level emissions data once — then share a trusted, verifier-ready pack with every EU customer who asks for it. Built for the documents your plant already produces.
Talk to our teamWhy This Lands On You
The importer files. The exporter proves.
The EU importer holds the legal declaration obligation. But where actual emissions are used rather than default values, the non-EU installation operator must supply verified emissions data — which puts the evidence burden squarely on the factory.
That makes exporter-side evidence readiness a commercial question, not just a compliance one: if your EU buyer cannot obtain actual data from you, they fall back to default values, and the carbon cost attached to your goods rises accordingly.
What Goes In
Four groups of factory evidence
The evidence locker organises documents by what they prove — so gaps are visible before they become a verification problem.
What powers the process
- Electricity bills — supports indirect emissions attribution
- Gas and fuel invoices — supports direct emissions
- PPA / REC certificates — needed only where a renewable electricity claim is made
How much you actually made
- Production logs and ERP activity records
- Tonnage per product, per reporting period
- Process routing where multiple products share a line
The carbon you inherited
- Supplier Material Test Reports — heat number and mass
- Supplier embedded-emissions declarations
- Purchase records linking input batches to output products
Where the goods went
- Export invoices — buyer, product and CN code
- Shipment mapping to reporting period
- Installation and factory profile records
The Workflow
From plant documents to buyer pack
Readiness
Know what's missing before your buyer does
A readiness view shows what is uploaded and linked, what is still outstanding, who owns each open request, and why each gap matters to the final carbon result.
What's available
Documents uploaded, reviewed and linked to the specific CBAM fields and calculations they support.
High-priority gaps
Missing supplier embedded emissions, absent fuel carbon-content support, or renewable proof needed only where a renewable claim is made.
Requests & owners
Each open request carries a named owner or recipient, a status, and a plain explanation of why it improves the result.
Exporter FAQ
Questions from plant, export and sustainability teams. See also the CBAM Copilot overview.
In practice the evidence falls into four groups: energy evidence (electricity bills, fuel and gas invoices, and renewable certificates such as PPAs or RECs where a renewable claim is made); production evidence (production logs and ERP activity records establishing tonnage per period); precursor evidence (supplier Material Test Reports and supplier emissions declarations for input materials); and export evidence (export invoices establishing buyer, product and CN code).
The EU importer holds the legal declaration obligation, but the exporter holds the source data. Where actual emissions are used rather than default values, the non-EU installation operator must provide verified emissions data. Without exporter-side evidence, the importer cannot use actual values, which typically results in a less favourable emissions figure for the goods.
This is one of the most common gaps. A Material Test Report proves material grade, heat number and mass, but frequently carries no supplier-specific embedded emissions figure. The platform flags the gap explicitly, identifies which supplier and which input material it relates to, and generates a data request to that supplier rather than silently substituting an assumption.
Yes. That is the core efficiency of preparing evidence at installation level. Once an installation's energy, production and precursor evidence is structured and reviewed for a reporting period, the same underlying record supports packs for every EU buyer requesting data for goods from that installation.
No. The workflow is built around the documents plant, export and finance teams already produce and hold. AI extraction handles the field-level reading, validation catches unit and date mismatches, and anything genuinely ambiguous is routed to a human reviewer with the specific issue highlighted rather than requiring the reviewer to know CBAM methodology.
Part of CBAM Copilot, built on the DocAI Platform. If you're on the EU side of the transaction, see Supplier Readiness & Review, or check the CBAM compliance timeline.
Find out how export-ready your evidence is
Bring a reporting period's worth of bills, production logs and supplier MTRs. We'll show you what's complete, what's missing, and what it changes.
Talk to our team