CBAM Reporting Requirements: What Companies Must Track and Why “Good Enough” Data Fails

‍CBAM is no longer a topic to watch from the side: reporting quality now matters

CBAM (the Carbon Border Adjustment Mechanism)  entered its definitive phase on January 1, 2026.The definitive CBAM obligations generally apply to importers exceeding the 50-tonne annual threshold, while electricity and hydrogen imports are not covered by that exemption. The first full CBAM declaration is due September 30, 2027, covering everything imported in 2026. From 2023 through 2025, importers filed quarterly reports and mostly treated CBAM as a data-gathering exercise. That grace period is over.

For import and compliance teams that already know CBAM exists, the real question has moved past what it is. What matters now is whether the numbers in a CBAM report can hold up when a national authority, a verifier, or an internal audit takes a close look. The risk has shifted from whether you report to how well your reported numbers stand up.

What companies actually need to track for CBAM

A CBAM report is only as strong as the inputs behind it. Before any declaration goes out, five categories of data need to be in place and traceable back to their source.

CBAM tracks product data, producer details, installation data, embedded emissions, and carbon price inputs

• Product data: CN codes, quantities, and the goods category each shipment falls under.
• Producer details: who made the goods, at which site, under what production route.
• Installation data: the specific facility where production happened, since emissions vary by installation, not just by country or sector.
• Embedded emissions: direct and indirect emissions attributable to that specific batch of goods.
• Carbon price inputs: any carbon price already paid in the country of production. If importers can prove that a carbon price has already been paid during production, the corresponding amount can be deducted.

Product data, producer details, and installation data are largely administrative, the kind of fields a customs team can pull from existing records. Embedded emissions and carbon price inputs are where the real difficulty sits, and where SINAI's support is concentrated: calculating embedded emissions per product, collecting primary data directly from suppliers, and structuring that evidence so it can hold up under audit.

This is the point where spreadsheets and scattered supplier emails stop scaling. A CBAM tracking and reporting platform exists precisely to close that gap, matching each shipment to the right emissions factor from actual verified supplier data or a published default value, and preparing that data to stand up to scrutiny instead of falling back on costlier default values.

Embedded emissions without the guesswork: which numbers matter for CBAM and where they come from

Embedded emissions are the numbers regulators and auditors will interrogate hardest. They cover direct emissions from the production process and, where required under the applicable CBAM sector rules, indirect emissions from electricity used in production.
In terms of The GHG Protocol, this is Scope 1 and Scope 2 data changing hands. Scope 1 covers the direct emissions from making the goods, Scope 2 covers the electricity used to make them, and once that number crosses the border, it becomes part of the importing company's own Scope 3 footprint. That handoff is exactly why the data has to be reliable and verifiable, not approximate. A Scope 3 number inherited from a supplier's Scope 1 and Scope 2 data is only as trustworthy as the process that produced it.

Two paths exist to arrive at that number. The first is actual, verified data supplied directly by the producer. The second is a default value published by the European Commission, used when actual data is not available. The gap between them is not abstract: default values include sector-specific mark-ups, which vary across CBAM goods and may increase over time, making continued reliance on defaults more costly in some sectors. SINAI helps importers replace defaults with actual verified supplier data, so they surrender fewer certificates and lower their CBAM cost.

Getting to actual data depends on the supplier, not just the importer. A producer’s data can be used as an actual value in a CBAM declaration only if the emissions are calculated in accordance with the CBAM methodology and verified by an independent CBAM verifier accredited by an EU national accreditation body, rather than estimated from spend or industry averages. We walked through what that comparison looks like in practice in a recent post on actual vs. default values in a CBAM declaration. Where a supplier is not there yet, SINAI's platform is built for onboarding them onto real emissions monitoring, so that gap becomes a project a company can run rather than a reason to keep filing on defaults.

Why good enough data creates CBAM reporting risk instead of control

Approximate data feels efficient in the short term. A rough embedded emissions estimate lets a team hit a filing deadline without chasing every supplier for documentation. The problem shows up later, when that estimate has to hold up under verification or a customs review.

CBAM regulations do not treat estimates and verified figures as interchangeable. A number built on an assumption, a proxy, or an outdated supplier response sits inside the report as a liability, waiting to surface. It tends to surface at the worst possible time: during an audit, a certificate reconciliation, or a dispute over what the company actually owes.

Good enough data also limits the company's ability to push back. A team that cannot explain where a number came from cannot challenge a default value, cannot claim a carbon price deduction with confidence, and cannot tell a supplier what needs to improve. Precision here is what gives a company control over its own CBAM exposure, instead of accepting whatever the default framework assigns.

Where CBAM reporting workflows usually break under pressure

Most CBAM reporting obligations do not fail because a company misunderstands the regulation. They fail because the operational workflow behind the report has weak points that only surface once a filing deadline puts pressure on it.

Supplier inputs, missing documentation, weak validation, disconnected files

• Supplier inputs: arrive late, incomplete, or in formats that do not match what the report needs.
• Missing documentation: means an embedded emissions figure exists with no evidence trail behind it.
• Weak validation: lets errors from a supplier spreadsheet pass straight into a CBAM declaration unchecked.
• Disconnected files: scatter product data, producer details, and emissions figures across separate documents nobody reconciles before submission.

Each of these is manageable on its own. Combined, they describe a workflow where the company doing the reporting has less visibility into its own numbers than the suppliers who provided them. This is where SINAI's supplier engagement tools are built to help: structured collection with due dates and reminders, so inputs stop arriving late or in the wrong format; an audit trail from each supplier response through to the declaration, so nothing is missing; data-quality checks at intake, so errors are caught before they reach the declaration; and one reconciled record in place of scattered files.

What verifiable emissions data looks like in a process that can stand up to scrutiny

Verifiable emissions data has one defining quality: every figure can be traced back to its source and its calculation method, without someone having to reconstruct that trail from memory when a question comes in.

That means installation-level data collected on an ongoing basis, not stitched together right before a deadline. It means supplier responses stored against the specific shipment they apply to, rather than left in a shared inbox, which is exactly what SINAI's Engage module is built to support. It means an embedded emissions calculation that shows its work, so a carbon price deduction or a verifier's question can be answered with a document instead of a guess.

An auditable emissions reporting system built around these habits turns CBAM from a recurring scramble into a process the company actually controls. The report itself is the last step. The real compliance work happens earlier, in how product data, producer details, and embedded emissions get captured and kept ready for the moment someone asks where a number came from.

Penn Engineering, a SINAI customer that both exports to and manufactures within the EU, has already built this kind of traceable process. Brian Bentrim, the company's Global Vice President of Sustainability, described how it works during a recent SINAI webinar on Scope 3 reporting:

“With CBAM, we're hit on both ends, since we're exporting to Europe and producing there too. The data we get out of SINAI links into our ERP system, so we can look at how we're manufacturing each part, what materials are going into it, and very transparently show where the carbon we're reporting for CBAM is coming from.”

— Brian Bentrim, Global Vice President of Sustainability, Penn Engineering

Brian shares the rest of Penn Engineering's Scope 3 journey, from supplier data to CBAM reporting, in SINAI's full Scope 3 Unlocked webinar.

CBAM reporting requirements will keep tightening as the definitive phase matures. Companies that treat data governance as the starting point, not an afterthought, are the ones that meet each new requirement without rebuilding their process from scratch.

Book a demo and see how SINAI can help you build the same auditable reporting process for your own imports.

‍