Exporter Evidence Requirements

Direct answer

Material CBAM inputs must carry evidence lineage: who issued the document, what period it covers, which field or calculation it supports, and cryptographic integrity of the stored file bytes.

Pending, rejected, unsupported, missing, tampered, unlinked, or hash-mismatched evidence must block sealing. Partially supported is not fully supported.

Who is affected

Non-EU producers and exporters assembling packages for EU importers, data preparers, internal reviewers, and read-only verifier recipients who must navigate evidence without altering source records.

Regulatory and operational rule

Embedded emissions claims used for CBAM reporting must be defensible. Operator-prepared packages are not accredited verification opinions, but they must still present coherent, evidence-linked calculations that an independent verifier can test.

CBAMValid enforces a fail-closed evidence contract before a sealed release: review status approved, support status supported, physical bytes matching registered SHA-256 and size, and tenant/case-bound storage paths.

2026 definitive-period impact

In the definitive period, weak evidence does not only create transitional learning friction — it undermines the annual declaration package that importers must defend, with the first 2026-import declaration cycle due by 30 September 2027.

Evidence gaps discovered late force recalculation, new sealed versions, and delayed handover to accredited verification.

Required evidence data

Every material evidence record should capture at least:

• Evidence identity, file name, document type, issuer, and issue date
• Reporting-period coverage and linked input fields / calculations
• MIME type, byte size, storage path, SHA-256 hash, upload time, uploader
• Confidentiality marking, review status, support status, and page/sheet/row references where relevant
• Reviewer notes and corrective-action linkage when findings exist

Decision tree

Before requesting seal:

• 1. Map each material calculation input to at least one evidence object.
• 2. Confirm period coverage matches the reporting year/period of the case.
• 3. Approve review status only after human review of content suitability.
• 4. Mark support status supported only when the document fully supports the claimed input.
• 5. Verify stored bytes match registered hash and size.
• 6. Close or remediate open material findings — do not suppress them.
• 7. Seal only when the readiness engine reports a sealable state.

Practical example

Electricity consumption used for indirect emissions is linked to a meter extract PDF. The evidence record stores issuer, period, SHA-256, and the exact input field IDs. After internal approval and support confirmation, the calculation node references that evidence ID in the sealed trace.

If a later upload replaces the PDF with different bytes, hash verification fails and sealing is blocked until the register and physical object are reconciled.

Common errors and risks

Frequent seal blockers:

• Uploading files without linking them to the fields they supposedly prove
• Using documents outside the reporting period
• Treating partially supported evidence as sealable
• Relying on metadata alone when bytes cannot be verified
• Cross-tenant or path-traversal storage mistakes
• Assuming client preview calculations are the sealed authoritative result

Official EU sources

Evidence expectations follow from the CBAM regulatory framework (Regulation (EU) 2023/956 and applicable implementing acts) and from verification practice: claims must be testable. Use primary EUR-Lex and Commission sources cited in the page footer.

Related CN and methodology

CN classification determines which producer data and evidence sets are material. Methodology decisions (boundary, actual/default, allocation) determine which calculations must be evidenced. Review the sample dossier to see how evidence register, field matrix, and calculation annex sit together.

How CBAMValid handles it

CBAMValid stores tenant-bound evidence, computes SHA-256, tracks review/support status, blocks seal on material gaps, and packages an evidence register plus field-to-evidence matrix inside the sealed release. Re-download returns the same immutable package.

Product boundary

CBAMValid is an exporter verification-preparation platform. It does not replace independent accredited verification, does not guarantee Registry or customs acceptance, and does not convert missing evidence into assumed zeros.