Verfahrensdokumentation is the process documentation the GoBD, an administrative directive of the German Federal Ministry of Finance, require for every IT system that creates, processes, or stores tax-relevant data, including invoicing, cash application, and accounting. It describes the full data lifecycle from capture through archiving, the internal controls in place, and how records stay complete, unalterable, and retrievable during a tax audit.
Verfahrensdokumentation is the formal, written process documentation that the GoBD (Grundsätze zur ordnungsmäßigen Führung und Aufbewahrung von Büchern, Aufzeichnungen und Unterlagen in elektronischer Form sowie zum Datenzugriff) require from any company that uses IT systems to create, process, or store tax-relevant records. The GoBD are not a law in their own right but an administrative directive issued by the German Federal Ministry of Finance (BMF) that sets out how the tax authorities interpret the statutory bookkeeping and retention rules. It is not a single form but a documented body of evidence showing exactly how data moves through a system, from initial capture to final archiving, and how the integrity of that data is protected along the way.
There is no direct English-language equivalent. The closest analogy in English-speaking markets is internal control documentation of the kind required under SOX or general audit standards, but Verfahrensdokumentation is a specific, standalone obligation under German tax law, tied to the retention periods that apply to accounting records: generally ten years, though the Fourth Bureaucracy Relief Act (Viertes Bürokratieentlastungsgesetz, 2025) shortened the retention period for certain accounting vouchers (Buchungsbelege) to eight years.
Accounts receivable and order-to-cash processes generate a large share of a company's tax-relevant data: invoices, cash application matches, remittance advice records, dunning notices, and deductions write-offs all feed into the general ledger and, eventually, tax filings. During a Betriebsprüfung (a German tax audit), auditors are entitled to request the Verfahrensdokumentation for any system that touches these processes, including the AR platform itself.
What they are checking is not whether the numbers are correct, but whether the process that produced them is traceable, complete, and tamper-evident. A finance team that cannot show how an invoice moved from creation through reconciliation to archiving, or how a DSO calculation was derived, faces the same audit risk as one with genuinely incorrect books, even if every figure is accurate.
Auditors and the GoBD guidance itself expect four components, kept current and consistent with each other:
Because AR systems change frequently, new matching rules, new dunning cadences, new deduction reason codes, the documentation has to be treated as a living artifact rather than a one-time deliverable. An outdated Verfahrensdokumentation is one of the more common findings in a German tax audit.
AI-driven matching and decisioning add a layer of complexity to process documentation: if a machine learning model is deciding how a payment is matched or which dunning step to trigger, that logic needs to be explainable and auditable, not a black box. Platforms like Vero, ClearMatch, CollectPulse, and CashPulse are built to log the reasoning behind each match, dunning action, and deduction classification, which gives finance teams the underlying evidence needed to write and maintain the process narrative auditors expect.
In practice, this shifts Verfahrensdokumentation from a manual, retrospective exercise, reconstructed once a year for the auditor, to something closer to a byproduct of how the system already operates. Structured, explainable audit trails do not replace the written documentation GoBD requires, but they make it far faster and more reliable to produce and keep current.
Yes. Under GoBD, any company using IT systems for accounting-relevant processes is expected to maintain current process documentation, and its absence is itself treated as a compliance gap during an audit.
German tax auditors can request it at any time, not only once an audit is formally underway, so it needs to be maintained continuously rather than assembled reactively.
Generally for as long as the underlying accounting records must be retained. That is usually ten years, though the Fourth Bureaucracy Relief Act (2025) shortened the retention period for certain accounting vouchers (Buchungsbelege) to eight years.
Yes. The obligation follows the data, not the vendor, so companies using cloud-based or outsourced AR platforms still need documentation covering those systems, often with the provider's cooperation.
It increases audit risk and can lead a tax auditor to challenge the reliability of records even when the figures themselves are accurate, sometimes resulting in an estimated additional assessment.
Not exactly. The closest concept in English-speaking markets is internal control or process documentation of the kind used for SOX compliance, but Verfahrensdokumentation is a distinct, German tax-specific obligation.
