GoBD, short for Grundsätze zur ordnungsmäßigen Führung und Aufbewahrung von Büchern, Aufzeichnungen und Unterlagen in elektronischer Form sowie zum Datenzugriff, is the German tax authority's binding standard for keeping and storing electronic accounting records. It requires that invoices, remittances, and ledger entries stay unaltered, timestamped, and traceable, and that auditors can access the underlying data in machine readable form for up to ten years.
GoBD is administrative guidance issued by Germany's Federal Ministry of Finance (BMF) that interprets existing tax code for the digital age. It is not a standalone law; it is the standard a Betriebsprüfer (tax auditor) applies when reviewing how a company creates, stores, and grants access to its electronic books and records. It applies to any business obligated to keep tax relevant records in Germany, regardless of whether that data lives in an ERP, a dedicated accounting package, or an AR platform handling cash application and collections.
For an AR team, GoBD translates into a short list of concrete obligations:
Every deduction write-off, dunning letter, or reconciliation adjustment touches tax relevant data, whether a person or a system performed it. Automating these steps does not remove the obligation; it raises the bar: the system has to leave the same quality of evidence a careful human clerk would.
AI matching engines add a specific wrinkle. GoBD's traceability principle covers algorithmic decisions as well as manual ones, so a system that flags a deduction or auto-matches a payment needs to be able to show why, not just report a confidence score. This becomes more visible as teams push to lower DSO, since faster exception handling and more automated write-offs are exactly the transactions an auditor is likely to sample.
Vendors touching invoices, remittances, or ledger postings should be evaluated against a few concrete capabilities:
This is where document capture and matching layers like DocSense and ClearMatch matter in practice: they need to preserve the original invoice image and remittance data untouched while continuously improving match accuracy, and modules like CollectPulse need the same discipline for dunning history. Built correctly, GoBD compliance is a byproduct of good audit design, not a separate project bolted on afterward.
It applies to any business obligated to keep tax relevant books and records under German law, including foreign companies with a German tax presence, and it covers whatever software they use to do it.
Invoices and accounting records generally need ten years of retention, while business correspondence and other supporting documents need six, and the data must remain readable and machine evaluable for the entire period.
GDPdU was the earlier German data access regulation for tax audits. GoBD superseded and expanded it in 2015 to also cover the proper creation and storage of digital records, not just auditor access.
Yes, as long as it keeps immutable logs of every match and reversal, preserves the original invoice and remittance data unaltered, and can explain the logic behind an automated match on request.
An auditor can reject the electronic records as insufficient evidence, which can shift the burden of proof back to the business and, in serious cases, lead to less favorable estimated tax assessments.
No. GoBD does not mandate a specific hosting location, it requires that the data stay accessible, unaltered, and exportable to German tax authorities regardless of where it is physically stored.
