GoBD Archiving for E-Invoices: Why Flattening a ZUGFeRD Destroys Compliance

The GoBD (Principles for the proper keeping and storage of books, records, and documents in electronic form and for data access) are the BMF's administrative rules that specify Sections 146 and 147 of the Fiscal Code (AO) for digital processes. They are not a law, but they bind every bookkeeper in Germany, from freelancer to corporate group. For e-invoices, one rule decides everything: the structured data record is the record to archive, and it must be archived unchanged.

The Core Rule

The BStBK FAQ states it directly: to archive an e-invoice in GoBD-compliant form, at least the structured data record must be kept unchanged, present in its original form, and meeting the requirements for immutability. Machine evaluability by the tax administration must be ensured.

In practice:

• XRechnung: archive the XML file as received or sent. That is the entire record.
• ZUGFeRD: archive the PDF/A-3 with the embedded XML intact. The structured part is authoritative; the visual layer may also carry tax-relevant content (booking endorsements, stamps) and must then be preserved too.

The Flattening Failure

The most common archiving error: an e-invoice arrives, someone prints it or converts it to a plain PDF "for the archive", and the original file is deleted. With a ZUGFeRD, conversion to ordinary PDF strips the embedded XML. What remains is a "sonstige Rechnung" in your archive, not the e-invoice you received.

Consequences in an audit:

• The archived document no longer supports the input VAT deduction you claimed
• The immutability requirement is broken: a re-generated or re-rendered file is not the original record
• Your Verfahrensdokumentation (process documentation) describes an e-invoice process that your archive contradicts

The rule of thumb: never let any transformation touch the archived record. Store what arrived, as it arrived.

The Six GoBD Requirements Applied to E-Invoices

1. Traceability (Nachvollziehbarkeit). Every booking traces back to the original record, the e-invoice file, without gaps.
2. Immutability (Unveraenderbarkeit). Once recorded, the record cannot be altered. Corrections create new records; originals stay.
3. Timeliness (Zeitgerechte Erfassung). Transactions are recorded within the statutory windows.
4. Completeness (Vollstaendigkeit). Every e-invoice in and out is archived, including the ones that failed validation and the corrections.
5. Order (Ordnung). Records are systematically organised and retrievable within a reasonable time.
6. Data access (Datenzugriff). In an audit, the tax authority gets direct data access (Z1, Z2, or Z3). Your archive must export the records in a machine-readable form on demand.

Retention Periods

Current law: 10 years for invoices and accounting records under Section 147 AO. The BMF's 26-point action plan of 16 July 2026 proposes extending retention for accounting documents to 15 years (Measure 19). Not yet law, but the direction is clear: size your archive for the longer horizon, and check that your storage contracts and media strategies actually cover it.

Two operational notes:

• The retention period generally starts at the end of the calendar year in which the record was created.
• Emails carrying e-invoices can themselves be tax-relevant (commercial correspondence). An e-invoice forwarded by email and archived only as an attachment can leave the correspondence context behind.

The Audit Access Duty

GoBD gives the tax authority three access modes:

• Z1: direct read access to your systems
• Z2: indirect access via your evaluation
• Z3: data carrier handover

In practice, Z3 dominates: you export the records and hand them over. The export must be machine-readable and evaluable. An archive that can only produce printed PDFs or screenshots fails this duty. Test your export once a year, before an auditor asks for it.

Process Documentation (Verfahrensdokumentation)

GoBD requires documented description of your systems and processes: how e-invoices are received, validated, booked, archived, and protected from alteration. For e-invoicing, the documentation should cover:

• Receipt channels (mailbox, Peppol, platform)
• Validation steps and tools (e.g., KoSIT validator)
• The archiving system and its immutability controls
• Roles and access rights
• The procedure for defective invoices and corrections

Missing Verfahrensdokumentation is itself a formal defect. In an audit it can shift the burden of proof against you even when the records are complete.

Archiving Checklist

1. Archive the original file, unchanged. No conversions, no re-renders, no prints.
2. For ZUGFeRD, keep the hybrid intact. PDF/A-3 plus embedded XML, together.
3. Log receipt metadata. Channel, date, validation result.
4. Make the archive tamper-evident. Hashing or certified archiving software; immutability must be demonstrable, not asserted.
5. Test the export annually. Z3 handover format, machine-readable, complete.
6. Keep the Verfahrensdokumentation current. Every process change updates the document.
7. Plan for 15 years. The action plan's proposal signals where retention is heading.

This material is information of a general nature and does not constitute legal or tax advice. For a specific situation, verify the current rules or consult a qualified adviser.