Document Management 2026: GoBD Updates, Deadlines, and E-Invoicing

Why Document Management Must Be Machine-Readable in 2026

Since July 14, 2025, legally compliant document management is no longer based on static PDF documents, but on machine-readable original files. With the second amendment to the principles for the proper keeping and storage of books, records, and documents in electronic form (GoBD), the Federal Ministry of Finance (BMF) reacted to the comprehensive e-invoicing mandate. Since January 1, 2025, all domestic companies must be able to receive and process electronic invoices. There is no transition period for this receiving obligation. This explicitly affects small business owners, landlords opting for VAT, and associations with commercial operations. The focus of archiving thus shifts from pure image information to structured datasets that comply with the European standard EN 16931.

Which Retention Periods Apply to Invoices and Receipts

The statutory retention period for accounting records and invoices has been eight years since January 1, 2025. This reduction from the previous ten years was passed with the Fourth Bureaucracy Relief Act (BEG IV) and affects the requirements under §14b UStG and §147 AO. The period always begins at the end of the calendar year in which the invoice was issued. However, annual financial statements, inventories, opening balance sheets, and commercial ledgers must still be kept for ten years. A frequently overlooked point in practice is procedural documentation: If, for example, software was introduced in 2017, the documentation for it must be kept for ten years, even if the invoices from this software can be deleted after eight years. A tension arises in consulting practice here: The Federal Chamber of Tax Consultants (BStBK) explicitly recommends applying a uniform retention period of at least ten years to minimize risks from competing regulations, such as in criminal tax law or subsidy law.

How the E-Invoicing Mandate Changes Billing from 2027

Starting January 1, 2027, companies with a prior-year revenue of more than 800,000 euros must issue e-invoices for domestic B2B transactions. The decisive year for this revenue threshold is 2026. For companies whose revenue in 2026 was below this threshold, the transition period is extended until December 31, 2027. From January 1, 2028, the comprehensive sending obligation will apply to all domestic B2B companies, regardless of revenue. Until these deadlines, billers may continue to send paper invoices or simple PDF files, provided the recipient agrees. A permanent exception exists for small business owners under § 19 UStG: They remain exempt from sending structured e-invoices but are still subject to the receiving obligation. EDI procedures can continue to be used beyond 2028, provided a correct reporting dataset according to the Value Added Tax Act can be extracted from the EDI invoice.

What the July 2025 GoBD Update Means for Archiving

If companies create their invoices electronically via an invoicing system, the second GoBD amendment states that it will be sufficient in the future to be able to generate an identical copy of the invoice on demand. Additional storage as a PDF or on paper is no longer necessary. For hybrid formats like ZUGFeRD, the retention of the structured data part, i.e., the XML file, is primarily decisive. The PDF file only needs to be kept if it contains additional, tax-relevant information such as booking notes. There are also simplifications for payment receipts: Receipts from card terminals only need to be archived if they serve as a booking receipt or are the sole basis for billing. Purely technical receipts without tax relevance are not subject to the archiving obligation. It remains important: A system alone does not establish GoBD compliance. An up-to-date, understandable, and verifiable procedural documentation is mandatory, which must be updated with every process change, while old versions must be preserved.

How an AI-Supported System Automates Accounting

A modern document and accounting system turns a pure document archive into largely automated, DATEV-compatible accounting. The process runs from receipt to booking without media breaks: Documents are read via OCR and AI vision, which also includes handwritten notes. The system creates a finished booking proposal including accounts, splits, and tax keys. A safety net of four sources is used: rigid rules, booking history, machine learning, and large language models. An orchestrator decides in three stages whether a receipt is booked automatically, submitted for review, or processed manually. Nothing is waved through blindly. Every confirmed or corrected booking trains the system, measurably increasing the proposal quality per creditor. Data sovereignty is maintained as the models run via EU endpoints such as Vertex AI or Azure. Users can ask questions directly to the archive. A question about the amount of back payments to the pension insurance from the previous year is answered in seconds, including a source link to every relevant notice. The entire process is GoBD-compliant, has procedural documentation, and is audit-proof up to the DATEV export.

How Retention Obligations and GDPR Deletion Rules Align

In the event of a conflict between the GDPR deletion obligation and tax retention periods, the retention obligation takes precedence. Article 17 (3) (b) GDPR explicitly states that there is no obligation to delete if processing is necessary for compliance with a legal obligation. The GDPR does not specify fixed periods but requires deletion as soon as the purpose of processing ceases to apply. In practice, this means: Documents must be kept for the duration of the eight- or ten-year period but should be blocked for other purposes. After the statutory retention period expires, the deletion obligation takes effect immediately, and the data must be removed from the systems.