Technical records
Under Regulation (EU) 2025/40, PPWR technical documentation and the EU Declaration of Conformity are retained for five years for single-use packaging and ten years for reusable packaging from placing on the market.
Audit & Evidence Control Engine
Build the evidence chain. Defend every compliance claim.
Organise EU packaging EPR and PPWR evidence by claim, country, period, provenance, retention rule, hold and audit request. Generate request-specific disclosure packs without pretending that a ZIP is an audit opinion or legal archive.
EU27 evidence controlClaim-to-evidence lineagePPWR 5/10-year retentionRequest-specific disclosureSHA-256 integrityNo automatic deletion
Direct answer
What should an EPR audit file contain?
An audit file should connect each legal or operational claim to the exact evidence that supports it: registrations, representation, PRO participation, packaging facts, classifications, reports, payments, marketplace outcomes, technical documentation and correspondence. The file must also preserve dates, versions, provenance, integrity fingerprints and the rule that controls retention.
Generated ≠ submitted ≠ accepted ≠ audit passed ≠ legally archived.Legal control layer
Different records follow different retention and request rules.
Not every audit is 10 days
The PPWR ten-day response logic is limited to the relevant reasoned national-authority technical-document request route. It is not a universal deadline for EPR authority, PRO, tax or marketplace audits.
No invented period
National EPR, PRO, tax, accounting and contractual retention periods are record-specific. This engine leaves a duration unresolved when no verified rule has been stored.
Hash ≠ authenticity
SHA-256 can show whether retained bytes changed. It does not establish the issuer, legal authenticity, submission, acceptance or qualified electronic archiving.
Evidence workspace
One control plane for your compliance evidence
Link files to claims, preserve versions, calculate only verified retention, build audit requests and disclose only what the request actually needs.
01
EU27Scope
An audit file should connect each legal or operational claim to the exact evidence that supports it: registrations, representation, PRO participation, packaging facts, classifications, reports, payments, marketplace outcomes, technical documentation and correspondence. The file must also preserve dates, versions, provenance, integrity fingerprints and the rule that controls retention.
02
0Evidence inventory
No evidence has been added yet.
03
LINEAGE · 0Claims & lineage
Preserve supersession and the upstream engine that produced or sourced each record.
04
NO INVENTED PERIODRetention
National EPR, PRO, tax, accounting and contractual retention periods are record-specific. This engine leaves a duration unresolved when no verified rule has been stored.
| Claim supported | Status | Expires | Rules | PPWR |
|---|
05
SHA-256Integrity & provenance
SHA-256 can show whether retained bytes changed. It does not establish the issuer, legal authenticity, submission, acceptance or qualified electronic archiving.
0Completeness
0SHA-256
0Provenance
0Sensitive / review before disclosure
SHA-256 can show whether retained bytes changed. It does not establish the issuer, legal authenticity, submission, acceptance or qualified electronic archiving.
06
0Audit request
The PPWR ten-day response logic is limited to the relevant reasoned national-authority technical-document request route. It is not a universal deadline for EPR authority, PRO, tax or marketplace audits.
Controlling deadline: None
No audit request has been added.
07
0Gaps & reconciliation
Find missing files, hashes, provenance, unresolved retention and quantity conflicts.
Quantity reconciliation: None
0%Completeness
0%Integrity
0%Provenance
0%Retention certainty
100%Request coverage
100%Reconciliation
100%Hold safety
08
0Holds & deletion review
No evidence is deleted automatically.
No preservation hold is active.
No evidence is deleted automatically.
09
EXPORTExport
Generated ≠ submitted ≠ accepted ≠ audit passed ≠ legally archived.
Audit Summary PDF
Corporate A4 summary with readiness, evidence index and retention state.
Evidence Register XLSX
Evidence register for audit preparation and reconciliation.
Retention Register XLSX
Retention rules, states, expiry calculations and deletion-review flags.
Response Index XLSX
Request-specific disclosure index.
Integrity Manifest JSON
Portable integrity, gaps, requests and boundary manifest.
Complete Evidence ZIP
Complete browser-local evidence binaries plus integrity manifest.
Evidence Gap Report PDF
Detailed gap and reconciliation report on the corporate A4 template.
Evidence Gap Report JSON
Portable gap, lineage, readiness and reconciliation record.
Audit Response ZIP
Only responsive/supporting non-sensitive evidence for the selected request.
How it works
From scattered files to a defensible evidence chain
Set the audit scope
Choose legal entity, Producer, country and reporting period.
Register evidence
Add the actual files and record issuer, dates, references and claims.
Build lineage
Preserve supersession and the upstream engine that produced or sourced each record.
Apply retention
Calculate PPWR 5/10-year rules only where applicable; keep unverified national periods unresolved.
Verify integrity
Fingerprint retained bytes and separately assess provenance and issuer evidence.
Record the request
Capture the requesting body, legal route, reference, claims, period and controlling deadline.
Detect gaps
Find missing files, hashes, provenance, unresolved retention and quantity conflicts.
Apply holds
Block deletion review for investigations, disputes, corrections or other preservation needs.
Generate the response
Create an evidence register or a minimized request-specific response package.
Natural questions
Audit and evidence retention answers
How long must PPWR records be kept?
For PPWR technical documentation and the EU Declaration of Conformity, Regulation (EU) 2025/40 uses five years for single-use packaging and ten years for reusable packaging from placing on the market. Other EPR, tax, PRO and commercial records may follow different rules.
Does the five-year PPWR rule apply to every EPR invoice and declaration?
No. The PPWR technical-document retention rule must not be generalized to unrelated national EPR, PRO, tax or accounting records.
Do I have ten days to answer every EPR audit?
No. The ten-day PPWR logic belongs to the relevant reasoned national-authority technical-document request route. Other requests use their own controlling deadline.
Does SHA-256 prove a document is authentic?
No. It proves integrity of the retained bytes when compared with the recorded fingerprint. Authenticity and issuer provenance require separate evidence.
Can I delete evidence when the calculated retention period expires?
Not automatically. Expiry only triggers human review. Open audits, holds, corrections, unresolved rules and other obligations may still require preservation.
What should an EPR audit file contain?
It should link each claim to its supporting registration, representation, PRO, packaging, reporting, payment, technical and correspondence evidence, with dates, versions and provenance.
Should I send my entire archive to an authority or PRO?
Normally the response should be scoped to what was actually requested. The engine distinguishes responsive, supporting, potentially irrelevant and sensitive-review evidence.
What happens after a corrected declaration?
The superseded declaration should remain linked to its replacement so the historical evidence chain explains what was filed, corrected and relied on at each point in time.
Does a generated Audit Response ZIP mean the authority accepted my response?
No. Package generation is only preparation. Submission and acceptance require real external evidence.
Is this browser archive a legally qualified electronic archive?
No. The public engine is a browser-local evidence management utility. It does not claim WORM, qualified trust-service or legally certified archive status.