CBAM Reporting Software for Cement and Steel in 2026

A mid-sized Polish precast manufacturer importing Turkish clinker filed its first CBAM quarterly report in Q1 2024 using the European Commission default values and a spreadsheet built by a junior cost engineer. It took two afternoons. In Q1 2026 that same shipment now requires a CBAM declarant authorization issued by the national competent authority, verified supplier emissions or marked-up default values, an annual declaration in the CBAM Registry by 30 September 2027, and certificates bought from February 2027 at an EU ETS-linked price. The spreadsheet did not survive the transition.

The transitional phase of the Carbon Border Adjustment Mechanism ended on 31 December 2025. From 1 January 2026, CBAM is in its definitive financial phase under Regulation (EU) 2023/956. For construction firms importing cement, steel, aluminum, and fertilizers from outside the EU, this is the year where the rules change from quarterly disclosure to an annual declaration and certificate surrender. The obligation sits with the importer, or the indirect customs representative, that declares the goods at customs (European Commission). A fabricator buying steel or aluminum profiles from an EU mill, distributor, or system house is generally not a CBAM declarant, and goods originating in Iceland, Liechtenstein, Norway, and Switzerland are excluded under Annex III. The software stack that produced the transitional report does not produce the definitive one.

This post is for finance, sustainability, and IT leads at construction companies, precast manufacturers, and steel fabricators that import in-scope goods directly, scoping their CBAM software build for 2026 and beyond. It assumes familiarity with the basic mechanics of CBAM and goes deeper into the implementation choices that decide whether quarterly reporting takes a week or a quarter.

What changed on 1 January 2026 and why default values get expensive

During the transitional phase (October 2023 to December 2025), importers could use Commission default values without limit only in the first three quarterly reports; from Q3 2024, estimates including default values were capped at 20% of the total embedded emissions of complex goods (European Commission). Those transitional defaults were world averages. The definitive-period defaults are country-specific and carry a mark-up of 10% in 2026, 20% in 2027, and 30% from 2028, set so that embedded emissions are not underestimated (European Commission).

From 1 January 2026, three things changed simultaneously:

1. Actual emissions must be verified; everything else falls back to marked-up defaults. Declared actual embedded emissions must be verified by an accredited CBAM verifier (Article 8). Where verified actual data is not available, the declarant uses the country default values including the mark-up.
2. CBAM certificates must be purchased and surrendered. Each tonne of embedded CO2 (and CO2 equivalent) above the free allocation adjustment that mirrors EU ETS free allowances triggers a certificate obligation. Sales start on 1 February 2027, and certificates for a year’s imports are surrendered by 30 September of the following year (Regulation (EU) 2025/2083). The price is the EU ETS auction price as a quarterly average in 2026 and a weekly average from 2027 (European Commission).
3. Authorized CBAM declarant status is required. From 1 January 2026 only authorized CBAM declarants can import in-scope goods above the threshold below (Article 25); importers that applied by 31 March 2026 could keep importing while their application was pending (Regulation (EU) 2025/2083). Authorization is issued by the national competent authority after a financial standing and good repute check.

The Omnibus simplification, proposed in February 2025 and adopted as Regulation (EU) 2025/2083 in October 2025, replaced the EUR 150 per-consignment de minimis with a threshold of 50 tonnes of imported goods per importer per calendar year, counted cumulatively across iron and steel, aluminum, fertilizers, and cement (electricity and hydrogen get no exemption). The Commission expects it to exempt about 182,000 importers, mostly SMEs and individuals, while still covering over 99% of embedded emissions (European Commission), because the largest importers (the volume tail) is concentrated in a small number of firms. For mid-size construction businesses, the practical effect is: a precaster importing 200 tonnes of clinker per year is in scope. A small builder whose only CBAM import is 10 tonnes of rebar from a UK merchant is not.

CBAM Registry and the declarant authorization workflow

The CBAM Registry, operated by the European Commission, is the single mandatory submission portal. National Competent Authorities (NCAs) authorize CBAM declarants and oversee compliance. Authorization is per-legal-entity, not per-shipment, and requires (Article 17, as amended by Regulation (EU) 2025/2083):

• Establishment in the member state
• EORI number
• Demonstrated financial and operational capacity (a guarantee is required if the applicant was not established throughout the two preceding financial years)
• No serious or repeated infringements of customs, tax, market abuse, or CBAM rules
• An indirect customs representative if the importer is established outside the EU

The application is submitted via the CBAM Registry and assessed by the NCA of the member state of establishment (Article 5).

After authorization, the CBAM Registry handles quarterly reports (for transitional period legacy submissions) and annual declarations (for the definitive period). The surfaces an integration has to cover:

• Declaration submission: structured data listing each consignment, CN code, supplier installation, and embedded emissions.
• Certificate transactions: purchase, holding, surrender, repurchase.
• Verifier interactions: verification reports prepared on the Commission’s electronic template in the CBAM Registry per Implementing Regulation (EU) 2025/2546. Accredited verifiers can register from September 2026 and issue their first reports from January 2027 (European Commission).

The first practical engineering challenge is access. Log-in to the CBAM Registry runs through the EU-wide UUM&DS, and each member state chooses whether its declarants come in through the CBAM domain or the customs domain (European Commission). Building an integration for a Polish establishment is not necessarily the same as building one for a German establishment, even though both are submitting to the same EU registry. Multi-member-state importers typically end up with one integration per establishment.

Mapping CN codes to your supplier emissions data

CBAM scope is defined by Combined Nomenclature (CN) codes listed in Annex I of Regulation (EU) 2023/956. For construction, the operationally relevant codes:

• Cement: CN 2523 10 00 (clinker), CN 2523 21 00 (white Portland), CN 2523 29 00 (other Portland), CN 2523 30 00 (aluminous cement), CN 2523 90 00 (other hydraulic cements).
• Iron and steel: CN chapter 72 (minus some ferro-alloys and scrap), which already includes rebar (7214) and structural sections (7216), plus selected chapter 73 codes such as sheet piling (7301) and structures and parts of structures (7308).
• Aluminum: selected CN chapter 76 codes, including construction-relevant downstream ones such as profiles (7604), sheet (7606), and structures including doors, windows, and their frames (7610).

Each CN code maps to a CBAM benchmark, adapted from the EU ETS benchmarks, that drives its free allocation adjustment (European Commission). The CBAM certificate obligation is calculated per-tonne-per-CN-code, then aggregated.

Two data engineering problems show up immediately:

1. The ERP’s CN code mapping is often stale. Cement formulations evolve; a customs broker may have reclassified a product without updating the ERP item master. A monthly reconciliation between the ERP item master, the customs broker classifications, and the actual import documents catches drift early.
2. Supplier emissions data is heterogeneous. Some Turkish steel mills supply ISO 14064-verified emissions per heat. Some Indian aluminum smelters supply a single annual average. Some Chinese clinker producers refuse to supply anything. The CBAM data pipeline must accept all three and route them differently (verified actual; supplier-supplied but unverified, which cannot be declared as actual until an accredited verifier has checked it; default value).

The World Business Council for Sustainable Development PACT (Partnership for Carbon Transparency) data model is the emerging standard for supplier emissions exchange. A few large suppliers already emit PACT-conformant carbon footprint data. Most do not. The pragmatic approach in 2026 is a supplier portal that accepts PACT format, a CSV upload fallback, and a manual entry path for the long tail.

Build vs buy: SAP Green Ledger, Carbmee, Plan A vs custom on top of your ERP

The vendor landscape for CBAM-and-ESG software has consolidated in the past 18 months:

• SAP Green Ledger / Sustainability Footprint Management. Native to S/4HANA, deep integration with MM (Materials Management) for shipment-level emissions data. Heavy lift to deploy if SAP is not already the operational ERP; relatively low marginal cost if it is.
• Carbmee. Berlin-based, CBAM-specific module. Strong supplier engagement tooling. Mid-market price point.
• Plan A. Berlin-based, broader ESG and CSRD coverage, with a CBAM module. Better fit when CBAM is one of several sustainability reporting streams.
• Tanso. German specialist for industrial emissions accounting with CBAM and CSRD coverage.
• CBAMEase, CarbonChain, Inverto for CBAM, and several smaller niche players. Most are competitive on price and CBAM-specific feature depth.

For construction firms with EUR 50 million to EUR 500 million revenue, a packaged CBAM module is an annual subscription plus an implementation project measured in weeks. A custom build, in contrast, is a longer engineering effort plus ongoing maintenance. The build option only pays off when CBAM is one of many sustainability data flows that share infrastructure (CSRD ESRS E1, EU Taxonomy, GHG Protocol Scope 3 reporting), and when in-house engineering is genuinely available.

The honest framing: if your team has built three integrations to a customs broker, an ERP, and a CBAM Registry before, you can build it. If you have not, buying is faster and cheaper in 2026.

Supplier portal architecture for collecting verified embedded emissions

The supplier portal is the part of the stack that most teams underbuild. It is also the part that decides whether actual-emissions reporting at scale is possible.

A working supplier portal has the following components:

• Authenticated supplier accounts with role-based access (data preparer, approver, verifier).
• Product master, mapped to the buyer’s CN code list, with each product carrying mass-balance allocation rules.
• Installation data: each supplier site with its production routes, energy mix, and any electricity contracts with guarantees of origin.
• Quarterly or shipment-level emissions submission in PACT format or a CBAM-aligned CSV template.
• Verifier upload: the supplier or its verifier uploads the verifier opinion and the underlying data per Implementing Regulation (EU) 2025/2546.
• Bilateral query workflow so the importer can ask clarifying questions and lock the data set for a reporting period.
• Versioning: every change creates a new immutable record. The CBAM submission and the GL posting reference a specific version.

Building this once for one supplier base is fairly straightforward. The difficulty is supplier onboarding. Most Turkish, Indian, Chinese, and Egyptian producers will not log into your portal voluntarily. Onboarding is a commercial conversation tied to renewal of supply contracts. Construction firms that started this conversation in 2024 are ahead; those that have not are now paying default-value rates while they catch up.

Audit trail and verifier handoff under Implementing Regulation 2025/2546

The verifier opinion is the artifact that converts a supplier emissions claim into a CBAM-acceptable verified actual. Under Implementing Regulation (EU) 2025/2546 and Delegated Regulation (EU) 2025/2551:

• Verification must be done by a verifier accredited by a national accreditation body, which has to demonstrate compliance with EN ISO 17029 and EN ISO 14065 (European Commission).
• The verification report is prepared on an electronic template the Commission provides via the CBAM Registry, with minimum content set in the Annex to Implementing Regulation (EU) 2025/2546.
• The declarant includes the operator’s emissions calculation and the verification report in the CBAM declaration.
• The declarant keeps the underlying records, including the verifier’s report, until the end of the fourth year after the year of the declaration (Article 7(6)) and presents them on request during NCA audits.

The software implication: every emissions value used in a CBAM declaration must carry a backreference to its verification source. When the auditor asks where a specific clinker shipment’s emissions number came from, the answer is a chain: declaration line, supplier production batch, verifier opinion, supplier audit trail. Without that chain, the importer takes the risk on its own.

Cost model: certificates, software, and internal compliance headcount

A realistic CBAM cost stack for a mid-size importer in 2026:

• Certificates: the dominant cost line. An illustrative example: an importer bringing in 50,000 tonnes of clinker per year with embedded emissions of 0.8 tCO2 per tonne and an EU ETS price of EUR 80 per tCO2 faces a gross certificate cost of approximately EUR 3.2 million per year, most of it offset in 2026 by the free allocation adjustment, which shrinks as EU ETS free allowances in CBAM sectors phase out by 2034 (European Commission).
• Software: a packaged-module subscription plus integration cost.
• Internal compliance headcount: 0.5 to 2 full-time equivalents depending on portfolio complexity and supplier diversity.
• Verification: under the definitive regime, verified emissions data comes from the producer’s side. The Commission’s Q&A warns importers that third parties offering to sell them verification reports are likely a scam.

The penalty exposure is real but manageable: under Article 26 of the regulation, the penalty for each CBAM certificate not surrendered by 30 September is the same excess emissions penalty applied under the EU ETS Directive to operators exceeding allocations, EUR 100 per tonne indexed to European consumer prices, plus the obligation to surrender the missing certificates retroactively.

A practical 2026 priority list for a construction firm now in definitive-phase compliance:

1. Confirm authorized CBAM declarant status is granted and live in each member state of establishment.
2. Audit supplier coverage. For each in-scope supplier, classify into verified actual, supplier-supplied unverified, or default value. The goal in 2026 is to halve the third category by 2027.
3. Lock the data pipeline. ERP item master to customs broker classification to CBAM module, with monthly reconciliation.
4. Build the certificate purchase governance: who approves, on what schedule, at what price tolerance. From 2027 the declarant must hold certificates covering at least 50% of the year’s embedded emissions at the end of each quarter (Regulation (EU) 2025/2083). Letting this slip means buying certificates at the worst price every quarter.
5. Rehearse the NCA audit. Pull a quarter’s imports and walk them backward to source evidence. Identify where the chain breaks.

CBAM is no longer the future tense. It is the operating tax on imported emissions for EU construction supply chains. The firms that treat the supplier portal, the registry integration, and the certificate governance as production systems are the ones for whom the quarterly cycle becomes routine instead of an emergency.