Odoo in Germany (2026): Is It GoBD-Compliant?

Germany — Europe's largest economy with a GDP exceeding $4.5 trillion — operates under one of the world's most rigorous accounting and tax compliance frameworks. The GoBD (Grundsaetze zur ordnungsmaessigen Fuehrung und Aufbewahrung von Buechern, Aufzeichnungen und Unterlagen in elektronischer Form sowie zum Datenzugriff) establishes strict rules for electronic bookkeeping, document retention, and audit trail requirements. Combined with the DATEV ecosystem that dominates German tax advisory, the mandatory Handelsgesetzbuch (HGB) accounting standards, and a complex payroll system with social insurance contributions exceeding 40% of gross salary, German businesses need an ERP that is deeply integrated with local compliance requirements. Odoo ERP with German localization provides this through GoBD-compliant bookkeeping, DATEV export, SKR03/SKR04 chart of accounts, and comprehensive payroll calculation.

Whether you are a Mittelstand manufacturer in Baden-Wuerttemberg, a tech startup in Berlin, a retailer in Hamburg, a logistics company in Frankfurt, or a professional services firm in Munich, this guide covers every aspect of implementing Odoo ERP for the German market.

Key Takeaways

GoBD compliance is mandatory for all German businesses using electronic bookkeeping — Odoo must ensure immutability, traceability, and proper archival

DATEV export is essential for collaboration with Steuerberater (tax advisors) — Odoo generates DATEV-compatible export files

German chart of accounts follows SKR03 (by function) or SKR04 (by nature) — Odoo includes both

German VAT (Umsatzsteuer/USt) has two rates: 19% standard and 7% reduced

German payroll involves employer social contributions exceeding 20% (health, pension, unemployment, nursing care insurance)

E-invoicing (XRechnung/ZUGFeRD) is mandatory for B2G; for domestic B2B every business must receive e-invoices since 1 January 2025 and issue them from 2027 (turnover above EUR 800,000) or 2028

Handelsregister filing and annual financial statements (Jahresabschluss) follow strict HGB requirements

Germany's Business and Regulatory Environment

Market Context

Indicator	Value
GDP (2025)	~$4.5 trillion
VAT (USt) rates	19% standard, 7% reduced
Corporate tax (KSt)	15% + 5.5% solidarity surcharge = ~15.83%
Trade tax (GewSt)	~14% average (varies by municipality — Hebesatz 200-900%)
Total corporate tax burden	~30% (KSt + GewSt combined)
Currency	Euro (EUR)
Official language	German
Fiscal year	Calendar year (January 1 – December 31) for tax; HGB allows flexible year-end
Social insurance (employer)	~20-21% of gross
Social insurance (employee)	~20-21% of gross
E-invoicing	XRechnung for B2G; XRechnung or ZUGFeRD 2.0.1+ for B2B (receive since 2025, issue 2027/2028)

Why German Businesses Need Specialized ERP

Germany's accounting compliance framework is among the strictest globally. The GoBD mandates that every booking entry must be traceable, verifiable, and unalterable — with a complete audit trail from the original document to the annual financial statements and vice versa. Any ERP system that fails to meet GoBD standards exposes the business to assessment penalties during tax audits (Betriebspruefung). Combined with the DATEV ecosystem (used by over 80% of German Steuerberater), mandatory double-entry bookkeeping, and the complex German payroll system, businesses need an ERP purpose-built for German requirements.

GoBD Compliance

What is GoBD?

GoBD is the German federal tax authority's (BMF) regulation governing electronic bookkeeping. It establishes principles that all electronic accounting systems must follow:

Core GoBD principles:

Principle	German Term	Requirement
Traceability	Nachvollziehbarkeit	Every transaction traceable from document to posting to financial statement and back
Completeness	Vollstaendigkeit	All business transactions must be recorded
Correctness	Richtigkeit	Entries must accurately reflect the underlying transaction
Timeliness	Zeitgerechtheit	Transactions must be recorded promptly (within 10 days is the general guideline)
Order	Ordnung	Systematic and logical structure of bookkeeping
Immutability	Unveraenderbarkeit	Once posted, entries cannot be deleted or altered — corrections only through reversal entries

Odoo GoBD Configuration

Odoo's German localization includes GoBD compliance features:

Immutable journal entries — once posted, journal entries cannot be deleted or modified; corrections are made through reversal entries with a new posting date
Sequential numbering — unbroken sequential numbering for all journal entries and invoices (no gaps allowed)
Document linking — every posting links to its source document (invoice, receipt, bank statement)
Audit trail — complete history of who created, posted, and modified each entry
Retention — digital archival of all accounting documents for 10 years (6 years for correspondence)
Access for auditors — GDPdU/GoBD export functionality for tax auditors (Z1, Z2, Z3 access levels)
Process documentation — system generates the required Verfahrensdokumentation describing the bookkeeping process

GoBD Audit Export

During a Betriebspruefung (tax audit), the auditor may request data access at three levels:

Access Level	Description	Odoo Support
Z1	Read-only access to the ERP system	Auditor user account with read-only role
Z2	Data export in machine-readable format	GDPdU/DSFinV-K export from Odoo
Z3	Data carrier provision	Export on USB/DVD for auditor analysis with IDEA/ACL software

Odoo generates exports in the formats required for Z2 and Z3 access, including the index.xml description file required by the GDPdU standard.

DATEV Integration

The DATEV Ecosystem

DATEV eG is a cooperative serving German tax advisors, auditors, and lawyers. Over 500,000 German businesses use DATEV through their Steuerberater. Integration with DATEV is effectively mandatory for most German SMEs.

Odoo DATEV Export

Odoo exports data in DATEV-compatible formats:

DATEV export types:

Export Type	Content	Format
Buchungsstapel	Journal entries (postings)	ASCII/CSV per DATEV specification
Debitoren/Kreditoren	Customer and vendor master data	DATEV partner format
Sachkontenbeschriftung	Account labels and descriptions	SKR03/SKR04 mapping
Rechnungsausgangsbuch	Sales invoice register	For VAT reporting
Rechnungseingangsbuch	Purchase invoice register	For input VAT

Export workflow:

Complete monthly bookkeeping in Odoo
Export journal entries in DATEV Buchungsstapel format
Export customer/vendor changes in DATEV partner format
Steuerberater imports into DATEV Kanzlei-Rechnungswesen or DATEV Unternehmen Online
Steuerberater performs tax calculations, USt-Voranmeldung, and annual return

DATEV Unternehmen Online

For businesses using DATEV Unternehmen Online (the cloud portal for document exchange with Steuerberater), Odoo can export:

Belegbilder (document images) linked to journal entries
Structured booking data for automatic import
Bank statement data for reconciliation

German Chart of Accounts (Kontenrahmen)

SKR03 vs. SKR04

Germany uses standardized charts of accounts. The two most common are:

SKR03 (Prozessgliederungsprinzip — by business function):

Organized by business process (procurement, production, sales, finance)
Most commonly used by manufacturing and trading companies
Account classes 0-9

SKR04 (Abschlussgliederungsprinzip — by financial statement structure):

Organized to mirror the structure of HGB financial statements
Increasingly popular, especially for companies reporting under IFRS alongside HGB
Account classes 0-9

Odoo Chart Setup

Account Class	SKR03	SKR04	Description
0	Fixed assets, financial assets	Fixed assets, financial assets	Anlage- und Kapitalkonten
1	Financial accounts	Umlaufvermoegen	Finanz- und Privatkonten
2	Liabilities, equity	Eigenkapital	Abgrenzungskonten
3	Inventory/materials	Fremdkapital	Wareneingangs-/Bestandskonten
4	Revenue	Revenue	Betriebliche Ertraege
5	Materials/COGS	Materials/COGS	Betriebliche Aufwendungen
6	Operating expenses	Operating expenses	Betriebliche Aufwendungen
7	Other income/expenses	Other income/expenses	Weitere Ertraege/Aufwendungen
8	Revenue/closing	Financial results	Ertraege und Aufwendungen
9	Statistical/off-balance	Closing accounts	Vortrags-/Abschlusskonten

Odoo's German localization includes both SKR03 and SKR04 with all standard account numbers, descriptions in German, and proper tax code mapping.

Key Tax Accounts

Account (SKR03)	Account (SKR04)	Description
1576	1406	Abziehbare Vorsteuer 19% (input VAT 19%)
1571	1401	Abziehbare Vorsteuer 7% (input VAT 7%)
1776	3806	Umsatzsteuer 19% (output VAT 19%)
1771	3801	Umsatzsteuer 7% (output VAT 7%)
1780	3820	Umsatzsteuer-Vorauszahlungen (VAT prepayments)
1790	3830	Umsatzsteuer laufendes Jahr (VAT current year)

German VAT (Umsatzsteuer)

VAT Rate Structure

Rate	Percentage	Examples
Standard (Regelsteuersatz)	19%	Most goods and services
Reduced (Ermaessigter Steuersatz)	7%	Food (most), books, newspapers, public transport (short-distance), hotel accommodation, cultural events, agricultural products
Zero/Exempt	0% / Exempt	Exports (steuerfreie Ausfuhr), intra-EU supplies (innergemeinschaftliche Lieferung), medical services, insurance, financial services
Reverse charge	—	Services received from abroad (Section 13b UStG)

Umsatzsteuer-Voranmeldung (VAT Advance Return)

German businesses file monthly or quarterly VAT advance returns:

Monthly: turnover > EUR 7,500 VAT liability in prior year
Quarterly: turnover EUR 1,000 – EUR 7,500
Annual only: turnover < EUR 1,000

Filing deadline: 10th of the following month (or 10th of the month after the quarter), with 1-month extension available (Dauerfristverlängerung with 1/11 special advance payment).

Odoo generates the Umsatzsteuer-Voranmeldung data in the ELSTER format for electronic submission to the Finanzamt:

KZ (Kennzahl)	Description
KZ 81	Taxable supplies at 19% (net amount)
KZ 86	Taxable supplies at 7% (net amount)
KZ 21	Tax-free supplies with input VAT deduction (exports)
KZ 41	Intra-EU supplies
KZ 46	Reverse charge supplies received (Section 13b)
KZ 66	Input VAT from invoices (Vorsteuer)
KZ 67	Input VAT from intra-EU acquisitions
KZ 83	Payable amount / refund

Zusammenfassende Meldung (EC Sales List)

For intra-EU B2B supplies, German businesses must file a Zusammenfassende Meldung (ZM) listing all intra-EU supplies by customer VAT ID. Odoo generates this data monthly or quarterly.

ELSTER Integration

ELSTER (ELektronische STeuerERklaerung) is Germany's electronic tax filing system. Odoo can export VAT return data in ELSTER-compatible format for submission through the Mein ELSTER portal or via ERiC (ELSTER Rich Client) API.

E-Invoicing (XRechnung and ZUGFeRD)

XRechnung

XRechnung is the mandatory e-invoicing standard for invoices to German federal and state government entities (B2G):

Format: XML based on EN 16931 (European e-invoicing standard)
Mandatory since: November 2020 for federal government suppliers
Submission: Through ZRE (Zentraler Rechnungseingang) or OZG-RE portals
Leitweg-ID: Unique routing identifier per government buyer

ZUGFeRD / Factur-X

ZUGFeRD (Zentraler User Guide des Forums elektronische Rechnung Deutschland) is a hybrid format combining a machine-readable XML (EN 16931 compliant) with a human-readable PDF:

Profiles: Minimum, Basic WL, Basic, EN 16931 (Comfort), Extended, XRechnung — MINIMUM and BASIC-WL do not count as e-invoices under the German B2B mandate
B2B e-invoicing: receiving mandatory since 1 January 2025; issuing mandatory from 1 January 2027 above EUR 800,000 prior-year turnover and from 1 January 2028 for everyone (see our E-Rechnung in Odoo guide)
Format: PDF/A-3 with embedded XML

Odoo E-Invoicing Support

XRechnung generation — Odoo generates XRechnung XML for B2G invoices with Leitweg-ID routing
ZUGFeRD/Factur-X — hybrid PDF+XML generation for B2B invoices
Incoming e-invoices — import and process received XRechnung/ZUGFeRD invoices
Validation — schema validation before submission
Portal submission — integration with ZRE/OZG-RE for government invoice submission

German Payroll (Lohnabrechnung)

German social insurance has four pillars, with contributions split between employer and employee:

Insurance	German Name	Employer	Employee	Total	Ceiling (West 2025)
Health (Krankenversicherung)	KV	7.3% + Zusatzbeitrag/2	7.3% + Zusatzbeitrag/2	~15.9%	EUR 66,150/year
Pension (Rentenversicherung)	RV	9.3%	9.3%	18.6%	EUR 90,600/year
Unemployment (Arbeitslosenversicherung)	AV	1.3%	1.3%	2.6%	EUR 90,600/year
Nursing care (Pflegeversicherung)	PV	1.7%	1.7% (+0.6% childless >23)	~3.4-4.0%	EUR 66,150/year
Total employer		~19.6-20.3%
Total employee			~19.6-20.9%

Zusatzbeitrag: Additional health insurance contribution that varies by Krankenkasse (health insurer) — typically 1.0-1.9%, split equally. Odoo configures the Zusatzbeitrag per employee based on their chosen Krankenkasse.

Income Tax (Lohnsteuer)

German income tax is progressive:

Taxable Income (EUR)	Rate
Up to 11,604	0% (Grundfreibetrag)
11,605 – 17,005	14% rising to 24% (linear-progressive zone 1)
17,006 – 66,760	24% rising to 42% (linear-progressive zone 2)
66,761 – 277,825	42% (Proportionalzone)
Above 277,825	45% (Reichensteuer — wealth tax rate)

Plus:

Solidaritaetszuschlag (solidarity surcharge): 5.5% of income tax (only for higher earners since 2021)
Kirchensteuer (church tax): 8% (Bavaria, Baden-Wuerttemberg) or 9% (other states) of income tax — if church member

Odoo calculates Lohnsteuer using the official BMF tax tables (Programmablaufplan), which factor in:

Steuerklasse (I through VI) based on marital status and circumstances
Kinderfreibetrag (child allowances)
Kirchensteuer membership
Faktorverfahren (factor method for dual-income married couples)

Steuerklassen (Tax Classes)

Class	Who	Effect
I	Single, divorced, widowed	Standard allowances
II	Single parent	Additional Entlastungsbetrag
III	Married (higher earner in III/V combination)	Higher allowances
IV	Married (equal earners)	Standard married allowances
V	Married (lower earner in III/V combination)	Minimal allowances
VI	Second and subsequent jobs	No basic allowance

Payroll Components

Component	German Name	Type
Gross salary	Bruttogehalt	Earning
Overtime	Überstunden	Earning (may be tax-free for nights/Sundays/holidays)
Holiday pay	Urlaubsgeld	Earning (13th/14th month)
Christmas bonus	Weihnachtsgeld	Earning
Travel allowance	Fahrtkostenzuschuss	Benefit (EUR 0.30/km first 20km, EUR 0.38/km above)
Meal vouchers	Essenszuschuss	Benefit (tax-free up to EUR 3.10/day employer contribution)
Company car	Firmenwagen	Benefit (1% of list price per month or logbook method)
Lohnsteuer	Income tax	Deduction
Solidaritaetszuschlag	Solidarity surcharge	Deduction
Kirchensteuer	Church tax	Deduction (if applicable)
KV (employee)	Health insurance	Deduction
RV (employee)	Pension insurance	Deduction
AV (employee)	Unemployment insurance	Deduction
PV (employee)	Nursing care insurance	Deduction
VWL	Vermoegenswirksame Leistungen (capital-forming benefits)	Deduction/benefit

Implementation Considerations

Typical Timeline

Phase	Duration	Activities
Discovery	2-3 weeks	GoBD assessment, DATEV compatibility, SKR03/04 decision, Steuerberater coordination
Configuration	4-6 weeks	Chart of accounts, VAT/ELSTER, payroll, GoBD compliance settings
Data migration	2-4 weeks	Opening balances (Saldenvortrag), customer/vendor master, employee data
Customization	3-5 weeks	DATEV export, XRechnung/ZUGFeRD, industry workflows, German report templates
Testing	2-4 weeks	GoBD audit simulation, DATEV export validation, payroll parallel run
Go-live	1-2 weeks	January 1 go-live (ideal for calendar year-end), parallel run, stabilization
Total	14-24 weeks	Varies by complexity

Key Success Factors

Involve the Steuerberater early — your tax advisor must validate the chart of accounts, DATEV export format, and tax code mapping before go-live
Choose SKR03 or SKR04 consistently — switching later is extremely disruptive; confirm with your Steuerberater which Kontenrahmen to use
GoBD process documentation — create the Verfahrensdokumentation describing your bookkeeping process in Odoo before go-live; this is required during tax audits
January 1 go-live — strongly recommended to align with the fiscal year and simplify DATEV transitions
Payroll Steuerklassen — verify each employee's Steuerklasse and Kirchensteuer status before the first payroll run; ELStAM (Electronic Lohnsteuer Abzugsmerkmale) should be configured for automatic retrieval

Hosting and Data Residency

EU hosting required — GDPR and GoBD require data to be accessible and stored within compliant jurisdictions
Cloud options — AWS Frankfurt, Azure Germany, Google Cloud Frankfurt, Hetzner, OVH DE
Backup and retention — 10-year retention for accounting records, 6 years for business correspondence
Auditor access — hosting must allow Z1-Z3 data access for Betriebspruefung

Frequently Asked Questions

What is GoBD and why does it matter for Odoo?

GoBD is the German federal regulation governing electronic bookkeeping systems. It requires that all entries be traceable, complete, correct, timely, and immutable. For Odoo, this means posted journal entries cannot be deleted or modified (only reversed), invoice numbering must be sequential without gaps, every posting must link to its source document, and the system must provide a complete audit trail. Non-compliance can result in penalties and estimated assessments during tax audits.

How does the DATEV export from Odoo work?

Odoo exports journal entries (Buchungsstapel) and master data in DATEV-compatible CSV format. Your Steuerberater imports these files into DATEV Kanzlei-Rechnungswesen for tax calculation, USt-Voranmeldung preparation, and annual financial statement compilation. The export includes all required fields: account numbers, amounts, tax codes, dates, document references, and cost center information. The export is typically run monthly after closing the books.

Should I use SKR03 or SKR04 in Odoo?

SKR03 organizes accounts by business function and is the most widely used in Germany, especially for manufacturing and trading companies. SKR04 organizes accounts to mirror the HGB financial statement structure and is preferred by companies that want closer alignment between their chart of accounts and their published financial statements. Consult with your Steuerberater — they likely have a preference based on their DATEV setup and client portfolio.

How does Odoo handle XRechnung for government invoices?

Odoo generates XRechnung-compliant XML files for B2G invoices. Each government buyer has a Leitweg-ID (routing identifier) stored in their contact record. When creating an invoice for a government entity, Odoo generates the EN 16931-compliant XML with the Leitweg-ID, which is then delivered over Peppol or uploaded to the ZRE (federal) or OZG-RE (state) portal.

Yes, Odoo's German payroll module calculates all four pillars of social insurance (health, pension, unemployment, nursing care) for both employer and employee shares, respecting the applicable Beitragsbemessungsgrenzen (contribution ceilings). It also calculates Lohnsteuer using the official BMF Programmablaufplan based on the employee's Steuerklasse, Kirchensteuer status, and Kinderfreibetraege. The system generates the monthly SV-Meldung (social insurance report) and Lohnsteuer-Anmeldung (wage tax return).

How does Odoo handle the Solidaritaetszuschlag after the 2021 reform?

Since 2021, the Solidaritaetszuschlag (5.5% of income tax) has been eliminated for approximately 90% of taxpayers. Odoo applies the updated rules: the surcharge only applies when the Lohnsteuer exceeds the Freigrenze (exemption threshold, approximately EUR 18,130/year for Steuerklasse I). For income slightly above the threshold, a Milderungszone (mitigation zone) applies where the surcharge phases in gradually. Odoo's tax calculation follows the BMF's official Programmablaufplan which includes these thresholds.

What about the mandatory B2B e-invoicing rollout in Germany?

Germany is implementing mandatory B2B e-invoicing in phases starting 2025: businesses must be able to receive e-invoices (XRechnung or ZUGFeRD) from January 2025, and must issue e-invoices from January 2027 (large businesses) or January 2028 (smaller businesses). Odoo supports both XRechnung (pure XML) and ZUGFeRD/Factur-X (hybrid PDF+XML) formats for generating and receiving e-invoices, preparing your business for the mandate.

Getting Started with Odoo in Germany

Germany's GoBD requirements, DATEV ecosystem, mandatory e-invoicing, and complex payroll system create one of the most demanding ERP compliance environments in the world. Odoo's German localization — with GoBD-compliant bookkeeping, DATEV export, SKR03/SKR04 charts, and comprehensive payroll — provides a solid foundation, but requires an implementation partner with deep German accounting expertise to configure correctly.

ECOSIRE has experience implementing Odoo for German businesses across manufacturing, trading, services, and technology sectors. We work closely with your Steuerberater to ensure DATEV compatibility, GoBD compliance, and seamless tax reporting from day one.

Explore our Odoo implementation services to learn how we deliver GoBD-compliant, DATEV-integrated Odoo deployments for German businesses. Contact us to discuss your specific requirements and get a detailed implementation plan.