Keep an invoice archive usable throughout daily operations
An archive is useful when a reviewer can retrieve the right original and explain its relationship to the accounts. A folder of PDFs or a successful backup does not establish that result. Missing attachments, broken identifiers and expired provider access can make stored files unusable.
Use the archive capture and retrieval worksheet to define the evidence set and test it throughout the year. This guide covers the live service. Use the separate ERP retirement guide when migrating or decommissioning a system.
The controls are recommendations. The legal record, retention period, storage conditions and any prescribed conservation process require a jurisdiction-specific decision. The finance record owner approves that decision with tax and legal support. IT operates the storage and restoration controls.
Specify the evidence set before selecting storage
For each entity and document type, identify the original structured file, required attachments, relevant acknowledgments and accounting references. Keep human-readable views where needed to interpret the transaction. Record whether a rendering is the original legal document or a convenience copy.
Germany's GoBD material distinguishes the structured invoice content from additional human-readable material with tax-relevant information. Do not discard meaningful attachments under a blanket "XML is enough" policy. BMF, 2026 GoBD, annex 33.
Define who captures each object and when. An outgoing invoice might be captured at issue, with delivery and validation evidence added later. An incoming invoice should enter the evidence set before conversion into ERP fields. Preserve failed or corrected versions where they explain the legally relevant history.
Link records without overwriting history
Give every archived business document an identity connected to the ERP transaction, legal number, issuer and external identifier. Link credits, cancellations and replacements to the original. Keep technical attempts separate from business documents so a retry does not create a second archival invoice.
Record the source system, capture time, format, size and integrity check. A checksum can help detect change, but a checksum alone cannot prove that the original transaction was lawful or correctly accounted for. Combine integrity evidence with access controls and the business audit trail.
Preserve original identifiers when suppliers change names or an ERP migration renumbers internal records. Store the new mapping alongside the old reference. A search that works only with today's supplier code can fail for an invoice issued several years earlier.
HMRC requires electronic invoice storage to preserve authenticity, integrity and legibility and to support reproduction of the original transmitted or received data. Use the applicable local requirements when defining your acceptance test. HMRC, VAT Notice 700/63, section 5.
Reconcile capture as a population
Compare issued and received document registers to the archive inventory. Check both directions. Find source documents without archive records and archive records without an explained source transaction. Reconcile by legal document identity rather than file count alone.
A business document may legitimately have several objects: XML, rendering, attachment and responses. Conversely, two identical copies of one invoice cannot compensate for another missing invoice. Keep separate counts for business documents, expected objects and successfully captured objects.
Assign missing-object cases to an owner. The integration team repairs failed capture, AP obtains missing supplier attachments and billing resolves incomplete outgoing evidence. Set internal response targets that leave time to meet the applicable legal requirements.
Work a missing-evidence exercise
Consider a synthetic month containing 100 issued invoices and ten credit notes. There are 110 business documents, each with one original structured file. Fifteen documents also require a meaningful attachment under the company's approved evidence policy. That creates 125 expected original-or-attachment objects, excluding convenience renderings and responses.
The archive reports 128 files. That headline count looks sufficient. Identity matching finds that all 110 structured files exist, but only 12 of the 15 required attachments are present. Six files are redundant convenience copies. There are therefore 122 required objects present, six additional copies and three required objects missing.
Open three missing-attachment cases. Recover the exact attachments from the approved source and confirm their document relationships and integrity evidence. The resulting archive has all 125 expected required objects. It can still contain the six explained convenience copies, making 131 files overall.
The operating control passes because the required population is complete, not because file count increased. Preserve the initial inventory, missing-case history and final reconciliation so the reviewer can reproduce the result.
Test retrieval from the reader's starting point
Choose samples by entity, period, document type, adjustment chain and older format. Start with a reference a tax reviewer or AP user actually has, such as the invoice number or ledger posting. Retrieve the original, meaningful attachments and supporting relationships without relying on the administrator who built the integration.
Open the structured content with an appropriate viewer. Check that the amount, parties and references agree with the source. Test the readable export too. A file that downloads successfully but opens as empty content has failed the retrieval exercise.
Record elapsed time as an internal service measure, without presenting it as a universal statutory limit. If retrieval requires a provider ticket, verify the contracted response and continued access through termination. Retain a usable export and index where your records obligations require independence from the service.
Rehearse restoration and permitted deletion
Restore a sample into a controlled environment and verify identifiers, relationships and integrity checks. A backup job's success message is evidence of the backup operation, not of successful restoration. Check that the restored index can find the same document chain as the live service.
Maintain a retention schedule by record category and jurisdiction. Include the start event, normal end date and approved holds. HMRC's recordkeeping notice describes record obligations and circumstances requiring original evidence. Avoid replacing that assessment with a single global deletion interval. HMRC, VAT Notice 700/21.
If a privacy request affects invoice information, route it to the privacy and record owners. Determine the applicable retention basis and any permitted restriction or deletion. Do not delete the finance original automatically because the same contact appears in a marketing system. Keep the decision and remove unnecessary copies through the approved process.
Close archive exceptions explicitly
If an original cannot be recovered, retain the incident and available evidence. Tax and legal owners decide the consequence and remediation. Do not manufacture an apparently original file from current master data or silently replace it with a newly generated invoice.
- ☐ Each evidence category has an owner and capture trigger.
- ☐ Required originals and meaningful attachments reconcile by identity.
- ☐ Corrections preserve the original chain and raw evidence.
- ☐ Users can retrieve and read older records from accounting references.
- ☐ Restoration and provider-exit access have verified results.
- ☐ Retention decisions and holds control deletion.
- ☐ Missing records have a documented consequence and resolution owner.
Keep the completed worksheet with the capture reconciliation and retrieval results. Use invoice reconciliation to align the archive population with reporting and cloud ERP data flows for access and transfer decisions.
Sources checked 17 October 2026. The BMF handbook was verified through indexed official text during a direct-access failure; confirm its current wording when approving the German retention policy.
Worksheet: Invoice archive capture and retrieval record
Copy this worksheet for each case. It records decisions and evidence; it does not determine the tax or legal treatment.
Show the worksheet
Use with the archive guide. Define legal record requirements separately from convenience copies.
Approve the evidence set
- Entity, jurisdiction, document types and record owner: ____
- Required original formats, attachments and related evidence: ____
- Legal basis, retention start/end rules and holds: ____
- Capture system, trigger and accountable operator: ____
- Provider access, export and exit conditions: ____
Reconcile capture
- Source business-document count and identifiers: ____
- Expected required-object count: ____
- Present required objects and missing cases: ____
- Convenience copies and explained extra objects: ____
- Missing-object owner, due date and recovery evidence: ____
Synthetic control: 110 business documents require 110 structured originals and 15 meaningful attachments, or 125 required objects. Initially 122 required objects plus six convenience copies produce 128 files. Recovering the three missing attachments produces 125 required objects and 131 total files.
Run a retrieval exercise
- Starting invoice or ledger reference: ____
- Retrieved original, attachment and correction-chain locations: ____
- Integrity check and readable-view result: ____
- Older-format compatibility result: ____
- Retrieval elapsed time and internal target: ____
- Restored-backup search and document comparison: ____
- ☐ Required objects reconcile by identity.
- ☐ Original and corrected histories remain distinguishable.
- ☐ A reviewer can retrieve without administrator knowledge.
- ☐ Backup restoration and provider exit have verified results.
- ☐ Retention, holds and permitted deletion have approval.
Open exceptions and consequences: ____
Record-owner acceptance and date: ____
Related on this site
- Country pages: key facts with sources
- E-invoicing matrix: country × ERP support
- All guides
Vendor documentation is cited only as an example of the level of evidence to ask for; it is not a recommendation or a ranking. This guide is general information, not tax or legal advice. Checked 2026-10-17.
Related: Glossary – abbreviations and terms used in these guides (SAF-T, Peppol, CTC, EN 16931, IFRS and more).
Page last updated: · Markdown version