DE Tax Compliance
Germany GoBD + DATEV on Odoo
Germany's GoBD (Grundsätze zur ordnungsmäßigen Führung und Aufbewahrung von Büchern, Aufzeichnungen und Unterlagen in elektronischer Form) sets the standard for digital bookkeeping integrity, audit trails, and document retention. DATEV is the platform almost every German Steuerberater (tax accountant) uses for tax filing and audit. Odoo handles both — GoBD-compliant bookkeeping built in, DATEV export ready for your accountant from day one.
Last reviewed:
What it is
Two pillars of German finance compliance handled in Odoo. GoBD (the BMF's principles for digital bookkeeping, current version 2019): immutable audit trails per transaction, no overwriting of posted entries, chronological ordering, 10-year archive, controls per § 145–147 AO. DATEV (the cooperative platform used by 90%+ of German Steuerberater): export of Buchungssätze (journal entries), Stammdaten (master data), Kostenrechnung (cost accounting) in DATEV-Format CSV/ASCII so your accountant can import into DATEV without manual re-keying. Our Odoo build covers both natively.
Why it matters
GoBD non-compliance can lead to rejection of your books in a tax audit (Betriebsprüfung), with penalties from estimation-based reassessment to criminal proceedings for serious cases. Manual DATEV handoff — finance team CSV-exporting, your accountant manually re-keying — eats 4–12 hours per month per entity in unnecessary effort. With Germany joining the EU e-invoicing trajectory (mandatory B2B e-invoicing receiving from January 2025; phased issuing through 2028), getting GoBD, DATEV, and e-invoicing all on Odoo at one go avoids three sequential rebuilds.
Features
-
Immutable audit trail per transaction
Every transaction recorded with timestamp, user, before/after state. Posted journal entries cannot be deleted or overwritten — corrections require explicit reversal-and-repost. GoBD-aligned by design.
-
DATEV export (Buchungssätze + Stammdaten + Kostenrechnung)
One-click export of journal entries, master data (customers, vendors, accounts), and cost-centre allocations in DATEV-Format. Your Steuerberater imports directly into DATEV Mittelstand or DATEV Kanzlei-Rechnungswesen.
-
SKR 03 / SKR 04 chart of accounts
German standard charts of accounts (Standardkontenrahmen 03 and 04) pre-configured. Customisation per business type while preserving the SKR structure for DATEV compatibility.
-
10-year document retention
All accounting-relevant documents archived 10 years per § 147 AO. Searchable retrieval by year, document type, transaction reference, or customer. Tax-audit-ready.
-
E-Bilanz preparation
Annual e-Bilanz (electronic balance sheet) submission data prepared in the Steuerbehörde-required XBRL format. Your Steuerberater handles submission; Odoo provides the structured data.
-
VAT (Umsatzsteuer) returns
Monthly / quarterly VAT returns (Umsatzsteuer-Voranmeldung) generated in ELSTER-compatible XML. Permanent VAT registration tracking, intra-Community supplies (Zusammenfassende Meldung), and VAT reclaim workflows.
-
EU + German e-invoicing readiness
Germany joined the EU B2G e-invoicing requirement (XRechnung format) in 2020; B2B e-invoicing receiving mandatory from January 2025; phased issuing through 2028. Odoo handles XRechnung, ZUGFeRD, and EU EN 16931 formats natively.
-
Multi-currency with Euro primary
Group entities with Euro primary plus foreign-currency dealings handled cleanly. FX gain/loss accounting per GoBD requirements; multi-currency reconciliation aligned with German VAT rules.
How it works
-
Compliance audit
Senior consultant reviews your current accounting state — chart of accounts, audit trail depth, archive setup, current Steuerberater handoff process. Output: GoBD compliance gap analysis + DATEV integration plan.
-
Odoo configuration
German localisation activated. SKR 03 or SKR 04 chart of accounts configured. Tax codes (Umsatzsteuer 19%, 7%, 0%, reverse charge, etc.) set up. ELSTER and XRechnung integrations configured.
-
DATEV interface setup
Coordination with your Steuerberater on the DATEV import workflow. Test exports validated against DATEV's expected format. Ongoing-month workflow defined: who exports, who imports, when.
-
Audit trail validation
GoBD audit trail features tested with sample transactions: timestamp accuracy, user attribution, before/after capture, archive retrieval. Compliance documentation produced for tax audit readiness.
-
User training
Finance team trained on the new GoBD-aligned workflows, DATEV export, and the new e-invoicing requirements (XRechnung for B2G, Factur-X / EN 16931 for B2B). Recorded modules for ongoing reference.
-
Steuerberater handoff
First production month — finance team exports DATEV, Steuerberater imports, both sides validate. Issues caught early; ongoing process stabilises within 1–2 months.
Deployment timeline
Single-entity German business: 4–6 weeks from green light. Multi-entity German groups: 6–10 weeks. The bottleneck is usually Steuerberater coordination on the DATEV format details — they prefer to validate before live use. For existing Odoo customers in other countries adding a German entity: 3–4 weeks.
Best for
Every German taxable business (GmbH, UG, AG, KG, OHG, sole proprietorship) where GoBD compliance and DATEV handoff are operational requirements. Particularly: businesses growing past the Steuerberater-handles-everything-in-Excel stage; multi-entity German groups consolidating Buchhaltung; multinational groups with German subsidiaries managing GoBD alongside HQ ERP; businesses preparing for the B2B e-invoicing mandate through 2028.
Frequently asked questions
-
What's GoBD and who does it apply to?
GoBD (Grundsätze zur ordnungsmäßigen Führung und Aufbewahrung von Büchern, Aufzeichnungen und Unterlagen in elektronischer Form) is the German Federal Ministry of Finance's principles for digital bookkeeping. Current version dated November 2019. It applies to every business in Germany maintaining electronic books, regardless of size or legal form. Non-compliance can lead to book rejection in a tax audit.
-
Does Odoo natively meet GoBD requirements?
Yes — Odoo's audit trail, immutability rules for posted entries, and archive retention align with GoBD requirements out of the box. The implementation work is in: ensuring your configuration enforces these (some configurations can be loosened); generating compliance documentation for a tax auditor; and integrating with DATEV for the accountant handoff.
-
Why does DATEV matter?
DATEV is the cooperative IT platform that 90%+ of German Steuerberater (tax accountants) use for tax-side accounting, payroll, and tax filings. Your accountant typically wants journal entries imported into DATEV monthly so they can do reconciliations, e-Bilanz, tax returns. Native DATEV export from Odoo eliminates manual re-keying and accountant frustration.
-
Does the e-invoicing mandate apply to all German businesses?
Yes, in phases. Since 2020: B2G transactions to federal authorities require XRechnung. Since January 2025: every German taxable business must be able to receive e-invoices in EN 16931-compliant format (XRechnung, ZUGFeRD, or Factur-X). Issuing requirements phase in 2027–2028 based on enterprise size. Odoo handles all formats.
-
What's the difference between XRechnung, ZUGFeRD, and Factur-X?
XRechnung: pure XML, German B2G standard. ZUGFeRD: hybrid PDF + XML, used B2B in Germany. Factur-X: French/German hybrid PDF + XML, increasingly interchangeable with ZUGFeRD. All three are EN 16931 compliant. Odoo generates each per buyer preference.
-
Can our Steuerberater work directly with Odoo or only via DATEV?
Both options. Some Steuerberater prefer DATEV-only — we provide clean DATEV exports monthly. Others welcome direct Odoo access for read-only reconciliation; we provide a Steuerberater user role with appropriate visibility. The choice is the Steuerberater's; Odoo supports both flows.
-
What about the Steuerprüfung (tax audit)?
Tax auditors typically request a GoBD-compliant data export (GDPdU / GoBD format) of accounting data for the audit period. Odoo generates this export natively — chart of accounts, journal entries, master data, in the BMF-prescribed format. We support multiple historical GoBD audits successfully without findings on the IT side.
-
What's the cost of implementing GoBD + DATEV on Odoo?
Single-entity German business: EUR 12,000–25,000 (USD 13,000–27,000) fixed-price. Multi-entity German groups: EUR 25,000–60,000 (USD 27,000–65,000). For existing Odoo customers in other countries adding German compliance: half to two-thirds of those numbers.
-
Will our Steuerberater agree to use Odoo?
Almost always, with the right DATEV export. The Steuerberater's main concern is workflow continuity — if they get clean monthly DATEV imports, their day-to-day doesn't change. We've onboarded with Steuerberater across Germany without resistance. The few who refused were typically retiring or stuck on non-DATEV legacy platforms.
-
Does Odoo support SKR 03 and SKR 04?
Yes — both standard German charts of accounts are pre-configured in Odoo's German localisation. SKR 03 (process-based) is typical for SME accounting; SKR 04 (account-form-based) is common in larger or specific industries. Your Steuerberater's preference determines which we use.
-
What about Lohnbuchhaltung (payroll)?
Odoo's German payroll module handles wage tax, social security contributions, ELStAM, and ELSTER submissions for payroll-related filings. For many German businesses, the Steuerberater handles payroll separately (often in DATEV LODAS) — Odoo can either run payroll natively or hand off the data to the Steuerberater's payroll system, depending on your preference.
-
What's the first step?
A 45-minute call. Bring: legal form (GmbH, UG, etc.), turnover bracket, current accounting setup, Steuerberater contact details if appropriate. We'll tell you whether discovery is worth scheduling and what the realistic project size looks like for your specific business.