GoBD-Compliant Archiving: What You Must Meet

GoBD-compliant archiving means: tax-relevant documents are stored in full, immutable, organized, and traceable for the statutory retention period – in such a way that they can be made readable and machine-evaluated during an audit within reasonable time. The GoBD letter from the Federal Ministry of Finance, last amended on July 14, 2025, is authoritative. It clarifies the statutory obligations under the Tax Code and Commercial Code.

Core Requirements at a Glance

From the GoBD, the following requirements can primarily be derived for archiving:

• Completeness: All documents subject to retention are captured – no gaps in the inventory.
• Immutability: Once archived, documents cannot be changed or deleted undetected; changes must be logged.
• Organization and findability: Documents are systematically filed and can be specifically retrieved.
• Traceability: The path of a document from receipt to archive is documented (keyword: process documentation).
• Timely capture: Documents are captured promptly, not months later.
• Format fidelity: Documents received electronically – such as e-invoices – remain in their original format.

Why the Standard File Folder Is Not Enough

A shared folder on a server or in the cloud typically does not meet the requirements on its own: files can often be overwritten, moved, and deleted without the system making these changes traceable. GoBD-oriented workflows therefore need appropriate technical protective mechanisms and clear organizational rules. webRichtung documents is the gateway for a structured document flow with upload, email import, batch processing, and archive search.

How to Implement GoBD-Compliant Archiving in Practice

1. Consolidate incoming channels: Define how documents enter the system – via email import or upload.
2. Capture promptly: The shorter the path from receipt to capture, the less that is lost.
3. Evaluate and review: documents evaluates documents and makes them retrievable again through archive search.
4. Regulate retention: Set the appropriate period and responsible process for each document type.
5. Document the process: Record your workflow in process documentation – this creates clarity for auditors and your team.

Distinction: GoBD Compliance Is an Interplay

Important to understand: a single module alone is not “GoBD-compliant” – compliance emerges from the interplay of technology and actual process. documents handles receipt, evaluation, and findability; the organizational side – complete capture, protection concept, and process documentation – remains under your control. The article Audit-Proof Archiving explains what lies behind the often-cited term “audit-proof.”

Common Mistakes in Practice

• Documents in personal mailboxes: What exists only in one email account is neither organized nor protected – and disappears during staff turnover.
• “Archive” on the file server: Without write protection, there is no immutability; every file could be swapped undetected.
• Batch capture at quarter-end: Violates timely capture and results in lost documents.
• Missing process documentation: Even a good process looks weak during an audit if no one has documented it.

If you address these four points, you create a solid foundation for GoBD-compliant archiving.

This article provides general information and does not replace legal or tax advice.