The first CBAM verifiers are expected to receive their accreditation around September 2026, once the EU's national accreditation bodies begin publishing the list on the Commission's own CBAM page. Once that list is live, the volume of actual engagements starts — and volume is exactly where a PDF-and-spreadsheet workflow stops scaling.
A verification engagement's cost isn't really the day rate. It's what a Lead Auditor spends the first day or two doing before any real verification work starts: reconciling a Specific Embedded Emissions calculation against an electricity bill that was emailed as a photo, tracing a precursor figure back to a supplier spreadsheet that uses a different unit convention than the one in front of it, confirming that the version of the monitoring methodology described in a Word document actually matches what was used to produce the numbers being reviewed. None of that is verification. It's data archaeology that has to happen before verification can begin — and it's the same archaeology, repeated from scratch, at every single site.
That cost doesn't show up as a line item. It shows up as fewer engagements per quarter, more time between accreditation and revenue, and — for the installation being audited — a longer gap between "we submitted our data" and "we have a verified opinion."
EnaQt CBAM Verify treats "verifier" as an actual role in the platform — not a generic external reviewer account, and not a one-time data export. A company invites a verifier by email, the same way they'd invite anyone onto an installation; that verifier logs in as themselves, and the same access carries across every client installation that invites them. There's no separate login to manage per engagement, and no one-company restriction to work around for a body that legitimately needs access across many clients.
Once inside, a verifier can run the actual engagement in the platform: risk assessment, materiality-based sampling, findings, and the formal opinion — structured against ISO 14064-3's own stages, not a spreadsheet template standing in for a workflow. The Monitoring Plan is one document you can view and export, not a self-written appendix assembled the week before the site visit. And supporting evidence is attached directly to the specific figure it substantiates, visible on the same screen as the number itself — not a folder of scans you have to cross-reference by hand.
What that changes in practice: the reconciliation work — matching a number to its source, confirming a methodology was applied consistently, spotting a gap before it becomes a finding — can start before you board a flight, not after you land. The mandatory physical site visit stays exactly what it should be: confirming what's real on the ground, not the first moment you see the data at all.
We'd rather be precise than impressive. A verifier's access today is scoped to the installations that invite them, is read-only on the underlying monthly activity data, and doesn't yet expose the full change-history audit log the way it's exposed internally to a company's own admins — that's on our roadmap, not in the product today. What's real, right now, is a working login that runs the verification workflow itself and puts evidence next to the number it supports. That's the part that actually saves a day on-site, and it's the part we'll show you directly rather than describe in the abstract.
If you're preparing for accreditation, we'd rather show you the workflow on a real installation than describe it on a page.
Request a Demo For EU Verifiers & Importers