---
title: "GoBD-compliant archiving: What you need to fulfill"
description: "What GoBD-compliant archiving means: immutability, completeness, traceability – and how to implement the requirements in practice."
type: "wissen"
product: "documents"
slug: "gobd-konforme-archivierung"
source_language: "de"
target_languages: ["de", "en", "es", "pl", "tr"]
published: "2026-06-10"
status: "publish"
faq_json: [{"q":"What does GoBD-compliant archiving mean?","a":"Tax-relevant documents are retained completely, immutably, in an orderly manner, and traceably over the statutory period – and can be found within a reasonable time and machine-evaluated during an audit."}, {"q":"Is a normal cloud folder enough for GoBD compliance?","a":"Usually not on its own: ordinary folders do not protect against overwriting or deletion. GoBD-oriented archives secure immutability technically, for example via Object Lock."}, {"q":"Which documents are affected by GoBD archiving?","a":"All tax-relevant documents, for example invoices, accounting vouchers, contracts with tax significance, business letters, and corresponding e-mails including attachments."}, {"q":"What is a procedural documentation?","a":"A description of how documents are created, processed, filed, and protected in your company. It makes the process traceable for auditors."}, {"q":"Are the GoBD a law?","a":"No, the GoBD are a letter from the Federal Ministry of Finance that specifies the administrative interpretation of existing statutory obligations from the Fiscal Code and the Commercial Code."}]
language: "en"
source_id: "wissen/gobd-konforme-archivierung"
source_hash: "259ab7eff4290385930839b495e3b2ccdef26ee7e8bd6deb3fee0fd270fc7b5a"
---

GoBD-compliant archiving means: tax-relevant documents are stored completely, immutably, in an orderly manner, and traceably over the statutory retention period – in such a way that they can be made readable and machine-evaluable within a reasonable time during an audit. The decisive factor is the GoBD letter from the Federal Ministry of Finance, which specifies the statutory obligations arising from the Fiscal Code and the Commercial Code.

## The core requirements at a glance

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

- **Completeness:** All documents subject to retention are captured – no gaps in the records.
- **Immutability:** Once archived, documents cannot be changed or deleted unnoticed; changes must be logged.
- **Order and findability:** Documents are stored systematically and can be retrieved in a targeted manner.
- **Traceability:** The path of a document from receipt to archive is documented (keyword: procedural documentation).
- **Timely capture:** Documents are captured promptly, not only months later.
- **Format fidelity:** Documents received electronically – such as e-invoices – are preserved in their original format.

## Why the normal file folder is not enough

A shared folder on the server or in the cloud usually does not meet the requirements on its own: files there can be overwritten, moved, and deleted without anyone being able to trace it. GoBD-oriented systems therefore rely on technical write-protection mechanisms. In [webRichtung documents](https://www.webrichtung.de/module/documents/), this is handled by a GoBD archive with Object Lock: archived documents are locked against overwriting and deletion for 6, 8, or 10 years – matching the respective retention period.

## How to implement GoBD-compliant archiving in practice

1. **Consolidate intake channels:** Define how documents enter the system – a scanner for paper, e-mail import for digital invoices, upload for the rest.
2. **Capture promptly:** The shorter the path from receipt to capture, the less gets lost.
3. **Classify and check:** documents reads every document during processing, classifies it, and shows you the result for review – including filters by type, date, and amount.
4. **Archive with a deadline:** Completed documents move into long-term retention; the archive storage is included in the current model.
5. **Document the process:** Record in a procedural documentation what your workflow looks like – this creates clarity for auditors and for the team.

## Distinction: GoBD compliance is an interplay

Important to understand: software alone "is" not GoBD-compliant – compliance arises from the interplay of technology and a lived process. A good archive system takes care of the technical requirements for you (immutability, logging, findability); the organizational side – complete capture, procedural documentation – is up to you. What lies behind the often-mentioned term "audit-proof" is explained in the article [Audit-proof archiving](/en/wissen/revisionssichere-archivierung.html).

## Typical mistakes in practice

- **Documents in personal mailboxes:** What lies only in one mail account is neither orderly nor protected – and disappears when staff change.
- **"Archive" on the file server:** Without write protection there is no immutability; any file could be swapped out unnoticed.
- **Batch capture at the end of the quarter:** Violates timely capture and produces lost documents.
- **Missing procedural documentation:** Even a good process appears weak during an audit if no one has described it.

Those who address these four points have covered the largest part of the path to GoBD-compliant archiving.

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