For your role

CBAM Pulse for ESG, tax, and trade advisers

CBAM (Carbon Border Adjustment Mechanism) workflow for advisers: organise goods, supplier evidence, calculation context, verification status, and gaps; not legal, tax, or customs advice.

Last updated: 2026-08-11 · Sources: Regulation (EU) 2023/956 (consolidated text) · Commission Implementing Regulation (EU) 2025/2546 — verification · Commission Implementing Regulation (EU) 2025/2547 — emissions calculation · Commission Delegated Regulation (EU) 2025/2551 — verifier accreditation · European Commission — Verification of CBAM emissions

Who this is for

ESG, tax, trade, and sustainability advisers helping EU importers organise supplier records, calculation context, evidence references, accredited-verification status, and open questions while keeping professional judgement outside the software.

First questions to answer

• Which supplier, operator, installation, goods, production process, and reporting period does each emissions figure cover?
• Is each figure supplier-reported, based on an official default, calculated as actual emissions, or accompanied by an accredited verification report?
• Are the monitoring plan, emissions report, method, source records, and revisions referenced together?
• Which gaps need an accredited verifier, qualified adviser, or National Competent Authority rather than a software status?

Recommended starting path

1. 1. Map the supplier evidence journey

   Separate the emissions figure, calculation context, supporting references, and verification status for each client goods line.

2. 2. Structure the evidence set

   Use the public checklist to make source records and open gaps visible without treating checked boxes as completeness.

3. 3. Understand accredited verification

   Review when actual emissions require verification, who grants accreditation, and what reasonable assurance means.

4. 4. Organise continuing preparation

   Use the workspace to organise client preparation records and gaps; CBAM Pulse does not verify them or issue an adviser conclusion.

5. 5. Follow official changes

   Track source-linked updates while checking situation-specific conclusions through the appropriate professional and official channels.

Define the adviser review question and evidence perimeter

An adviser engagement becomes more useful when each workstream states the client entity, import period, goods population, decision requested, records available, records excluded, and the professional or official boundary that applies.

Open with a factual client profile rather than a conclusion. Record the importing entity, responsible contacts, import year, sectors, customs-data source, supplier population, current internal owners, and the client's stated concerns. Translate a broad request such as review our CBAM position into bounded questions: data population review, classification-issue inventory, supplier-evidence preparation, emissions-basis review, cost-planning assumptions, verification-path preparation, or an authority-facing question. The engagement letter and the adviser's professional framework remain outside the software and govern the actual service.

Build an evidence perimeter for every question. List the customs extracts, goods master, contracts, supplier replies, monitoring and calculation references, emissions reports, verification materials, internal assumptions, and official sources available. Also list what was requested but not received and what was not reviewed. A preparation workspace can hold metadata and open gaps, but it does not establish that the set is complete or legally sufficient. That distinction protects the client from reading a neat dashboard as an opinion and gives the adviser a defensible record of the material actually considered.

• Question: exact client issue, affected entity and period, requested output, and decision owner.
• Perimeter: records received, versions, provenance, exclusions, missing items, and review cut-off date.
• Boundary: matters for customs specialists, emissions specialists, accredited verifiers, or the National Competent Authority.

Run a provenance-first evidence review

Review starts by asking what each record is, who produced it, which goods and installation it covers, which period and method it uses, and what claim it appears to support before judging its relevance.

Create an evidence index with a stable reference, document type, provider, received date, version, language, period, goods, supplier, operator, installation, production process, and related data field. Keep the original reference and any translated or summarised working note distinct. If the client provides a spreadsheet assembled from several sources, ask for row-level provenance or mark the provenance gap. Avoid treating a folder name, file presence, or client label as proof of content. The review record should let another professional locate the source and understand why it entered the workstream.

Then connect evidence to claims cautiously. A customs entry may support imported quantity and code used; a supplier response may support that the supplier reported a value; a monitoring record may describe a method; a verification report may contain an opinion within its scope. One record does not automatically support every adjacent fact. Record conflicts and superseded versions rather than choosing silently. CBAM Pulse can store evidence-reference metadata and expose gaps, but it does not read the underlying material, authenticate it, assess sufficiency, or issue the adviser's conclusion.

• Identity test: provider, version, date, language, goods, installation, process, period, and source location.
• Support test: exact fact or assertion the record appears to support, with limitations and conflicts.
• Status test: received, indexed, reviewed, clarification requested, superseded, referred onward, or unresolved.

Separate data states before discussing verification

Supplier-reported information, an official default, a calculated actual-emissions figure, evidence supporting that calculation, and an accredited verifier's opinion are distinct states. Adviser workflow should preserve those distinctions at row level.

For each emissions figure, record the value, unit, goods, operator, installation, process, reporting period, data basis, method reference, report version, precursor context where relevant, and source records. If the basis is unclear, mark it unknown rather than inferring actual or default from the number's format. If part of a complex calculation uses a different basis, keep component-level status visible. An adviser can review and explain the evidence within the engagement, but the software should not promote the row to verified because a consultant has looked at it.

Where the applicable actual-emissions route calls for accredited verification, inspect the verification report, opinion, verifier identity, accreditation information, activity scope, goods and installation scope, period, findings, and unresolved qualifications. The presence of a report is not the same as a satisfactory opinion, and a satisfactory opinion is not approval of the client's entire CBAM position. Accreditation comes through the competent accreditation framework, not from the client, adviser, supplier, or CBAM Pulse. Keep expected or announced operational timing separate from a verifier's published status at the time relevant to the engagement.

• Data origin: supplier-reported, official source, calculated actual emissions, mixed basis, or unknown.
• Evidence state: references present, reviewed, conflicting, incomplete, superseded, or sent for specialist review.
• Verification state: no report recorded, report received, scope under review, opinion recorded, or issue requiring verifier clarification.

Prepare the client for verifier engagement without pre-verifying

Adviser preparation can organise the installation, monitoring, calculation, controls, evidence, contacts, versions, and open issues a verifier may need. It should not predict the opinion or present adviser review as independent verification.

Build a verifier-preparation index around the producing operator and installation. Connect the relevant goods and production processes, reporting period, monitoring plan, emissions report, calculation workpapers, source records, data systems, responsible contacts, changes since the prior version, and known control issues. Identify where information sits with the importer, supplier, operator, or another party. If access, language, site, or document-availability constraints exist, make them visible early so the client and verifier can plan through the proper engagement.

Use a pre-engagement gap list that describes facts rather than outcomes. Examples include missing installation identifier, report period mismatch, unsupported unit conversion, unclear precursor source, absent method reference, unresolved correction, or verifier accreditation scope not yet checked. Do not call the set verification-ready or present the gap list as exhaustive. The accredited verifier designs and performs the independent work, applies the applicable assurance and materiality framework, determines evidence needs, handles site-visit questions, and issues the verification report. CBAM Pulse and the adviser-preparation workflow do none of those things automatically.

• Index the operator, installation, processes, goods, periods, plans, reports, systems, controls, and contacts.
• List known changes, judgement areas, data limitations, access constraints, and unresolved corrections.
• Let the accredited verifier define the verification plan, evidence requests, findings, and opinion.

Write client deliverables with layered confidence

A strong adviser deliverable distinguishes sourced fact, client representation, software output, adviser analysis, unresolved issue, and official or verifier decision. Readers should never have to guess which layer a sentence belongs to.

Use a finding structure that names the affected entity, goods or process, period, evidence reviewed, factual observation, interpretation or analysis if within scope, limitation, and recommended next review step. Cite the current official source for legal or regulatory statements and date the research cut-off. Where a proposal is relevant to planning, label it as proposal-stage and separate it from the current-law section. Do not convert political announcements, consultation material, or draft text into adopted requirements. If the source position changed after the client's initial memo, preserve the earlier source date and issue a controlled update.

Avoid broad labels that imply an official or complete outcome. A client may need a concise executive summary, but compression should not erase uncertainty or actor boundaries. State what the software calculated from which inputs and what the adviser independently reviewed. State which matters remain for the customs process, accredited verifier, or National Competent Authority. This layered style is commercially honest: it demonstrates the adviser's real work and judgement without borrowing authority from software, the Commission, an accreditation body, or a verifier.

• Fact layer: source, date, effective period, client record, and observed data state.
• Analysis layer: adviser reasoning within the engagement, assumptions, limitations, and alternatives considered.
• Decision layer: client action, customs determination, verifier opinion, accreditation status, or authority response kept separately attributed.

Manage multi-client work without cross-client shortcuts

Advisers can standardise methodology, intake, evidence indexes, issue taxonomies, and review gates. They cannot assume that one client's classifications, supplier figures, official response, or verification outcome applies to another.

Create controlled templates for client profile, import population, evidence index, supplier-data status, issue log, source ledger, review notes, and deliverable sign-off. Version the template and explain status meanings. Keep client workspaces, documents, exports, and communications segregated according to the firm's approved controls. When reusing a public official source, re-check its current status and applicability in the new engagement. When a technical issue resembles an earlier case, reuse the question framework, not the prior client's confidential facts or outcome.

Use portfolio views for operational management: work awaiting client data, evidence-review backlog, source refresh due, unresolved verifier questions, and deliverables awaiting partner review. Do not create unsupported risk or readiness scores. The current CBAM Pulse product can support one-organisation preparation and public adviser workflows, but it does not yet claim a full adviser multi-client tenancy, client-scoped assurance system, or professional sign-off engine. Firms should use their approved engagement, confidentiality, access, and retention systems for client work until a suitable reviewed workflow exists.

• Reusable method: definitions, intake sequence, source-check routine, evidence fields, issue types, and review gates.
• Client-owned record: customs population, supplier data, evidence, assumptions, advice, communications, and decisions.
• Portfolio management: workload and dependency states only, not a substitute for engagement-level professional review.

Close the review with an explicit actor map

The closing pack should identify who owns each remaining action and which actor can make each kind of decision: client, customs professional, qualified adviser, accredited verifier, accreditation body, or National Competent Authority.

Summarise the engagement question, material reviewed, source cut-off, findings, assumptions, limitations, and unresolved items. For every open point, identify the affected record, why it matters to the workflow, information needed, client owner, professional reviewer, and target date. Distinguish a request for more supplier evidence from a request for the verifier's assessment, and distinguish a customs-classification question from a general evidence-organisation task. Preserve draft, review, and final versions of the deliverable under the firm's own controls.

State the software boundary plainly. CBAM Pulse helps organise source-linked public information, deterministic user-input tools, supplier-request drafts, evidence-reference metadata, open gaps, and preparation summaries. It does not provide the adviser's professional opinion, decide legal or customs questions, authenticate evidence, verify actual emissions, grant accreditation, predict a verifier outcome, communicate with the National Competent Authority, or file through the CBAM Registry. The clear actor map is not a disclaimer afterthought; it is part of a trustworthy client deliverable.

• Client owns factual confirmations, internal decisions, supplier engagement, and use of the deliverable.
• Adviser owns the agreed professional analysis and its stated scope, evidence perimeter, limitations, and review controls.
• Verifier, accreditation body, customs process, and authority retain the independent or official decisions assigned to them.

Questions esg, tax, and trade advisers ask about CBAM