Odoo DATEV Integration – Cleanly Connecting Your Accounting to Your Tax Adviser
An ERP platform in the German Mittelstand stands or falls on the connection to the tax adviser. In Germany, this means a connection to DATEV in practice – the market-standard system used by more than 90 percent of German tax-advisory firms. Anyone introducing Odoo must ensure that monthly, quarterly, or annual data flows reliably and in the right format to the tax adviser.
This guide explains the four ways to connect Odoo to DATEV, frames the difference between posting export and document transfer, and walks through the typical pitfalls to avoid.
Quick verdict: For most mid-market companies, the native DATEV export in Odoo Enterprise is sufficient – postings, master data, and documents in DATEV format. Companies with higher requirements (fully automated document transfer, GoBD audit trail, large document volumes, multiple legal entities) benefit from certified extensions like ODION, manaTec, or much. Consulting. All four paths are GoBD-compliant when correctly configured.
Posting export vs. document transfer – what's the difference?
DATEV distinguishes between two data flows that are often confused:
Posting export (DATEV CSV or ASCII format)
The classic variant: Odoo exports a period's postings as a CSV file in DATEV format. Your tax adviser imports the file into DATEV Kanzlei-Rechnungswesen and works with it. Advantages: simple, robust, widely deployed. Disadvantages: documents are not directly attached; PDFs must be transmitted separately.
Document transfer (DATEV Unternehmen Online)
In addition to postings, the related documents (incoming invoices, outgoing invoices as PDFs) are automatically transferred to DATEV Unternehmen Online. Your tax adviser sees the document linked to the corresponding posting directly inside DATEV and can review content without separately requesting the original. Advantages: seamless data flow, high audit efficiency. Disadvantages: higher implementation complexity, additional licensing depending on the path.
In practice, our customers usually combine both: posting export as the foundation, document transfer for incoming bills.
The four connection paths compared
Path 1: Native Odoo DATEV interface (in the localisation module)
Odoo Enterprise ships DATEV export out of the box in the German localisation module (l10n_de and l10n_de_skr03/04). This path covers:
- Posting export in the official DATEV CSV format
- Master-data export (general accounts, customers, suppliers)
- Prepared reports for UStVA and GoBD audit data
Implementation effort: included in the Quick Start package, no additional effort.
Suitable for: small to mid-sized mid-market setups with classic accounting, one legal entity, monthly transfer to the tax adviser.
Not suitable for: fully automated document transfer, high-frequency transfers, complex multi-entity consolidation.
Path 2: ODION (Open Data Interface for Odoo)
ODION is a specialised DATEV extension for Odoo that adds document transfer and deeper audit functionality on top of the native export. Features:
- Fully automated document transfer via DATEV Unternehmen Online API
- Extended audit trail with seamless document-to-posting chaining
- GoBD compliance certificate
- Automatic pre-coding with OCR support
Implementation effort: additional €4,000 to €12,000 setup, low four-digit annual licence.
Suitable for: mid-market companies with high document volume (300+ documents per month), demand for fully automated data flow.
Path 3: manaTec DATEV Connector
manaTec is a German Odoo Gold Partner with its own DATEV extension. The solution covers:
- Posting and document export in DATEV format
- DATEV Unternehmen Online connection
- Automatic translation of Odoo tax rules into DATEV tax codes
- GoBD compliance
Implementation effort: comparable to ODION (€4,000 to €10,000 setup).
Suitable for: companies that prefer a German vendor with local support.
Path 4: much. Consulting DATEV Bridge
much. Consulting is a specialised consultancy with focus on DACH localisations for Odoo. Their DATEV bridge covers in particular:
- Complex multi-entity consolidation
- Flexible tax-rule mapping (including unusual setups like reverse-charge, OSS scheme)
- Audit functions for statutory-audit requirements
Implementation effort: €8,000 to €20,000 depending on complexity.
Suitable for: corporate groups with multiple legal entities, unusual industry setups, high audit-functionality requirements.
Comparison table
| Function | Native | ODION | manaTec | much. |
|---|---|---|---|---|
| Posting export | ✓ | ✓ | ✓ | ✓ |
| Document transfer (DUO) | – | ✓ | ✓ | ✓ |
| Multi-entity consolidation | limited | ✓ | ✓ | ✓ extended |
| OCR pre-coding | (via Odoo standard) | ✓ extended | ✓ | ✓ |
| GoBD certificate | ✓ (via Odoo) | ✓ | ✓ | ✓ |
| Setup effort | in standard | €4–12k | €4–10k | €8–20k |
| Recurring licence | – | low four-digit | low four-digit | custom |
Setup steps for the native DATEV interface
Starting with Odoo's native DATEV interface, these are the essential configuration steps:
1. Activate the localisation module
In Odoo Enterprise, install module l10n_de_skr03 or l10n_de_skr04 depending on the chosen chart of accounts. This loads the full chart of accounts, German tax rules, and DATEV export functions.
2. Enter consultant and client number
The DATEV consultant number (7 digits) and client number (5 digits) come from your tax adviser. They are stored in accounting settings and are essential for correct DATEV export.
3. Map tax rules to DATEV codes
Odoo uses its own tax rules (e.g. "VAT 19%"); DATEV expects specific tax codes (e.g. "9" for 19% VAT). This mapping is done once per tax rule and is a critical configuration task.
4. Test run with the tax adviser
Before going live, export a test file from Odoo and have your tax adviser import it. Common findings during the test run: wrong client number, faulty tax-code mapping, formatting issues with the date format.
5. Set up periodic export
Define the export cadence (monthly, quarterly) and decide whether the export file is automatically emailed to the tax adviser or whether your finance team triggers and transmits the export manually.
Typical pitfalls
The most common mistakes from our practice when connecting DATEV:
1. Inconsistent tax-code mapping An incoming document at 7% VAT is recorded with tax rule "VAT 7%" in Odoo, but the mapping to the DATEV code is misconfigured. Result: every 7% document lands incorrectly in the UStVA. Solution: complete tax-code testing for every relevant rule before going live.
2. Missing documents in export Odoo only exports documents marked as "posted". Documents in "draft" status are not exported. Result: monthly balances differ. Solution: verify before export that all period documents are correctly posted.
3. Number-range duplication in multi-company setups With multiple legal entities in one Odoo database, number ranges must be configured separately per entity. Otherwise document number duplications occur, which DATEV rejects on import. Solution: separate number ranges, prefixes per entity if needed.
4. Foreign-currency documents without exchange-rate detail Odoo posts foreign-currency documents at the current rate; DATEV expects both the original currency and the EUR value at the posting rate. Solution: exchange-rate configuration in accounting settings, automatic ECB rate retrieval.
5. Document transfer without correct PDF format DATEV Unternehmen Online expects PDFs that meet specific minimum requirements (resolution, file size, metadata). PDFs from Odoo meet these requirements; scanned documents sometimes do not. Solution: scan profiles with OCR and PDF/A compliance.
GoBD compliance in practice
The GoBD (Principles for Properly Maintaining and Storing Books, Records, and Documents in Electronic Form) is the German regulatory framework for electronic accounting. Odoo Enterprise is GoBD-compliant when operated with the German localisation module – covering:
- Immutability: posted documents cannot be altered, only corrected via reverse postings
- Completeness: uninterrupted document number ranges, capture and posting timestamps documented
- Traceability: complete audit trail with user, timestamp, and pre-value for every change
- Availability: data remains available for at least 10 years (statutory retention)
Important: GoBD compliance is an implementation responsibility, not a software property alone. We configure Odoo to meet GoBD requirements and document the configuration in the Verfahrensdokumentation – a mandatory document for tax audits.
Final take
The DATEV connection is a core criterion of any ERP implementation in the German mid-market. Odoo Enterprise ships the connection by default – sufficient for most setups. For higher requirements, ODION, manaTec, and much. Consulting offer three specialised paths.
We advise without obligation on which path fits your specific situation.