CBAM guide

Default values or actual emissions data?

Many teams start with default values, but they still need auditable supplier data over time. Emissions-data quality decides how stable the process becomes. This guide explains how to turn the topic into a practical import, review, and declaration workflow.

How to make this practical

01

Clarify scope

Bring affected HS/CN codes, suppliers, and goods flows into one review list.

02

Review data

Check quantities, supplier evidence, and emissions values before declaration.

03

Export declaration data

Reviewed data becomes a reliable path for XML and declaration workflows.

Context

Operational context

In practice, the safest approach is to combine scope screening, data enrichment, expert review, and structured XML preparation. Keep the assumptions, supplier evidence, and approval decisions together so the quarterly workflow can be repeated without rebuilding it every time.

Common questions

What is the first practical step?
Bring HS/CN codes, suppliers, quantities, countries of origin, and product groups into one review list before building reports or exports.
Which data should be checked before declaration?
Check customs codes, imported quantities, supplier emissions data, default-value assumptions, production route, and evidence files.
How does CBAM-OK help?
CBAM-OK structures classification, supplier data, review status, and XML export so teams can work from one auditable workflow.
What should remain documented?
Keep source data, supplier responses, assumptions, reviewer decisions, and generated exports together for audit readiness.