CBAM brings carbon-cost clarity into ERP landed-cost workflows.
CBAM is becoming a useful finance design prompt: connect supplier emissions data, customs validation, certificate price signals, landed-cost estimates, close accruals, and annual declaration evidence in the same operating chain.
Thesis
Carbon cost becomes manageable when it is designed into the transaction flow.
CBAM can be treated as a tax and trade-compliance requirement, but the better operating answer is broader. It is a new evidence chain for import-heavy finance teams: which goods are in scope, which supplier installation produced them, which emissions basis applies, which customs declaration validated the import, which certificate price drives the estimate, and which cost or accrual entry reflects that exposure.
That is ERP design work. When the data model is clean, CBAM helps teams price imports earlier, avoid surprise margin leakage, reconcile customs and inventory quantities, support close estimates, and prepare declaration evidence continuously. The result is a calmer landed-cost workflow, not another disconnected compliance calendar.
What changed, and why operators should care.
Definitive period
The European Commission says the CBAM definitive period started on 1 January 2026, and importers or indirect customs representatives above the 50-tonne threshold need authorised CBAM declarant status.
CBAM is now an operating workflow. ERP buyers should expect authorisation references, customs validation status, and importer responsibility to be structured fields, not end-of-period notes.
Covered goods
The Commission lists cement, iron and steel, aluminium, fertilisers, electricity, hydrogen, and selected precursors in the initial CBAM scope.
Item masters, HS/CN codes, supplier records, purchase orders, receipts, and import declarations need a common scope decision so finance can identify exposure before goods arrive.
Customs integration
The Commission reported that CBAM Registry integration with customs systems, Taric, and the EU Customs Single Window enabled real-time validation at the external border in the first week of 2026.
Customs release and finance data are now closer together. Finance teams gain speed when ERP records can reconcile customs declarations, CBAM account status, quantities, and supplier evidence automatically.
Certificate prices
The Commission calculates 2026 CBAM certificate prices quarterly from EU ETS auction information, with Q1 2026 published at 75.36 euros and Q2 2026 at 75.28 euros per tonne of CO2.
Carbon cost can move into landed-cost estimates, purchase commitments, inventory costing policies, accruals, margin analysis, and supplier negotiation models during the year instead of waiting for 2027 settlement.
First declaration
Commission implementation material says importers must submit the first CBAM declaration and surrender corresponding certificates by 30 September 2027 for 2026 imports.
The finance close in 2026 should capture quantities, embedded emissions, certificate price basis, carbon price paid abroad, verification status, and settlement assumptions while the evidence is fresh.
Verification
The Commission states that actual emissions data must be verified by independent accredited verifiers, and the first CBAM verifiers are expected to receive accreditation around September 2026.
ERP evidence should separate default values, supplier-provided actuals, verified actuals, verifier reports, and reviewer sign-offs so audit support reflects the evidence tier used in the declaration.
Data Model
Make carbon cost a first-class landed-cost component.
Finance teams already know how to model freight, duty, insurance, rebates, FX, and supplier surcharges. CBAM deserves the same discipline: a cost component with a source price, an evidence basis, a transaction link, an approval state, and a true-up path.
The operational win is timing. Buyers and category managers see expected exposure before they commit. Inventory and margin reports carry a more complete cost view. Controllers can accrue and reverse with source evidence attached. Trade compliance can prepare the declaration without rebuilding the purchase history.
Scope and classification
Classify goods at item, commodity, HS/CN, supplier, installation, country of origin, legal entity, and importer-of-record level.
Evidence to retain
SKU, HS/CN code, CBAM sector, importer entity, supplier ID, installation ID, scope decision, effective date, reviewer.
Supplier emissions evidence
Capture embedded emissions factors, methodology, reporting period, installation data, supporting documents, and evidence status before PO release where practical.
Evidence to retain
Direct emissions, indirect emissions where applicable, measurement method, default value flag, actual value flag, verifier report ID, source timestamp.
Customs and registry link
Connect customs declarations, CBAM account or application references, import quantities, country of origin, and release status back to purchase and inventory records.
Evidence to retain
Import declaration ID, TARIC code, CBAM account number, application reference, release status, quantity, net mass, border timestamp.
Carbon cost basis
Store quarterly certificate price, forecast price, carbon price paid in a third country where deducted, FX treatment, and costing policy in a versioned cost layer.
Evidence to retain
Quarter, price source, EUR/tCO2e, FX rate, deduction amount, costing method, accrual policy, approval.
Finance posting
Route estimated and actual CBAM exposure into landed cost, inventory, cost of goods sold, AP accruals, provisions, or separate tax/control accounts according to policy.
Evidence to retain
Journal source, product batch, quantity, emissions basis, amount, account mapping, reversal date, settlement reference.
Audit packet
Generate a declaration-ready evidence packet from the transaction system instead of rebuilding support from emails and spreadsheets.
Evidence to retain
Evidence packet ID, source objects, open exceptions, verifier status, declaration year, preparer, approver, retention owner.
Design the controls where the cost is created.
The control points should sit close to commercial decisions. Scope classification belongs in item and supplier setup. Evidence completeness belongs in sourcing and PO release. Customs validation belongs on the import chain. Cost estimates belong in landed cost and close. Verification status belongs in the declaration evidence packet.
This is good news for operators. A well-designed workflow gives buyers clearer prices, gives AP fewer late exceptions, gives controllers better accrual support, gives treasury and FP&A cleaner exposure signals, and gives auditors a single chain from supplier evidence to finance posting.
Implementation checklist
1. Build a CBAM scope service
Create one controlled decision service for CBAM scope by product, HS/CN code, supplier, country, entity, and importer role. Feed procurement, inventory, customs, AP, and reporting from the same source.
2. Move supplier evidence upstream
Ask for installation and emissions data during sourcing, supplier onboarding, contract renewal, and PO release. Waiting until invoice approval makes AP the cleanup desk.
3. Tie customs events to finance records
Store import declaration IDs, CBAM account or application references, release status, quantities, and net mass on the same transaction chain as the PO, receipt, inventory lot, and bill.
4. Estimate carbon cost during 2026
Use the published quarterly prices and approved forecast assumptions to estimate exposure, then true up when actual evidence, verification, or final declaration data changes.
5. Gate evidence by decision point
Use soft warnings for early sourcing gaps, hard gates for customs-release blockers, approval routing for costing assumptions, and close tasks for unresolved verification gaps.
6. Package declaration evidence continuously
Generate an annual evidence packet from controlled transaction data: quantities, emissions basis, price basis, deductions, verification reports, approvals, exceptions, and postings.
Constructive failure modes to design around.
CBAM data lives only in a compliance portal
Keep the portal as a specialist system if needed, but sync stable IDs, statuses, quantities, emissions basis, and evidence links back to the ERP objects finance uses.
Landed cost ignores carbon exposure
Add CBAM as a versioned cost component so pricing, purchasing, inventory valuation, and margin review see the exposure while decisions are still adjustable.
Supplier actuals and defaults are mixed
Track default values, unverified actuals, verified actuals, and verifier reports as separate evidence tiers with different approval and disclosure implications.
Customs quantities do not reconcile to purchasing
Reconcile declaration quantities, net mass, goods receipts, inventory lots, and supplier invoices using tolerance rules and exception ownership.
The first declaration becomes a year-end scramble
Run a monthly CBAM sub-close in 2026 so missing evidence, accrual estimates, and verification status are reviewed while the underlying transactions are still current.
Deductions lack support
If a carbon price paid abroad is deducted, retain the jurisdiction, price instrument, calculation, source document, approval, and link to the relevant imported goods.
API and data-contract considerations.
CBAM readiness needs stable IDs more than another spreadsheet. A practical ERP design should expose events such as cbam_scope.classified, supplier_emissions.received, customs_import.validated, cbam_cost.estimated, cbam_accrual.posted, and cbam_packet.generated.
Each event should carry entity, product, supplier, installation, customs declaration, quantity, emissions basis, certificate price source, actor, timestamp, and idempotency key. That gives finance a repeatable chain for estimates, approvals, reversals, declaration support, and audit review.
Example evidence payload
{
"cbam_packet_id": "cbam_2026_q2_steel_0042",
"importer_entity": "EU-NL-01",
"product": {
"sku": "steel_fastener_m12",
"hs_code": "731815",
"cbam_sector": "iron_and_steel",
"scope_status": "in_scope"
},
"supplier_installation": {
"supplier_id": "sup_1842",
"installation_id": "inst_steel_771",
"country_of_origin": "TR",
"emissions_basis": "actual_verified",
"verifier_report_id": "vr_2026_09_118"
},
"customs": {
"import_declaration_id": "imp_2026_06_7714",
"cbam_account_reference": "cbam_app_44821",
"net_mass_tonnes": "18.400",
"release_status": "validated"
},
"costing": {
"quarter": "2026-Q2",
"certificate_price_eur_per_tco2e": "75.28",
"embedded_emissions_tco2e": "42.700",
"estimated_cbam_cost_eur": "3215.46",
"posting_policy": "landed_cost_accrual"
},
"controls": {
"scope_review": "approved",
"quantity_reconciliation": "passed",
"accrual_review": "approved",
"evidence_packet_generated": true
}
}Questions CFOs and controllers should ask ERP vendors.
Practical Takeaway
Treat CBAM as a landed-cost intelligence upgrade.
The best operating outcome is practical and positive: finance sees carbon exposure while buying decisions are still live, import teams reconcile customs and ERP facts quickly, controllers close with evidence attached, and the annual declaration becomes a prepared output of the transaction system.
For ERP buyers, CBAM is a useful test of architecture. If the platform can connect supplier emissions, customs validation, cost layers, journal evidence, and annual declarations without forcing manual reconciliation, it is ready for the next wave of finance operations work.
Sources
- European Commission: Carbon Border Adjustment Mechanism overview
- European Commission: CBAM successfully entered into force on 1 January 2026
- European Commission: Price of CBAM certificates
- European Commission: First CBAM certificate price is now available
- European Commission: CBAM verification
- Council of the EU: CBAM simplification regulation
- Council of the EU: Carbon border adjustment mechanism policy page