Every e-invoicing mandate ends the same way: with a file that has to be kept, unchanged, for years. Yet most compliance projects spend their budget on issuing and clearing invoices and treat archiving as something the ERP "already does". This guide explains what electronic invoice archiving actually requires across the EU and the GCC in 2026: how long invoices must be retained in each country, what integrity and authenticity mean in practice, when a digital signature or qualified electronic seal is needed, and where the data may physically sit. It is written for compliance officers and IT managers who need one reference before signing off an archive design.
Under the paper regime, "keeping invoices" meant a filing cabinet and a retention schedule. Under mandatory e-invoicing, the archived object is a structured data file (UBL, CII, XRechnung, Factur-X, FA(3) or a national XML), often carrying a tax-authority identifier, a hash chain or a cryptographic stamp. Tax authorities expect to be able to re-validate that file, not a PDF printout of it, years after the transaction. Three things changed at once:
If you are still mapping which mandates apply to your group, start with our complete guide to global e-invoicing compliance. This article goes one layer deeper into the retention and integrity rules that outlive the mandate itself.
The EU VAT Directive (2006/112/EC, as amended by Directive 2010/45/EU) sets the common frame that every member-state rule builds on.
Article 233 requires that the authenticity of origin, integrity of content and legibility of an invoice are ensured from the moment of issue until the end of the storage period. It leaves the method to the business, but names three that are always accepted:
The practical point is that a digital signature is one option, not a general EU requirement. What is mandatory is that you can demonstrate, for every archived invoice, which of the three methods protected it and that the protection held for the whole retention period.
The storage articles set the division of labour. Every taxable person must store copies of invoices issued and received (Art. 244). The member state decides the retention period (Art. 247) and may require that invoices be stored in the form in which they were sent or received, meaning the original structured data for e-invoices. Member states may allow storage outside their territory, but typically only if the invoices remain fully accessible online to the tax authority, and some require prior notification. The VAT in the Digital Age (ViDA) package, adopted in March 2025, harmonises the e-invoice definition around EN 16931 and introduces digital reporting from 2030, but it does not harmonise retention periods. Those remain national, which is why the table below still varies from four to ten years inside one single market.
The following table summarises the general rule for VAT invoices. Longer periods frequently apply to capital goods, real estate, open audits and suspended limitation periods, and accounting law often runs longer than VAT law. Always confirm the current statute before fixing a deletion policy; several of these figures changed within the last 24 months.
| Country | General invoice retention | Counted from | What the archive must hold / notable rules |
|---|---|---|---|
| Germany | 8 years (§ 14b UStG, since 1 Jan 2025); 10 years for books and accounts (§ 257 HGB) | End of the calendar year of issue | Structured XML must be kept unchanged (GoBD, BMF letter of 15 Oct 2025); PDF alone is not sufficient; storage in Germany or elsewhere in the EU with full remote access |
| France | 6 years for tax (LPF art. L102 B), rising to 10 years for documents whose period expires after 1 Jan 2027 (Law 2026-534 of 25 June 2026, art. 36); 10 years for accounting (C. com. L123-22) | Close of the financial year / last entry | Keep the reference invoice in the format exchanged via your PA (Factur-X, UBL or CII) plus audit-trail evidence; AFNOR NF Z42-013 / NF 461 archives are the recognised benchmark |
| Belgium | 7 years (art. 60 VAT Code); the 2022 extension to 10 years has been repealed, applying to VAT chargeable from 1 Jan 2023 (Circular 2026/C/31) | 1 January after the year of issue | Peppol BIS invoices under the 2026 B2B mandate must be stored in structured form; e-reporting from 2028 adds reported data to the audit trail |
| Poland | KSeF stores structured invoices for 10 years (art. 112aa VAT Act); beyond that, or where the tax liability is not yet time-barred, the taxpayer stores them | End of the year of issue | KSeF storage relieves the taxpayer for KSeF invoices; invoices issued outside KSeF (offline modes, B2C, foreign buyers) follow the normal 5-year rule from the end of the year the tax fell due |
| Spain | 4 years for VAT (statute of limitations); 6 years for accounting books (art. 30 Código de Comercio) | End of the filing period / last entry | Verifactu invoicing records and the forthcoming B2B mandate (from 6 Oct 2027) require tamper-evident records; see our Spain mandate guide |
| Italy | 10 years (art. 2220 Civil Code) | Date of the last entry | All B2B invoices pass through SDI, but each party must run its own "conservazione a norma" archive with digital signature, time stamp and a conservation manual |
| Netherlands | 7 years (art. 52 AWR); longer for real estate | End of the financial year | Storage abroad allowed if the tax authority keeps access |
| Portugal | 10 years (art. 52 CIVA) | End of the year | PDF invoices need a qualified electronic signature or seal from 1 Jan 2026 to be valid e-invoices |
| Hungary | 5 years for VAT; 8 years for accounting | 1 January of the year after issue | Real-time invoice reporting (Online Számla) is mandatory; e-invoicing itself is voluntary, with QES, business controls or EDI as integrity methods |
| Saudi Arabia | 6 years; 11 years for real-estate-related records | End of the tax period | XML must be kept with cryptographic stamp, UUID, hash and QR code; records must be accessible inside the Kingdom |
| United Arab Emirates | 5 years; 7 years for real estate (Cabinet Decision 74/2023, art. 3); extended during audits | End of the tax period | MD 243/2025 art. 11 requires storage "within the State"; the MoF guidelines clarify that servers abroad are acceptable if records are retrievable and reproducible for the FTA |
| Egypt | 5 years | End of the tax year | Every B2B e-invoice, credit and debit note must be digitally signed (HSM or USB token) before submission to the ETA |
Two patterns are worth drawing out. First, the EU is drifting toward longer tax retention (France) while shortening general invoice retention where paper logic no longer applies (Germany, Belgium). Second, the GCC regimes are shorter on paper but stricter on form: the Saudi and Egyptian archives must preserve the signed object exactly as cleared, which rules out "re-generating" an invoice from ERP data at audit time.
Retention periods are easy to state and hard to evidence. When a tax auditor pulls an e-invoice from 2027 in 2034, they will typically check four things.
For hybrid formats such as ZUGFeRD and Factur-X, both the PDF container and the embedded XML must be preserved; the XML is the legally relevant part. If you convert invoices to an internal format for processing, Germany's GoBD requires that both the original and the converted version are kept under one index. Printing a received e-invoice and archiving the paper is explicitly not allowed. Our XRechnung vs ZUGFeRD vs Factur-X comparison explains what each format carries and therefore what must be archived.
This is where the Article 233 method matters. A business-controls approach needs the audit trail documents and logs to survive as long as the invoice. A signature-based approach needs the signature, certificate chain and, over long periods, re-timestamping or an archive-level seal so that the signature remains verifiable after the certificate expires. Clearance regimes do part of this work for you: a Saudi invoice carries ZATCA's cryptographic stamp and a hash linking it to the previous invoice, a Polish invoice carries its KSeF number and official receipt (UPO), and a French invoice carries the lifecycle statuses exchanged through the PA. Archive those tokens with the invoice; they are the cheapest integrity evidence you will ever obtain.
Legibility means a human can read it, which for XML implies a stylesheet or viewer that renders the archived data without altering it. Reproducibility means the tax authority can receive the file in its original form within a reasonable time, and some administrations (France, the UAE, Saudi Arabia) expect machine-readable export, not screenshots.
Data-location rules are the most frequently overlooked. Germany permits storage anywhere in the EU with full remote access; the Netherlands allows storage abroad if the authority retains access; the UAE statute speaks of storage "within the State" while the Ministry of Finance guidelines accept foreign servers provided records are retrievable and reproducible for the Federal Tax Authority; Saudi sources differ on whether servers must physically sit in the Kingdom or only be accessible from it. A multinational archive therefore needs per-country location tags and, in the GCC, a documented access path from inside the country.
The question "do we need to sign our e-invoices?" has a different answer depending on where the invoice is issued and which regime governs it.
In Germany, France, Belgium, Poland, Spain, Hungary and the Netherlands, a qualified electronic signature or seal is one acceptable method under Article 233 but is not mandatory. Clearance and exchange models (KSeF, the French PA network, Peppol) typically provide equivalent evidence through platform identifiers and status messages. Many companies nevertheless apply a qualified seal at archive level, because it is the simplest way to prove integrity across the whole retention period without maintaining a bespoke audit trail for each process.
Under the eIDAS Regulation (910/2014, revised by Regulation 2024/1183), an electronic signature belongs to a natural person, while an electronic seal belongs to a legal entity; invoices issued by a company therefore use seals. A qualified seal is created with a qualified certificate on a qualified signature-creation device and carries the strongest legal presumption of integrity and origin across all member states. Where a national rule says "advanced electronic signature based on a qualified certificate" (the Directive's wording), a qualified seal from an EU trust-service provider satisfies it.
This is the question that trips up groups operating in several clearance countries. The short answer is: sometimes, partially, and never for everything.
The design consequence is simple: treat platform storage as a convenience, not as your system of record. The model-level differences between clearance, reporting and post-audit regimes are covered in our comparison of continuous transaction controls and periodic e-reporting.
Companies that archive compliantly in several jurisdictions tend to converge on the same building blocks:
Infinite's eArchive is built on exactly this pattern, with country retention profiles, qualified-seal integration and tax-authority export formats, and it is maintained alongside the mandate changes tracked in our Compliance Tracker.
There is no single EU period. The VAT Directive leaves retention to each member state, so the general rule ranges from 4 years in Spain to 10 years in Italy and Portugal, with Germany at 8 years, Belgium and the Netherlands at 7 and France moving from 6 to 10 years for tax documents whose retention expires after 1 January 2027. Accounting law frequently runs longer than VAT law.
Not in most EU countries. Under Article 233 of the VAT Directive, a qualified electronic signature or seal is one of three accepted ways to ensure authenticity and integrity, alongside business controls with a reliable audit trail and EDI. It is mandatory in specific regimes such as Egypt, for Saudi Phase 2 invoices (cryptographic stamp), for Portuguese PDF invoices from 1 January 2026 and for Italian conservation packages.
Yes, for structured invoices issued through the system. KSeF stores them for 10 years counted from the end of the year of issue, and taxpayers do not need a separate archive for those invoices during that period. After 10 years, or while a tax liability is still open, and for any invoice issued outside KSeF, the taxpayer must store the invoices themselves.
Often, but with conditions. Germany allows storage anywhere in the EU with full remote access, the Netherlands allows storage abroad if the tax authority keeps access, and the UAE Ministry of Finance guidelines accept foreign servers provided records are retrievable and reproducible for the FTA. Saudi Arabia expects records to be accessible from inside the Kingdom, and some advisers read the rules as requiring in-country servers. Check each country's rule before consolidating an archive in one region.
Germany's issuing obligation starts on 1 January 2027, Slovakia's mandate on the same day, Spain's in October 2027 and the UAE's in January and July 2027. Each of them will produce invoices that have to remain verifiable into the late 2030s. If you would like a country-by-country review of your current retention settings, integrity method and data location, or a demonstration of how Infinite's eArchive handles them, contact our e-invoicing compliance team.