Every CBAM tool can calculate emissions and produce a report. The part that decides whether the number survives an audit happens earlier — inside a factory, usually in India, often on paper. This page sets out the six jobs any CBAM software has to do, where reporting platforms tend to stop, and the ten questions worth asking before you sign anything.
Products in this category differ far more than their marketing suggests. Most are strong on steps three and five and thin on step two — which is unfortunate, because step two determines everything downstream of it.
Match every line of your import or export book to the CN codes CBAM actually covers. Chapters 72, 73 and 76 carry most of the traffic, and the boundary is not intuitive — a fabricated structural assembly is in scope while much of the machinery built from it is not.
Pull real production, fuel, electricity and precursor data from the plant that actually made the goods. This is the step that decides whether the rest of the number is real, and it is the step furthest from the software.
Apply the EU methodology per production process — direct and indirect emissions, precursor mass balance, and the allocation rules that decide how a shared furnace is split across products.
Document the methodology behind the number. This is the artifact an accredited verifier audits. A figure without a Monitoring Plan behind it cannot survive verification, however well it is calculated.
Emit the filing in the exact structure the EU registry expects, in the declarant’s name, with the evidence trail attached.
Hold up when an accredited verifier asks where a number came from. Verification is the point at which the previous five steps are tested, and the first annual declaration covering 2026 is due 30 September 2027.
“CBAM software” describes two distinct jobs. Buying the wrong one is the most common and most expensive mistake in this category.
Strong at workflow and filing. Its weak point is the one input it does not control: whether the supplier ever sends real data.
This is where the number is actually made. It is also the side with the least software built for it, because the buyer of the software is rarely the party who feels the cost.
Most CBAM platforms are, at the data layer, a structured request sent to a supplier. If the supplier fills it in accurately, the software works. If they do not, the software cannot tell — and the declarant quietly falls back to default values.
The reason this happens so often with Indian suppliers is not reluctance. It is that the request assumes a shape the data does not have. An installation in Ludhiana or Rajkot holds its production reality in electricity bills, fuel purchase invoices, weighbridge slips, furnace logs and a production register — frequently on paper, frequently in a regional language, and never organised by EU production process.
Turning that into a monitored emissions figure is not data entry. It is a mapping exercise that requires knowing both the EU methodology and how an Indian secondary steel plant actually runs. Asking the supplier to do it themselves, through a portal, is asking the least-equipped party in the chain to do the hardest part of the work.
A handful of India-based providers do offer collection at the installation rather than a self-reporting form. It is worth establishing which model you are buying, because the two produce very different numbers from the same factory.
Including us. Any vendor worth buying from will answer all ten without hesitating, and the answers will differ enough to make the choice obvious.
If the answer is "the supplier enters it", the platform is a form. The number is only as good as whoever typed it in.
A verifier audits the methodology. Software that outputs a figure without the documented method behind it leaves the hardest artifact to you.
Only the Authorised CBAM Declarant can file. Software that files "for you" is either acting as your declarant or is not filing at all — know which.
This is the normal case, not the edge case. Ask what the platform does on day 30 of supplier silence.
A large share of Indian MSME suppliers keep production data on paper. A CSV upload requirement is a wall, not a workflow.
Generic international factors will overstate an Indian installation’s indirect emissions, and the exporter pays for that error through the buyer’s certificate cost.
Downstream articles inherit the embedded emissions of the steel or aluminium they were made from. Mass-balance allocation is where most calculations quietly go wrong.
Ask to see a real evidence pack that an accredited verifier has actually accepted.
The honest comparison is not software price versus software price. It is software cost versus the certificate cost of staying on default values.
A portal that transcribes your input carries no responsibility for it. Establish where liability sits before you file.
CarbonSettle runs the calculation and reporting layer you would expect — CN-code scoping, embedded-emissions calculation to the EU methodology, Monitoring Plan, declaration output and evidence trail. What we add is step two: our team collects the underlying data at the installation itself, in the language the plant runs in, from whatever form the records take.
We coordinate accredited verifiers; we never verify our own work, because the independence requirements do not allow it and a number that cannot survive an independent audit is worth nothing to the buyer who has to file it.
CBAM software is a tool that helps a company meet its obligations under the EU Carbon Border Adjustment Mechanism: identifying which goods are in scope, collecting emissions data from the installations that produced them, calculating embedded emissions using the EU methodology, and producing the declaration and supporting evidence. Most products on the market concentrate on the calculation and reporting steps and rely on suppliers to provide the underlying data.
Both, but they are different products solving different problems. Importer-side software manages the declarant’s obligation: scoping imports, chasing suppliers, aggregating data and filing. Exporter-side software addresses the supplier’s problem: producing a defensible emissions figure for their own installation, with a Monitoring Plan behind it, in the format their EU customer needs. A tool built for one rarely does the other well.
No. Under the EU rules verification must be carried out by an independent accredited verifier, and independence requirements prevent the party that prepared the data from also verifying it. Software can make a submission verifier-ready; it cannot verify it. Treat any claim to "verify" your emissions as a reason to ask exactly what is meant.
Published pricing in this category generally starts in the low thousands of euros per year for importer-side reporting platforms, rising with the number of suppliers and CN codes in scope. The more useful comparison is against the alternative: on default values, the certificate cost attached to a single 1,000-tonne consignment of Indian steel is typically far larger than any software licence, which is why the accuracy of the underlying data usually matters more than the tool’s price.
Because the hard part happens before the software starts. An Indian installation’s data usually exists as electricity bills, fuel invoices, weighbridge slips and production registers — often on paper, often in a regional language, and rarely mapped to EU production processes. A platform that expects a structured upload puts that translation work back on the supplier, who has no reason and no expertise to do it. That is why data arrives late, arrives wrong, or does not arrive at all, and the importer falls back to default values.
The declarant falls back to default values, which are set deliberately conservative so that they are never cheaper than reporting real data. The gap is paid through CBAM certificates, and in practice it is passed back to the supplier through price. Using verified actual data is not a compliance nicety; it is the commercial reason the exercise exists.
We will answer every one of them about our own product, in writing, before you commit to anything.