CBAM reporting in Turkey means Turkish exporters supplying EU importers with verifiable, installation-level data on the emissions embedded in cement, iron and steel, aluminium, fertilisers, electricity or hydrogen. The EU's Carbon Border Adjustment Mechanism charges a carbon price on those imports. The importer pays, but the bill is calculated from the producer's own data or, failing that, from conservative default values.
The email that starts it all
For most Turkish manufacturers, CBAM arrived as a message from an EU customer: "Please send the specific embedded emissions per tonne for everything you shipped last year, with your calculation method." It sounds like a simple request. Answering it means knowing which furnace burned how much of which fuel, which line drew how much electricity, and which inputs went into which product, all for the same period.
In most plants that information exists, but in pieces. Gas invoices sit with accounts, meter readings live in a maintenance spreadsheet, production volumes are in the ERP and recipes are held by quality. CBAM asks you to tie those pieces to one installation, one product and one period. It is less an environmental reporting problem than a data integrity problem.
This guide does not cover company-wide carbon footprint and Scope 1, 2 and 3 emissions reporting. It is about the product-level data an EU buyer needs for goods you actually ship. If you are still deciding what to digitise first, our digital transformation roadmap sets out the wider sequence.
Why CBAM is no longer just a questionnaire
The transitional period only required reporting. From 2026 the mechanism carries a financial obligation, and the dates are fixed in EU law:
According to the European Commission, CBAM entered its definitive, paying phase on 1 January 2026, after a 2023–2025 transitional period. It covers cement, iron and steel, aluminium, fertilisers, electricity and hydrogen. (European Commission, Taxation and Customs Union: Carbon Border Adjustment Mechanism)
Regulation (EU) 2025/2083, adopted in October 2025, introduced a single annual threshold of 50 tonnes to spare small importers. The same regulation caps that exemption at no more than 1% of embedded emissions, so at least 99% stay within scope (EUR-Lex, Regulation (EU) 2025/2083). Buyers of industrial volumes will not fall below it.
Under the amended rules, authorised declarants file their annual CBAM declaration by 30 September; the first, covering 2026, is due in 2027, and CBAM certificates go on sale from 1 February 2027. From 2027, a declarant must also hold, at the end of every quarter, certificates covering at least 50% of the embedded emissions in goods imported since the start of the calendar year (EUR-Lex, Regulation (EU) 2025/2083). Your customer will therefore need reliable figures quarter by quarter, not once a year.
Türkiye is building its own framework in parallel. Climate Law No. 7552, published on 9 July 2025, establishes a national Emissions Trading System, and plants within its scope must obtain a greenhouse gas emission permit within three years of the law taking effect (Mevzuat Bilgi Sistemi, Climate Law No. 7552). The same emissions data will go to your EU buyer and your domestic regulator, so it makes sense to build one source rather than two spreadsheets.
When a producer cannot supply data, the importer typically falls back on the EU's default values. Defaults are set conservatively, so even an efficient plant can look dirtier than it is. That shows up directly in price negotiations and in supplier selection.
What data does CBAM reporting in Turkey require?
CBAM calculations work at the level of the installation and the production process. Direct emissions from kilns, boilers and process combustion, indirect emissions from purchased electricity for certain goods, and the emissions of precursor materials are allocated per tonne of product. The table below shows where each input usually comes from and where it tends to break:
| Data item | Typical source | Common weakness | What good looks like |
|---|---|---|---|
| Fuel use (natural gas, coal, fuel oil) | Invoices, meters | Monthly totals with no split by furnace or line | Time-stamped readings per consumption point |
| Electricity use | Utility bill, automated meter reading | Site total that cannot be allocated to products | Sub-metering per line or machine |
| Process emissions (calcination, anodes etc.) | Laboratory, production records | Paper forms that do not match the reporting period | Samples and analyses linked to production batches |
| Production output | ERP, MES | Shipments confused with production | Net output per installation and product group |
| Precursors | Purchasing, suppliers | No emissions data from suppliers | Supplier data in an agreed format |
| Method and evidence | Environmental team | One person's spreadsheet | Documented method, versioned calculations, audit trail |
The last row is the one most often forgotten. In the definitive period, emissions data is expected to be checked by an accredited verifier, who wants to see the route to the number as well as the number itself. One cell with no traceable source undermines the whole report.
A 7-step plan for CBAM-ready data
This sequence works for a producer starting from scratch or from a set of spreadsheets:
- Pin down scope. List every product you ship to the EU by its Combined Nomenclature code and match it against the CBAM annex. Note out-of-scope goods too, because buyers will still ask.
- Draw installation boundaries and processes. Map which furnaces, lines and utilities serve which products. Agree allocation keys for shared assets such as boilers and compressors before you start collecting data.
- Identify measurement points. Inventory existing meters and decide where sub-metering is needed. If you already have automated meter reading for electricity, use it as your starting point.
- Automate collection. Pull meter, PLC and SCADA data with time stamps instead of reading it by hand. The machine-level approach in our factory energy monitoring guide is the foundation for the per-line allocation CBAM needs.
- Join it to production and purchasing data. Bring ERP output, recipes and precursor purchases together with energy data on a shared period and product key. A data warehouse with a proper ETL layer is the most robust way to do this.
- Document and lock the method. Keep emission factors, allocation keys and formulas under version control, with a record of who changed what and when. A data governance framework gives you ownership and sign-off rules.
- Standardise the output. Send every EU buyer the same structured emissions statement, refreshed quarterly, and link the supporting evidence to each shipment file.
Step 7 follows the same discipline as export paperwork. Our guide to import-export document management shows how to keep invoices, certificates of origin and now emissions statements together per shipment. The same principle applies to the calculation files and factor sources in step 6: with a versioned archive in SmartFiles, a calculation sheet uploaded under the same name becomes a new version, the list shows who uploaded it and when, and an earlier version can be restored. When the company administrator places a retention lock on a folder, with a stated reason, those documents cannot be deleted or moved, and the calculation no longer depends on one specialist's laptop.
Common mistakes and a quick self-check
First attempts at CBAM tend to repeat the same errors. A site-wide energy bill gets split across products by sales tonnage, which makes energy-hungry and energy-light products look identical. The calculation lives in one specialist's file, and the process stops when that person is on leave.
Another mistake is treating CBAM in isolation from other EU product data requests. Textile exporters face the digital product passport, and carmakers send supplier scorecards asking for similar numbers in different formats. With batch-level production traceability in place, all of these can be fed from the same source.
Test where you stand with five questions:
- Can you produce last quarter's gas consumption per furnace within a day?
- Does the ERP show the same production tonnage as your energy spreadsheet for that period?
- Is it written down where your emission factors came from, and when?
- Could someone other than the person who built the calculation reproduce the result?
- Have you asked your precursor suppliers for their emissions data?
More than two "no" answers mean the data foundations need work before any reporting. For a broader view of readiness, a digital maturity assessment is a sensible first step.
How Digital Bridge builds the data layer for CBAM
Emission factors and the formal methodology are set by your environmental adviser or verifier. Our job is to make sure the data behind that calculation is measured, collected and stored in a way that can be traced:
- Discovery and needs analysis. Through our digital transformation consultancy we map the products you ship to the EU, installation boundaries, existing meters and data sources, and hand over a written list of missing measurement points and priorities.
- Measurement and pilot. Using our energy monitoring and management platform, we start with one energy-intensive line or furnace, collecting electricity, gas and compressed air data with time stamps. The aim of the pilot is to make energy per unit of product visible for that line.
- Integration. We connect meters, PLCs, SCADA and the ERP through system integrations, so that output and recipe data meet energy data on the same time and product key.
- One source with an audit trail. The combined data lands in a data warehouse, and data governance and quality rules flag missing readings, mismatched tonnages and manual overrides. Quarterly buyer statements and domestic ETS preparation then come from the same numbers.
A useful side effect is that energy saving opportunities become visible. If you supply the automotive industry, we recommend building this layer as part of your wider automotive supplier digital transformation. Funding for efficiency projects is covered in our overview of SME digitalisation grants in Türkiye.
EU expectations of supply chains go beyond carbon; cybersecurity is under similar pressure, as our piece on NIS2 requirements for suppliers explains. You will find related guides on our Digital Transformation topic page.
Next step: be ready before your buyer asks again
The first definitive CBAM declaration is due in 2027, but it covers goods imported in 2026, so the emissions data for what you ship today will end up in it. From 2027, quarterly certificate holdings will spread your buyers' data requests across the year. A producer that starts measuring which product uses how much energy on which line today can offer its own verified figures instead of default values. The same metering also feeds the annual reporting required by energy efficiency obligations for Turkish industry in plants above the consumption threshold.
If you would like to plan measurement points and data flows for your EU exports together, get in touch with our team. In a first conversation we listen to how your products and plant are organised and follow up with a written plan of which data to collect and from where.