Compliance does not end when the invoice is transmitted. Article 233 of the VAT Directive requires the authenticity of the origin, the integrity of the content and the legibility of an invoice to be ensured from the point of issue until the end of the storage period — a window that in some Member States runs for eleven years, and in Austria for twenty-two where immovable property is involved. Transmission is a moment. The archiving obligation is a decade-long commitment, and it is the part of the mandate that no clearance platform discharges for you.
It is also the part that ViDA does not harmonise. Article 247 continues to leave the retention period to each Member State, and national rules on what format the archive must hold, whether you may convert it, and where the servers may sit remain divergent. By 2030 you will send one standardised invoice and store it under 27 different rulebooks.
Four things to archive, not one
The most common design error is treating the archive as a place to put the invoice file. The obligation is composite. Four distinct artefacts have to survive:
- The invoice in its original format. Not a rendering, not an extract into your ERP tables, not a PDF print — the file as issued or received.
- The means of rendering it legibly for the whole period. Legibility is a standing requirement, not a property of the file.
- The evidence that authenticity and integrity were ensured. Where a qualified electronic signature or EDI was used, that evidence is a separate object with its own storage requirement. Several jurisdictions have been explicit that the data establishing authenticity of origin and integrity of content must be preserved alongside the invoice, not merely referenced.
- The audit trail linking invoice to supply. Article 233(1) offers business controls creating a reliable audit trail between the invoice and the supply as the default route to authenticity and integrity, with a qualified electronic signature and EDI as named alternatives. If you have chosen business controls — as almost everyone has — the audit trail is your compliance evidence.
Systems that store only the first item are common. They pass a superficial review and fail the moment an auditor asks how you knew the invoice came from the supplier it claims.
The original-format trap
Two operations regularly destroy compliance without anyone noticing: printing and converting.
Printing and deleting the file. Whether you may print an electronic invoice and delete the electronic original has historically differed sharply across Europe. In a comparative mapping of 22 European jurisdictions carried out in the mid-2010s, it was permitted in Austria, Croatia, the Czech Republic, Finland, Greece, Romania and the United Kingdom, and prohibited in Cyprus, France, Germany, Ireland, Latvia, Malta, the Netherlands, Poland, Portugal, Spain, Sweden and Switzerland, where the electronic original had to be retained. France added a specific consequence worth understanding on its own terms: a recipient who prints an electronic invoice and deletes the file may do so, but the document then ceases to count as an electronic invoice on the recipient’s side. Italy reached the same result by a different route, permitting it only where the recipient had declined to accept electronic invoices in the first place.
Converting to a storage format. Migrating an archive to a new format is normal IT hygiene and a compliance hazard. The recurring national formula was that conversion is allowed provided both the original format and the converted version are archived, stored under the same index, with the original identifiable as such. Several jurisdictions did not permit conversion at all: Sweden required the original data format to be maintained, Latvia permitted only the same format, Portugal required archiving in the original format to preserve all original elements.
France ran the most distinctive rule of the set: electronic invoices archived in the original format for three years, after which other formats become permissible, within an overall retention period of ten years. Two clocks, not one — a design that no generic archiving product handles by default.
Retention periods are not harmonised
The VAT Directive sets the obligation; Member States set the duration. The spread below is drawn from that same mid-2010s comparative mapping, and national tax codes have moved since — treat it as evidence of how wide the divergence runs and how it is structured, not as a current compliance table. Verify every line against national law before configuring a retention policy.
| Jurisdiction | Retention period as documented |
|---|---|
| Greece, Hungary, Poland | 5 years (Hungary: 8 years for accounting purposes) |
| Cyprus, Finland, Ireland, Malta, United Kingdom | 6 years (UK: HMRC may agree a shorter period on application) |
| Austria, Belgium, Netherlands, Sweden | 7 years (Austria: 22 years for immovable property; Belgium: 15 for investment goods; Netherlands: 10 for real estate and electronic services; Sweden: 10 under the accounting act) |
| Czech Republic, France, Germany, Italy, Latvia, Portugal, Romania, Spain, Switzerland | 10 years |
| Croatia | 11 years |
Note the second axis of divergence, which matters as much as the number: the start date. Some countries count from the end of the year of receipt, some from the year the invoice relates to, some from the year in which the tax return is filed, and Belgium from the first day of the year following issue. A single global retention setting of “ten years from document date” will be simultaneously over-compliant and under-compliant depending on the jurisdiction.
Where the archive may sit
Storage location is a third divergence, and it is the one that constrains cloud architecture. The Directive permits storage anywhere provided the authorities have access, but Member States attach conditions, and in the same survey those conditions ranged across at least four models: no notification required provided online access is given; prior notification to the tax authority; storage restricted to countries with a mutual tax assistance treaty; and prior authorisation. Portugal required authorisation; Romania required notification by registered mail a month before outsourcing and limited storage to treaty countries; the United Kingdom permitted storage anywhere in the world provided the records could be produced to HMRC on request.
The practical implication is that “we use a European cloud region” is not an answer. The questions are whether the specific Member State requires notification, whether it restricts the country, and whether your provider can give a tax auditor online access to the archive rather than exporting a copy on request.
Legibility across a decade
Legibility is where structured invoicing creates a problem that paper never had. An XML file is not legible in the sense the Directive means; it requires a rendering mechanism, and that mechanism has to work for the full retention period. Archiving requirements historically demanded that visual inspection remain possible and that analysis functions on the electronic data remain unchanged — meaning both human readability and machine queryability have to survive.
Three specific risks follow.
Stylesheet drift. If legibility depends on an XSLT stylesheet or a viewer application, that dependency is part of the archive. Storing the XML and losing the transform leaves you with a file no auditor can read.
Hybrid formats. Where an invoice combines a PDF rendering with embedded structured data, the two components can disagree. The archive has to record which one is the original and legally authoritative version — a point several national rules made explicitly in the context of format conversion, requiring that it be clear which version is the original.
Platform dependence. Where a national clearance platform holds a copy of your invoices, that is the authority’s record, not your archive. Retention obligations sit on the taxable person. Some platforms do not retain documents beyond a short window at all, and none of them assume your storage obligation.
The audit trail is the deliverable
Where authenticity and integrity rest on business controls rather than signatures or EDI, the control itself is what an auditor examines. The canonical control is matching the invoice against the underlying business documents — the purchase order, the goods receipt, the contract — so that a reliable link exists between the invoice and the supply it evidences.
Two nuances from national practice are worth carrying.
First, documentation requirements differ from evidence requirements. Some jurisdictions required evidence to be stored where EDI or electronic signatures were used, while imposing no obligation to document the business controls themselves. Others required detailed process documentation, kept up to date, particularly where paper invoices were scanned and the originals destroyed. If you operate across both, document regardless: the cost is low and the alternative is reconstructing a control environment years later.
Second, a weak control does not automatically cost you the deduction. Austria’s position was that insufficient business controls have no impact on input VAT recovery provided the incoming invoices are correct — the control failure and the substantive entitlement are separate questions. That is a jurisdiction-specific answer rather than a general principle, and it is exactly the kind of nuance that gets lost when a group applies one global archiving policy.
What ViDA changes, and what it leaves alone
Three shifts under the European standard framework and Council Directive (EU) 2025/516 affect the archive.
Recipient acceptance is being dismantled. Acceptance by the recipient has been a fixture of electronic invoicing since Article 232 was written, and national practice on how it could be given — tacitly, by conduct, by written contract, or by a written statement that silence counts as consent — was a live source of divergence. From 1 July 2030 the replaced Article 232 provides that issuing an EN 16931-compliant electronic invoice to a taxable person or non-taxable legal person is not subject to acceptance by the recipient. Invoices in other standards or other electronic formats still are. The consequence for archiving is that “we never agreed to receive electronic invoices” stops being a defence for holding paper.
The default flips. The replaced Article 218 provides that invoices shall be issued as electronic invoices, with Member States able to accept paper or other electronic formats only for transactions outside the digital reporting obligations. Archives that were designed around a paper-primary, electronic-exception model have that assumption inverted.
Correction references become archive keys. The new Article 226 point (16) requires a corrective invoice to carry the sequential number of the invoice it corrects. That turns the original invoice number into a reference that must remain resolvable inside the archive for as long as corrections are possible — which is a retrieval requirement, not just a storage one.
What ViDA does not do is harmonise retention. Article 247 is untouched by the reform, national periods and start dates continue to apply, and the ten-year record-keeping obligations ViDA does introduce — for platforms under Article 242a and under the transfer-of-own-goods scheme — sit alongside national VAT retention rather than replacing it.
A working checklist
- Store the original file, byte-identical, for every invoice issued and received. Whatever else you do, this is recoverable from; nothing else is recoverable without it.
- Record the retention period and its start rule per jurisdiction, not per company. The start date varies as much as the duration.
- Store authenticity evidence as a first-class object. Signature validation data, EDI acknowledgements, transmission receipts and platform identifiers belong in the archive, indexed to the invoice.
- Version-control your rendering. Keep the stylesheet or viewer alongside the data, and test rendering of old documents whenever the archive platform changes.
- Treat format migration as a compliance event. Where conversion is permitted at all, keep both versions under the same index and mark the original unambiguously.
- Check storage location rules before choosing a region, and confirm the provider can grant a tax auditor online access rather than a data export.
- Do not rely on a clearance platform as your archive. Pull your own copy at the point of clearance and store it yourself.
Frequently asked questions
Can I print an electronic invoice and throw away the file?
In several Member States, no — the electronic original must be kept. Where it is permitted, there can be a consequence beyond the file: in France, a recipient who prints and deletes loses the document’s status as an electronic invoice on their side. Check the specific jurisdiction; this is one of the widest divergences in the whole area.
Does the clearance platform’s copy satisfy my archiving obligation?
No. The obligation to store copies of invoices issued and received sits on the taxable person under the VAT Directive. A tax administration’s platform holds the authority’s record for the authority’s purposes, sometimes only briefly, and does not discharge your retention duty.
How long must I keep e-invoices in the EU?
There is no single answer. Article 247 leaves the period to Member States, and documented national periods have ranged from five to eleven years, with longer periods for immovable property and investment goods, and different rules on when the clock starts. ViDA does not change this.
Is a digital timestamp required?
Almost nowhere, with Italy the notable exception — its rules required a digital timestamp on the electronic files for each filing period, applied within a set window after the tax return. Elsewhere timestamps have generally been optional, though useful as evidence of integrity. As with everything in this area, confirm the current national position.
What actually counts as an adequate audit trail?
A reliable link between the invoice and the supply. In practice that means matching the invoice to the order, the goods receipt or the contract, in a process you can describe and demonstrate. Article 233 does not prescribe a technique — it prescribes an outcome — which is why the process documentation matters more than the tooling.