Produce the file you submit
From ledger
to lodged.
An approved ledger isn’t a filing. Sustys writes the XSD-valid v23 XML the CBAM registry actually accepts, bundles the prep pack around it, and walks you through the upload — no hand-built XML, no rejected submission.
Almost-right doesn’t lodge
The registry doesn’t grade on effort.
The CBAM XML schema is strict and unforgiving — one malformed field, one unit out of place, and the submission bounces. A spreadsheet exported by hand is a rejection waiting to happen, days before a filing deadline.
v23
the current CBAM XML schema — XSD-valid or the registry rejects the file outright
3 artefacts
the prep pack: a PDF summary, the XLSX workings, and the submission XML
Annual
the definitive-period prep pack — a full year of approved lines, filed once
The file itself
The exact XML the registry accepts — sealed before you send it.
Every approved line becomes a node in the v23 schema: CN code, net mass, country of origin, and the direct and indirect embedded emissions. Sustys validates it against the XSD, then seals it ready to lodge.
- Schema-true
Built against the published v23 XSD — not an interpretation of it. The structure the registry expects, exactly.
- Validated first
The file is checked against the schema before you open the registry, so a malformed line is caught on your screen, not theirs.
- Carbon inside
Direct and indirect embedded emissions are written into every goods node — the € and the tCO₂e, in the file.
The annual prep pack
Three artefacts, one approved truth.
The XML is what you lodge — but the file alone won’t satisfy a reviewer or a future-you. Sustys produces the whole pack from the same approved ledger, so every figure ties out.
cbam_declaration_2026_v23.xml
The submission file itself — XSD-valid against schema v23, every line and its embedded emissions, ready to lodge.
declaration_summary.pdf
A human-readable summary of what you’re filing — totals in € and tCO₂e, per line, for sign-off and the file.
workings.xlsx
The full workings behind every figure — defaults, actuals, sources — so the number is never a black box.
Guided to lodged
The last mile, walked with you.
The hardest part of CBAM isn’t the maths — it’s the registry. Sustys takes you from an approved ledger to a lodged declaration without leaving you alone at the upload screen.
- 01
EXPORT
Generate the prep pack from your approved ledger — the XML, the summary, the workings, in one click.
- 02
CHECK
Sustys validates the XML against the v23 XSD before you ever open the registry. Errors are caught here, not there.
- 03
LODGE
Follow the guided upload into the CBAM Registry — field by field, with the file already in hand.
Built for the timeline
The definitive period is here — on the rail you built.
The transitional period (2023–2025) reported embedded emissions in XML; the definitive period — underway since 2026 — turns them into the CBAM certificates you buy and surrender, with sales opening February 2027 and the first annual declaration due September 2027. Sustys carries you across without re-platforming: the ledger stays, the export evolves with the schema.
Quarterly v23 XML reports of embedded emissions, XSD-valid, lodged in the Transitional Registry. No certificates — but the data discipline the definitive period now demands.
The obligation is financial: an annual declaration, with CBAM certificates bought and surrendered against verified embedded emissions. Certificate sales open February 2027 and the first declaration falls due September 2027 — the proven actuals you build now are what keep that bill honest.
The file has company
What goes in, and who else files.
CBAM-as-a-Service
Produce a file that passes validation.
Join the pilot beta to turn your first approved ledger into an XSD-valid v23 submission — prep pack and guided upload included.