← All guides · How-to & workflow
Archiving e-invoices: which files to keep, and why the XML is the record
By the Ingenious AI team · Published 14 November 2026 · Reviewed 14 November 2026
Convert an invoice free
Put this guide into practice now: convert one invoice free — validated UBL 2.1 XML plus a Factur-X PDF, with the acceptance checker for your client’s country. See pricing for bulk conversion, country rule packs and monitored clients.
Short answer
Archive each invoice as a set: the UBL XML (the operative structured record your client's system booked), the Factur-X PDF (the human-readable twin, generated from the same data), the acceptance verdict for its date and buyer, and the delivery evidence where a channel provides one (the Qvalia confirmation for Peppol sends). File the set under the invoice number, reconcile the sequence monthly, and never edit an archived document — corrections travel as new documents (381/384).
What is the record of an e-invoice?
The record is the structured document itself. In mandate countries the structured invoice is the operative artefact — in Italy's model, per the mandate table, 'a plain PDF is not an invoice' — so the XML is what must be preserved as issued, with the Factur-X PDF as its identical-content readable form. This product generates both from one validated dataset per conversion, which is what makes archiving the pair a complete record rather than two partial ones.
Why the XML, not the printout, is the original
Every prior era archived the visible artefact: the paper, then the PDF. Structured invoicing inverts the hierarchy — the data is the invoice, and every rendering (the Factur-X page, a portal's preview, your accounting tool's display) is a view of it. When a figure is questioned, the XML settles it, because the XML is what the client's system validated, booked and paid against. An archive holding only printouts holds pictures of evidence.
The inversion has a practical corollary: file formats matter. XML is plain text — readable by any tool, in any decade, with no proprietary viewer. The structured archive is therefore more durable than the paper one it replaces, provided the files are kept as generated: unedited, un-renamed in ways that break their link to the invoice number, and backed up like the financial records they are.
The complete set: four artefacts per invoice
One: the UBL XML, exactly as generated and sent. Two: the Factur-X PDF from the same conversion — the readable twin whose embedded XML is byte-identical, so the set is internally provable. Three: the acceptance context — the conversion's verdict for that invoice's date, buyer country and size — which records why the structured form was (or was not yet) the operative one. Four: delivery evidence where the channel issues it — the Peppol confirmation from your Qvalia account, platform acknowledgements where they exist.
Most queries an invoice ever attracts are answered by one of the four: What was billed? (PDF/XML.) What did their system book? (XML.) Was structured required? (Verdict.) Did it arrive? (Confirmation.) An archive that holds the set answers in minutes, from the record, without archaeology through inboxes — which is where invoice evidence traditionally goes to be lost.
The never-edit rule and the document family
An archived invoice is immutable. Errors are not corrected in the file; they are corrected in the record — by a credit note (381) that reverses value or a corrected invoice (384) that supersedes the document, each with its own number, date and archive set. The sequence then reads as history: original, credit, reissue — every state preserved, every figure traceable, no silent overwrites for an auditor to find and wonder about.
This discipline is what makes the structured archive trustworthy in a way a folder of editable documents never is. It is also cheap: storage is not the constraint, and the converter's per-conversion artefacts are already separate files. The rule costs nothing but the refusal to take the shortcut — edit nothing, append documents, let the sequence tell the story.
Sequence reconciliation: the monthly ten minutes
Once a month, reconcile the archive against the sequence: every invoice number in the period present with its set, every credit and correction present and paired to its original, every delivery confirmation filed for channel-sent invoices. Gaps found in the month they occur are clerical; gaps found at audit are suspicious. The reconciliation also produces the population your accountant's exports draw on — completeness there is completeness everywhere.
Agencies on Team workspaces hold this as a shared duty with shared visibility; solo suppliers hold it as a calendar habit. Either way the metric is the same: the archive can reproduce, for any invoice number, the complete story — data, document, verdict, delivery — on demand. If it can, your record-keeping has quietly become better than most of your clients'. If it cannot, the reconciliation names the missing set while the trail is still warm.
Retention: keep the structured set as long as the liability
Retention periods for invoices are set by your jurisdiction's tax law — your accountant owns the number for your case — and the structured set should be retained for that full horizon in its original form. The good news is that the set is small, text-based and self-describing: a decade of a small firm's invoice XMLs is a trivial storage footprint, and the Factur-X PDFs keep the archive human-readable without any conversion tooling.
Plan for the archive's own survival as you plan for any records: the files live in your business storage with the same backup discipline as your accounts, not solely inside any single tool's account. Tools change; obligations persist. The firm that can produce a ten-year-old invoice's complete structured set on request has nothing to fear from the question — and in the mandate era, the question is increasingly asked by systems, which accept only the real artefact in reply.
Archiving discipline in 5 steps
- File the set per invoice number: UBL XML, Factur-X PDF, acceptance verdict, delivery confirmation where issued.
- Never edit an archived document — corrections and credits are new documents (384/381) with their own sets.
- Keep the pair provably paired: the PDF's embedded XML is byte-identical to the XML file; archive them together.
- Reconcile the sequence monthly: every number present, every credit paired, every confirmation filed.
- Retain the full set for your jurisdiction's full tax horizon, in your own backed-up storage — not only inside a tool.
Worked example: the query that took four minutes
Eighteen months after payment, a client's new finance manager queries invoice 2025-112, EUR 6,480.00: their system shows a different payable than their approver remembers approving. The supplier opens the archive set: the XML shows the computed payable (net EUR 6,000.00, tax EUR 480.00 on the mixed breakdown), the Factur-X PDF shows the identical page the approver saw — its embedded XML byte-identical to the filed XML — and the Qvalia confirmation shows delivery two days before the approver's own approval stamp.
The 'discrepancy' resolves as a memory of the pre-discount quote, not of the invoice. Four minutes, three artefacts, no correspondence archaeology. Archives earn their keep exactly once per query — and queries, across a business's life, are certain.
Frequently asked questions
Which file is the legal record — XML or PDF?
In the structured model, the structured document is the operative record (in Italy's formulation, a plain PDF is not an invoice at all). The Factur-X PDF is the readable twin of the same invoice — archive both, treat the XML as primary.
Can I correct an archived invoice's file if I spot an error?
No — never edit the record. Issue a credit note (381) or a corrected invoice (384) as a new document with its own archive set, leaving the original intact.
How long must I keep e-invoices?
For your jurisdiction's tax retention period — ask your accountant for the number that binds you. The structured set is small and durable; keep it for the full horizon in backed-up storage.
Do I need delivery confirmations in the archive?
Where the channel issues them (Peppol sends via your access point; platform acknowledgements), yes — they are the receipt evidence. This product never marks invoices as sent; your Qvalia confirmation is the Peppol record.
What if I only kept PDFs from before I converted?
That is the historical record you have — keep it. From conversion onward, archive the full structured set. The boundary is honest and explainable; a silent gap would not be.
Keep going
Run the free tool this guide is about: convert an invoice · acceptance checker · pricing · about EInvoice Translator · all guides
Related guides
- Invoice numbers and dates on an e-invoice: the rules that keep your sequence clean
- How to verify a Factur-X PDF really contains its XML invoice
- Exporting converted invoices to Xero, QuickBooks and CSV
- How to issue a credit note as an e-invoice (type code 381)
- Do structured e-invoices get paid faster? The mechanisms, honestly stated