11 min read

E-Invoice Archiving Requirements in the EU and GCC: Retention Periods, Integrity and Digital Signatures Explained

E-Invoice Archiving Requirements in the EU and GCC: Retention Periods, Integrity and Digital Signatures Explained

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.

Why e-invoice archiving is now a compliance topic, not a storage topic

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:

  • The archived object changed. In Germany, for example, the structured XML part of an e-invoice is the invoice; a PDF rendering does not replace it. In Saudi Arabia, the archived XML must still carry the cryptographic stamp, UUID, hash and QR code applied at issuance.
  • The retention clocks changed. Several countries revised their periods in 2025 and 2026: Germany shortened invoice retention to eight years, Belgium reverted to seven, and France is moving tax retention from six to ten years for documents whose retention period expires after 1 January 2027.
  • Government platforms now hold copies. Poland's KSeF stores structured invoices for ten years; Italy's SDI keeps copies; UAE and French invoices flow through accredited providers. That creates a new question: does the platform's copy discharge your own obligation? In most countries it does not.

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 baseline: Articles 233 and 244–249 of the VAT Directive

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: authenticity, integrity and legibility

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:

  1. Business controls that create a reliable audit trail between the invoice and the underlying supply (purchase order, delivery note, contract, payment). This is the most common approach and the one most EDI and procure-to-pay processes already satisfy.
  2. An advanced electronic signature based on a qualified certificate (in eIDAS terms, a qualified electronic signature or, for legal entities, a qualified electronic seal).
  3. Electronic data interchange (EDI) under an interchange agreement that guarantees authenticity and integrity.

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.

Articles 244–249: who stores, where and in what form

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.

Invoice retention periods by country (EU and GCC, November 2026)

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.

CountryGeneral invoice retentionCounted fromWhat the archive must hold / notable rules
Germany8 years (§ 14b UStG, since 1 Jan 2025); 10 years for books and accounts (§ 257 HGB)End of the calendar year of issueStructured 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
France6 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 entryKeep 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
Belgium7 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 issuePeppol BIS invoices under the 2026 B2B mandate must be stored in structured form; e-reporting from 2028 adds reported data to the audit trail
PolandKSeF 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 themEnd of the year of issueKSeF 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
Spain4 years for VAT (statute of limitations); 6 years for accounting books (art. 30 Código de Comercio)End of the filing period / last entryVerifactu invoicing records and the forthcoming B2B mandate (from 6 Oct 2027) require tamper-evident records; see our Spain mandate guide
Italy10 years (art. 2220 Civil Code)Date of the last entryAll 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
Netherlands7 years (art. 52 AWR); longer for real estateEnd of the financial yearStorage abroad allowed if the tax authority keeps access
Portugal10 years (art. 52 CIVA)End of the yearPDF invoices need a qualified electronic signature or seal from 1 Jan 2026 to be valid e-invoices
Hungary5 years for VAT; 8 years for accounting1 January of the year after issueReal-time invoice reporting (Online Számla) is mandatory; e-invoicing itself is voluntary, with QES, business controls or EDI as integrity methods
Saudi Arabia6 years; 11 years for real-estate-related recordsEnd of the tax periodXML must be kept with cryptographic stamp, UUID, hash and QR code; records must be accessible inside the Kingdom
United Arab Emirates5 years; 7 years for real estate (Cabinet Decision 74/2023, art. 3); extended during auditsEnd of the tax periodMD 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
Egypt5 yearsEnd of the tax yearEvery 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.

Integrity and authenticity: what auditors will actually test

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.

1. Is this the original structured file?

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.

2. Can you prove it has not changed?

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.

3. Is it legible and reproducible on demand?

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.

4. Where is it stored, and who can reach it?

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.

Digital signatures and qualified electronic seals: when are they required?

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.

Where a signature or seal is mandatory

  • Egypt: every B2B e-invoice, debit note and credit note is digitally signed using an HSM or USB token before it is submitted to the Egyptian Tax Authority.
  • Saudi Arabia: Phase 2 (integration) invoices carry a cryptographic stamp generated with the Cryptographic Stamp Identifier issued by ZATCA; the stamp is applied by the compliant e-invoicing solution, and ZATCA clears or reports the invoice.
  • Portugal: PDF invoices exchanged B2B must carry a qualified electronic signature or seal from 1 January 2026 to count as electronic invoices.
  • Italy: the invoice sent to SDI is not signed in B2B, but the "conservazione a norma" archive package must be digitally signed and time-stamped.

Where it is optional

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.

eIDAS vocabulary in one paragraph

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.

Does the government platform archive for you?

This is the question that trips up groups operating in several clearance countries. The short answer is: sometimes, partially, and never for everything.

  • Poland (KSeF) stores structured invoices for ten years from the end of the year of issue and relieves taxpayers of a separate archiving duty for those invoices. Invoices that never entered KSeF (offline-mode invoices not yet uploaded, B2C invoices, invoices to foreign buyers issued outside the system) and any invoice whose tax liability is not yet time-barred after ten years remain your responsibility.
  • Italy (SDI) stores a copy, and the tax agency offers an optional free conservation service, but legally each party must still run or subscribe to a compliant conservation process.
  • France (PA): accredited platforms must keep evidence of their own obligations, but the taxpayer remains fully responsible for archiving the reference invoice and the audit trail. See our France post-go-live guide for the platform model.
  • UAE and Saudi Arabia: accredited service providers transmit and, in the UAE, report invoices, but legal accountability for records stays with the supplier. The Peppol five-corner model used in the UAE is explained in our UAE Peppol e-invoicing guide.
  • Germany and Belgium have no central platform at all; the archive is entirely yours.

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.

A reference architecture for multi-country e-invoice archiving

Companies that archive compliantly in several jurisdictions tend to converge on the same building blocks:

  1. One canonical archive object per invoice: the original structured file (and PDF container for hybrids), the authority tokens (KSeF number and UPO, ZATCA stamp and hash, PA statuses, Peppol transmission evidence), the business documents that form the audit trail, and the metadata needed for retrieval (country, counterparty, tax period, retention end date).
  2. Integrity protection at ingestion: a hash recorded in an append-only log and, where required or chosen, a qualified electronic seal and time stamp, with scheduled re-sealing before certificates expire.
  3. Per-country retention policies with legal-hold capability. Deletion must be blocked while an audit, limitation-period suspension or litigation is open, and documented when it finally happens. France's AFNOR guidance explicitly expects destruction to be traceable and irreversible.
  4. Data-residency controls: EU data in the EU with remote access for German and other EU authorities; GCC data either in-country or on infrastructure that can demonstrably be retrieved from inside the country; documented access procedures for each tax authority.
  5. A viewer and export path that renders XML legibly and exports original files in bulk for an audit request, including the format that the local authority expects (for example SAF-T extracts in Portugal, Poland and Romania).
  6. Separation from the ERP. ERP document storage is rarely designed as an immutable, legally compliant archive, and vendor compliance add-ons are not automatically a complete archive either; an independent e-archive layer is the usual answer.

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.

Common archiving mistakes in mandate projects

  • Archiving the PDF, discarding the XML. Common in AP departments that "already have" a document management system. In Germany, Saudi Arabia and under the Factur-X rules in France, this breaks compliance.
  • Assuming the longest period everywhere. Over-retention is not free: personal data in invoices is subject to GDPR minimisation, and some countries now shorten rather than lengthen periods. Use real per-country clocks.
  • Starting the clock from the invoice date. Almost every regime counts from the end of the year or tax period, which adds up to twelve months to the retention.
  • Relying on the platform copy. KSeF's ten years and SDI's copy do not cover offline invoices, non-KSeF invoices or open tax liabilities.
  • Ignoring certificate expiry. A qualified seal that cannot be validated in year eight is weaker evidence than a documented audit trail.
  • No exit plan from the archive provider. Retention outlives most vendor contracts; require bulk export in original format and standard metadata.

Frequently asked questions

How long do e-invoices have to be kept in the EU?

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.

Is a digital signature mandatory for e-invoices?

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.

Does KSeF archive invoices for Polish taxpayers?

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.

Can e-invoices be archived on servers outside the country?

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.

Next step: audit your archive before the next mandate goes live

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.

E-Invoice Archiving Requirements in the EU and GCC: Retention Periods, Integrity and Digital Signatures Explained

E-Invoice Archiving Requirements in the EU and GCC: Retention Periods, Integrity and Digital Signatures Explained

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...

Read More
How to Choose an EDI Provider in 2027: 10 Criteria for Companies Facing E-Invoicing Mandates

How to Choose an EDI Provider in 2027: 10 Criteria for Companies Facing E-Invoicing Mandates

Choosing an EDI provider used to be a supply-chain decision: which retailers it already connects to, how fast it onboards suppliers, what it charges...

Read More
Spain E-Invoicing Mandate: Deadlines Start 6 October 2027 as Verifactu Slips Toward 2028

Spain E-Invoicing Mandate: Deadlines Start 6 October 2027 as Verifactu Slips Toward 2028

Spain's e-invoicing mandate finally has fixed dates. On 5 October 2026 the Official State Gazette (BOE) published Order HAC/1028/2026, the...

Read More