Welcome to Euraltis
A Predictable, Auditable Technical Process
Current supported CBAM Registry schema
Version-locked to the latest published XSD at the time of generation.
When the CBAM XSD schema is updated by authorities, Euraltis logic versions increment to process against the new schema. Prior logic versions remain accessible for audit and traceability.
At the core of Euraltis is a single design commitment: deterministic processing.
Step 1 — Structured Input
You upload CBAM data using the approved Euraltis Excel template.
The template structure accommodates only non-personal CBAM trade data fields, such as: - Commodity and CN codes - Quantities and units - Emissions values - Installation identifiers
Template fields correspond strictly to technical CBAM reporting requirements.
Step 2 — Technical Validation
Before XML generation, Euraltis performs machine-checkable validations only: - XSD schema structure checks - Field type and format validation - Internal technical consistency checks
Euraltis does not validate: - Emissions logic or calculations - CN code correctness - Regulatory thresholds - Cross-field semantic meaning
These remain the responsibility of you, the client.
Step 3 — XML Generation
When deterministic processing is possible: - XML is generated using version-locked transformation logic
- No human judgment is applied
- No values are inferred, corrected, or substituted
If deterministic processing is not possible, the XML is declined rather than guessed.
​Step 4 — Delivery & Traceability
Each transaction produces:
- The generated CBAM XML file
- A technical validation result (pass or fail)
- Clear diagnostics if generation fails
- Audit metadata including timestamp, logic version, and file hashes
​
This enables traceability without introducing interpretation risk.
Explicit Boundary
Euraltis determines only whether structured CBAM data can be transformed into technically valid XML.
It does not determine whether the data is correct, complete, or regulatorily acceptable.
