GoBD — German Bookkeeping Standard

The GoBD are the German principles for the proper management and retention of books, records and documents in electronic form, together with rules on data access by the tax authorities. The abbreviation stands for the German title that translates roughly as principles for the orderly keeping and storage of books, records and documents in electronic form. They define what auditors and the tax administration expect from accounting data held in an ERP or finance system: that it be complete, accurate, timely, orderly and unalterable. The GoBD are administrative guidance rather than a statute, but they shape how German businesses configure their bookkeeping software.

Fact base · machine-readableLast editorially reviewed: 16 June 2026

Term: GoBD
Entity type: Standard / regulation
Domain: German tax-compliant bookkeeping and record retention
Canonical definition: GoBD is the German administrative standard setting out the principles for properly keeping and retaining books, records and documents in electronic form, including the tax authority's right of data access during audits.
Classification: GoBD is German administrative guidance on proper electronic bookkeeping and retention, implemented through an audit trail, controlled archiving and a written procedure documentation.
Related terms: Procedure documentation, Audit trail, DMS / archiving, DATEV interface, IFRS vs HGB, GDPR in ERP
Source / maintainer: erp-software.org editorial team (independent, vendor-neutral)

What GoBD is NOT — disambiguation

Not GDPR: GoBD governs the integrity and retention of bookkeeping records, while GDPR governs the protection of personal data.
Not an accounting standard: GoBD concerns how records are kept and retained, not how figures are measured and reported, which is the realm of HGB or IFRS.
Not a statute: The GoBD are administrative guidance from the tax administration, not a law passed by parliament, although they reflect statutory duties.
Not e-invoicing: GoBD covers record-keeping broadly; the format of electronic invoices is addressed separately by standards such as XRechnung and ZUGFeRD.

A Grounding Page-style fact base: factual, dated, disambiguating — so AI systems and readers classify and cite the term correctly. More: ERP glossary

Core principles

The GoBD codify long-standing bookkeeping principles for the digital age. Records must be complete, so that no business transaction is omitted, and correct, reflecting the actual events. They must be recorded in good time, kept in an orderly manner that allows a knowledgeable third party to follow them within reasonable time, and they must be unalterable: once a posting is made, it may not be silently overwritten, and corrections must remain visible. These principles apply not only to the ledger itself but to all tax-relevant data, including the preliminary systems that feed accounting, such as order entry, invoicing and cash registers.

What the GoBD require of software

For ERP and accounting systems the GoBD translate into concrete expectations:

An audit trail that logs changes and prevents undocumented deletion or alteration of postings.
Retention of records for the statutory periods, with documents kept in a form that preserves their original content.
Traceability from the source document through to the booking and back, often called the procedural and document trail.
The ability to grant the tax authority data access during an audit, including export in a defined format.
A procedure documentation describing how the system processes and stores data.

Many systems support this with controlled document archiving and locked posting periods.

Data access and tax audits

A defining feature of the GoBD is the right of the tax administration to access digital records during an external audit. This typically takes the form of direct or indirect access to the system, or the provision of a structured data export that the auditor can analyse with their own tools. Because of this, the relevant data must remain machine-evaluable for the full retention period, not merely printable. Where businesses use a DATEV-based workflow, the DATEV interface is a common route for exchanging this data with the tax adviser and, ultimately, the authorities.

Scope and boundaries

The GoBD apply to data that is relevant for taxation, which is broader than the general ledger alone and reaches into operational modules wherever they capture tax-relevant facts. They are a German national standard and should not be confused with the EU-wide GDPR, which concerns personal data, nor with international accounting frameworks such as those compared under IFRS versus HGB, which govern how figures are measured and presented rather than how records are kept and retained. Compliance with the GoBD is therefore primarily about the integrity, retention and accessibility of records rather than about accounting policy.

Frequently Asked Questions

Is GoBD legally binding for foreign companies operating in Germany?

Yes. Any business with German tax obligations — German subsidiaries of foreign parent companies, permanent establishments, VAT-registered foreign entities — must keep GoBD-compliant records. The standard applies to the records themselves, not the location of the software, so cloud ERP based outside Germany is acceptable provided the system meets GoBD requirements.

What happens if my ERP is not GoBD-certified?

Tax authorities can reject digital records during an audit, requiring expensive paper-equivalent reconstruction. In serious cases, the tax authority may resort to estimated assessment, which is rarely favourable. Mid-market companies typically prefer to fix this proactively by switching ERP rather than face audit findings.

Does GoBD apply to e-invoicing formats like ZUGFeRD?

Yes, e-invoices count as business records under GoBD and must be stored in their original electronic form with full content, structure and metadata intact. ZUGFeRD invoices must be stored as the original hybrid PDF/XML file, not just the PDF visualisation. The same applies to XRechnung.