DATEV Interface
A DATEV interface is the export and exchange mechanism that lets a German ERP or accounting system hand bookkeeping data to a tax adviser (Steuerberater) using the data formats of DATEV eG, the cooperative whose software dominates the German tax-advisory market. Because many DACH SMEs keep order entry, invoicing, and operational accounting in their ERP but delegate financial bookkeeping and tax filings to an external adviser, the interface bridges the two worlds. It typically produces structured files — postings, debtor and creditor master data, and document references — that the adviser imports into DATEV without manual re-keying.
- Term
- DATEV Interface
- Entity type
- Standard / interface
- Domain
- Financial accounting and tax (Germany)
- Canonical definition
- A DATEV interface is the export and data-exchange function by which a German ERP or accounting system delivers bookkeeping data in DATEV formats to a tax adviser for further processing.
- Classification
- The DATEV interface is a market-driven accounting exchange format that connects an ERP system to the software used by German tax advisers.
- Related terms
- GoBD, UStVA, Cost-centre accounting, Audit trail, OCR document recognition, E-invoicing, Accounts payable
- Source / maintainer
- erp-software.org editorial team (independent, vendor-neutral)
What DATEV Interface is NOT — disambiguation
- Not an ERP module: The DATEV interface is an export and exchange function, not a full financial-accounting module inside the ERP.
- Not e-invoicing: E-invoicing transmits structured invoices between business partners, whereas the DATEV interface transfers bookkeeping data to a tax adviser.
- Not the GoBD: The GoBD is a regulatory standard for proper digital bookkeeping; the DATEV interface is a transport mechanism that must comply with it but does not define it.
- Not an API standard: It is a specific exchange format tied to one vendor's ecosystem, not a generic open API or banking standard.
Why a DATEV interface matters in Germany
DATEV eG provides the software used by the large majority of German tax advisers and auditors. As a result, a clean DATEV export is a practical requirement for any ERP or accounting product sold into the German market, even where the system itself uses an entirely different internal data model. The interface removes manual transfer of figures between the company and its adviser, reducing both effort and the risk of transcription errors. It also supports the legally required separation of duties where bookkeeping is handled externally.
What the interface typically transfers
A DATEV export usually covers more than just journal entries. Depending on the configuration it includes:
- Booking records (postings) with accounts, amounts, tax keys, and dates.
- Debtor and creditor master data, often aligned to the standard chart of accounts (SKR 03 / SKR 04).
- Document links so scanned invoices can be matched to postings.
- Cost-centre information feeding cost-centre accounting.
The modern, structured format used for these exchanges is commonly referred to as the DATEV format or DATEV-Format/EXTF; older systems may still reference the historic ASCII postings format. Correct mapping of accounts and tax keys is essential, because errors propagate straight into the financial books.
Direction and integration patterns
Most ERP systems implement the export direction: the company sends data out to the adviser. Some setups are bidirectional, returning booked or corrected data so that the ERP and the adviser's ledger stay reconciled. Document-related workflows increasingly rely on OCR document recognition and digital document storage so that the relevant receipts travel alongside the postings. Where companies operate their own financial accounting in the ERP, the interface may instead feed monthly or annual handovers for the tax return and the advance VAT return (UStVA).
Compliance considerations
Because the exported data forms part of the official books, the export and its handling must respect German retention and audit requirements under the GoBD, including immutability of booked records and a traceable audit trail. The interface itself does not replace those obligations; it is a transport mechanism. When evaluating an ERP system for the German market, buyers should confirm not only that a DATEV export exists but that it maps the chart of accounts and tax keys correctly and preserves document references in line with the adviser's expectations.
Related Topics
Frequently Asked Questions
Is DATEV integration optional for international ERPs in Germany?
For larger enterprises with in-house tax functions, sometimes — they may operate independently of DATEV and submit reports directly. For mid-market and SMB with German operations, DATEV integration is effectively mandatory because most German Steuerberater require it. Foreign ERPs without DATEV integration consistently lose German selections to alternatives that have it.
How is e-invoicing changing DATEV integration?
Structured e-invoicing (XRechnung, ZUGFeRD) flows naturally through DATEV Unternehmen online and DATEVconnect, with the Steuerberater receiving invoices in structured form. The shift simplifies AP automation: the OCR step disappears, data is already structured, posting accuracy improves. By 2027, when B2B e-invoicing is mandatory in Germany, DATEV integration will increasingly be e-invoice-centric.
Can SaaS ERP integrate with DATEV effectively?
Yes, via DATEVconnect online API and DATEV Unternehmen online. Modern cloud ERPs (Business Central, NetSuite, weclapp, Xentral) deliver credible DATEV integration. Public-cloud multi-tenant ERPs handle the integration via APIs; the integration depth has caught up to traditional on-premises ERPs.
