A regulatory position is only as defensible as the evidence that supports it. Weetra examines whether regulatory data can be traced to the documents, identities, relationships, periods and versions that are supposed to support it.
Regulatory data may come from suppliers, manufacturers, installations, commercial intermediaries, ERP systems, monitoring systems, declarations, certificates and external source records. The review asks where the information came from, who produced it, what it relates to, which period and version apply, and whether different records reconcile.
A regulatory value can be technically correct and still be difficult to defend if its origin is unclear. Review therefore starts from the proposition being relied upon and works backwards to the relevant source records. It asks whether the evidence belongs to the right product, legal entity, producer, installation, parcel, reporting period or product identifier, depending on the regime.
A document can be authentic and still fail to support the claim attached to it. Documentary review therefore tests relationships: product to supplier, supplier to producer, producer to installation, reported value to source record, and current file to the versions that preceded it.
Those relationships are where apparently complete files often weaken. A commercial invoice may show a seller but not the manufacturing installation. A supplier declaration may contain a number but not the source record from which the number came. A revised monitoring plan may exist, while the calculation still refers to the previous version. Documentary review is the discipline of testing those links rather than treating documents as isolated attachments.
CBAM, EUDR and the Digital Product Passport are different legal systems and do not use identical data. They nevertheless create recurring evidence-governance questions about identity, source support, traceability, versions, contradictions, remediation and the ability to understand the record later.
Goods → producer → installation → reporting period → embedded emissions → source records. CBAM is Weetra’s primary operational review application.
Product → commodity → production source → geolocation and legality → risk assessment → due-diligence records. The legal duties are different from CBAM.
Product → unique identifier → responsible economic operator → required data field → source system or supplier → version → passport data.
More data-intensive customs and regulatory systems increase the importance of stable identifiers, provenance, cross-system reconciliation and documentary support. A digital submission does not remove the need to understand the sources behind it.
Weetra examines the documents in scope, the facts asserted by those documents, the relationships between actors and regulated objects, the consistency of quantities and periods, competing versions, contradictions, remediation and what the available records cannot establish.
Source support: which record supports a specific reported fact or regulatory position.
Identity: which legal entity, operator, producer, installation, product, parcel or regulated object the evidence belongs to.
Relationships: whether commercial, production, regulatory and source records point to the same underlying object.
Time and versions: whether periods align and the version used in a calculation or declaration is the applicable one.
Contradictions and limits: where records conflict or the available evidence cannot establish the position claimed.
Remediation history: what was clarified, replaced or corrected and how the reviewed file changed before conclusion.
A review can produce findings, remediation questions, a human-governed Determination and, where the mandate provides for it, a Determination Package preserving the reviewed documentary history. The exact output depends on the mandate and review depth.
Weetra does not turn every documentary problem into the same product. A first screen may be sufficient. A deeper engagement may be appropriate when the file contains complex relationships, multiple source systems, unresolved contradictions or high-consequence positions. If no deeper review is required, no further engagement is recommended.
Regulatory files are often revisited after the operational work has finished. Preserving what was received, what changed, what was corrected and what was relied upon makes later internal review, professional advice, verification or authority scrutiny easier to reconstruct.
The point is not to preserve bureaucracy for its own sake. It is to preserve the history needed to understand why a regulatory position was accepted, changed, limited or rejected at a particular point in time.
CBAM is Weetra’s primary operational review application today. EUDR and Digital Product Passport work are developing regulatory-evidence applications: the website explains their documentary requirements without presenting them as identical commercial services.
