Mill-grade CBAM XML
for steel exporters
Pig iron, hot-rolled coil and alloy steel — embedded emissions declared and validated against the live XSD.
Reg (EU) 2023/956 · IR (EU) 2025/2620 Annex II · XSD v2.1
CN CODES IN SCOPE — CHAPTER 72 & 73
Annex I to Reg (EU) 2023/956 as amended. Precursors: pig iron, sinter, hot metal, direct reduced iron, scrap (where emissions-bearing).
PRODUCT TYPE — EMBEDDED EMISSIONS SPREAD
* Electric arc furnace route embedded emissions depend on scrap quality and origin-grid intensity behind the furnace.
WHAT THE XML MUST CONTAIN
INSTALLATION DATA
- Installation ID
- Production route
- Operator name
- Country of origin
- Reporting period
GOODS DATA
- CN code
- Net mass (tonnes)
- Quantity
- Unit of measure
- Production method code
EMISSIONS DATA
- Direct emissions (Scope 1)
- Indirect emissions
- Specific embedded emissions per tonne
- tCO₂e total
CARBON PRICE PAID
- Carbon price paid in country of origin
- Deduction amount
- Rebates applied
- Currency
INGESTION
Upload anything
VALIDATION
Catch errors early
HANDOVER
Ready to submit
FAQ
Common questions from non-EU exporters.
Do I need a CBAM XML for every shipment to the EU?
CBAM reporting is per quarter, not per shipment. One XML declaration covers all CBAM-covered goods imported by your EU customer in that reporting period. The 50-tonne annual threshold under Reg (EU) 2025/2083 applies at importer level across all suppliers.
What if I do not have actual emissions data and need to use defaults?
IR (EU) 2025/2620 publishes Annex II default emission values for iron and steel by product type. Carbon Mandate maps these defaults to your CN codes automatically. Actual emissions always take precedence but defaults are regulatory compliant for the transitional period.
My importer is asking for an XML — what format does the EU Registry actually accept?
The EU Registry accepts CBAM XML conforming to the DG TAXUD XSD schema. A PDF report or spreadsheet is not an accepted submission format. Carbon Mandate produces a file that validates against the live XSD before transmission so your importer receives an EU-Registry-ready file, not a communication template.
Live demonstration
See the XML engine validate a real file — in 20 minutes
No slides. No sales pitch. We open a live CBAM file from your sector, run it through the XSD validator, and show you exactly what the EU Registry receives.