CBAM for Steel Importers: A Procurement and Customs Task Matrix

CBAM for steel imports is a handoff task, not a one-person job

For an organisation importing steel into the EU, CBAM should not be treated as one more spreadsheet beside procurement. Since 1 January 2026, the definitive regime has applied. Depending on commodity code, quantity, and import model, work can arise around authorisation, emissions data, declarations, certificates, and evidence. The operational question is therefore simple: who supplies which information, who checks it, and who may stop a case? The supplier onboarding playbook offers a useful model for making multi-team handoffs explicit. This article turns that model into a practical CBAM task matrix for procurement, customs, and sustainability.

The legal framework remains decisive. The European Commission’s definitive-regime guidance describes, among other things, application from 2026, the role of authorised CBAM declarants, and the annual declaration and surrender of certificates. An operational summary does not replace checking the relevant CN code or classifying a specific import. Training should make that boundary clear: people learn which data and warning signs to recognise, while legal and technical determinations stay with the named accountable owners.

Open the case correctly before chasing data

Procurement should not open the case only when an order is placed. During supplier selection, quotation comparison, or framework contracting, the team should be able to see whether goods may arrive from a third country, what technical description is available, and which function owns tariff classification. The customs and import verification chain shows why sourcing, classification, and release must be visible as separate decisions. For a matrix, the first column can stay simple: case, possible CBAM relevance, source of the goods description, and accountable technical check.

Customs or trade-compliance staff do not check information as a favour to procurement. It is a distinct control step. The commodity code, origin and shipping picture, and the role of the declarant must fit together. If a supplier sheet conflicts with contract data or import documents, the team needs a defined clarification route rather than a quiet spreadsheet edit. The training matrix by role is a useful example of separating sourcing, expert review, and documentation without leaving gaps between them.

Sustainability or environmental management should not automatically own every number that concerns emissions. The role needs to define which supplier data are plausibility-checked, which method or source is recorded, and when specialist advice, verification, or escalation is required. Role-based access training provides a transferable principle: do not give a function a vague mandate, give it a specific decision, the data it may use, and a route for exceptions. For importers, the key question remains which information can be used reliably in their own declaration.

AI-generated

Build the task matrix as five controllable rows

Row one is goods master data and scope. Record the technical description, expected commodity code, supply route, supplier, and the person who confirms the expert classification. This prevents a product labelled simply “steel part” from travelling through the organisation without anyone checking the specific regulatory scope. Training should include a counterexample: two similar parts, different documentation, different escalation. The goal is not for everyone to master tariff classification. It is for them to recognise when expert review is mandatory.

Row two is supplier data. Do not ask only for a value. Ask for origin, reference period, product link, accountable contact, and traceable source. Missing information is a status, not a blank cell. The matrix should distinguish requested, received, plausibility-checked, rejected, and escalated. Procurement can then see whether it needs to chase the supplier, while sustainability can see what is missing for review. That reduces the familiar late rush before a declaration.

Row three is import and responsibility data. Record the import date, customs declaration, accountable legal entity, role of the declarant, and link to the internal case. In group structures, freight arrangements, or indirect representation, the actual responsibility can differ from the purchasing workflow. A practice case should therefore not begin by asking who pays the invoice. It should ask who submits which declaration under the actual model and who must be able to retrieve which evidence.

Row four is review and approval. Each data type needs a reviewer, date, result, and reason. “Looks plausible” is not a dependable approval. Use simple criteria instead: does the period fit the delivery, is the product link understandable, has a discrepancy been explained, and is the source stored so another person can follow the path? These criteria work well in a short case exercise and can later be checked through samples.

Row five is declaration and evidence. Link the approved case to the annual declaration, certificate process, and the supporting material used. The principle behind audit-ready training records transfers well: not only the final completion matters, but the path from assigned case through decision to retrievable evidence. CBAM teams should document the same path without creating an endless requirement to store every email.

AI-generated

Turn the matrix into training with decision points

A strong module does not begin with the whole regulation. It begins with a deliberately incomplete case. Procurement has a goods description, the supplier sends a spreadsheet, customs identifies an open question, and sustainability receives an emissions value with no clear product link. Ask groups to decide: what is missing, who asks, what may proceed, and what must stop? The matrix then becomes a shared language rather than a document understood by one person only.

The second case should contain a plausible but conflicting detail. Perhaps the period does not fit the shipment, or the unit differs from the agreed product description. Here people learn to name a discrepancy precisely and send it to the right place. Mandatory employee training guidance reinforces that evidence is not a participation list alone. For this topic, organisations need roles, learning objectives, exercise outcomes, and a recorded response to open cases.

The third case is time pressure. A delivery is at the port, but data are missing or approval is not traceable. The right learning question is not how a team somehow meets the deadline. It is who decides the next step, how the exception is recorded, and which follow-up remains open. The same boundary appears in online occupational safety instruction: digital learning can structure actions, but it does not replace expert evaluation or an operational measure.

Prepare evidence and governance for the next declaration

Regulation EU 2023/956 on CBAM and the current Commission material are the sources for legal requirements. In day-to-day work, a short versioned list per case is practical: goods classification, supplier data, reviewed assumptions, approval, escalation, and storage location. Add an owner for the list and a date for the next review. This lets the organisation distinguish cases ready for declaration from cases needing data or an expert decision.

Leaders do not need a second operational spreadsheet for this. They need a view of open data, recurring discrepancies, upcoming deadlines, and training effectiveness. Each quarter, review a small sample: were owners named, were queries recorded, and was an exception closed rather than merely postponed? Feed the results back into the practice cases. The matrix then improves from real error patterns without burdening people with abstract repetition.

Set the right expectation: training does not create automatic CBAM compliance and does not replace customs, legal, or emissions expertise. It helps people recognise their information and escalation duties, avoid working past one another, and surface open points early. That is its value for small and medium-sized steel importers: fewer hidden assumptions, faster queries, and a traceable route from a supplier sheet to an accountable decision.

Add a data-quality review before the declaration process begins. Procurement presents the cases with a supplier link, customs checks the connection to import events, and sustainability assesses data gaps, assumptions, and unusual values. Each review ends with three clearly separated lists: approved, awaiting a query, and escalated. This prevents the false impression that a missing number can be cured by a carefully formatted spreadsheet. It also lets leaders see whether the same gap recurs with certain suppliers, goods categories, or teams, and whether contract clauses, onboarding, or learning content need to change.

For implementation, three cadences are often enough: a short case opening when procurement starts, an expert clarification when data are missing or inconsistent, and a periodic review before declaration. Define participants, inputs, decision, and record for each cadence. A deputy does not need to know the entire history, but must be able to find the status, last decision, and next escalation point. A good matrix is therefore not an archive report. It is a working tool for the next controlled handoff.

Sources and limits

For a specific case, consult the legal acts, the current European Commission CBAM legislation and guidance, and the appropriate specialist functions. The matrix is an organisational and learning tool. It does not determine whether a particular product, supply chain, or legal entity is legally in scope for a particular transaction.

• Regulation (EU) 2023/956 on CBAM at EUR-Lex
• European Commission: CBAM definitive regime
• European Commission: CBAM legislation and guidance

Manage training and evidence status in steel operations in a structured way