For your role

CBAM Pulse for customs brokers and advisers

CBAM (Carbon Border Adjustment Mechanism) workflow for customs brokers: organise client CN context, importer records, annual mass, and handoffs; not legal, tax, or customs advice.

Last updated: 2026-08-11 · Sources: Regulation (EU) 2023/956 (consolidated text) · Regulation (EU) 2025/2083 · EC DG TAXUD — Carbon Border Adjustment Mechanism · Commission Implementing Regulation (EU) 2025/2547 — emissions calculation · Commission Implementing Regulation (EU) 2025/2546 — verification

Who this is for

Customs brokers, and the ESG, tax, and trade advisers who support EU importers — professionals handling many clients and product lines who need quick, source-linked answers and material they can share with clients.

First questions to answer

• Which of my clients' goods are in CBAM scope, and under which CN codes?
• How do I keep scope, thresholds, and deadlines straight across many clients at once?
• How do I give clients a clear, source-linked explanation rather than a dense legal citation?
• How do I stay ahead of regulatory changes so I can brief clients early?
• Where do I point a client who is just starting to prepare?

Recommended starting path

1. 1. Screen clients' goods

   Run CN codes across a client portfolio to see what is in scope, by sector, with the exclusions flagged.

2. 2. Frame the picture by sector

   Use the sector overviews to explain coverage for a client's specific materials.

3. 3. Share a starting checklist

   Hand clients the readiness checklist as a structured preparation aid.

4. 4. Track the dates

   Keep the 2026–2027 milestones in one place across every client.

5. 5. Follow the feed

   Watch the updates feed so you can brief clients as soon as something changes.

Define the broker engagement before collecting CBAM data

A broker workflow starts with a clear client intake: importer entity, representation model, service boundary, goods population, customs-data source, named client decision-makers, and an escalation path for questions outside the broker's agreed role.

Create one engagement header per importer legal entity and import year. Record the EORI or internal client identifier used in the customs workflow, the relevant representation facts as provided by the client, the broker team member responsible for the file, and the client contacts for customs, procurement, sustainability, and finance. State what the broker is preparing: for example, a customs-data extract, a CN-code inventory, a source-linked screening, or a handoff pack. Do not let a general request for CBAM help silently expand into an assurance, verification, filing, or legal-opinion engagement.

Agree the handoff format and correction route at intake. The client should know which fields come from customs declarations, which are enriched by the broker, which are supplied by the client or producer, and which remain unresolved. Record whether the broker is expected to flag anomalies, coordinate supplier requests, or only provide a data extract. CBAM Pulse can give the team a consistent preparation structure, but it does not decide who holds a regulated role, interpret a representation contract, or determine whether the broker or client has satisfied an obligation.

• Client header: importer entity, year, representation facts, contacts, agreed deliverable, and review dates.
• Data boundary: customs-origin fields, broker annotations, client inputs, supplier inputs, and unresolved questions.
• Service boundary: preparation tasks included, decisions excluded, escalation recipient, and acceptance route for corrections.

Create a repeatable client intake and triage queue

The best first deliverable is a structured triage queue, not a blanket conclusion. It identifies the imports to inspect, the source of each field, obvious data gaps, and the next owner for every exception.

Ask for the client's legal entity, import period, customs-declaration population, known product families, supplier list, and any existing scope or classification work. Confirm the extract format, date range, amendment treatment, cancellations, and whether net mass is consistently populated. Keep clients isolated in both storage and working views. Reusable templates are useful, but copying rows, notes, or evidence between clients without a controlled reason creates provenance and confidentiality risk. A standard intake should make the differences between clients easier to see, not erase them.

Triage rows into clear operational states: ready for scope screening, missing CN code, missing or inconsistent net mass, product description mismatch, classification question, client confirmation needed, supplier context needed, and outside the current agreed population. Use severity labels based on workflow impact rather than invented regulatory risk scores. A missing code blocks scope screening; an unrecognisable description may require client clarification; a new supplier may trigger a later data request. The queue helps the broker route work. It does not turn a data-quality label into a customs or legal conclusion.

• Validate population completeness and extract logic before assessing individual goods rows.
• Separate missing data from disputed data; they require different client conversations.
• Keep every exception attached to the declaration reference, client owner, broker owner, and next action.

Handle CN codes as a classification-review ledger

Brokers should preserve the classification basis and review trail behind each code while keeping CBAM scope screening distinct from the customs classification decision itself.

For each recurring goods line, retain the code used, declaration references, description, product or specification reference, origin, reviewer, date, and basis documents available in the broker's normal process. Flag inconsistent codes used for apparently similar goods, codes that changed during the year, and codes supplied only in a commercial spreadsheet without a customs source. A CBAM lookup can then compare that known code with a reviewed current-scope snapshot. The lookup result is useful for triage, but it does not validate the code or issue a binding classification result.

When a code is uncertain, describe the issue precisely for the client: which products or entries are affected, what conflicting facts exist, what documentation is missing, and which route the client uses for a classification decision. Preserve the prior code and affected periods when a correction is made. Keep proposal-stage product expansion out of the current-scope field; it can sit in a watch column with its proposal status. This prevents a future-policy discussion from contaminating current customs instructions or client reporting preparation.

• Screening result answers whether the supplied code matches the reviewed CBAM scope snapshot.
• Classification ledger records why a code was used, what changed, and who reviewed the customs question.
• Escalation packet contains affected entries, product evidence, competing codes, exact question, and requested reviewer.

Reconcile customs data before the client handoff

A reliable customs-data handoff explains the population, transformations, exclusions, exceptions, and reconciliation totals so the importer can connect broker output to its own annual preparation register.

Document how the extract was built. State the source system, import period, importer identifier, declaration states included, treatment of amendments and cancellations, quantity units, net-mass conversions if any, and fields enriched after extraction. Preserve source values alongside normalised values. If the broker aggregates entries for usability, keep a route back to the underlying declaration references and state the grouping keys. Unexplained transformations create more work later because the importer cannot tell whether a difference is a real customs correction or a spreadsheet convenience.

Run factual quality checks before handoff: duplicate references, missing codes, zero or absent mass, impossible date ranges, mismatched importer identifiers, unexpected units, and rows changed after the original extract. Reconcile row counts and mass totals at each transformation stage without presenting those checks as a determination of CBAM treatment. Send exceptions in a separate schedule with owner and status. The broker's value is a cleaner, traceable customs dataset and a shorter question list, not a claim that the client's annual CBAM record is complete.

• Population note: systems, filters, dates, entities, declaration states, and known limitations.
• Transformation note: renamed fields, normalised units, controlled aggregations, enrichments, and retained source values.
• Reconciliation note: source rows, output rows, excluded rows, amendments, duplicate handling, and unresolved differences.

Coordinate the customs-to-supplier data handoff

The broker can connect customs rows to the client's supplier workflow by passing accurate goods context and visible gaps. The producer, importer, adviser, and verifier still retain their separate roles in producing and reviewing emissions information.

Build a supplier-request seed from customs facts the broker can support: importer, import year, CN code used, goods description, origin, supplier or exporter shown in the available records, shipment references, and affected mass. Ask the client to confirm the commercial contact and producing installation because those details may not be available or reliable in a customs entry. When several entries appear to relate to one product and site, provide the mapping logic but do not assume the sales entity is the operator of the production installation.

Track the handoff rather than claiming ownership of the supplier's answer. Record when the seed data was sent to the client, what the client corrected, whether a supplier request was opened, and which customs rows are affected by a partial response. If supplier material reveals a description or origin inconsistency, route it back to the classification or customs-data queue. CBAM Pulse can help organise request drafts and evidence references. It does not send the public draft, collect supplier files through that tool, calculate the producer's emissions, or decide whether received material is sufficient.

• Broker contributes customs provenance, entry references, known code, description, origin, quantity, and anomaly notes.
• Client contributes commercial ownership, producing-site mapping, supplier contact, engagement decisions, and acceptance of corrections.
• Specialists address emissions methodology, accredited verification, situation-specific interpretation, and official questions.

Design a client-facing exception and escalation report

A useful broker report is an exception-led handoff: facts supplied, checks performed, rows needing client action, rows needing customs review, supplier-data dependencies, and questions routed outside the broker service boundary.

Lead with a concise scope note describing the client, period, dataset, and agreed work. Then present factual coverage: rows received, rows screened, rows blocked by missing data, classification-review items, data-reconciliation differences, and supplier-context gaps. Avoid a green status that implies acceptance. Use neutral states such as recorded, screened against current source, awaiting client confirmation, under classification review, referred to adviser, and unresolved. Every exception should link back to the underlying customs references and show the evidence or reason behind the status.

Make escalation purposeful. A question for the client may ask which legal entity owns an import or which supplier contact is correct. A customs-review question may include competing codes and product specifications. An adviser or NCA question should identify the specific rule or situation needing interpretation without the broker answering it in the report. An accredited-verifier question belongs to the independent verification path, not a software checklist. This structure protects the broker-client relationship because it shows useful preparation work without quietly assuming a role the engagement did not cover.

• Client action list: missing facts, owner, due date, affected entries, and consequence for the preparation workflow.
• Broker correction list: extract defect, transformation issue, classification record update, or reconciliation task.
• External review list: exact question, supporting facts, documents available, requested reviewer, and current status.

Standardise across clients without blending client responsibility

Brokers can standardise intake fields, quality checks, statuses, and handoff formats across a portfolio. They should not reuse one client's decisions, supplier evidence, or assumptions as if they automatically apply to another.

Maintain a controlled template with field definitions, status meanings, source-review dates, and change history. Train the team to distinguish customs-source facts from client assertions, broker annotations, software lookups, and professional conclusions. Use peer review for high-impact transformations and classification exceptions. Measure workflow health with operational signals such as unassigned exceptions, stale client questions, unreconciled extracts, or rows lacking provenance. Do not invent a readiness score or rank clients by an unsupported model.

At engagement close, provide the agreed export or handoff pack, explain limitations, record client corrections, and retain information according to the broker's approved policies. CBAM Pulse can support source-linked screening and preparation records, but the current product is not a broker filing platform, customs declaration service, client approval system, or multi-client adviser decision engine. The importer, its qualified advisers, accredited verifier where relevant, and National Competent Authority remain the appropriate parties for decisions beyond the software preparation layer.

• Reusable: data dictionary, intake questions, exception types, review steps, and handoff structure.
• Client-specific: importer facts, customs population, classification basis, supplier records, decisions, and evidence.
• Never portable by assumption: another client's code outcome, emissions basis, authority response, or verifier opinion.

Questions customs brokers and advisers ask about CBAM