
An EU customer asks for product, installation or emissions information. Your export team finds several spreadsheets, an old supplier statement and a PDF with a different reporting period. The immediate operational task is to establish which evidence answers the request, where it came from and who can validate it.
The European Commission's CBAM registry guidance describes a portal for operators of installations outside the EU to share installation and emissions information. Its definitive-regime guidance states that the regime began on 1 January 2026. Both were checked on 9 October 2026. Applicability and reporting responsibilities must be established for the actual transaction by the responsible specialist.
Start with the request and confirmed scope
Keep the customer's request, requested period, product reference, response deadline and responsible reviewer together. Ask the appropriate customs or CBAM specialist to confirm which information is required and who is responsible for any submission.
Do not apply a generic checklist to every export shipment. A workflow can organize the confirmed request; reading a product description does not determine legal coverage. Preserve any uncertainty as a question for the specialist rather than converting it into a completed field.
Give each requested fact a source owner
In a fictional request for product EX-204, the customer needs an installation reference and information for a specified period. Operations holds a current production record, while an older emissions document covers another period. The older document is available, but it does not automatically answer the current request.
Record the requested field, source document, page or spreadsheet location, unit, period, version and person responsible for validation. A supplier declaration should remain identifiable as a supplier source. A calculated value needs its method and inputs available to the authorized reviewer.
Missing information remains missing. OCR cannot create an emissions measurement from a shipping invoice.
Check units and periods before compiling the pack
A field may be legible and still unsuitable. Kilograms and tonnes, annual and quarterly records, and different installation references should not be merged without review. Preserve the original values when a specialist approves a conversion.
Keep source dates distinct from the reporting period. A document issued this month may refer to last year's activity. Show that distinction to the customer-facing owner so a recent upload does not appear to be current evidence by default.
For conflicts across sources, use the principles in choosing the source of truth.
Deliver a reviewed version, with outstanding questions visible
Create a manifest listing the request, included evidence, approved values and unresolved points. Preserve previous pack versions and explain what changed. Record who approved the release and which version the customer received.
A successful upload or email delivery proves transmission, not acceptance by a customer or authority. Keep those states separate. The authorized specialist remains responsible for validation, calculation methodology and any regulated filing.
Use document automation for retrieval and review
A controlled spreadsheet and shared folder may be sufficient for occasional requests. A structured workflow becomes useful when several people supply evidence, documents are revised repeatedly or the customer needs traceability across many references.
Kaliits can scope classification, extraction, source links, missing-field review and pack preparation. Emissions calculation, CBAM certification and regulated submissions are separate responsibilities. The scope must not imply an existing certified CBAM product.
Test the gaps before expanding
Use authorized samples with an absent period, conflicting units, a revised source and an unknown installation. Measure retrieval effort, unresolved gaps and version completeness. Do not report a financial or compliance benefit without verified outcomes.
In a Kaliits workflow diagnostic, describe the recurring customer request, source owners and review process. An anonymized request is enough to begin. Keep sensitive production data within the agreed document controls throughout the pilot.

