CBAM period and version mismatch
CBAM-PERIOD means the selected data period does not fit the explicit preflight mode. An archived QReport for 2024 Q4 is a transitional quarterly report. Changing its Year to 2026 does not turn that document into an annual declaration. The European Commission places transitional resources in its archive and describes the definitive regime separately from 1 January 2026. This diagnostic helps ERP and customs teams stop that version confusion before they investigate downstream errors.
Reproduce the period failure
Open the fictional worksheet example with Year 2025 and Period annual. Run the check: CBAM-PERIOD points to line 3, /p:CBAMData[1]/p:Year[1]. The independent worksheet mode accepts years from 2026, so this combination fails the chosen data contract. Correct the year only if your underlying source records support that correction. Do not relabel a historical dataset to make a checker pass.
Choose the actual document family
For historical analysis, select Historical QReport and explicitly choose 18.30 / stypes 17.03. The supported transitional period is 2023 Q4 through 2025 Q4. The common namespace cannot identify a precise schema release, and an absent version confirmation leaves the independent business layer unexecuted. A different package may share field names while enforcing different constraints. Preserve your original export, period and package provenance before making a correction.
For current filing XML, choose the other/current profile and supply the exact schema you are entitled to process locally. The business mapping remains unknown, even when a supplied XSD compiles and accepts the file. A schema proves constraints of those supplied bytes; it does not prove current register applicability. There is no confirmed current annual filing XSD bundled in this release.
Resolve the archive dependency explicitly
The downloaded archive names its simple types stypes_17.03.xsd, while QReport_18.30.xsd includes stypes.xsd. A missing dependency is a package error, not evidence that your report violates the schema. If your rights permit a local filename alias, retain identical original bytes and record the official source, exact version and notices under the supplied path. The browser never fetches a substitute or silently edits that include.
Read the result before exporting
Keep the report's XML, XSD, independent business and plausibility layers together. The error location is useful for finding the generating ERP field, but fixing it does not establish complete CBAM validity, authorisation or acceptance of a late correction. Registration windows and permission to amend a report require separate confirmation with the competent authority. This guide does not make that decision.
Primary evidence: EC transitional archive and EC definitive regime; artifact reuse remains subject to the EC legal notice and individual exceptions. Checked 6 November 2026.