Verfahrensdokumentation (Procedural Documentation)
The Verfahrensdokumentation is the mandatory description of all processes and systems a business uses to capture, process, output and retain tax-relevant documents and data. It makes the bookkeeping traceable for a knowledgeable third party and is a core requirement of the GoBD.
The Verfahrensdokumentation (procedural documentation) is a written, structured description of every process and IT system a business uses to create, capture, process, output and retain tax-relevant documents and data. It is meant to let a knowledgeable third party – typically a tax auditor from the tax office – trace the full path of a business transaction, from the original document to the evaluated posting, within a reasonable time. It is therefore not an end in itself but the written proof that the bookkeeping is organised in a proper, complete and unalterable way.
Legally, the Verfahrensdokumentation is required by the GoBD, the German Federal Ministry of Finance’s administrative directive on electronic bookkeeping. It is thus mandatory for virtually every business subject to bookkeeping or record-keeping obligations – regardless of size or sector. Its scope depends on the complexity of the systems in use: a sole trader with a single cash register documents less than an online retailer whose documents flow through a shop, marketplaces, an ERP system and financial accounting. If the documentation is missing or inadequate, it can weaken the evidentiary value of the bookkeeping and, in extreme cases, justify an estimated assessment by the tax office.
At a glance
- Mandatory document under the GoBD – describes how tax-relevant data and documents are created and archived
- Classic structure: general description, user, technical system and operational documentation
- The audience is the knowledgeable third party (tax auditor) – traceability is the goal
- Must be kept current, versioned and itself archived over the retention period
- Particularly relevant for replacement scanning and multi-stage ERP/e-commerce processes
What belongs in a Verfahrensdokumentation?
By common practice and the model templates issued by industry associations, the Verfahrensdokumentation is divided into four building blocks. The general description sums up what the business does, which tax-relevant processes exist and which systems are involved – it puts the remaining parts into context.
The user documentation describes the operational workflows from the employees’ perspective: how a document is received, captured, checked, posted and released, who is responsible and which controls apply. The technical system documentation documents the software in use, data models, interfaces and safeguards. Finally, the operational documentation records how day-to-day operations are organised – data backup, access protection, contingency planning and change management.
Process description and document flow
The centrepiece is the description of the document flow: where a document comes from, in what format it exists, how it enters the system, how it is coded and posted, and where it is archived audit-proof. Each stage – capture, processing, output, retention – is described so that it is understandable without verbal explanation. This is complemented by an internal control system (ICS) that sets out which checks ensure completeness and accuracy.
Why the Verfahrensdokumentation matters
The practical benefit becomes clear at the latest during a tax audit. Without a meaningful Verfahrensdokumentation, the auditor has to reconstruct the propriety of the bookkeeping themselves – which brings follow-up questions, longer audits and, in case of doubt, a more critical stance. Good documentation reverses this: it signals that processes are well thought out, controlled and traceably organised, and thus shortens the audit.
A formal defect – missing or outdated documentation – does not automatically lead the tax authority to reject the entire bookkeeping. It can, however, weaken the evidentiary value of the records. In case of serious substantive defects, for example when data flows can no longer be traced, an estimated assessment of the tax bases may be threatened. Beyond the tax obligation, the documentation acts as an organisational tool: it preserves knowledge about processes, eases the onboarding of new employees and forms the basis for audits under other standards.
The Verfahrensdokumentation in the ERP system
An ERP system bundles many tax-relevant processes in one place – order processing, invoicing, warehousing, purchasing and the handover to financial accounting. It is precisely these processes that must be mapped in the Verfahrensdokumentation: which document types the system generates, how number ranges are assigned, when documents are committed, and how the audit trail logs changes. The documentation is thus closely interwoven with the technical foundations of audit security.
The interfaces must also be described: how orders from the shop and marketplaces reach the ERP, how postings and documents are handed over to the tax adviser via the DATEV interface, and how the document reference is preserved in the process. No ERP vendor can deliver the Verfahrensdokumentation in full, because it describes the specific processes, configurations and responsibilities of the individual business. Many providers do, however, supply system descriptions and templates that feed in as a technical building block.
Documenting replacement scanning
A particularly audit-relevant case is replacement scanning: if paper documents are scanned and the originals are then destroyed, the digitisation must be described without gaps – who scans, with which device, with which controls, how visual and content-wise correspondence is ensured and how the files are archived audit-proof. Without this documented scanning procedure, destroying the originals is risky.
Distinction: Verfahrensdokumentation, GoBD and audit security
The terms are related but mean different things. The GoBD are the overarching framework – the tax authority’s principles for electronic bookkeeping, which require the Verfahrensdokumentation in the first place. The Verfahrensdokumentation is one of the means of demonstrating GoBD compliance: it is the paper that describes the processes.
Audit security, by contrast, is the technical-organisational property of the systems themselves – the unalterability of data once captured, secured through commitment, journal and audit trail. Put simply: audit security makes the data unalterable, the Verfahrensdokumentation describes how that happens, and the GoBD mandate both. All three together make up traceable, proper bookkeeping. No building block replaces another: an audit-secure system without documentation satisfies the tax authority just as little as documentation that does not match the practice actually lived.
Creation, maintenance and DACH specifics
The Verfahrensdokumentation is not a one-off project but a living document. It must be updated and versioned with every material process or system change – such as an ERP switch, a new interface or changed responsibilities. Older versions must be retained so that the version valid at the time is available for every period; the documentation itself is generally subject to the ten-year retention period. What matters is the match between description and reality: if the documentation describes processes that are not actually lived, it is worthless or even harmful.
In the DACH region, the model Verfahrensdokumentation issued by associations such as the AWV as well as by the Federal Chamber of Tax Advisers (BStBK) and DStV has established itself as a point of orientation, especially for document filing and replacement scanning. These templates are not an official form but a field-tested structure. Note that the Verfahrensdokumentation is exclusively a German tax-law requirement in the context of the GoBD; Austria and Switzerland have comparable but independent regulatory rules. For binding design in an individual case, a tax adviser or auditor should be consulted – this article does not replace legal or tax advice.
Example
Example: mid-sized online retailer with an ERP
A retailer sells through its own shop and three marketplaces and handles everything via an ERP system. The Verfahrensdokumentation describes how orders reach the ERP via an interface, how invoices with a sequential number are generated there and committed after dispatch, and how incoming supplier invoices end up as PDFs in the document archive. A section on replacement scanning stipulates that paper documents in goods receipt are digitised through a defined procedure and then destroyed.
When questions about the document flow arise during a tax audit, the tax adviser presents the versioned Verfahrensdokumentation. From it, the auditor can trace which systems are involved, who holds which permissions and how the monthly handover of postings including documents works via DATEV. Because documentation and lived practice match, the audit proceeds swiftly and without any objection to the propriety of the bookkeeping.
Frequently asked questions
Matching ERP systems
Related services
Sources
Questions about Verfahrensdokumentation (Procedural Documentation) in your ERP project?
We advise vendor-neutrally – and implement it ourselves on request.