CBAM precursors and data consistency: keeping a reporting set coherent

What a precursor chain must preserve

A precursor is an input good whose embedded emissions are taken into account when the embedded emissions of a complex good are calculated under the applicable official method. That makes the reporting trail a chain of source records rather than one supplier figure copied onto every finished-good line.

Start with the exact goods and CN-code context, then keep each precursor identifier tied to the source installation, production process, reporting period, quantity and unit, emissions-data basis, evidence reference, and current version. A commercial material name or company-level figure does not establish that the same record belongs to every goods line.

The operating goal is consistency, not a calculation shortcut. One chain can contain a supplier actual candidate, a complete evidence package awaiting verification, verified actual evidence, a corrected official default, and an unresolved input at the same time. Those states must remain visible at precursor level before any authorised method is applied.

CBAM Pulse can organise the factual source and version trail. It does not assign a CN code, decide whether a material is a precursor in a particular case, select an emissions method, perform verification, or determine what may be declared.

Articles 13–15: period, aggregation, and mixed data bases

Article 13 of Commission Implementing Regulation (EU) 2025/2547 sets the default reporting period of a precursor as the year of production of the complex good. Where the operator gives the verifier sufficient evidence of the actual time of production, the precursor reporting period is the period in which that precursor was produced. Record the period and the evidence used to depart from the default; do not silently reuse an earlier period.

Article 14 addresses precursors under a given CN code that come from different reporting periods or multiple installations. It provides weighted average rules for those cases. It also provides that, where sufficient evidence shows a given production process used precursors from a single installation or a subset of installations, the relevant embedded emissions are based on that installation or the weighted average for that subset.

That rule is why source installation and production-process identity must survive data intake. It does not mean every supplier or process is always a separate final calculation line, and it does not allow an importer to choose whichever source record produces a preferred result. The official method and evidence determine the treatment.

Article 15 allows an actual-emissions calculation for complex goods to determine actual emissions for production processes within the installation producing the complex goods while using default values for one or more precursors. Keep each actual/default basis explicit. The dedicated default-versus-actual guide owns route-state definitions; this page owns consistency across the precursor chain.

Precursor-chain state matrix

Use one state per precursor source record. The state describes what is evidenced now and the next preparation action; it is not an applicability or verification conclusion.

Do not promote a state because a number looks complete or favourable. Move it only when the missing source, period, method, report, or accredited verification evidence is actually attached and reviewed.

Record the total precursor mass required

Annex III to Commission Implementing Regulation (EU) 2025/2547 describes the precursor-mass parameter as the total mass of precursor required to produce the amount of complex goods. It includes quantities that do not end up in those goods because they may be spilt, cut off, combusted, chemically modified, or leave the production process as by-products, scrap, residues, wastes, or emissions.

For preparation, keep the supplier's quantity, unit, reporting period, and explanation of what is included together. The net amount visible in a finished good may not represent the official input boundary, and a purchase quantity may cover more than one process, installation, period, or downstream product.

Record the quantity as evidence, not as a result. This guide does not derive specific mass consumption, multiply emissions values, allocate losses, or calculate precursor or finished-good embedded emissions.

Keep source installation and production process identifiable

Article 14 makes the source path operationally important. A precursor under one CN code may have been produced in different reporting periods or received from multiple installations, and the official rule can use a weighted average. Keep the source-specific monitoring data traceable before those weighted average rules are applied. Evidence can support treatment based on one installation or a subset for a given production process in the defined circumstances.

Preserve the source records before aggregation: installation identity, production process, period, precursor CN context, quantity, evidence state, and source version. That allows a reviewer to see which records entered a weighted set and which downstream lines depend on it.

Do not turn this preservation rule into a universal instruction that every different production process must be treated separately in the final calculation. The source model preserves options and evidence; the applicable official method controls the calculation.

Evidence and version ledger

Use one stable ledger row per field or reference family, then link it to every affected precursor source and downstream goods line. The minimum ledger below is a preparation contract, not an official reporting template.

A value without its source version is not safely reusable. Preserve the previous version when a revision arrives, record the effective period and review state, and show which downstream lines are waiting for reassessment.

Synthetic steel-fastener chain: three different evidence states

Consider a synthetic steel-fastener goods line with three input records. The example is deliberately non-numerical: it shows evidence and version handling only, not the legally applicable precursor inventory or an embedded-emissions calculation.

Input A has a completed accredited-verification reference tied to one installation, process, and period. Input B uses a corrected official default source record. Input C came through a trader, but the producing installation and method reference are still missing. The finished-good line must retain all three states rather than collapsing them into one average or treating the unresolved input as zero.

The immediate output is a review queue: confirm that Input A's report version and period map to the goods record; retain the exact corrected source identity for Input B; and block Input C while the upstream source fields are requested. The example does not decide whether any route may be used in a declaration.

Change propagation without silent overwrite

Use one dated source reference for each precursor evidence package and link every downstream goods line that depends on it. A supplier revision should create a new review event, not overwrite the only copy of the previous record.

Compare the new installation, process, period, quantity/unit, evidence state, and source version with the accepted record. Then identify the downstream lines affected, mark their prior review state stale or under review, and assign an owner for the next decision.

This is a data-control workflow, not an emissions method. Do not recalculate, reclassify, or promote the data state automatically when a file or number changes.

• Freeze the previous source and version before recording the revision.
• Record what changed, when it changed, and who supplied it.
• Rebuild the affected-downstream-line list from the stable precursor ID.
• Mark every dependent line for review; do not update only the first visible copy.
• Close the change only after the source, period, basis, and evidence state are reconciled.

Do not invent missing precursor values

An explicit gap is safer than a plausible-looking substitution. Missing fields remain unresolved until the source record or the applicable official fallback is established through the correct review path.

Use the supplier request and evidence checklist to turn each gap into a named action. The list below prohibits common shortcuts; it does not prescribe the official calculation treatment for a specific good.

• Do not copy a prior period, corporate average, adjacent supplier, or zero into a missing precursor field.
• Keep source installation, production process, reporting period, quantity, and unit explicit before changing state.
• Do not use a nearby CN code, product description, production route, or country row because it looks similar.
• Do not describe supplier-reported information as accredited verification.
• Do not merge unresolved and evidenced inputs into one unlabeled total.
• Assign one owner, one request, and one review date for every blocked field.

Operational handoff

The final handoff should let a reviewer answer four questions without reconstructing the chain: which precursor source is this, what evidence state does it have, which version is current, and which downstream lines depend on it?

Use the supplier request template for missing installation, process, period, quantity/unit, method, and evidence references. Use the reporting evidence checklist to record what is present and what remains open. Use the default-versus-actual guide for the route-state definitions and the exporter/importer data-flow guide when the direct supplier is not the producer.

Those tools organise preparation. They do not send supplier requests, store evidence files, calculate embedded emissions, perform accredited verification, or determine declaration treatment.

• Export or copy the stable precursor/source references.
• Attach the current evidence/version ledger and previous-version pointer.
• List every dependent finished-good line and its current review state.
• List unresolved fields with owner, request date, and next review date.
• Keep route, calculation, verification, and applicability decisions with the authorised review process.