CBAM · LOCAL LITE · SCOPE ALWAYS VISIBLE

EU CBAM XML preflight

Catch inconsistent goods and emissions data before your ERP export becomes more compliance work. For importers of steel, aluminium, cement and other relevant goods, customs agents and integration teams.

Runs on this device. No XML upload. Rule-only demo: XSD not executed.

EN · DE

2026 annual declarations are a separate regime. No current annual filing XSD confirmed in this build. The archived 18.30 quarterly schema is never presented as a 2026 filing schema.

Check data locally

Explicit scopeHistorical package version · namespace alone is insufficientXML · UTF-8 · ≤10 MB

One file free. Existing Pro / Team batches: 25 / 100 files, 50 MB total; separate results per file. ZIP blocked.

XML

Optional authorised local XSD

Supply original XSD 1.0 files and every dependency with sufficient local processing rights. Public/free/BYO does not establish permission. No official CBAM schema is bundled; EC software/third-party exceptions remain unresolved for the archive pack.

Complete local schema folderOr individual XSD filesRoot path relative to selected folderPer-file provenance / rights JSON

30 XSDs, 1 MB each, 10 MB total. Original SHA256 recorded. Relative local dependencies only, no network fetch or schema rewriting. For the archived pack, QReport_18.30.xsd includes stypes.xsd while the archive supplies stypes_17.03.xsd: only create a local filename alias with identical bytes if your rights permit it; record that source/version under its supplied path. Missing dependencies remain unexecuted.

Own teaching worksheet XSD · Provenance JSON

Historical weighted emissions · explicit unit agreement

No official unit list is included. Only confirm after checking your actual package/code meanings. This computes an arithmetic aggregate, never measures or verifies emissions. Electricity-specific calculations are outside scope.

MeasurementUnit code meaning tonnes net massMeasurementUnit code meaning tonnes CO2e per tonne

What the layers mean

XSD

Optional authorised supplied XSD only. The sample leaves this layer unexecuted. A supplied schema pass says nothing about whether it is the current filing schema.

Independent business checks

EORI shape, explicit year/period, CN/HS shape, country shape, quantities, units and conditional arithmetic. Data worksheet: direct + indirect absolute emissions. Historical: procedure/production sums in equal units; weighted emissions only with explicit unit agreement.

Plausibility and unchecked

Unknown profiles never receive full green. External codelists, verification, authorisation, certificates, thresholds and register acceptance are not checked. Country differences are review prompts, not automatic legal conclusions.

Own data worksheet, not an annual declaration

The 2026+ demo uses the independent CBAMData namespace urn:xsdhub:cbam:data-preflight:1. Export these fields from your ERP explicitly; TNE and TCO2E are our worksheet labels. It is not official XML and cannot be submitted to the register. Generic current filing XML can use authorised BYO XSD; unsupported mapping leaves the independent business layer unexecuted.

The historical fictional fragment demonstrates only our independent rules; it omits official mandatory fields and uses fictional unit labels. Selecting 18.30 is an explicit user assertion; the shared namespace does not prove the package version. No claim that historical corrections are still accepted.

Two practical error guides

CBAM period and version mismatch · CBAM emission totals and units

EC archive · EC definitive regime · EC legal notice

Sources checked 6 November 2026. Choose the exact data scope and retain the source evidence behind quantities, periods and emissions for your reporting process.

Existing Pro / Team batch plans →