What it means
A defensible archive preserves the authoritative invoice, validation artefacts, delivery evidence, status history and readable access for the required retention period.
Retention, immutability, location and accessibility rules vary by jurisdiction.
Implementation method
- 1Store the original bytes and a cryptographic hash.
- 2Retain validation versions, signatures, receipts and status transitions.
- 3Use immutable or tamper-evident controls and tested restore procedures.
- 4Provide controlled human-readable access without altering the source.
Common mistakes
Build an explicit control or test case for this condition.
Build an explicit control or test case for this condition.
Build an explicit control or test case for this condition.
Build an explicit control or test case for this condition.
Questions and answers
Is cloud storage automatically compliant?
No. You must evaluate location, access, immutability, retention, deletion and audit controls against the applicable rules.
Should validation software versions be archived?
Yes. Store enough artefact identity to reproduce why the document passed or failed at that time.
Can EInvoiceLab officially certify invoice archiving?
No. EInvoiceLab can inspect, prepare and explain technical data, but official conformance, delivery or acceptance depends on the active authority, network, accredited provider and validation artefacts.
Should I keep the original structured file?
Yes. Preserve the original XML or JSON, its hash, every validation report and the final authority or network response. A readable PDF should not replace the source document.