GrandScope links entity, shipment, CN code, supplier, facility, emissions method, evidence, calculation, and filing status so a reviewer can follow the record without rebuilding it from spreadsheets and inboxes.
Each layer carries the context required by the next. The product record is built around traceable relationships, not isolated files.
Keep the importer group, legal entities, EORI records, addresses, users, roles, and country authority metadata attached to the reporting obligation they govern.
Connect internal product references to CN or HS codes and retain the mapping used to place each shipment line inside the reporting workflow.
Record reporting period, quantity, net mass, customs value, country of origin, product, and supplier at import-line level.
Link supplier contacts, countries, facilities, secure request links, submission states, and supporting files to the imports they support.
Make actual or default source mode visible, normalise units, retain calculation inputs, record formula versions, and expose review flags.
Bring reporting-period checks, filing packs, evidence metadata, alerts, and filing status into the same controlled record.
A reviewer should be able to move backwards from the report result to the import line, supplier response, calculation context, and supporting evidence.
The value of compliance data is not the number of fields stored. It is the speed with which a preparer, reviewer, auditor, or authority can understand where a result came from.
Organisation, legal entity, EORI, and authority metadata.
Import, product, CN code, quantity, value, origin, and supplier.
Supplier submission, facility record, or an explicit default-data path.
Input reference, input hash, formula version, output, timestamp, and actor.
Files linked by purpose to the supplier, facility, calculation, or report.
Readiness flags and filing states from drafted through accepted or rejected.
Quality controls bring missing information, unresolved mappings, source-mode gaps, and anomalies into view before they become filing rework.
Identify missing entity, import-line, supplier, emissions, or reporting-period information before export work begins.
Expose product and CN-code mapping gaps so reporting lines do not move forward with an unresolved classification.
Separate supplier-specific information from default-data use and retain the path behind the selected source mode.
Apply consistent unit, rounding, and missing-value rules before calculation results enter the reporting record.
Surface sanity-check failures, outliers, and supplier submissions that require investigation or correction.
Confirm that supporting files are connected to the record and purpose for which they are being relied upon.
A calculation is easier to review when the workflow clearly distinguishes supplier-specific information from a default-data path and retains the reason behind the selected mode.
Use accepted information supplied for the relevant facility, product, or reporting line and retain the submission that supports it.
Record the fallback source separately when supplier-specific information is unavailable, then keep the mode visible during review and reporting.
The calculation record is designed to retain the references and control information needed to explain how an emissions output was produced.
Reference and hash for the data used.
Formula version and source mode retained.
Timestamp, actor, output, and flags recorded.
Files become more useful when their purpose, linked record, review state, and place in the reporting chain are visible.
| File | Purpose | Linked record | State |
|---|---|---|---|
| supplier-method.pdf | Supplier emissions method | Submission SUP-0184 | Verified |
| facility-meter-data.xlsx | Electricity input | Facility FAC-0074 | Linked |
| calculation-record.json | Calculation context | Calculation CAL-00481 | Recorded |
| reporting-pack.zip | Structured filing pack | Report RPT-2026-01 | Exported |
The compliance record sits inside organisation, entity, access, and evidence controls rather than a shared folder with no ownership.
Keep each importer organisation and legal entity inside a defined tenant and ownership structure.
Scope access by organisation, entity, internal role, and supplier token rather than sharing unrestricted files.
Retain the actor, timestamp, source, status, and calculation context needed to explain material changes.
Organise evidence with purpose tags, naming standards, record links, and retention controls suited to the operating model.
Internal access can be scoped through the authenticated importer workspace. Supplier contacts can use secure token-based requests limited to the context required for their submission.
Advanced governance, retention, audit-pack, alerting, and integration controls can vary by plan and implementation.
The connected record can support the operational views needed by compliance, procurement, finance, and management without creating a second source of truth.
Use governed import, supplier, emissions, and evidence records to prepare the structured output workflow.
Review emissions and cost exposure by product, supplier, and country from the same underlying records.
Compare supplier-specific and default-data positions without creating disconnected calculation copies.
Bring missing data, deadlines, evidence gaps, and compliance warnings into the operational workflow.
Test the journey from import data and supplier inputs through calculation context, evidence, and reporting output.
