How GrandScope worksEU CBAM operating workflow

One controlled chain from import records to CBAM-ready output.

GrandScope connects legal entities, CN codes, shipment lines, suppliers, emissions inputs, evidence, calculations, and reporting controls in one traceable operating model.

Start free CBAM reportView plans

Product walkthrough

Watch the complete importer-to-supplier workflow.

1 min 06 secGrandScope product demo

Entity-separated access Supplier evidence linked to imports Calculation context retained

Product walkthrough

Watch the complete importer-to-supplier workflow.

See how an importer starts with basic details, sends a secure supplier link, receives facility and emissions evidence, reviews the response, and moves the record towards CBAM-ready output.

1 min 06 secGrandScope product demo

Importer starts with basic details Secure link collects supplier data Review leads to CBAM-ready output

The operating chain

Seven linked stages. One source of reporting truth.

Each stage creates the structured input for the next. Data is not copied between disconnected spreadsheets, inboxes, and filing tools.

Entity control

Set up the importer structure

Create the organisation, legal entities, EORI records, addresses, user roles, and country authority metadata that define who owns each reporting obligation.

Key controls

Organisation and entity details
EORI and establishment data
Users, roles, and access boundaries

Stage outputA controlled reporting workspace for each legal entity.

Import spine

Upload and map shipment data

Bring in customs or shipment records, validate the file, map internal products to CN or HS codes, and connect every import line to the correct supplier.

Key controls

Quantity and net mass
Customs value and origin
Product, CN code, and supplier mapping

Stage outputValidated import lines ready for supplier and emissions work.

Supplier collection

Request data through secure supplier links

Generate token-based requests, collect supplier and facility details, capture emissions inputs, receive evidence files, and track each request from draft to verified or rejected.

Key controls

Supplier contacts and facilities
Secure request links
Submission evidence and status

Stage outputSupplier responses linked directly to the relevant records.

Calculation control

Normalise, calculate, and review

Apply unit and rounding rules, handle missing values, distinguish actual data from defaults, and expose the source and flags behind every calculated result.

Key controls

Actual or default data mode
Electricity and precursor inputs
Unit normalisation and fallback logic

Stage outputPer-line embedded emissions with deterministic calculation context.

Reporting gate

Validate the reporting period before export

Aggregate the reporting period, identify missing data, default usage, and outliers, then move the filing pack through a controlled export and submission checklist.

Key controls

Reporting period aggregation
Completeness and outlier checks
Filing status controls

Stage outputA structured reporting pack prepared for the export workflow.

Exposure planning

Model emissions and cost exposure

Compare actual and default scenarios, review exposure by product, supplier, and country, and apply certificate or ETS price assumptions for planning.

Key controls

Product and supplier comparisons
Actual versus default scenarios
Certificate and price assumptions

Stage outputA management view of operational and financial exposure.

Audit control

Retain evidence, alerts, and lineage

Keep supporting evidence connected to the record, surface deadline or missing-data alerts, and preserve the chain from import line to supplier submission, calculation, and report.

Key controls

Evidence metadata and retention
Risk and deadline alerts
Calculation and reporting lineage

Stage outputA reviewable evidence trail for internal and external scrutiny.

Record lineage

What happens to one import line.

The product model links the customs record, supplier response, emissions result, and reporting output instead of treating them as separate tasks.

01Import lineCN code, mass, value, origin Validated

02Supplier responseFacility data, emissions, evidence Linked

03CalculationSource mode, formula version, result Logged

04Reporting packChecks, aggregation, structured output Controlled

Why the connection matters

A reviewer can follow the path from an import record to the supplier data used, the calculation context applied, and the reporting record produced from it.

Supplier collection

Replace one-off email chasing with a controlled request lifecycle.

The importer launches the request. The supplier receives a secure link, submits the required information and evidence, and the status returns to the importer dashboard.

Importer workspace

Create supplier links and campaigns
Track draft, sent, viewed, and submitted states
Review evidence and verify or reject responses
Trigger reminders and escalation rules

Supplier portal

Open a token-based request link
Review the relevant request context
Enter facility and emissions information
Upload evidence and submit the response

Calculation ledger

The result is only useful when its source can be explained.

GrandScope's calculation model is designed to retain the inputs, source mode, formula version, output, time, actor, and review flags behind each emissions result.

Actual dataSupplier or facility inputs

Used when the required information is supplied and accepted.

Default modeExplicit fallback logic

Recorded separately when actual information is unavailable.

Calculation recordReviewable

Import line: IMP-2026-00481
Data source: Actual
Input reference: Supplier submission 0184
Input hash: 7f9c...3a21
Formula version: CBAM-CALC-1.4
Output: 2.418 tCO2e
Recorded: Timestamp and actor retained
Review flags: No unresolved flag

Illustrative record structure. Values shown are examples.

The reporting gate

Resolve the weak points before they reach the filing pack.

Reporting controls combine period aggregation with checks for missing information, default usage, outliers, and unresolved supplier records.

Completeness

Identify import lines, suppliers, or reporting fields that remain incomplete.

Method visibility

Separate actual information from default-value use and expose the fallback path.

Anomaly review

Surface sanity-check failures, outliers, and submissions requiring investigation.

Output control

Move the report through the filing checklist and defined filing states.

Structured output workflow

From review to controlled filing status.

The reporting model supports a structured output stage and a filing status chain covering drafted, exported, submitted, accepted, and rejected records.

Module availability can vary by plan and implementation.

Drafted

Exported

3Submitted

4Accepted

5Rejected

Management and audit controls

Use the same reporting data for planning, alerts, and evidence.

Exposure dashboard

Review emissions and cost exposure by product, supplier, and country.

Scenario comparison

Compare default and actual-data positions and supplier-level differences.

Actual data Default mode

Deadline and data alerts

Bring missing information, deadlines, and compliance warnings into view.

Action requiredSupplier evidence incomplete

Evidence and audit lineage

Connect import records, submissions, calculations, reports, and evidence.

ImportSubmissionReport

Workflow FAQ

Practical questions about the reporting process.

What data do I upload first?

The workflow starts with legal entity information and import records. Import lines can include quantity, net mass, customs value, country of origin, internal product references, CN or HS codes, and supplier mapping.

How do suppliers provide emissions information?

Importers generate token-based supplier links. The supplier opens the request, reviews the context, provides supplier and facility information, enters emissions inputs, uploads evidence, and submits the response without needing an importer account.

Can the workflow distinguish actual data from default values?

Yes. The calculation design separates actual-data mode from default-value mode and records the fallback logic used when information is missing or incomplete.

What is retained behind a calculation?

The calculation ledger is designed to retain the input reference, input hash, formula version, output, timestamp, actor, data source, and any warning or review flag connected to the result.

What checks happen before an export?

The reporting gate reviews missing data, default usage, outliers, reporting-period coverage, and unresolved items before the filing pack moves into the structured output workflow.

Can several entities and team members use the same workspace?

The operating model supports an importer organisation with legal entities underneath it, entity-level EORI records, role-based access, and strict tenant boundaries.

How is supplier progress tracked?

Requests move through defined states such as draft, sent, viewed, submitted, verified, and rejected. Campaign controls can also support bulk sending, reminders, and escalation rules.

Are all modules included in every plan?

Core workflow and advanced controls can vary by plan and implementation. The pricing page sets out entity limits, supplier limits, forecasting, governance, integration, and support levels.

See the workflow on your data

Start with one import file and one reporting chain.

Test the operating model on a real CBAM record, or ask for a walkthrough covering entities, suppliers, calculations, and output.

Start free CBAM report Request demo