kolum
Log in
The Imports upload template changed on September 4, 2026. Older versions of the template are no longer accepted, please download the new one:Download the new Imports template
CBAM · EU Companies

Enter Emission Data Directly

Overview

Reporting Timeframe. Emission data is scoped by a Reporting Timeframe selector at the top of the Emission Data screens. Set it to the period the data applies to; the screen then shows the emission data relevant to that timeframe, and the currently running forecast timeframe is selected by default.

kolum supports manual capture of emissions where values are known from external sources. Emissions are now recorded at the Supplier × CN Code level. Once saved, the values are inherited by all articles that are linked to the same supplier and CN code, ensuring consistency and traceability across your portfolio.

Access Path

Supplier subpage (authoritative entry point): Supply Chain → Suppliers → [Select Supplier] → CBAM tab → Purchased CBAM Goods → Edit on the relevant CN code row.

Scope and Data Model

  • Granularity: Values are stored on the Supplier × CN Code tuple and propagate to all linked articles.
  • Direct emissions (tCO₂e/t): Process emissions under the producer's operational control.
  • Indirect emissions (tCO₂e/t): Emissions associated with purchased electricity/steam/heat/cooling consumed in production. If configured, kolum calculates: Indirect emissions = Consumed electricity × Emission factor.
  • Production Method: Required for specific CN codes; must match the allowed methods for that classification.

Procedure: Provide or Update Emissions (Supplier Subpage)

  1. Navigate to Supply Chain → Suppliers and open the relevant supplier.
  2. On the CBAM tab, in Purchased CBAM Goods, locate the CN code to be edited and select Edit.
  3. In the edit drawer, review or complete the following fields:
    • Article classification (CN code): Pre-filled and non-editable.
    • Buying company: Pre-filled where applicable.
    • Country of origin.
    • Production facility: Select if known/required.
    • Production method: Must be valid for the CN code.
    • Direct emissions (tCO₂e/t): Enter a numeric value.
    • Source of electricity: e.g., Received from the grid.
    • Consumed electricity: Quantity per tonne of output.
    • Emission factor: Factor applicable to the electricity source/unit.
    • Indirect emissions (tCO₂e/t): Auto-calculated where enforced; otherwise provide a numeric value.
  4. Click Save.

Result: The values are stored against the Supplier × CN Code and immediately applied to all articles linked to that combination. No article-level edits are required.

Uploading Emission Data by File

You can enter many records at once with the emission data template (Upload Emission Data from CSV or Excel).

  • Download the current template from kolum before you start.
  • The template uses a Reporting Timeframe column; each row must state a timeframe from the currently selectable set.
  • Actual emission data is accepted independent of a connection to an import: no row is skipped for lacking a matching import. kolum still looks for a fit using the row's Reporting Timeframe together with Supplier, Company, CN Code, Production Facility, and Country of Origin: when all of these overlap with an import inside that timeframe, the entry is shown as connected in the Emission Data table; when there's no fit, the entry is still stored and shown, just unconnected. This applies to Actual emission data only. Default emission data without a connected import is still not shown, unchanged.
  • For rows whose Reporting Timeframe is 2026 or later, kolum also validates the (CN Code, Production Route) combination against the permitted set for that CN code; rows with an invalid combination are rejected with a row-level error while the remaining valid rows in the file are still committed. Enter the route as its letter or as letter, name.
  • A row no longer needs to omit whichever of Production Route or Production Method doesn't apply to its own Reporting Timeframe: a 2026+ row that also carries a Production Method, or a pre-2026 row that also carries a Production Route, is accepted and the value that isn't relevant to its timeframe is simply ignored. A row is only rejected when the value required for its own timeframe is missing or invalid.
  • Validation errors now name the specific column that failed, and legitimate production facility IDs and 0 values in the electricity emission fields are accepted; they are no longer rejected by mistake, and the old misleading "check table structure" error and its dead-end button are gone.
  • Review the validation view, correct any skipped or invalid rows, and re-upload until the file is accepted.

What's new

Uploading actual emission data no longer depends on a matching import: every actual row is saved and shown in the Emission Data table, connected to an import where one fits and unconnected otherwise. A row that carries both a Production Route and a Production Method is accepted, and kolum simply ignores the value that does not apply to the row's reporting timeframe.