DATEV Interface for E-Commerce

Financial accounting is one of the areas where e-commerce companies have the greatest automation need. Every order generates an invoice, every return a credit note, every payment a journal entry. A store with 500 orders per month quickly generates over 1,500 posting transactions monthly – manual capture is error-prone, time-consuming and not scalable with growing business volume.

Germany's principles for proper management and storage of books (GoBD) place clear requirements on document management: completeness, accuracy, timely posting and traceability. An automated DATEV interface fulfills these requirements at the system level, as documents are transferred directly from the store system to DATEV – without manual intermediate steps that could cause errors or delays.

Furthermore, automation enables timely accounting: instead of working through a mountain of documents at month-end, postings are transferred to DATEV daily. The tax advisor has access to current figures at all times, which significantly accelerates the preparation of management reports and VAT returns. For growing e-commerce companies, this transparency is an important building block for informed business decisions.

DATEV offers various interfaces and formats for data exchange. The right format depends on the store's technical capabilities, the degree of automation and the tax advisor's requirements. The three main integration approaches are the DATEV posting batch (CSV), the DATEV XML document exchange and the DATEV API.

The DATEV posting batch in CSV format is the most widely used approach. Journal entries are generated as a CSV file according to the standardized DATEV schema and can be imported directly into DATEV Unternehmen Online or DATEV Kanzlei-Rechnungswesen. The format includes mandatory fields such as revenue, contra account, document date, posting text and document field, plus optional fields for cost centers and document links. For Shopware-based stores, we generate these files automatically from order data.

The DATEV XML document exchange goes one step further: in addition to posting data, the associated document images (invoice PDFs) are transferred and archived in DATEV Belegtransfer. This fulfills the GoBD requirement for audit-proof document storage and enables the tax advisor to directly access original documents. XML document exchange is particularly suitable for companies with high document volumes.

The DATEV API is the most modern integration approach and enables real-time synchronization. Via REST-based endpoints, posting data can be transmitted directly to DATEV without the detour through files. The API also offers the possibility to synchronize master data such as debtor accounts bidirectionally. For companies with high automation requirements, we recommend API-based integration.

Correct account assignment is the heart of every DATEV integration. Every journal entry must be assigned to the right revenue account, tax key and debtor account. In e-commerce, this is particularly complex as different product categories may be assigned to different revenue accounts and tax rates vary by delivery country and customer type.

For the German market, the standard chart of accounts SKR 03 or SKR 04 is typically used. Revenue from product sales is posted to different accounts by tax rate: 8400 (SKR 03) / 4400 (SKR 04) for 19% VAT and 8300 (SKR 03) / 4300 (SKR 04) for 7% VAT. Intra-community deliveries to companies with valid VAT ID are posted tax-free to separate revenue accounts. This mapping is configured once and then automatically applied by the interface.

Special attention is required for tax rate mapping with international sales. Since the EU-wide introduction of the One-Stop-Shop (OSS) procedure, online retailers selling to consumers in other EU countries must apply local tax rates and report via OSS. The DATEV interface must correctly recognize these tax rates and post to the corresponding tax accounts – an area that is particularly error-prone with manual capture.

Every customer in the online store needs a corresponding debtor account in DATEV. For B2B stores with hundreds or thousands of business customers, manually creating and maintaining these accounts is considerable effort. Automated debtor management creates new debtors automatically on first order and synchronizes master data changes such as address, VAT ID and payment terms.

Debtor numbers are assigned according to a configurable scheme – typically in the number range 10000–69999 for debtors. The mapping between store customer number and DATEV debtor number is stored in a mapping table and automatically resolved with every document transfer. For B2B customers with multiple order addresses or corporate structures, hierarchical debtor accounts can be set up.

Payment matching is one of the most time-consuming accounting tasks in e-commerce. Payments via various channels – credit card, PayPal, SEPA direct debit, purchase on account, prepayment – must be assigned to the correct invoices. A professional DATEV interface automates this matching and significantly reduces manual effort for open items management.

Technical implementation includes recognizing payment receipts in the store system or via the payment provider, automatic matching based on invoice number, amount and debtor account, and posting the payment to the correct bank account in DATEV. Partial payments, overpayments and payment differences are detected and flagged for manual clarification. For the B2B sector, correct assignment of SEPA payments with structured reference is particularly relevant.

Returns and credit notes require particular care in DATEV accounting. A credit note must reference the original invoice, use the correct tax rate and be posted to the right revenue account (as a reversal entry). For partial returns, the credit note must itemize the returned positions individually while the remaining positions stay untouched.

The DATEV interface maps the entire returns process: from the return notification in the store through quality inspection to credit note creation and automatic posting in DATEV. The return document is attached as a document image (PDF) to the posting and archived in an audit-proof manner. For stores with high return rates, this automation saves several hours per week of manual posting work.

Implementing a DATEV interface for an online store follows a structured process. In the first phase, we analyze the current accounting process together with the tax advisor, the chart of accounts used and the specific requirements for document transfer. This phase typically takes 1–2 weeks and lays the foundation for smooth integration.

In the second phase, account mapping is configured: which product groups are posted to which revenue accounts, how tax rates are assigned and which scheme is used for debtor numbers. The third phase covers technical implementation of the interface, including error handling, retry mechanisms and audit logging. In the fourth phase, all document types are tested with real test data and results validated by the tax advisor. The entire process takes 4–6 weeks.

In practice, we encounter recurring challenges in DATEV integration projects that can be avoided through forward-looking planning. The most common pitfall is inconsistent account mapping: when the tax advisor adjusts the chart of accounts without updating the interface, postings are made to incorrect accounts. We solve this through a central configuration file that only needs to be updated in one place when the chart of accounts changes.

Another frequent error is insufficient handling of rounding differences. With tiered pricing and volume discounts, rounding differences can occur between store calculation and DATEV posting. The interface must detect these differences and automatically post to a rounding difference account, rather than rejecting the document transfer. For B2B stores with high order volume, these small differences add up and must be handled correctly from an accounting perspective.

Finally, test coverage is crucial for successful DATEV integration. Before go-live, we test every document type with real test data: standard invoices, partial delivery invoices, credit notes, cancellations, foreign invoices, reverse charge documents and collective invoices. The tax advisor validates the posting results in the DATEV test environment. Only after complete approval of all document types is the interface transferred to the production environment.

DATEV integration is one of the most impactful automation measures in the entire value chain for e-commerce companies. It eliminates the most time-intensive manual process in accounting, ensures GoBD compliance at the system level and creates the transparency necessary for informed business decisions. Especially for growing B2B merchants who want to increase their order volume, automated accounting integration is a crucial prerequisite – because manual processes do not scale with business success. The one-time investment in a professional DATEV interface pays off sustainably through saved personnel costs, reduced error costs and accelerated month-end closings.

A structured implementation plan with clear milestones and early involvement of all stakeholders is the key to success for every DATEV integration project.

Many B2B merchants sell through multiple channels: their own online store, marketplaces and direct sales. Each channel generates its own document streams that must be consolidated in DATEV. A professional DATEV interface consolidates these different document streams and ensures that all postings are consistent across channels – with uniform debtor numbers, correct revenue accounts and complete document archiving.

The challenge lies in the different data formats and processes of individual channels. The own Shopware store delivers structured API data, marketplaces send CSV settlements with their own reference numbers, and direct sales may work with manually created invoices. The middleware layer normalizes these different formats into a unified DATEV-compatible schema and ensures correct assignment to accounting accounts.

Particularly with marketplace sales, commission settlement is a complex posting process. The marketplace commission retained from the sales price must be posted as a separate expense. At the same time, the payout amount differs from the invoice amount, which must be considered during payment matching. Our DATEV integration maps these marketplace-specific posting logics fully automatically.

The automated transfer of posting data to DATEV significantly simplifies the preparation of monthly or quarterly VAT returns. Since all invoices and credit notes are posted with the correct tax keys, the VAT calculation in DATEV can be done at the push of a button. Manual corrections that are regularly necessary with spreadsheet-based accounting are virtually eliminated.

Since the introduction of the One-Stop-Shop (OSS) procedure, online retailers selling to consumers in other EU countries must apply the local tax rates of the destination country and report these centrally. The DATEV interface supports the OSS procedure by correctly recognizing country-specific tax rates, posting to separate tax accounts and providing the data required for OSS reporting in aggregated form. For B2B merchants who also serve B2C customers, this functionality is indispensable.

The transfer of financial data between store and DATEV places high demands on data security. All document data is transferred encrypted (TLS 1.3) and authentication uses token-based mechanisms. Access rights are configured so that only authorized systems and users can transfer or view posting data.

For audit compliance, a complete audit log is essential. Every document transfer is logged with timestamp, document type, amount and processing status. In the event of a tax audit, it is possible to trace for each journal entry when it was created, when it was transferred to DATEV and whether errors occurred. Archiving of original documents (invoice PDFs) is GoBD-compliant with immutability proof and long-term retention in accordance with the statutory periods of 10 years.

Another aspect of data security is the error resilience of the interface. During temporary connection problems to DATEV, posting data is cached in a local queue and automatically resent when availability returns. Dead-letter queues catch permanently unprocessable records and alert the operations team. This ensures that no document is lost – even during technical disruptions.

Requirements for a DATEV interface vary considerably depending on the business model and store complexity. A pure B2B store with purchase on account as the only payment method has different requirements than a B2X store with B2B and B2C customers, various payment methods and international shipping. We configure the DATEV integration individually for each scenario.

For pure B2B stores, the focus is on automated accounts receivable: each business customer is managed as a separate debtor, invoices are transferred with payment terms and discount information, and payment matching occurs via SEPA references. Document transfer covers invoices, credit notes and correction invoices. Regular customers with framework agreements receive special terms that must be correctly considered in the posting logic.

For subscription models and recurring orders, the DATEV integration is extended to correctly handle subscription invoices. Monthly billings are automatically generated and created as recurring postings in DATEV. Changes to subscriptions (upgrade, downgrade, cancellation) are processed as correction postings. This automation is particularly relevant for SaaS companies and merchants with consumable subscriptions.

An often overlooked aspect is the treatment of discounts and vouchers in DATEV accounting. Discounts can be posted as revenue reductions on the item account or as separate expenses – the accounting-correct treatment depends on the discount type. Volume discounts are typically posted as reduced revenue, while marketing vouchers can be posted as separate advertising expenses. The interface automatically distinguishes these cases and posts accordingly.

For international B2B merchants shipping to third countries, the correct posting of customs duties and import VAT is also required. When goods are delivered DDP (Delivered Duty Paid), the merchant must pre-finance customs duties and post them as expenses. For DAP deliveries (Delivered at Place), the buyer bears import costs, which accordingly do not appear in the merchant's accounting. The DATEV integration must correctly translate these different delivery terms into journal entries.