CBAM verification materiality and evidence prep

Preparation is not verification

An evidence pack is a structured handoff, not a verification opinion. It should show which installation, goods, process, reporting period, monitoring-plan version, operator-report version, source records, controls, calculation references, and open issues belong together. It should also show who supplied each record and which version is current.

That preparation reduces avoidable search and reconciliation work. It does not decide whether evidence is sufficient, whether a misstatement is material, whether a site visit can be replaced or waived, or whether an operator's emissions report can be verified as satisfactory. Those are verifier decisions under the adopted rules.

Keep the evidence object separate from the decision object. A complete-looking folder, spreadsheet, checklist, or CBAM Pulse record is not accredited verification, a compliance result, a filing decision, or confirmation that actual emissions may be used.

When verification enters the CBAM workflow

Article 8 of the consolidated Regulation (EU) 2023/956 applies where the embedded emissions declared in the CBAM declaration are determined on the basis of actual emissions. The authorised CBAM declarant must ensure those declared total embedded emissions are verified by a verifier accredited under Article 18.

Article 8(2) allows the declarant to use verified information disclosed under Article 10(7) for goods produced in a registered third-country installation. Registration, disclosure, a supplier reply, or an internally reviewed pack does not by itself make the information verified.

This page owns evidence-pack preparation. The accredited-verifier guide owns who can verify, accreditation scope and timing, and national accreditation body roles. The default-versus-actual guide owns route-state definitions; the precursor guide owns source/version consistency; the exporter/importer guide owns commercial-chain lineage.

Before assembling a pack, label the data basis at each affected goods/process record. Supplier-reported actual candidates, evidence assembled for handoff, verified actual information, official defaults, and unresolved inputs must not collapse into one 'done' state.

Installation evidence-pack manifest

Use one manifest to identify every pack object and its current version. The manifest is an index to source records, not a substitute for the monitoring plan, operator emissions report, verification report, or underlying evidence.

The fields below are a product-designed preparation structure. Where an official template or Registry field applies, preserve its identity and reference rather than rewriting it into an internal format that loses provenance.

Evidence-pack states and owners

Assign one state to each pack object. The state says what has been evidenced and what happens next; it does not predict the verifier's opinion.

Do not promote a record because it has a filename, signature image, percentage, or polished summary. Promote it only when the referenced source, version, owner, scope, period, and evidence relationship have been checked.

Monitoring plan to verification report lineage

Implementing Regulation (EU) 2025/2547 requires operators to set out the main methodological criteria for collecting installation data and calculating emissions in a monitoring plan. The operator emissions report then carries the installation, goods, specific embedded emissions, free-allocation information, and other information needed for verification and later review.

The report path must preserve versions. Where the verifier identifies misstatements, non-conformities, or non-compliance, the operator corrects the monitoring plan and operator emissions report as applicable and provides the final versions to the verifier. The pack should retain the superseded-to-final relationship rather than silently overwriting the earlier source.

Commercially sensitive and declarant-specific information also needs the correct object boundary. The operator-report summary and any declarant-specific addendum are not interchangeable, and access to one does not imply access to every underlying record.

The 5% materiality level is not an automatic tolerance

Article 5 of Commission Implementing Regulation (EU) 2025/2546 requires the verifier, for each tonne of the relevant good identified by CN code, to apply materiality levels of 5% of total specific embedded emissions and 5% of total specific embedded free allocation when assessing reported-data misstatements.

Article 5(2) also requires verifier expert judgment. A misstatement below the quantitative level, or a parameter outside those two measures, can still be material because of its size and nature. The relationship is directional: below 5% does not mean immaterial, acceptable, or safe to ignore.

For preparation, record the issue's affected goods, report field, source, size if already calculated by the source owner, nature, recurrence, and control impact. Do not calculate a CBAM Pulse materiality score or automatically close an issue because a percentage appears small.

Reasonable assurance is defined in Delegated Regulation (EU) 2025/2551 as high but not absolute and is expressed positively in the verification opinion. The verifier applies professional scepticism and risk-based work; an importer checklist cannot reproduce that judgment.

• Keep the two official 5% parameters separate from every other issue class.
• Record below-level issues instead of auto-closing them.
• Preserve qualitative factors such as source reliability, recurring control failure, period mismatch, or key-parameter impact.
• Leave materiality and opinion decisions to the accredited verifier.

Issue queue: misstatement, non-conformity, and non-compliance

The adopted rules use different issue concepts. A misstatement is an omission, misrepresentation, or error in reported data. A non-conformity concerns an operator act or omission that does not meet the monitoring-plan or applicable monitoring-methodology requirements. The verification process can also identify non-compliance with applicable requirements.

The pack should preserve the source wording and affected object. Do not convert every issue into a generic 'data error' because the correction owner, evidence, and effect on the operator report can differ.

When an issue is corrected, record the correction, corrected object/version, date, owner, and verifier status. A closed internal task does not prove that the verifier accepted the correction.

Site-visit readiness without making the verifier's decision

A physical site visit is part of the verification framework, but the verifier decides whether the source conditions for a physical visit, virtual replacement, or waiver are met. The pack can organise logistics and evidence; it cannot issue the decision.

Implementing Regulation (EU) 2025/2546 treats the first year subject to verification differently from later consecutive years. The recitals state that a physical visit should be required in the first year. In a second consecutive year, virtual replacement or waiver can be considered only under specified conditions, including the prior physical-visit and risk/reliability requirements. Physical visits should occur at least every two years, with distinct flexibility for specified electricity cases.

Serious, extraordinary, and unforeseeable circumstances have their own virtual-visit conditions. Do not merge that path with routine cost or convenience arguments. Record facts and leave the decision with the verifier.

Synthetic installation evidence pack

This example uses fictional names and reference states only. It contains no emissions values, factors, calculations, customer data, verifier identity, or opinion. It shows how a pack stays blocked or moves to handoff without pretending to predict verification.

Installation Atlas produces Goods Line Cedar. The current monitoring plan and operator-report candidate are identified, but one precursor-source version conflicts with the period mapping. The pack can be internally reviewed while the conflicting object remains blocked; it cannot be labelled ready for verifier handoff until the conflict and version relationship are recorded.

After the operator provides the corrected precursor record and final operator-report version, the coordinator can mark the manifest ready for verifier handoff. The state still remains unverified until an accredited verifier performs the work and the issued verification report/opinion is received and reconciled.

Accredited-verifier handoff checklist

The handoff should let the verifier navigate the pack without reconstructing the installation's data flow from disconnected emails. It should also show every unresolved issue rather than presenting a cleaner fictional state.

The verifier controls the engagement, verification plan, risk analysis, sampling, data testing, recalculation, site-visit path, findings, and opinion. Use the sibling accredited-verifier guide for accreditation actors and scope.

• Pack manifest with current object identities and versions.
• Installation, goods, process, activity-group, and reporting-period mapping.
• Current monitoring plan plus superseded/corrected version links.
• Operator emissions report candidate/final status and summary/addendum map.
• Source-data, measurement, calculation, attribution, control, process, and precursor references by report field.
• Free-allocation input/source references without a CBAM Pulse calculation.
• Complete issue queue with source wording, owner, correction status, and retained versions.
• Site-access/logistics facts and prior-visit evidence where relevant, with no pack-level waiver decision.
• Keep adviser review notes separate from accredited-verifier requests, findings, and decisions.
• Explicit product boundary: CBAM Pulse does not contact the verifier, transmit files, connect to the Registry, or perform verification.

Verification-report receipt and reconciliation

Delegated Regulation (EU) 2025/2551 provides defined verification-opinion statements. The report records a satisfactory or unsatisfactory opinion. An unsatisfactory opinion can result because material misstatements/non-conformities remain, clarity is insufficient, or the verification scope is too limited. A satisfactory opinion requires the operator emissions report to be free from material misstatements.

Record the exact opinion and report version; do not paraphrase it into a generic success or requirements-met badge. Reconcile the report's installation, activity-group scope, goods, reporting period, operator-report version, findings, and any remaining conditions to the pack manifest.

The verifier may only issue for the activity-group scope in which it is accredited. From 1 January 2027, the adopted act specifies Registry issuance and operator transmission paths according to whether the operator is registered; the pack should record the received route/reference without claiming a Registry integration.

If the report is unsatisfactory or references a different operator-report version, keep the downstream row blocked and route the exact finding/version mismatch to the responsible owner. CBAM Pulse does not decide whether or how a declaration should proceed.

• Verification-report ID, issued version, date, and exact opinion statement.
• Verifier identity and relevant accreditation-scope reference.
• Installation, goods/activity group, reporting period, and operator-report version match.
• Material findings, unresolved non-conformities, scope limitations, and required corrections.
• Registry/direct transmission reference as received, without copying inaccessible confidential material.
• Downstream affected goods rows and named owner for any mismatch or unsatisfactory result.

How CBAM Pulse fits the handoff

CBAM Pulse can organise factual references, versions, owners, supplier data references, supplier-request history, reporting evidence checklist states, and open gaps. That helps prepare a source-linked handoff and keeps unresolved objects visible.

CBAM Pulse does not store supplier evidence files, calculate materiality, determine site-visit treatment, choose or contact a verifier, connect to the CBAM Registry, conduct verification, issue an opinion, decide evidence sufficiency, or determine filing, applicability, liability, or a requirements-met status.

Use the reporting evidence checklist to inspect preparation coverage, the supplier-request workflow for missing upstream fields, and the precursor guide for source/version consistency.

Use the accredited-verifier guide for the actor/accreditation path.