DATEV interface in Odoo — how Mate iT builds the bridge

Why Odoo + DATEV is non-trivial

Odoo is an internationally grown ERP platform — over 7 million users in over 120 countries, each with its own accounting standards. DATEV is the German standard, but for Odoo S.A. (based in Belgium) it’s just one sub-market among many. The result: no native DATEV interface. What exists are third-party modules — some good, some half-finished, some actively abandoned.

Mate iT chose to develop its own DATEV connector. Not from idealism, but necessity: when we roll out Odoo in production for a customer and the DATEV handover doesn’t run stably, the entire rollout success is at risk. With our own connector, we control the interface quality.

What the Mate iT connector can do

DATEV ASCII and XML export: Both formats are supported. The tax advisor chooses which they prefer — older DATEV setups work with ASCII, newer ones with XML. The connector exports both from the same booking stack.

Chart-of-accounts mapping with editor UI: In the Odoo backend, there’s a screen where the mapping between Odoo accounts and DATEV accounts is maintained. The advantage: when the tax advisor signals a chart-of-accounts change, the mapping can be adjusted without an IT appointment — the bookkeeper or management can do it themselves.

Document-image attachment: Each booking in Odoo has an attachment (incoming invoice PDF, outgoing invoice from Odoo, document). When the booking stack is exported, all attachments are bundled in — the tax advisor has direct access in the DATEV document center. Format conversion (e.g., Word to PDF) the connector handles automatically.

Multi-tenant capability: Holdings with multiple subsidiaries typically have multiple companies configured in Odoo. The connector exports a separate DATEV booking stack per company with the respective client number.

Tax-key logic: Standard DATEV keys are mapped out of the box. Special keys (e.g., for third-country revenue, intra-community supplies with order-type differentiation) we configure per customer — that’s the Mate iT consulting share, not pure connector function.

Debtor/creditor sync: Bidirectional synchronization. New customers in Odoo automatically receive a DATEV client number; address changes are passed in the next booking stack.

Setup effort

Typical setup sequence:

1. Connector installation (½ day): install module, activate license, enter base config.
2. Chart-of-accounts mapping (1 day): align with the tax advisor, build the mapping table, add special accounts.
3. Tax-key configuration (½–1 day): map DATEV standard keys, add special keys.
4. Test export and tax-advisor sign-off (1 day): export sample bookings, import into DATEV Kanzlei-Rechnungswesen, check, correct.
5. Hypercare (4–8 weeks): accompany the first monthly closes, document edge cases.

In total, we plan for 3–5 days of effort additional to the Odoo base setup. For a typical mid-market project, that’s an additional ~€3,000–5,000 implementation effort, plus the marketplace-based connector license.

When Odoo + DATEV fits

• Your business needs Odoo customization depth or open-source sovereignty — DATEV is important but not the top-1 driver
• You have a tax advisor open to a mapping workshop
• Your chart of accounts isn’t too exotic (true for most DACH mid-market companies)
• You want no third-party modules with uncertain quality — but an interface someone is responsible for

Pillar overview

More on DATEV integration in the mid-market as a whole: /en/blog/datev-anbindung-mittelstand. Comparison of platforms weclapp/Odoo/Zoho: /en/blog/weclapp-vs-odoo-vs-zoho. More on Odoo: /en/plattformen/odoo.

Next step

If you’re planning Odoo or already running it, and the DATEV integration is an open point — write to us. 30 minutes initial call, we check your status and tell you clearly whether our connector is the right fit.