All news
Regulation September 17, 2026 6 min

German deletion schedules have been wrong since 1 January 2025 — in both directions

Booking vouchers and invoices: eight years. Books, inventories and annual accounts: still ten. And the § 22 VAT records the legislator simply forgot

TL;DR

Since 1.1.2025: booking vouchers eight years (§ 147(3) AO, § 257(4) HGB), invoices eight years (§ 14b(1) UStG). Unchanged at ten years: commercial books, inventories, opening balance sheets, annual accounts — and the records under § 22(1) UStG, which the Federal Ministry of Finance expressly confirmed on 8 July 2025. Commercial letters received and sent remain at six.

What the BEG IV changed, and what it did not

The Fourth Bureaucracy Relief Act came into force on 1 January 2025 and cut the retention period for booking vouchers from ten years to eight. The same cut applies for VAT purposes to invoices. The shortened period applies first to vouchers whose period under the old law had not yet expired on 31 December 2024 — vouchers from 2014 and earlier were free in any case.

What the statute did not touch sits in the same paragraph one line above: commercial books, inventories, opening balance sheets, annual accounts, individual and consolidated accounts all stay at ten years. Commercial letters received and sent stay at six. Three periods where there used to be two, on documents that live in the same filing system.

The exception the legislator skipped

The reduction in § 14b UStG covers invoices. It does not cover the records under § 22(1) UStG — the VAT records on which those invoices rest. The Federal Ministry of Finance put this in writing in its letter of 8 July 2025: those records must still be kept for ten years.

The result is a configuration no deletion schedule written in 2023 knows about: the invoice may be deleted after eight years, the record it derives from only after ten. Keeping both on the same line of the deletion matrix means choosing one of the two errors.

  • Keeping data two years too long is not a harmless surplus: it breaches Art. 5(1)(e) GDPR, and it hits the archive holding the most personal data on customers, suppliers and staff.
  • Deleting two years early breaches the retention duty, and only becomes visible at the next audit — by which point it cannot be repaired.
  • § 147(3) sentence 5 AO suspends the period anyway for as long as the documents matter for taxes not yet time-barred. A routine that looks only at the document date destroys, mid-audit, papers that would have to be produced.
  • For e-invoices, the structured part must be kept unchanged in its original form. An archived PDF of the human-readable rendering does not discharge the duty, however complete it looks.

What to do about it now

Split the deletion schedule into the three groups — eight, ten, six — instead of one blanket period. Insert a check on audit and appeal status before every automated deletion. And date the change: a statutory amendment that obliges the controller to act should be implemented demonstrably, not silently.

The quick test on your own record is a single question: does the retention column hold a number, or does it say which document type follows which provision? If it holds only a number, the record does not describe the law but a simplification that has been wrong in both directions since 1 January 2025.

Looking for a workspace for your DPO work?

DPO Workspace is built by a certified DPO. 30-day free trial.

Start free

Related articles

Regulation
nullathe decision on a worker taken by the algorithm alone, from 23 October

A dismissal decided by the algorithm is void: from 23 October in Italy

Published in Official Gazette no. 234 of 8 October 2026 and in force since 23 October, decree no. 179/2026 provides that final decisions on the employment relationship cannot be based solely on automated processing, that the worker may request an understandable explanation, and that decisions taken in breach are void. In parallel, AI systems affecting work organisation enter the risk assessment under Article 28 of decree 81/2008. For a DPO this is the rare case where the consequence is not economic but civil, and it changes how the check is framed.

Oct 08, 2026New 8 min
Regulation
3signals that make notification due

Poland's UODO: not every breach must be notified. Public-register data on one side, PESEL, health and financial data on the other

If an invoicing system leaks only a sole trader's name, business name, tax number and registered address, already public in the business register, risk is normally unlikely. If it also leaks the national ID number, purchase details revealing health, or financial data, notification is due. Either way, the decision goes into the internal register.

Oct 05, 2026New 5 min
Regulation
120days to charge you, not to fine you

The 120 days are not the deadline to fine you: they are the deadline to charge you

Anyone who built an appeal on the authority's delay should re-read the calendar. The Court clarifies three things: the complaint procedure and the sanctioning procedure are autonomous, so overrunning the nine-to-twelve months on the complaint does not extinguish the power to fine; the 120 days are for notifying the charge, not for imposing the fine; and they run from the «definitive finding», which is not the first notice but the moment the authority can assess every element — including the hearing of your side. After the charge, only the five-year limitation period remains.

Sep 20, 2026 7 min