Pillar April 22, 2026 7 min read
DATEV integration for German mid-market — the practical guide 2026
DATEV is the DACH standard between ERPs and tax advisors. What makes a clean integration — and how weclapp, Odoo and Zoho Books each build the bridge.
- datev
- accounting
- weclapp
- odoo
- zoho
- mid-market
TL;DR — DATEV is the language, the ERP is the translator
Quick context for non-German readers: DATEV is a software cooperative based in Nuremberg that’s been serving German tax advisors, auditors, and lawyers for decades. Over 70 % of German tax advisors work with DATEV software — which makes a clean DATEV interface the silent obligation for any mid-market ERP in Germany. A bad integration means manual preparation, error-prone Excel bridges, and a strained relationship with the tax advisor. A good one means: daily data stream, automatic documents, monthly close in hours instead of days.
This guide is the Mate iT inside view from 400+ mid-market projects. We show what makes a good integration technically and procedurally, where the most common pitfalls are, and how weclapp, Odoo, and Zoho Books each build the bridge — with concrete recommendations for the ERP choice.
What is DATEV exactly?
DATEV eG is a cooperative based in Nuremberg, developing software for tax advisors, auditors, and lawyers — established in the German market for decades. The relevant products from an ERP perspective:
- DATEV Kanzlei-Rechnungswesen — the accounting software that tax advisors use to process client data.
- DATEV Unternehmen online — the cloud service for clients (i.e., mid-market companies) submitting documents digitally.
- DATEV format — the data exchange standard. Thousands of third-party systems (ERPs, POS, payroll) can export DATEV-formatted booking stacks.
From an ERP perspective, “DATEV interface” is an umbrella term for: chart-of-accounts mapping, tax-key mapping, booking-stack export, document-image export, and possibly master-data sync (debtors, creditors). A good integration covers all four — a poor one covers only two.
What makes a good DATEV integration
Six criteria we use at Mate iT to measure a DATEV setup:
1. Chart of accounts aligned with the tax advisor
This is the most common stumbling block. The ERP uses standard charts (typically SKR03 or SKR04 in Germany), but the tax advisor may have customized their client’s chart. If the ERP exports accounts the tax advisor doesn’t know, every monthly close generates queries. We align the chart of accounts with the tax advisor before go-live — and document it in a central mapping.
2. Tax-key logic understood
DATEV distinguishes between standard tax keys (VAT 19 %, 7 %, 0 %, intra-community supply, etc.) and special keys for intra-community supplies, reverse-charge, third-country revenue. The right keys must be set per booking in the ERP, otherwise the tax advisor books with the standard mapping — which regularly leads to incorrect VAT returns when international business is involved.
3. Booking-stack workflow with approval
Bookings going directly into DATEV cannot be recalled if errors occur. We typically build an approval step: the ERP exports the booking stack as a file, someone (accountant or tax advisor) reviews, then the stack is uploaded. For small mid-market companies, the tax advisor as review instance is often enough; for larger ones, an internal accountant or at least the management as sign-off is recommended.
4. Document image in the document center
DATEV requires a document image per booking — for incoming invoices the PDF, for outgoing invoices the document generated by the ERP. A good integration sends the document image automatically, so the tax advisor has direct access in the DATEV document center. A bad integration leaves the document image in the ERP — and the tax advisor calls on every query.
5. Master-data sync for debtors/creditors
When a new customer is created in the ERP, they must also exist in DATEV as a debtor — otherwise the booking can’t be assigned. A good integration synchronizes master data automatically (or semi-automatically with approval). A poor integration leaves it manual — which becomes a bottleneck quickly with growing business.
6. Audit capability (GoBD)
GoBD compliance is not optional in Germany. Every booking stack must be traceable to its original document, master-data changes must be historicized, tamper-resistant storage is mandatory. A good integration delivers this out of the box; a poor one needs workarounds that surface during audits.
DATEV in the three big ERPs
weclapp — the gold standard for German mid-market
weclapp is developed in Karlsruhe and was designed with DATEV in mind from day one. The interface is native:
- Chart of accounts is aligned once with the tax advisor at setup, then runs automatically
- Tax keys are correctly mapped out of the box for SKR03/SKR04, intra-community supplies, reverse-charge
- Booking-stack export in DATEV ASCII or DATEV XML, configurable per client
- Document image is automatically attached — both for incoming and outgoing invoices
- Debtor/creditor sync runs bidirectionally, with mapping rules per account
Setup effort: typically 1–2 days additional to the ERP base setup. When the tax advisor already knows weclapp setups (which is increasingly the case among DACH tax advisors), the alignment runs particularly fast.
More on weclapp: /en/plattformen/weclapp. Detail article: /en/blog/datev-schnittstelle-weclapp.
Odoo — DATEV via Mate iT connector
Odoo has no native DATEV interface out of the box — which is logical, because Odoo is internationally oriented and the German DATEV standard is just one sub-market. Odoo offers DATEV modules from third parties, with quality varying widely. Mate iT therefore developed its own DATEV connector, optimized for the German tax-advisor workflow.
What our connector can do:
- DATEV ASCII export with correct tax keys, chart-of-accounts mapping, cost-center logic
- Document-image attachment with every booking stack — automatically generated or pulled from the attachment
- Debtor/creditor sync with mapping table that the tax advisor can maintain
- Multi-tenant capability for holding structures with multiple subsidiaries
Setup effort: typically 3–5 days additional to the Odoo base setup. License for our connector is project-based.
More on Odoo: /en/plattformen/odoo. Detail article: /en/blog/datev-schnittstelle-odoo.
Zoho Books — DATEV via add-on
Zoho Books is the accounting component of Zoho One. The DATEV integration runs via an add-on that exports the booking stack in DATEV format. What works:
- Booking-stack export in DATEV standard format
- Chart-of-accounts mapping configurable in the Zoho UI
- Document image is attached (with minor limitations on format conversion)
What’s limited:
- The depth of the DATEV integration is shallower than weclapp’s — special tax keys and complex condition logic sometimes need workarounds
- The UI is English-oriented — configuring on SKR03/SKR04 requires maintaining the mapping yourself
Setup effort: typically 2–3 days additional to the Zoho Books base setup. Zoho Books is the right choice when the overall setup is CRM- or marketing-driven and accounting is the sub-track — not when DATEV is the main focus.
More on Zoho One: /en/plattformen/zoho. Detail article: /en/blog/datev-schnittstelle-zoho.
Decision matrix
| If… | …then typically |
|---|---|
| DATEV is central, classic German mid-market business | weclapp |
| Complex industry logic, open-source preference | Odoo with Mate iT DATEV connector |
| CRM/marketing focus, DATEV as sub-track | Zoho Books in the Zoho One bundle |
| Existing ERP, DATEV integration runs poorly | DATEV audit with Mate iT, then repair or migration |
Mate iT recommendation — three rules of thumb
First: Align the chart of accounts with the tax advisor before you start the ERP setup. Nothing is more expensive than an ERP rollout with chart-of-accounts chaos discovered late.
Second: If the tax advisor doesn’t know what DATEV format is, find another tax advisor or build the bridge yourself. This happens less often than you’d think — but when it does, it’s a clear signal.
Third: DATEV integration is hygiene-level, not bonus. If you roll out an ERP that doesn’t support DATEV cleanly, you’ll regret it — either at the tax inspection, during the staff handover in accounting, or simply in the stress of the monthly close.
Next step
If you’re setting up a new DATEV integration, repairing an existing one, or planning the ERP switch with DATEV in mind — write to us. 30 minutes initial call, we capture your current state, listen in with your tax advisor, and tell you clearly what to do.
More on our accounting service: /en/leistungen/buchhaltung-integrieren. ERP-platform comparison article: /en/blog/weclapp-vs-odoo-vs-zoho.
Frequently asked questions
What is a DATEV interface and why does it matter for German mid-market companies? +
A DATEV interface transfers booking and master data from the ERP to the tax advisor's DATEV software automatically — typically in DATEV ASCII or XML format. In the German mid-market this is standard, because most German tax advisors work with DATEV. Without a clean integration, the data stream gets manually prepared every month — costing hours, prone to errors, and making the relationship with the tax advisor unnecessarily painful.
Which ERP has the best DATEV interface? +
weclapp — without question. The interface is native out of the box, developed in Karlsruhe with the German tax-advisor workflow in mind. It handles standard chart of accounts, conditions, VAT logic, asset register, and DATEV document images without additional modules. Odoo has DATEV integration via external modules (Mate iT offers its own as a marketplace module). Zoho Books has DATEV integration via add-on. Both work, but weclapp is the standard fit when DATEV is the central lever.
How much effort is the DATEV setup with Mate iT? +
On weclapp, the base settings are done in 1–2 days — chart-of-accounts mapping, tax keys, booking-stack configuration. On Odoo or Zoho with our custom connector, it's an additional 3–5 days of setup. Plus the alignment with your tax advisor, which we always include — even the best integration is useless if the tax advisor doesn't accept the data stream.
What does a DATEV integration cost? +
On weclapp: included in the standard rollout, no add-on. On Odoo: roughly €4,000–8,000 setup effort (depending on complexity), plus our Mate iT connector license (marketplace-based). On Zoho Books: ~€3,000–6,000 setup. In all cases the amount relativizes quickly — a poorly-integrated accounting setup costs 5–10 hours of manual work per month at the tax advisor's hourly rate, that's €600–1,200 monthly.
What are the most common mistakes during DATEV setup? +
Three: First, an unaligned chart of accounts — when the ERP uses accounts the tax advisor doesn't know, chaos is inevitable. Second, a missing booking-stack approval workflow — bookings going directly into DATEV without review can delay the monthly close on a single error. Third, missing document images in the DATEV document center — DATEV expects a document image for every booking, supplied from the ERP; without it, every booking comes back as a query. We address all three during setup.
Can you take over or repair an existing DATEV integration? +
Yes. Customers often come to us with an already-configured setup that never ran cleanly — typically due to chart-of-accounts chaos, wrong tax keys, or half-built booking-stack logic. We do a DATEV audit (typically 2–3 days), document the gaps, and rebuild the setup. We work closely with your tax advisor during this repair — they're the recipient of the data stream.
How does document routing work in e-commerce setups? +
In e-commerce setups (Shopify + weclapp, Shopify + Odoo, etc.) documents are generated automatically — Shopify creates the invoice, the ERP picks it up, and the document file is included with the DATEV booking-stack export. The tax advisor has direct access to every invoice in the DATEV document center. If needed, supplier invoices can be captured digitally via DATEV-Unternehmen-online — the booking then flows back into the ERP.
What happens during an audit or tax inspection? +
A clean DATEV integration is your safety anchor here. In an audit case, the tax advisor can trace every booking back to its original document — that's mandatory under German GoBD. We make sure every ERP booking has a unique booking number, every document is in the document center, and master-data changes are historicized. A tax inspection is significantly less stressful with a properly-integrated ERP than with Excel-based work-arounds.
Cluster
Keep reading
Other articles in the same topic cluster.
- Nº 01 Pillar
weclapp vs Odoo vs Zoho — the mid-market comparison 2026
Three ERP worlds, one mid-market segment. We've rolled out all three platforms in production and write down here when which fits — without marketing fluff, with concrete decision criteria.
Read article - Nº 02
DATEV interface in Zoho Books — what works and where workarounds are needed
Zoho Books is the accounting component of Zoho One. DATEV integration runs via add-on — functional, but with less depth than weclapp. When it pays off and where Mate iT typically fine-tunes.
Read article - Nº 03
DATEV interface in Odoo — how Mate iT builds the bridge
Odoo has no native DATEV interface — internationally oriented, not DACH-centric. Mate iT developed its own connector serving the German tax-advisor workflow cleanly.
Read article