CBAM Certificate Ledger for Authorised Declarants

Analysis

CBAM Certificate Ledger for Authorised Declarants

Thesis

Build a narrow CBAM operations workspace for indirect customs representatives and midsize EU importers that treats CBAM as a regulated declarant-liability and certificate-inventory problem, not just a supplier-emissions data collection problem. The wedge is: “who is the authorised declarant, what certificate exposure sits on whose account, which client/import file caused it, and what action is due before the quarterly buffer / annual surrender / repurchase / cancellation deadlines?”

Classification

opportunity / idea_filter. The pain is regulatory, deadline-driven, and attached to cash exposure. The product is monetizable if sold to customs representatives, freight forwarders, trade-compliance teams, and finance/compliance owners at midsize importers handling CBAM goods.

ICP

Primary ICP: EU indirect customs representatives, customs brokers, and freight forwarders deciding whether to offer authorised-CBAM-declarant service for clients, especially where non-EU importers cannot practically act without an EU indirect representative.

Secondary ICP: midsize EU importers above the CBAM mass threshold that import iron/steel, aluminium, cement, fertilisers, hydrogen, or electricity and do not want a full enterprise ESG platform just to stay import-ready.

Economic buyer: head of customs/compliance, customs brokerage owner, trade operations lead, or finance controller with CBAM cash-planning responsibility.

Pain evidence

The official regime creates an operations problem with legal status, deadlines, and money movement:

• The European Commission says importers of CBAM goods, or their indirect customs representatives, are urged to apply for authorised CBAM declarant status; EU importers or indirect representatives importing more than 50 tonnes of CBAM goods must apply, buy certificates, declare embedded emissions, and surrender certificates.
• The CBAM Registry and Reporting page says the Authorisation Management Module has allowed importers and indirect customs representatives to apply for authorised declarant status since 31 March 2025 in the Member State of establishment, independently of where goods are imported.
• Regulation (EU) 2023/956 Article 5 makes the representative handoff explicit: if an EU importer appoints an indirect customs representative and the representative agrees to act as authorised CBAM declarant, the representative submits the authorisation application; for non-EU importers, the indirect customs representative submits.
• Article 6 requires each authorised declarant to submit an annual CBAM declaration by 31 May, first in 2027 for 2026, including imported quantities, verified embedded emissions, and total certificates to surrender.
• Article 22 creates a true ledger requirement: the declarant must surrender certificates via the registry and must ensure that, at the end of each quarter, its account holds at least 80% of embedded emissions for goods imported since the start of the year, using default values.
• Article 20 requires certificate sale records with unique certificate ID, price, sale date, and account transfer into the CBAM registry. Article 23 caps repurchase of excess certificates at one-third of prior-year purchases and requires repurchase request by 30 June. Article 24 cancels old certificates on 1 July without compensation.
• Article 26 makes the downside concrete: failure to surrender certificates creates penalty exposure per missing certificate, and unauthorised imports face three to five times that penalty per certificate; paying the penalty does not eliminate the surrender obligation.
• Advisory sources focused on customs representatives are already using “danger and opportunity” language: Paradigmes Avocats warns that customs representatives acting as authorised CBAM declarants become the front-line obligor, and CustomsClear highlights certificate surrender, annual declaration obligations, and direct exposure to CBAM costs for representatives depending on direct versus indirect representation.
• EY notes the authorised declarant application process may take up to 180 days, which turns “we will handle CBAM later” into an operational readiness risk rather than a reporting-only nuisance.

The evidence supports a pain pattern beyond normal sustainability reporting: import continuity, authorisation status, client/representative liability allocation, quarterly certificate sufficiency, and cash exposure.

Why now

2026 is the phase change. Transitional CBAM reporting trained the market to think in quarterly reports and supplier data; the definitive regime adds authorised declarant gating, annual verified declarations, certificate purchases, quarterly 80% inventory sufficiency, surrender, repurchase, cancellation, and penalties. That moves CBAM from “collect emissions data for reports” into “operate a regulated account with cash exposure.”

The timing is also good because the software category is crowded but still story-misaligned. Existing CBAM tools mostly lead with supplier engagement, emissions collection, CN-code calculations, and XML/report generation. Buyers who are customs representatives need something closer to a client-by-client obligation ledger and authorisation workspace.

Product wedge

Do not compete head-on as “CBAM emissions data platform.” Position as “authorised declarant ops and certificate exposure ledger for customs representatives.”

Core jobs:

• Declarant readiness: track authorised-CBAM-declarant application, EORI, Member State of establishment, role per client, and whether the representative has agreed to act.
• Client handoff: for each importer/client, record who is legal declarant, who supplies emissions data, who funds certificate purchases, indemnity/terms accepted, escalation owner, and missing evidence.
• Exposure ledger: estimate certificate requirement by client, CN code, shipment, supplier, and quarter; show actual purchased certificates, sale price, registry/account reference, surrender, repurchase, and cancellation risk.
• Quarterly buffer watch: calculate the Article 22-style 80% end-of-quarter certificate sufficiency buffer using imports to date and default values; alert when a client or representative account needs purchase action.
• Annual close: prepare the 31 May declaration/surrender evidence pack and the 30 June repurchase decision pack.
• Finance view: convert EU ETS-linked certificate prices into cash forecasts, client recharge schedules, margin-at-risk, and “certificate float” exposure for brokers.

This wedge explicitly avoids generic ESG dashboards. It can interoperate with emissions-data providers rather than replacing them.

MVP

A credible weekend-to-month MVP can be narrow:

1. CSV import from customs declaration/export files: EORI/client, CN code, net mass, origin, supplier, import date, customs reference.

2. Rules table for CBAM goods and default-value placeholders; enough to estimate exposure even before supplier verified data arrives.

3. Client/declarant registry: importer, representative, authorised declarant status, application status, agreement/indemnity status.

4. Certificate exposure ledger: required certificates, purchased certificates, price/date, target quarter, surrender status, repurchase candidate, cancellation timer.

5. Quarterly 80% buffer dashboard and alert email/CSV exports.

6. Client data-chase portal: request missing supplier/emissions files, approvals, and funding confirmations.

7. Exportable evidence pack for broker/importer: per-client exposure, unresolved data, certificate purchase recommendation, and annual declaration checklist.

Do not build calculation perfection first. The sharp MVP is a reconciled operational ledger that tells the representative: “For this client, these shipments create this certificate exposure; you are short by X before quarter-end; the client has/has not accepted funding and liability terms.”

Competition and substitutes

The CBAM software category exists, which validates urgency but raises positioning risk.

• IntegrityNext: broad CBAM workflow, supplier emissions collection, registry-ready XML, certificate forecast/cost simulation.
• Certivo: explicitly leads with verified supplier emissions data, default values increasing certificate costs, audit-ready declaration, and mentions the 50-tonne threshold and first declaration/surrender deadline.
• Climease: import and supplier data upload, reporting, certificate cost tracking, authorised importer guide, and customer claim around cutting quarterly reporting time.
• CBAM Desk: import processing, quarterly/annual declarations, EU XML schema export.
• CBAMBOO: closest adjacent; it explicitly markets financial liability tracking and shows certificate ledger-like language and purchase planning.
• Coolset/Kolum/Sphera/Normative/Sinai/Assent-type tools: broader carbon/compliance suites that can absorb CBAM for enterprise buyers.

Substitutes today are spreadsheets, broker email threads, customs management systems, ERP exports, consulting retainers, and generic CBAM tools. The best beachhead is not “we calculate emissions better.” It is “we let a representative safely operate CBAM for multiple clients without accidentally warehousing unpriced certificate liability.”

Novelty test versus adjacent corpus

The proposed wedge passes the novelty test only if the product story stays disciplined.

Not novel enough:

• Supplier emissions request workflow.
• CBAM XML report generation.
• CN-code screening.
• Generic certificate cost simulator.
• ESG carbon accounting for importers.

Potentially novel / under-served:

• Multi-client authorised-declarant operations for customs representatives.
• Representative/importer legal-role matrix and “agreed to act” workflow.
• Client-funded certificate purchase approvals and evidence of authority.
• Certificate inventory ledger reconciled to quarterly 80% sufficiency, annual surrender, one-third repurchase cap, and cancellation dates.
• Per-client exposure and recharge accounting for a broker who may hold the regulated account but does not want to finance clients’ CBAM costs.
• Non-EU importer handoff where the indirect representative is the practical gateway to EU import continuity.

CBAMBOO and Climease partially encroach on certificate tracking. The defensible differentiation is therefore the broker/representative workflow, not the existence of a ledger alone.

Business model and pricing

Start with a broker/importer SaaS tier:

• Small customs representative: €300–€800/month for up to N clients/import lines, with certificate exposure dashboard and exports.
• Midsize brokerage: €1,500–€4,000/month for multi-client workspace, branded client portal, approval workflows, audit/evidence packs, and API/CSV ingestion.
• Implementation/import mapping: €2,000–€10,000 one-time for messy customs data and client setup.

Willingness to pay should be anchored to avoided penalties, avoided import blocks, avoided staff time, and prevented certificate over/under-purchase. A representative that might otherwise front certificate cash or absorb client disputes has a clear budget rationale.

Distribution wedge

Best initial channel: customs representatives and customs/compliance advisors already publishing CBAM explainers and offering readiness services. They need tooling to standardize delivery.

Tactics:

• Build a “CBAM authorised declarant risk checklist” lead magnet for indirect representatives.
• Offer a free certificate-exposure spreadsheet audit: upload last quarter’s customs export; get a client-by-client exposure and missing-authorisation map.
• Partner with boutique customs law firms and CBAM consultants: give them branded evidence packs and client portals.
• Target non-EU exporter/importer flows through brokers: “If you need an EU indirect representative to act as CBAM declarant, here is the operating workspace.”
• Publish highly specific content around Article 22 quarterly sufficiency, Article 23 repurchase cap, and representative/client handoff. Most generic CBAM content will not speak this language.

Risks

• Regulatory churn: the CBAM Omnibus/simplification process and national implementation details can change thresholds, timings, certificate-sale dates, and reporting burdens. The product must encode rules as configurable policy tables and cite versioned rule assumptions.
• Existing CBAM platforms may add the same ledger workflow. CBAMBOO already uses financial liability/ledger positioning, so the representative-specific workflow must be real, not cosmetic.
• Customs representatives may refuse the authorised declarant role rather than buy software. This is still a wedge: sell readiness/risk assessment and “should we offer this service?” tooling, but it shrinks the market if many refuse.
• Liability sensitivity may require legal templates and insurance-aware workflows. Software cannot solve bad contract allocation.
• Data quality remains hard. If supplier emissions data is missing, the ledger still helps with default-value exposure, but customers may expect full emissions automation.
• Registry integration may be constrained. MVP should assume CSV/XML/manual reconciliation before promising direct registry sync.
• Midsize importers may choose broad ESG suites if they already have procurement sustainability programs.

What might be wrong here?

The strongest contrary signal is that “certificate tracking” is already appearing in CBAM software messaging. If buyers perceive it as a feature inside a broader CBAM tool, not a standalone category, this becomes a positioning feature rather than a company. The second uncertainty is regulatory timing: several market pages discuss certificate starts/deadlines differently as simplification proposals evolve. A serious build must re-verify final delegated/implementing acts and national guidance before selling deadline automation. Third, the customs-representative buyer may be conservative and legal-risk-averse: many may simply refuse to act as authorised declarant for high-risk clients, leaving fewer SaaS buyers but more consulting-style readiness assessments.