CBAM · definitive period, since 1 Jan 2026

Exports with the proof attached.

Carbon-End turns a plant's invoices and meter readings into a CBAM figure an EU importer can put straight into a declaration — verified, traceable, and impossible to alter after the fact.

  • Disclosing
  • Reading
  • Hashing
  • Versioning
  • Attributing
  • Verifying
Disclosure · 2026 SEALED
Factor tablesfuel_factors · grid_electricity
Evidence read14 documents · sha-256 verified
Enginecarbon_end_engine 0.1.0
Verificationaccredited body, named
0.0928

t CO₂e per tonne of rebar

Installation totals

Scope 1, direct 8,078.4 t
Scope 2, grid average 23,870.0 t
Scope 2, contractual 0.0 t

Both electricity figures stay on the buyer's page. Showing only the flattering one is how a disclosure stops being worth anything.

Regulation (EU) 2023/956 Default values cost 10% more in 2026 · 20% in 2027 · 30% from 2028 Records kept to the end of 2031 for a 2026 import

Why actual data

The default value is a penalty, not a shortcut.

An importer that accepts default values pays for emissions your plant may never have produced, and the gap widens every year. Actual data is the way out, and actual data has to be verified.

+30% +20% +10% 0 +30% Declared on default values Declared on actual, verified data 2026 2027 2028

The lower line is a plant that measured. It does not move. The distance to the line above it is what an importer is charged for a figure nobody produced.

10%

Added to a default value in 2026 — before the figure even reaches the certificate price.

20%

In 2027. The same product, the same plant, a bigger bill for not having proved anything.

30%

From 2028 onward. At that point the cost of not measuring is a line item nobody can defend to a board.

The workflow

Four inputs, one engine, and a number that holds up.

Everything on the left carries its own record: an invoice behind a reading, a hash behind a document, a version behind a coefficient, a named person behind a judgement. The engine holds no emission factor of its own — every value comes from a dated table, and each calculation records which version it used.

INVOICES · METERS EVIDENCE · SHA-256 FACTOR TABLES EXPERT RULING ENGINE FIGURE VERIFIER SEAL DISCLOSURE

The seal changes nothing but the seal. A correction after it does not edit the figure; it opens a new period, and the disclosure already issued goes on showing what it showed.

The chain

One figure, four hands, and no two can do each other's job.

01 · The plant

Enters what it actually used

Fuel, electricity, purchased precursors, tonnes out — each with the invoice behind it. It makes no regulatory judgement, and there is no control on the screen for one.

02 · The engine

Computes it from versioned tables

No emission factor is written into the code. Every value comes from a dated regulatory table, and each calculation records which version produced it.

03 · The expert

Rules on what qualifies

Whether a green electricity contract counts under CBAM is a legal judgement. It is made by someone who knows the regulation, on the record, against a document.

04 · The verifier

Reads the whole trail and attests

An accredited body sees which input produced which number, under which table, changed by whom. Only for the clients that engaged it, and it changes nothing but the seal.

Committed to clarity

A figure is worth what cannot be done to it afterwards.

Records cannot be altered

Evidence, calculations and the audit log are append-only, refused at the database level. The application connects as a role that owns nothing, so the guarantee does not rest on the application behaving.

An issued figure never moves

A buyer's link carries the numbers as they stood when it was issued. Recalculating does not touch it. A correction opens a replacement, and the old link starts saying so.

Verification is named

The body, its country, its accreditation number, the person and the date — on the page the buyer reads. An unnamed attestation is not something a compliance officer can use.

FAQ

The questions that actually get asked.

Do we have to be verified?

The obligation sits with your EU importer, not with you. But an importer that declares actual emissions must have them verified, and one that does not accepts the default-value mark-up instead. Handing them verified data removes work and risk from their side, which is why it wins orders.

Who sees our invoices?

Your own people, Carbon-End, and only the verification body your organisation has engaged. A verifier with no engagement sees nothing at all, and ending an engagement removes the access the same day.

What if a figure turns out to be wrong?

It is corrected by opening a replacement period, never by editing the old one. The original stays readable, because the records behind a declaration have to survive to the end of the fourth year following it, and every link already issued starts telling the buyer a correction exists.

Where does our data live?

On servers in the European Union, with encrypted backups also held in the EU. That is a cross-border transfer under Turkish data protection law, and it is addressed in the customer agreement rather than left to be discovered later.

Start with one reporting year.

Bring a year of invoices and meter readings. You will see the figure, the warnings the engine raised, and exactly what a verifier would be shown.

Carbon-End is operated by Atlas Noya · Ostim Teknopark, Ankara Request access