Archiving Structured E-Invoices the GoBD Way: The Eight-Year Question

The debate around e-invoicing mostly turns on issuing and receiving. The quieter but longer-lived obligation only begins afterwards: retention. A structured invoice is not a document in the classic sense but a data set, and it must remain unalterable and machine-readable for years. Building that into your processes from the start avoids costly rework later.

What changed about the retention period

For a long time, accounting records had to be kept for ten years. Germany’s Fourth Bureaucracy Relief Act (BEG IV) shortened this to eight years as of 1 January 2025. The new period applies to all records whose previous ten-year period had not yet expired at that point.

Two qualifications matter. First, the reduction covers accounting records such as invoices, receipts and payment vouchers. Annual financial statements and the procedural documentation stay at ten years. Second, the shorter period is not purely a relief: being allowed to delete records after eight rather than ten years means the deletion concept should be adjusted accordingly, also with the GDPR in mind. A blanket extension “to be safe” sits in tension with the duty not to retain personal data longer than necessary.

What “audit-proof” demands technically

For electronic records subject to retention, the GoBD essentially require three properties: immutability, complete and timely capture, and continuous availability and machine evaluability across the whole period. Immutability does not mean a file sitting in a folder nobody touches. It means subsequent changes are technically excluded or fully logged, and that the original state remains recoverable.

For structured formats a second, often underestimated, requirement is added.

A visual copy is not the data set

An XRechnung is a pure XML data set. ZUGFeRD is hybrid: a PDF with embedded XML. The decisive point: what must be retained is the structured data set, not a PDF visual copy generated from it. Anyone who prints or renders an incoming XRechnung as a PDF and archives only that image has not retained the authoritative record in a GoBD-compliant way. The original is the XML structure, and it is exactly this that must be available unchanged and evaluable for eight years.

This has consequences for the architecture. Producing a nice view on receipt is not enough. The data set must be stored in its structured form, indexed and protected against alteration. A procedural documentation records exactly how this path runs: from receipt through checking to storage.

Where this comes together in practice

From 2027 at the latest, when the structured e-invoice becomes the rule in domestic B2B traffic, three things meet: the format (XRechnung or ZUGFeRD per EN 16931), the booking in the commercial core, and audit-proof storage. In our Datargo ERP module, e-invoicing per EN 16931 and GoBD accounting are laid out as one continuous path, but the requirement itself is tool-independent: the authoritative data set must stay unchanged, evaluable and findable for the full period.

The eight-year period sounds like less effort than the old one. In substance it merely shifts the effort: away from deletion, towards clean retention of the right object, namely the data set, not its image.