EXPORTER · IMPORTER HANDOVER · CBAM
What your EU importer needs from you
Your importer is the declarant. They file with the EU Registry and they carry the liability for what the declaration says. Everything in it comes from you. This is the data they need, per goods line, and the format that survives the handover.
What your importer needs
The production site has to be identifiable, not just named
A declaration line is tied to the installation that made the goods, not to your company as a whole and not to the shipment. Your importer needs the operator and installation identifiers for each production site, and they need them to stay stable across every quarter you supply into. Change a site mid-year without telling them and the declaration breaks in a way they will only discover at the Registry.
Every goods line carries its own emissions basis
Embedded emissions are declared per goods line, on the CN code, not averaged across an invoice. For each line your importer needs to know whether the figure is your actual measured emissions or a default value, and they need that stated explicitly — because the two are not interchangeable and the choice sits on the record. Direct and indirect emissions are reported separately; indirect follows the carbon intensity of the electricity actually drawn at the site.
Your inputs carry emissions, and they have to survive the handover intact
Steel made from imported pig iron carries the pig iron’s embedded emissions. So does clinker in cement, and so does every precursor upstream of the goods you ship. The chain has to arrive at your importer whole — each precursor with its own emissions basis and its own origin — because a collapsed single total cannot be reconstructed once it reaches them. This is the point where a spreadsheet or a PDF summary stops being enough.
Annex II, point A.1(1)(f) to IR (EU) 2025/2547: the embedded emissions of a precursor are added to the embedded emissions of the complex good produced, repeated recursively where precursors are themselves complex goods. Per-precursor origin and emissions data sets: Annex II, point E.
What you actually send, and in what format
Your importer does not need your production system, your invoices, or a narrative report. They need a structured declaration file they can submit without re-keying anything: installation identity, goods lines with CN codes, emissions basis per line, and the precursor chain beneath each one. Carbon Mandate prepares that file. You send it to your importer. Your importer files it.
Carbon Mandate produces an XSD-validated XML declaration file. That is the artefact the EU Registry accepts. A communication template or a PDF report is not — it makes your importer re-enter your data by hand, and every re-entry is a place the declaration can go wrong. We prepare, we do not file. The importer is the declarant and files with the Registry themselves.
EXPORTER PROTOCOL
Secure your European market access.
Do not let formatting errors block your cargo at the border. Route your manufacturing ledgers to us and equip your European importer with a machine-readable submission file. We process the data; your buyer executes the filing.
Reg (EU) 2023/956 · IR (EU) 2025/2621 · IR (EU) 2025/2620 · Reg (EU) 2025/2083Not an exporter? If you’re the EU importer receiving these files: Importer solutions