DATEV Connection in E-Commerce: Automated Accounting

In e-commerce, hundreds to thousands of documents are generated daily: invoices, credit notes for returns, payment receipt notifications and debtor master data. Manual transfer of these documents to DATEV is not only time-consuming but also error-prone. According to a Bitkom study, manual document entry generates average error costs of 12,500 euros per accounting employee annually in German companies (Bitkom, 2025).

Automating the document flow virtually eliminates this error source entirely. Furthermore, it enables timely accounting: instead of weekly or monthly batch exports, documents are transferred to DATEV in real time or daily. The tax advisor always works with current figures, and the business owner has an up-to-date overview of the financial situation of their e-commerce business at all times.

From a compliance perspective, automated DATEV integration is also advantageous. The GoBD (Principles for Proper Management and Storage of Books) require a seamless document chain. An automated integration solution ensures that every business transaction is posted completely and promptly, generating an audit log that serves as evidence during tax audits.

DATEV offers several standardized formats for data exchange. The choice of the right format depends on the desired automation level, the DATEV product in use and the tax advisor's requirements. The three most important formats for e-commerce integration are the posting batch (CSV), the XML document format and the DATEV API.

The DATEV posting batch is the most widely used format. It is a CSV file with defined columns for posting information: turnover, debit account, credit account, tax code, document date, document field, posting text and additional fields. The format is specified in DATEV documentation and has established itself as the standard for document import in DATEV Unternehmen Online and DATEV Kanzlei-Rechnungswesen. According to DATEV, over 85 percent (project experience) of tax advisor clients use posting batch import (DATEV, 2025).

The DATEV XML format is particularly suited for document exchange including document images. Via DATEV Unternehmen Online, invoice PDFs can be uploaded together with structured posting data. This approach combines automated posting entries with audit-proof document archiving, thus comprehensively fulfilling GoBD requirements.

The DATEV API (DATEV Connect Online) is the most modern interface enabling real-time integration. Via RESTful endpoints, posting data, document images and master data can be transferred directly to DATEV. The API is under active development and offers increasingly more capabilities for deep integration. For new integration projects, the API is the most future-proof approach.

The heart of every DATEV integration is account mapping -- the assignment of store transactions to the correct posting accounts in DATEV. This mapping is configured once and forms the basis for all automated postings. Configuration requires close coordination with the tax advisor, as chart of accounts are individual.

The most important assignments concern revenue accounts (differentiated by tax rate and delivery country), debtor collective accounts (collective account for receivables), payment accounts (one transit account per payment provider) and tax codes (19 percent (project experience), 7 percent (project experience), 0 percent (project experience) for intra-community deliveries, reverse charge). A typical e-commerce chart of accounts encompasses 15 to 25 relevant accounts (project experience), which are stored as a mapping table in the middleware.

Particular attention is required for handling international orders. Deliveries within the EU to business customers with valid VAT ID are posted as intra-community deliveries exempt from VAT. Deliveries to private customers within the EU are subject to the destination country's tax rate under the One-Stop-Shop (OSS) procedure. The middleware must correctly map these tax law rules and dynamically assign the tax code.

The central data flow of DATEV integration is transferring invoices from the online store to financial accounting. Every Shopware order that reaches the 'invoice created' status is captured by the middleware, converted to DATEV format and transferred. The process encompasses several steps: extraction of invoice data from the store API, application of account mapping, generation of the DATEV posting batch and upload to DATEV Unternehmen Online.

Each posting entry contains at minimum the invoice amount, revenue account, debtor account, tax code, document date and a unique document number as reference. Optionally, the invoice PDF as document image, customer name as posting text and a cost center for internal allocation are also transferred. Studies by DIHK show that companies with automated document flow can reduce their accounting costs by an average of 35 percent (DIHK, 2024).

Credit notes for returns are posted as separate entries with negative amounts to the revenue reduction account. The middleware ensures the link to the original document via the reference number, so credit notes in DATEV can be assigned to the correct business transaction. This bidirectional document flow ensures seamless documentation of all transactions.

Automatic payment reconciliation is the most sophisticated discipline of DATEV integration. When a customer pays by credit card, PayPal or SEPA direct debit, the payment passes through the payment provider before arriving in the merchant's bank account. The middleware must correctly map these payment flows in DATEV -- ideally via transit accounts that trace the payment status from receipt at the provider to credit in the bank account.

A common problem with payment reconciliation is timing delays: the order is placed today, the payment provider collects the money tomorrow and transfers it three days later as a batch to the business account. The batch transfer must then be split into individual orders and matched to open items. According to a survey by ibi research, 62 percent (project experience) of online merchants spend more than five hours per week on manual payment reconciliation (ibi research, 2024). An automated solution reduces this effort to virtually zero.

The middleware implements intelligent matching: each payment is assigned to the correct open item in DATEV based on order reference or customer number. For batch transfers from payment providers, the payout file is analyzed and resolved into individual postings. Unassignable payments are provided in a clarification list for manual processing by the accountant.

Every customer in the online store needs a corresponding debtor number in DATEV to correctly assign invoices and payments. For stores with hundreds or thousands of new customers per month, manual debtor creation is not practical. The automated DATEV connection creates debtors automatically on first order.

The debtor number can either be derived from the store customer number (for example with a prefix: customer number 1234 becomes debtor 10001234) or assigned via a dedicated number range in DATEV. What is important is a unique and consistent assignment that remains stable for subsequent orders from the same customer. The middleware stores the mapping between store customer number and DATEV debtor number and uses it for all subsequent postings.

For B2B customers with invoice payment, debtor management is particularly relevant: open items are posted to the debtor account in DATEV and can be monitored via the tax advisor's open items list. Dunning runs, payment terms and credit limits can thus be managed efficiently.

Correct posting of tax rates is one of the most complex requirements of DATEV integration. In Germany, 19 percent and 7 percent VAT apply domestically. For EU deliveries to business customers with VAT ID, the tax exemption for intra-community deliveries applies. Deliveries to EU private customers have been subject to the One-Stop-Shop (OSS) procedure since July 2021, where the destination country's tax rate applies.

The middleware must determine the correct tax code for each document. The logic is based on delivery country, customer status (B2B or B2C), validity of the VAT ID (verification via VIES database) and goods value. For OSS-liable deliveries, a separate tax code in DATEV is used for each EU country. A typical international e-commerce store requires 20 to 30 different tax codes (project experience), which are stored in the mapping configuration.

Another tax-specific consideration is marketplace sales: since the EU marketplace liability directive, platforms like Amazon must collect VAT for certain deliveries themselves. These revenues must be posted differently in DATEV than direct sales through the merchant's own store. The integration must consider the sales channel as a differentiating factor.

Two fundamental strategies are available for DATEV integration: daily batch export and real-time transfer. Both approaches have advantages and disadvantages, and the choice depends on the requirements of the company and tax advisor.

The batch export collects all documents from a day and transfers them as a single posting batch to DATEV. This approach is simpler to implement and suitable for stores with up to 500 orders per day (project experience). The disadvantage: accounting always lags one day behind daily operations, and errors are only detected the following day.

Real-time transfer sends each document immediately after creation to DATEV. This requires using the DATEV API and robust error handling, but offers the advantage of always-current accounting. For growing stores and companies with high order volume, real-time integration is the future-proof choice. The investment in an API-based solution pays off long-term through lower error rates and faster closings.

Errors in DATEV transfer can have various causes: invalid account assignments, missing debtor master data, inconsistent tax codes or temporary connection problems. A professional integration must catch all these scenarios without documents being lost.

The middleware implements multi-level error handling: validation before export (missing required fields are detected before the document is sent to DATEV), retry logic for temporary errors (up to three automatic retry attempts with increasing wait time) and a dead letter queue for documents that could not be processed after all attempts. Unprocessed documents trigger a notification to the accountant or administrator.

A complete audit log documents every export operation: which document was exported when, which DATEV format was used, whether the export was successful or not, and if not, what error occurred. This log is a valuable evidence document during tax audits and facilitates error analysis for discrepancies.

A DATEV integration for an e-commerce store follows a structured process typically spanning four to eight weeks. The most important success factor is close collaboration with the tax advisor, who defines the chart of accounts and tax code assignment.

Experience from numerous DATEV integration projects reveals recurring challenges. The biggest error source is incomplete or incorrect account mapping. When revenue accounts are not correctly differentiated by tax rates or shipping costs are posted to the wrong account, errors arise that only surface during the VAT return.

DATEV integration is often part of a broader integration strategy. When an ERP system such as SAP Business One or Microsoft Dynamics is also in use alongside the online store, it makes sense to integrate the DATEV interface into the existing middleware architecture. Invoice data then flows from the store through the ERP to DATEV, with the ERP handling invoice creation and document control.

For multi-channel merchants who sell through marketplaces in addition to their own store, revenues from all channels must be consolidated in a unified posting logic. The middleware aggregates document data from all sales channels, applies channel-specific account mapping and generates a unified DATEV export. The tax advisor thus receives all documents in a consistent format, regardless of sales channel.