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.
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.
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.
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.
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.
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.
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.
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.
“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.
A German tax audit is less formal than it sounds and more specific than most people expect. These four come up almost every time.
The division matters when you are choosing a system, so here it is in full rather than in a footnote.
Aktenplatz provides
No software can do for you
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.