CBAM Declaration
Draft and validate a CBAM declaration package for EU importers filing under the Carbon Border Adjustment Mechanism (EU Regulation 2023/956). The EU has no submission API: this skill prepares and checks the package against the EU's own schema, and the user downloads it and uploads it themselves on the CBAM Registry portal. The transitional quarterly report period ended in 2025; the definitive period's annual declaration module is scheduled to open in 2027.
Developed jointly by WeCarbon and Siemens SiTANJI
Draft and validate a CBAM declaration package for EU importers filing under the Carbon Border Adjustment Mechanism (EU Regulation 2023/956). The EU has no submission API: this skil…
What you'll get
XML and ZIP package checked against the EC's own CBAM XSD (version 18.30), with a validation report, for you to download and upload yourself
Based on official standards
How it works
Commercial invoices, supplier data, production records, in any format or language.
The AI guides you through missing data, validates inputs, and clarifies methodology in real time.
Each field cites the source document it came from, in the conversation. Edit, approve, or re-upload as needed.
Download the official output, ready to submit to the regulator.
Frequently asked questions
When is the next CBAM declaration due?
The transitional quarterly reports ended with the 2025 Q4 period, so there is no quarterly filing left to make. The definitive period's annual declaration module is scheduled to open in 2027, with a first deadline of 30 September 2027; the EU had not yet published that module's format as of late 2026.
Who is legally responsible for filing: the importer or the exporter?
The EU importer (or their indirect customs representative under role 02) is legally responsible. Non-EU exporters have no direct obligation under CBAM, but in practice most of the data collection burden falls on them because the importer needs production-level emission data only the supplier has.
Do I need third-party verified emission data?
During the transitional phase (October 2023 to December 2025), verification was not required and EU default values could be used when actual data was unavailable. From the definitive period (1 January 2026 onward), actual emissions data verified by an EU-accredited third-party verifier becomes mandatory for most goods.
Which products are covered by CBAM?
Six sectors currently fall under CBAM: iron and steel, aluminum, cement, fertilizers, hydrogen, and electricity. Downstream products, chemicals, and polymers are expected to be added in future phases.
What happens if a filing is late, incomplete or incorrect?
Penalties for late, incomplete, or inaccurate reports range from 10 to 50 EUR per tonne of undeclared embedded emissions. Falsified data can trigger fines up to three times the CBAM certificate price, and repeat or severe infractions can lead to loss of import authorization.
What format does Formist produce, and who submits it to the EU?
An XML file validated against the EU's own CBAM XSD (version 18.30), wrapped in a ZIP with a validation report. There is no EU submission API, so Formist never submits anything on your behalf: you download the package and upload it yourself, logged into the CBAM Registry portal with your own EU Login identity.
Start your CBAM Declaration in minutes
Skip months of manual form-filling. Formist handles the methodology so you can focus on the real work.
Start for freeRelated skills
Calculate embedded emissions and CBAM certificate costs for goods imported into the EU under the Carbon Border Adjustment Mechanism (EU Regulation 2023/956). Use this skill whenever the user mentions CBAM, carbon border adjustment, embedded emissions, CBAM certificate, CBAM declaration, CBAM reporting, EU carbon border tax, or needs to calculate specific embedded emissions for cement, iron, steel, aluminium, fertilisers, electricity, or hydrogen imports into the EU. Also trigger when the user asks about precursor tracking, CBAM XML generation, CBAM Registry communication template, IR 2023/1773, IR 2025/2547, default values for CBAM, or carbon price deduction for China ETS / origin-country carbon pricing.
Extract every structured field from an uploaded Bill of Lading (B/L), Sea Waybill, or house/master B/L pair (photo, scan, PDF, Word, or Excel) into a standardized JSON record, structured to match the DCSA (Digital Container Shipping Association) Bill of Lading Standard 3.0's current published data model wherever the source document's content maps onto it. A Bill of Lading is a trade/shipping document (carrier receipt, evidence of the contract of carriage, and for a negotiable B/L, a document of title), NOT a regulatory filing: this skill extracts it as INPUT EVIDENCE for downstream filings (a CBAM declaration, a customs entry, a letter-of-credit check). It does not itself submit anything anywhere, and it does not validate dangerous-goods compliance. Use this skill whenever the user mentions Bill of Lading, B/L, Sea Waybill, house bill / master bill, parse my shipping documents, or needs shipment particulars (shipper, consignee, vessel/voyage, container, cargo description, weight) pulled out of a document into structured data.