German law

Audit-proof archiving

Four requirements decide whether an archive holds up when a German tax auditor sits down at the table. Not one of them can be met by software on its own.

Two words worth clearing up first

Audit-proof translates the German revisionssicher. It is a term from audit practice and from the software market, not from legislation. Nobody issues an audit-proof licence, and no product can carry the property on its own, because it describes a whole procedure.

GoBD is an abbreviation you will meet in every German vendor pitch. It stands for principles published by the Federal Ministry of Finance describing how books and records kept electronically are to be maintained, stored and made accessible to the authority. They are administrative guidance rather than a statute, and they are not a certification scheme. The duties themselves sit in the Fiscal Code and the Commercial Code, where the retention periods come from.

How a sound archive is recognised

These four properties have to hold at the same time. An archive that meets three of them has not met three quarters of the requirement; it has a gap in the one place an auditor is going to look.

Unalterability

An archived document must not be changeable without the change becoming visible. What counts is not that editing is technically impossible, but that every change creates a new version while the original stays intact and retrievable.

Traceability

Every access and every change is logged: who, when, what. Without that record there is no way to demonstrate afterwards that a voucher has been untouched for years, and demonstrating it is the whole point of the requirement.

Retrievability for the full period

A voucher that cannot be found after eight years has not, in practice, been archived. Full-text search and an unambiguous link to the right file therefore belong to the requirement rather than to the comfort features.

A documented procedure

Technology alone is not enough. It has to be written down how documents enter the archive, who is responsible and how the result is checked. In German that description is called the Verfahrensdokumentation, and an auditor will ask for it by name.

The most common misconception

“We have an audit-proof system” is not a statement that carries any weight. What is sound is never the software by itself, but the combination of technical functions, organisational rules and the documentation of both.

An auditor consequently does not ask for a product name. The questions are about how a voucher reached the archive, who is answerable for that, and how it is assured that nothing has changed since. An organisation that can answer those questions has a sound procedure, whichever vendor it bought from.

Four questions, and what a good answer sounds like

A German tax audit is less formal than it sounds and more specific than most people expect. These four come up almost every time.

“How does a document get into this archive?”
A good answer names the route and the person: scanned at reception, imported from the email account, filed by the accounts team. A bad answer is that it depends.
“Who could have changed it since?”
Permissions per group and per file, and a log that answers the question instead of a promise that nobody would.
“Show me this invoice from 2019.”
Found in seconds, with its version history, and legible without the software that created it. Format matters here: PDF/A survives, proprietary formats sometimes do not.
“Where is this written down?”
The procedural documentation, kept current. Not a document written once at go-live and never opened again.

What we supply, and what stays with you

The division matters when you are choosing a system, so here it is in full rather than in a footnote.

Aktenplatz provides

  • Storage that keeps every version and surrenders none
  • A complete log of access and changes
  • Retention periods per document type, tracked automatically
  • Full-text search across scanned paper, through OCR
  • Permissions per group, file and compartment
  • Export in open formats, so the archive outlives the contract

No software can do for you

  • The rules on who files what, and when
  • The procedural documentation, and keeping it current
  • The check that a scan matches its original
  • The decision about which records are destroyed, and the authorisation for it

We help with the right-hand column, in plain language and in English. What we will not do is pretend that buying a licence settles it.

Common questions