EU CBAM

Check CBAM records before you file

dVeracity checks EU CBAM import records and annual declarations against approved CBAM policy rules. It shows which inputs are missing and which provisions were and weren't checked, and keeps an audit record. Use it from your AI assistant or through the API.

Request CBAM accessSee what gets checked

Last reviewed 1 November 2026.

The first annual CBAM declaration, covering goods imported in 2026, is due by 30 September 2027, together with the surrender of CBAM certificates. European Commission

What gets checked

A single import record

Send one record, with fields such as CN code, goods category, quantity and unit, specific direct embedded emissions, installation country, production route and reporting period. It is evaluated against the approved CBAM policy. A CN code outside Annex I of the CBAM Regulation comes back as not applicable, not as a pass.

An annual declaration

Each declaration line is evaluated against the import record it summarises, which must already be stored in dVeracity. The declaration itself is then checked for:

  • the de minimis exemption (Article 2a and Annex VII of Regulation (EU) 2023/956),
  • the Article 6(1) 30 September deadline,
  • the annual total,
  • each line's quantity against its linked imports,
  • the import year,
  • duplicate customs references.

What you get back

  • A decision: passed, denied, unevaluable (inputs missing) or not applicable.
  • Per-check results, so you can see exactly which rule decided.
  • Missing inputs and remediation, telling you what to supply before you try again.
  • The policy version and hash that made the decision.
  • A coverage note listing provisions the policy does not encode.
  • A stored audit record you can retrieve later.

What a pass means, and what it doesn't

  • A pass means the encoded checks passed. The policy register lists every provision with its status, including the ones that are not encoded, so you can see the gap.
  • dVeracity does not verify your suppliers' emissions. It checks the records you provide against the policy rules.
  • dVeracity does not file anything in the CBAM registry. It doesn't replace your authorised CBAM declarant or an accredited verifier.

Where it runs

  • In AI assistants that support MCP, such as Claude, ChatGPT and Cursor, connect to https://api.dveracity.com/mcp and sign in.
  • Through the dVeracity API, for your own systems.

Example requests:

  • "Which regulatory policies can dVeracity run?"
  • "Check this CBAM import record against the approved CBAM policy and tell me what's missing."
  • "What does the CBAM policy check, and what doesn't it?"
  • "Evaluate our 2026 CBAM declaration before we file."

Access

CBAM checks are part of the VaaS (Verification as a Service) plan. dVeracity enables it for your organisation after a short conversation about your import volumes and data. Buying API credits does not enable it. Request access below; we reply within two business days.

Request CBAM access

Optional. Import volumes, timelines, or a request for a trial on sample data.

Questions

Do you file our CBAM declaration?

No. You or your indirect customs representative file in the CBAM registry. dVeracity checks the data first.

Is this a CBAM verification?

No. Checking records against policy rules is not the verification of actual emissions by an accredited verifier.

Which goods are covered?

Goods whose CN codes fall under Annex I of the CBAM Regulation, to the extent the approved policy encodes them. The policy register shows exactly what is encoded.

Can we try it first?

The free Explorer account includes the Open Footprint model and validation tools. CBAM checks need VaaS; mention in the form that you'd like a trial on sample data.

Where is our data stored?

See our Trust and Privacy pages.