CBAM Excel - Free Template

1. Open the Instructions tab first. Read the limitations, then replace the illustrative sample rows rather than treating them as verified shipment records.
2. In Emissions Data, enter the Shipment ID, Import Date, Exporting Country, verified CN Code, Product Category, and Quantity (Tonnes).
3. Enter the supplier-supported Direct Emissions Factor and Indirect Emissions Factor in tCO2e/t. Use zero for indirect emissions only when that zero scenario is justified; blank data is not measured zero.
4. Review the Assumed carbon price credit and edit it only when you have a documented EUR assumption. Do not treat it as an approved deduction.
5. Review the Scenario price pulled from Reference Rates. The supplied values are illustrative EUR assumptions, not official prices or live data.
6. Set Evidence review for each row and investigate any Scenario check result showing Check inputs or Check category.
7. Use Dashboard to review totals by category, then share the underlying evidence and CN-code decisions separately with the EU importer.

A U.S. exporter, freight coordinator, or supplier-account manager can use this CBAM register when an EU importer requests shipment-level information for covered goods. It is most useful during quotation review, monthly shipment reconciliation, or a year-end evidence request when several suppliers are providing different emissions formats.

Shipment-Level Information Sharing

For example, the sample register separates a 500-tonne Iron and Steel shipment from a 320-tonne Aluminum shipment and a 900-tonne Cement shipment. Each row keeps the origin, CN-code placeholder, emissions factors, scenario prices, and evidence status together instead of mixing supplier records in email attachments.

Supplier Review Meetings

A purchasing team can use the Evidence review dropdown to show whether a supplier record is Verified, Pending Review, Flagged, or Under Audit. The Dashboard then summarizes five product categories, helping an exporter discuss which assumptions still need supporting documentation before sending information to an EU importer.

This workbook preserves the European scope and EUR inputs needed for a planning conversation, but it does not determine an official CBAM obligation. The Instructions tab expressly excludes threshold testing, free-allocation adjustments, eligibility decisions, verification, and official Registry submission.

Illustrative Calculations

The embedded-emissions formula is I = F × (G + H), where F is tonnes, G is direct emissions in tCO2e/t, and H is indirect emissions in tCO2e/t. Gross scenario amount is L = I × K; assumed credit is M = I × J; net scenario amount is N = MAX(0,L-M). These are arithmetic scenarios, not regulatory conclusions.

Reference Rates Require Review

Reference Rates contains five categories and an illustrative scenario price of EUR 80/tCO2e in the populated examples. Column C is unused by formulas, and the workbook has no official factor library, live price feed, exchange conversion, or certificate calculation. Verify CN codes, emissions scope, evidence, and any applicable EU requirements outside this file.

The most damaging errors usually begin with a shipment record that looks complete but has an unverified CN code or unsupported emissions factor. The sample rows display VERIFY CN CODE, which is a warning to replace the placeholder, not a classification result.

Missing Inputs Are Not Zero

If quantity or either emissions factor is missing, the total embedded-emissions formula stays blank because all three inputs are required. Entering 0 for indirect emissions without supplier support can understate the scenario; the Instructions tab says zero is appropriate only where indirect emissions do not apply or an explicitly zero scenario is justified.

Credits Can Create False Confidence

The assumed credit column multiplies emissions by a user-entered EUR assumption. A net scenario amount of zero therefore does not prove an exemption, approved deduction, or zero official liability. The Scenario check labels such a row Zero scenario balance, while valid populated rows remain Scenario only.

Range Limits Matter

The prepared register covers rows 5 through 14, and Dashboard formulas summarize those same rows. Adding an eleventh shipment without rebuilding formulas, chart ranges, and validation can leave the new record out of totals, so treat the ten-row design as a defined working range.

Use the workbook at a fixed point in your shipping process rather than waiting for an EU importer to request everything at once. A practical routine is to update shipment inputs after the monthly freight reconciliation, then hold a separate evidence review before sharing the file.

A Repeatable Review Sequence

• Enter shipment facts first: date, origin, CN code, category, and tonnes.
• Add supplier emissions factors only from the documentation selected for that shipment.
• Review the Scenario check column before looking at the Dashboard.
• Set Evidence review to the current status and retain supporting references outside the workbook using Shipment ID.

Keep Assumptions Controlled

Change Reference Rates only when the team agrees on the scenario assumption and records its source. Keep EUR inputs in EUR; this workbook has no exchange-rate conversion. Do not overwrite calculated columns I and K:N unless you are intentionally redesigning the workbook and checking every dependent formula.

Know When to Move On

Once shipment volume exceeds the prepared ten-row range or several people need simultaneous updates, a controlled data system may be more reliable than a single XLSX file. Until then, keep one consistent scenario version, date your shared copies, and send the Dashboard together with the underlying shipment and evidence records.