Why “DATEV Export Included” Is Not Enough
Almost every ERP or invoicing tool advertises “DATEV export.” In practice, that label spans everything from a bare CSV list without VAT keys to an automated API pipeline with PDF document images, BEDI-GUID links, and a tax-firm return channel. For a calm month-end close, three questions matter:
- Which data flows where? Are you sending pre-coded journal entries directly to the DATEV data center, or transmitting invoice data and PDFs to DATEV Unternehmen online?
- Is the receipt attached to the entry? Does a single click inside your tax firm's DATEV accounting software immediately open the linked original PDF, or does the firm have to match documents by hand?
- Who owns which account? Where are debtor and creditor account numbers created, who verifies EU/OSS tax cases, and how do tax-firm adjustments (payroll, depreciation, accruals) flow back into the ERP?
Teams that only settle these questions after go-live pay the price every single month in clarification loops, reclassifications, and delayed monthly management reports (BWA).
EXTF, Accounting Data Service & Invoice Data Service 1.0
Within the DATEV ecosystem, four integration paths cover different divisions of labor between internal finance and external tax advisors:
| Interface / Path | Data Payload | Document Images | Typical Role |
|---|---|---|---|
| Manual EXTF Export (CSV) | Pre-coded posting batches & master data in DATEV format | Separate (usually exported as ZIP or uploaded manually) | Starting point for low document volumes or interim migration phases |
| DATEV Accounting Data Service (API) | Pre-coded EXTF posting batches delivered straight to the DATEV data center | Linked via Document Image Service & BEDI-GUID |
Standard for ERP systems with reliable pre-coding (Odoo, weclapp) |
| DATEV Invoice Data Service 1.0 (API) | Structured invoice records (outgoing/incoming) sent to Unternehmen online | Transferred directly alongside metadata (PDF / ZUGFeRD / XRechnung) | Ideal when the tax firm controls account coding inside DATEV |
| DATEV Accounting Export Service | Return channel: general ledger entries, chart of accounts, and SuSa data from DATEV | Reference back to tax-firm journal entries | Reconciling internal ERP balances against official tax-firm figures (e.g., in Odoo) |
A critical distinction: the DATEV Accounting Data Service requires your ERP to pre-code entries accurately (revenue accounts, expense accounts, VAT keys, and sub-ledger accounts). If you operate without dedicated in-house bookkeepers and leave account coding to your tax firm, DATEV Invoice Data Service 1.0 or direct document delivery into DATEV Unternehmen online is often the lower-risk choice.
DATEV Unternehmen online, Digital Receipts & BEDI-GUID
The biggest drag on month-end closing happens when accounting entries and PDF invoices travel down separate tracks. The fix is the BEDI-GUID: when a PDF receipt (up to 20 MB) is uploaded to DATEV Unternehmen online, DATEV assigns a unique GUID, which the ERP writes into the document-link field (BEDI) of the EXTF posting row. As soon as your tax firm imports the batch, the original document stays permanently bound to the entry.
In addition, the API integration should detect the client's workspace version (DuoNow vs. DuoNext) so freshly uploaded supplier invoices are not prematurely hidden as already processed. Structured e-invoices (ZUGFeRD/XRechnung) must remain archived unaltered in their original machine-readable format.
SKR03/SKR04, Tax Keys & Sub-Ledger Accounts
Nine out of ten DATEV import rejections have nothing to do with the API—they stem from master-data and account-coding mismatches between the ERP and the tax firm. Before your first live export, five conventions must be agreed in writing:
| Parameter | Typical DACH Convention | Impact of Mismatch |
|---|---|---|
| Chart of Accounts & Digit Length | SKR03 or SKR04, usually 4 digits (occasionally 5 digits in corporate groups) | DATEV rejects the entire batch or posts to unintended ledger accounts |
| Debtor / Creditor Accounts | Sub-ledger accounts 10000–69999 (debtors) and 70000–99999 (creditors) | Open items (OPOS) diverge; dunning runs become unreliable |
| Automatic VAT Accounts vs. Tax Keys | Never combine an automatic VAT account (e.g., 8400/4400) with a duplicate BU tax key | Double or distorted VAT calculation in the advance VAT return |
| EU, OSS & Reverse Charge | Dedicated revenue/expense accounts for intra-EU supplies, § 13b UStG, non-EU exports, and OSS countries | Incorrect EC Sales List (ZM) filings and costly rework on OSS returns |
| Payment Service Providers | Dedicated clearing account per PSP (Shopify Payments, Stripe, PayPal, Klarna) | Lump-sum bank payouts can no longer be reconciled against individual invoices |
In e-commerce, one rule is non-negotiable: never post payouts from Stripe, PayPal, or Shopify Payments straight against your bank account without a clearing account. Because payment providers deduct fees, offset refunds, and bundle payouts across days, open receivables stay cleanly reconcilable only when customer claims, PSP clearing, and fee postings remain cleanly separated.
GoBD, Posting Locks & Procedural Documentation
Germany's principles for proper electronic bookkeeping and archiving (GoBD) demand traceability, completeness, timeliness, and immutability. On a technical level, your ERP-to-DATEV pipeline must enforce three safeguards:
- Posting locks before or upon export: Once journal lines have been handed over to DATEV, the ERP must prevent silent edits or deletions. Any correction must be booked exclusively through traceable reversal entries or credit notes.
- Unbroken export audit logs: Every transmission requires a timestamp, user ID, client ID, document period, file hash, and status confirmation returned by the DATEV endpoint.
- Preservation of original formats: Incoming electronic invoices must be stored in an audit-proof archive in their original data format; printing and rescanning does not replace the electronic original.
Important boundary: a technically sound interface supports your GoBD compliance, but it never replaces company-wide GoBD procedural documentation or professional tax counsel. Binding sign-off on coding rules and retention policies always takes place together with your tax advisory firm.
Aligning with Your Tax Firm in Five Steps
Across more than 400 mid-market projects, one disciplined sequence has consistently prevented first-month closing emergencies:
- Collect the tax firm's master data sheet: Consultant number, client number, fiscal year start, chart of accounts (SKR03/SKR04), G/L account digit length, required sub-ledger numbering ranges, and active revenue, expense, and clearing accounts.
- Activate DATEV data services early: Have your tax firm enable the required services (Accounting Data Service, Document Image Service, and optionally Accounting Export Service) and provision an authorized SmartLogin or SmartCard.
- Sign off on the account and tax matrix: Walk through every real transaction type (domestic 19%/7%, EU B2B, OSS, non-EU export, down payments, cash discounts, credit notes, PSP fees) using test documents inside the ERP.
- Run a trial EXTF import in a test client: Transmit one complete sample month including PDF document images and reconcile both the trial balance (SuSa) and open-items list (OPOS) down to the exact cent.
- Document the monthly closing routine: Agree on fixed cutoff dates, ownership for queries, handling of late-arriving supplier invoices, and a clear return path for tax-firm adjustments.
Common Project Pitfalls & Realistic Effort Drivers
Five recurring mistakes consume the most time and budget in day-to-day operations:
- Involving the tax advisor only after go-live: Cleaning up hundreds of miscoded invoices costs far more than two hours of upfront alignment.
- Duplicate receipt capture: Supplier invoices enter both the ERP and DATEV Unternehmen online via email—virtually guaranteeing duplicate bookings.
- Split invoicing without a source of truth: Some invoices are issued in the online shop and others in the ERP, causing number gaps and revenue mismatches.
- Overlooking DATEV service fees: DATEV bills data services and document storage separately depending on your plan—clarify these fees with your tax firm upfront.
- No return channel from DATEV: Payroll, depreciation, and accruals exist only inside DATEV, causing internal ERP dashboards and the firm's monthly BWA to drift apart.
Technical setup often takes just a few days; the bulk of project effort goes into account mapping, PSP clearing, multi-company separation, and tax-firm sign-off. To see how this fits into 3-year total cost of ownership, read our ERP Cost Guide for SMEs.
Platform Guides & Next Step
How a DATEV integration looks under the hood depends heavily on your target ERP. In our three platform-specific deep dives, we break down concrete architectures, pitfalls, and system boundaries:
- DATEV Interface for Odoo 18, 19 & 20 – why standard CSV often falls short, MATE Hub (
datev_export&datev_online), SmartLogin, multi-company, and the return channel (DV-IN). - DATEV Interface for weclapp Cloud ERP – native handoff, DATEVconnect online, automated retail tax rules, and reconciling Shopify, Stripe, and PayPal payouts.
- DATEV Interface for Zoho Books & Zoho One – export paths, § 13b reverse charge, Zoho CRM architecture, and honest system boundaries.
You can review the technical specifications of our own connector modules on our DATEV Interface page in the MATE Marketplace. If you would like to evaluate your current setup together before committing, schedule a free introductory call via our Contact page.
Frequently Asked Questions
What is the difference between an EXTF export, the DATEV Accounting Data Service, and Invoice Data Service 1.0?
A manual EXTF export produces a structured CSV file transferred via file download. The DATEV Accounting Data Service transmits those pre-coded EXTF posting batches—along with linked receipt images via BEDI-GUID—directly into the DATEV data center over an API. By contrast, DATEV Invoice Data Service 1.0 delivers invoice metadata and document images into DATEV Unternehmen online, where your tax firm manages final account coding and posting approval.
What does the BEDI-GUID do when sending documents to DATEV Unternehmen online?
The BEDI-GUID is a unique identifier assigned to every document image uploaded to DATEV Unternehmen online. When that same BEDI-GUID is included in the document-link field of the EXTF posting line, your tax advisor can open the matching invoice PDF in DATEV accounting with a single click—eliminating manual searching and duplicate filing.
Should our ERP use individual debtor accounts or collective accounts for DATEV?
For B2B customers with open receivables, partial payments, or dunning workflows, individual sub-ledger accounts (typically 10000 to 69999 for debtors and 70000 to 99999 for creditors) provide the cleanest foundation. In high-volume B2C e-commerce with prepayment or payment service providers, agreed collective accounts per sales channel are often clearer—provided each payment provider is reconciled through a dedicated clearing account.
Is a technical DATEV interface alone enough for GoBD compliance?
No. The interface provides immutable export logs, posting-lock flags, and unbroken document links. Full GoBD compliance also requires up-to-date procedural documentation, defined role and access controls, audit-proof archiving, and aligned workflows with your tax advisory firm.
How long does it take to set up a clean DATEV integration for an SME?
The technical connection usually takes only a few days. The main schedule driver is almost always operational alignment with your tax firm: chart of accounts, VAT keys, sub-ledger numbering ranges, activation of DATEV data services, and a trial import of a real accounting month. Realistically, we plan two to four weeks within an ERP project.
Does Mate iT also handle tax account mapping for our company?
We deliver the technical architecture, the mapping matrix, and a verifiable trial export. Binding decisions on revenue, expense, and VAT accounts—as well as special tax treatments—remain the responsibility of your finance team and tax advisory firm; we explicitly do not provide legal or tax advice.