Your CSRD assurance provider will not sign off on Scope 3 data that can't be traced to source evidence. Your PPWR recycled-content claims will not survive EU Green Claims enforcement without document-level proof.
Xworks turns the operational documents your suppliers already produce into audit-grade records — with full data lineage, a nominated VVB, and a complete evidence pack your assurance provider can rely on.
The next scene shows the verified record, the full evidence pack, and how it lands in your assurance workflow. Tell us who you are.
Upload the documents your suppliers already produce. Xworks turns them into audit-grade records — with full data lineage, a nominated VVB, and an evidence pack your assurance provider can rely on.
CBAM, CSRD, PPWR and digital tracking systems are now forcing companies to prove — not claim — what happens in their supply chain.
In force today: GHG Protocol (measured / estimated labelling under the 2026 revision), SBTi V2.0 (offsets no longer eligible for Scope 3 abatement under the revised guidance), ISO 14064-5 (independent on-site VVB verification for project-level GHG assertions), FuelEU Maritime & IMO CII (emissions intensity targets with member-state penalty mechanisms), Article 6.2 Paris (corresponding-adjustment requirements to avoid double-counting between sovereigns).
Imminent: EU WSR digitalisation — DIWASS (from 21 May 2026) replaces paper Annex VII for cross-border waste shipments. UK Digital Waste Tracking (expected late 2026). EU Green Claims / ECGT — independent accredited verification for environmental claims, with member-state enforcement penalties.
Phased: EU CBAM (carbon border adjustment, definitive regime from 2026 with phased reporting). EU PPWR recycled-content targets (indicatively 10–35% by 2030 and 25–65% by 2040, depending on packaging type and application). EU Digital Product Passport (sector-by-sector, from 2027).
The common thread: across these frameworks, the verifier is increasingly expected to be independent of the participant. CDP scores, supplier certifications and self-declared data are less likely to satisfy assurance reviewers on their own. Specifics, deadlines and penalty levels vary by jurisdiction — confirm with your assurance provider for the regimes that apply to you.
Live today: Mechanical recycling, plastics waste flows, cross-border waste shipments (EU WSR, Basel, OECD). Weighbridge tickets, transport documents (CMR/BL), Annex VII forms, site permits, ISO 14001 certificates, scale calibration records, customer due-diligence questionnaires. PPWR provenance chain — origin → recovery facility — verified at the kilogram level.
Next on the roadmap: Manufacturing input verification — Bill of Materials, batch production records, quality certificates, Tier 2 supplier declarations. Logistics records — Bills of Lading, customs declarations, carrier authorisations. Same verification logic. Same evidence model.
Beyond: Agricultural origin verification (cocoa, soya, palm), textile fibre provenance, electronics component lineage. The gates don't change — registries and classification taxonomies extend per material domain.
Where we start matters: Plastics and waste shipments are where the verification gap is most acute and most regulatorily urgent. PPWR recycled-content mandates, EU Green Claims enforcement, and the May 2026 DIWASS cutover converge on a single domain. We start there because the deadlines are now — not because the system is limited to it.
Provenance leg. The verified record evidences that a specific tonne of recycled material moved from origin to recovery facility, with documented chain of custody, valid permits and reconciled mass balance. The upstream side is resolved at the kilogram level.
Attribution leg. Verified input tonnes are linked through to a recycled-content percentage at the finished-product level, against the applicable threshold for that packaging type. The calculation is reproducible and reviewable by an independent VVB rather than self-asserted.
What this means in practice. A buyer asserting a recycled-content percentage receives a record showing the recycled tonnes existed, were lawfully moved, were received, and were converted into the finished product — with the percentage calculation traceable end to end. A single verified output that an assurance reviewer can test against the relevant threshold (indicatively 10–35% by 2030 and 25–65% by 2040 under PPWR, depending on packaging type).
Same documents. Same workflow. The verification spine sits on top — converting fragmented operational evidence into audit-grade records, prepared for independent VVB validation.
The verification spine is identical for everyone. What changes is what you see at the end. Pick a role — you can switch at any time.
Upload what you already have. The record cannot proceed unless it passes independent checks — but you'll know immediately what passes, what doesn't, and why.
Every uploaded file is captured immutably at the moment of receipt, hashed for tamper-evidence, and timestamped against the supplier's authenticated session. The original file is never altered. Read-only metadata is extracted to populate the verified record; the source remains intact for independent review.
Where extracted fields fall below the confidence threshold, the supplier is asked to confirm or correct before the document advances — supplier confirmation is captured as an independent signal alongside extraction, matching, and verification. None of the four can override another.
Evidence types covered include: weighbridge software exports, transport documents (CMR / BL), cross-border shipment forms, waste and material codes, container seal records, scale calibration certificates, jurisdictional environmental permits, ISO 14001 management certificates, and customer due-diligence questionnaires.
Nothing operational changes. Only the outcome does.
Fix and re-upload. That's it. This is the line that keeps the system audit-grade — every record is source-captured. If a document fails a check, it goes back to the supplier, not to a back-office team to "fix".
Failed documents are returned to the supplier with a structured reason — what failed, why, and what to resubmit. The reasons are drawn from a fixed catalogue, not free-text, so every rejection is comparable across suppliers, sites, and time. There is no editorial discretion at the back office.
Every rejection is logged immutably with timestamp and supplier identity, and the original file is retained as captured. No member of staff has the ability to alter a supplier file at any stage — and any attempt to do so is logged. The supplier always sees the same reason the auditor sees.
Once an evidence package is complete, it enters the spine. Each gate runs deterministically, in order, against the captured evidence. No gate is skippable. No outcome is overrideable.
Pick one to see what it looks like.
Each gate produces a deterministic pass / fail decision against the captured evidence — not a probability, not a confidence score. Trust validates the entity against the authoritative public register for its jurisdiction and confirms active permits. Classification confirms material codes against the relevant published taxonomy — no free-text fallback.
Registry cross-references the load against cross-border notification status, jurisdictional capacity, national environmental licences, and carrier registers. Mass balance reconciles input and output quantities against accepted industry norms. Decision records the outcome immutably with a unique code, the full reason trail, and a tamper-evident hash of the evidence pack.
Once written, a decision cannot be updated or deleted. The original supplier files remain unmodified and are retained alongside the decision record. An independent VVB can re-run every check against the same evidence and arrive at the same outcome.
A decision-grade record that buyers, auditors, and regulators can rely on. Every field source-captured. Every decision reproducible. Every hash verifiable.
This output isn't abstract — every field traces back to a real file the supplier uploaded.
This evidence pack is structured for independent review by accredited Verification & Validation Bodies. Xworks operates with a nominated VVB for plastics records. Validation outcomes are determined solely by the VVB and are not implied by the contents of this pack.
The pack is a structured, tamper-evident archive containing every original supplier file (unmodified), the verification decision and its full reason trail, and the audit log enumerating every event from intake through decision. Each evidence file is bound to the decision by a verifiable hash so the pack cannot be tampered with after issue.
Contents typically include: business registration, tax certificate, ISO 14001, jurisdictional environmental permits, customer due-diligence questionnaire, scale calibration certificate, weighbridge ticket, transport document (CMR / BL), cross-border shipment form, container and seal photo, customer delivery export, site receipt, and signed declaration of finality.
An independent VVB can re-run every check against the pack and arrive at the same decision. The pack is compatible with the EU WSR DIWASS submission and UK Digital Waste Tracking machine-readable formats.
Verified tonne → verified emissions number. Xworks issues a verified record of physical activity with full provenance and lineage. The conversion to a tCO₂e number happens by applying GHG Protocol emission factors (Category 5 for waste, Category 1 for purchased goods). Today this is done downstream — the verified record feeds your existing Scope 3 calculation engine. Xworks does not assert the emissions number; it asserts the activity that the number is derived from.
ESG platforms. The evidence pack is structured for ingestion by enterprise Scope 3 platforms (Watershed, Persefoni, Sweep, Salesforce Net Zero Cloud). Live API integrations are on the roadmap. Today the pack is exported as a versioned archive uploadable by the customer's sustainability team. CDP and CSRD assurance providers receive the same pack.
ERP linkage. SAP, Oracle, Microsoft Dynamics — purchase-order and goods-movement linkage via standard enterprise interfaces. Order references in the verified record reconcile back to PO numbers in the source ERP.
What this means commercially. Xworks does not replace your Scope 3 platform, your ERP, or your CDP submission tooling. It supplies the source-of-truth evidence layer that those systems do not produce themselves. Your assurance provider receives a complete lineage from final disclosure number back to original supplier-issued document.
A complete data lineage from final disclosure number back to original supplier-issued document. Reproducible by any reviewer. Acceptable to your assurance provider. Defensible under regulatory enforcement. You don't change your operations — you change what they produce.