EU Cloud Archive BYOK
BYOK archive manifest & FR/BE/NL retention manager for invoices — upload runs via your own job
EU Cloud Storage & Invoice Archive (Benelux, BYOK)
Key Features
Archived Object (retention-tagged)
Retention-tagged archive object with an immutable audit trail (chatter log + field tracking on state, legal hold and due date). Tracks Object key, Storage target, Source document, Source attachment, Size (bytes). One-click prepare, mark mirrored, verify, destroy, set legal hold.
BYOK Cloud Storage Target
BYOK Cloud Storage Target. Tracks Endpoint URL, Bucket / Container, Path prefix, Access key (BYOK), Secret key (BYOK). One-click set ready, disable, reset to draft, view objects.
Destruction Schedule Builder
Destruction Schedule Builder. Tracks Up to date, Lines. One-click compute, destroy eligible.
Archive Mirror Run
Archive Mirror Run. Tracks Objects. One-click queue, mark mirrored, verify, reset, generate manifest attachment.
Legal Retention Rule (FR/BE/NL)
Legal Retention Rule (FR/BE/NL). Tracks Retention (years), Statutory reference, Legal hold by default.
Build Archive Mirror Run
Build Archive Mirror Run. One-click build run.
Use Cases
Screenshots
Build Mirror Run
Retention Rules
Why Choose This Module
Key capabilities BYOK storage targets: the customer supplies their own endpoint, bucket and keys. We never store or transmit documents on our infrastructure - we generate the object keys, retention manifest and the export payload; the upload itself runs against the customer's own credentials from their own job/script. Per-country retention rules seeded as data: France: 10 years for accounting books & supporting documents (Code de commerce art. L123-22 / art. L102 B LPF), 6 years for VAT/tax (art. L102 B LPF). Belgium: 10 years for accounting books (Code de droit economique art. III.86), 7 years for VAT (Code TVA art. 60). Netherlands: 7 years general (AWR art. 52), 10 years for real-estate (onroerende zaken) per Belastingdienst guidance. Retention-tagged manifest with SHA-256 fingerprint, legal-hold flag, destruction due-date and an immutable audit trail (chatter log with field tracking) recording every lifecycle transition per archived object. Mirror runs (batches) with draft -> queued -> mirrored -> verified state flow and a re-verification scan that re-hashes the Odoo source attachment against the recorded fingerprint to detect source tampering (the cloud-side copy is checked by your own tooling).
Specifications
- Compatible: Odoo 18.0 / 19.0
- License: OPL-1
- Languages: English
- Author: Pokutsoft
- Dependencies: account
- Support: support@pokutsoft.com
Update date: 2026-07-02