DATEV Interface for E-Commerce: Automating Accounting
DATEV is the most widely used accounting software in Germany, serving over 2.7 million businesses (DATEV eG, 2025). For B2B online shops, connecting to DATEV represents a central automation lever: instead of manually posting invoices, credit notes, and payment receipts, an interface automatically generates the correct journal entries in DATEV format. This not only saves considerable time but reduces errors to a minimum and accelerates the monthly close. In this article, you will learn how a DATEV integration works, which formats and data fields are relevant, and what to watch for during implementation.
Why DATEV Integration Is Essential for B2B Shops
Manual posting of e-commerce transactions is one of the biggest time drains in accounting. For a B2B shop with 500 orders per month, at least as many sales invoices are generated, plus credit notes, reversal entries, and payment allocations. According to a Bitkom survey, an accountant needs an average of 4.8 minutes for manual entry of a journal posting (Bitkom, 2024). With 500 postings, that amounts to over 40 hours per month, a full work week just for transferring shop data to accounting.
Additionally, there is the error-proneness of manual entries. Transposed digits in amounts, incorrect account assignments, or forgotten tax amounts lead to discrepancies that must be painstakingly corrected at the latest during the annual close. An automated DATEV interface virtually eliminates these error sources. The investment pays for itself within a few months for most B2B shops.
DATEV in Numbers
DATEV Formats and Interfaces Overview
DATEV offers various import formats and interfaces that differ in scope and automation level. The choice of the right format depends on the DATEV version in use, the tax advisor's requirements, and the desired degree of automation.
| Format | Type | Automation | Use Case |
|---|---|---|---|
| DATEV Format (ASCII) | CSV/Text file | Manual import | Journal stack, debtor master |
| DATEV XML online | XML interface | Automatic | Documents and posting data |
| DATEV Document Link | Document transfer | Semi-automatic | Linking invoice PDFs |
| DATEV Unternehmen online | Cloud platform | Automatic | Complete document management |
| DATEV Connect online | REST API | Fully automatic | Real-time synchronization |
For most B2B shops, the classic DATEV format (also called DATEV journal stack or ASCII format) is the pragmatic entry point. It is supported by all DATEV versions and can be reliably generated from the shop system. The file contains one journal entry per line with all relevant fields: amount, debit and credit account, document date, posting text, tax code, and cost center. The tax advisor imports the file into DATEV and can immediately begin the review.
For advanced automation, DATEV Connect online offers a REST-based API enabling bidirectional data exchange in real time. Posting data is transferred directly from the B2B shop to DATEV without needing to export and import a file. This solution, however, requires DATEV activation by the tax advisor and registration as a DATEV interface partner.
Account Mapping: Correctly Assigning General and Debtor Accounts
The correct assignment of shop transactions to DATEV accounts is the heart of any DATEV integration. Incorrect account assignments lead to erroneous balance sheets and require extensive corrections. In B2B e-commerce, various business transactions must be correctly posted to the appropriate general ledger accounts.
Revenue Postings
Sales invoices are posted to the corresponding revenue account (e.g., 4400 Revenue 19% VAT, 4300 Revenue 7% VAT). When different tax rates apply, the interface must split the line items accordingly.
Debtor Accounts
Each business customer receives their own debtor account (typically starting from 10000). The interface must automatically create new debtors and consistently maintain the mapping between shop customer number and DATEV debtor number.
Credit Notes and Reversals
Returns and credit notes require offset entries on the corresponding reversal accounts. The link to the original invoice must be preserved so the tax advisor can trace the relationship.
Payment Allocation
Incoming payments are allocated to the respective debtor account and clear the open items. For partial payments or cash discount acceptance, the interface must generate the correct journal entries.
A common problem with account mapping involves international business transactions. Deliveries within the EU (intra-community supply) and to third countries are subject to different tax regulations that must be posted to different general ledger accounts. The interface must automatically select the correct tax code and revenue account based on the delivery address and the customer's VAT ID. Errors at this point can lead to significant tax consequences and should therefore be coordinated with the tax advisor.
VAT Handling: Tax Codes and International Cases
Correct VAT treatment is the most complex aspect of a DATEV integration in e-commerce. In the B2B sector, various special cases must be reliably mapped by the interface in addition to the standard tax rate.
- Standard taxation 19%: Standard tax code for domestic deliveries (DATEV tax code 1)
- Reduced rate 7%: For certain product groups such as food or books (tax code 2)
- Tax-exempt intra-community supply: Deliveries to businesses in other EU states with valid VAT ID (tax code 41)
- Tax-exempt export delivery: Deliveries to third countries (tax code 30)
- Reverse charge procedure: For certain services to EU business customers (tax code 94)
- OSS procedure (One-Stop-Shop): For B2C deliveries to other EU countries above the 10,000 euro threshold
The DATEV interface must automatically determine the correct tax code for each business transaction. This requires the following information from the shop: the customer's country, the VAT ID (for B2B verification), the delivery address, the product group, and the type of service (goods or services). Validation of the VAT ID via the EU Commission's VIES database should already occur during customer registration in the B2B portal, not only during posting creation.
Attention: VAT ID Verification
Implementation: Steps to DATEV Integration
Implementing a DATEV interface follows a structured process that should be closely coordinated with the tax advisor. It is crucial that the chart of accounts and posting logic are clarified in advance so the interface delivers correct data from the start.
- Requirements analysis: Coordinate chart of accounts (SKR03 or SKR04), debtor number ranges, cost centers, and tax codes with tax advisor
- Mapping definition: Create a mapping table that assigns each shop business transaction to a DATEV posting pattern
- Format selection: Decision between DATEV format (file export), DATEV XML online, or DATEV Connect online (API)
- Development: Implement interface module with mapping engine, validation, and export/upload functionality
- Test phase: Parallel operation with manual bookkeeping, comparison of results, fine-tuning of account assignments
- Go-live: Switch to automated operation, monitoring of initial monthly closes, feedback loop with tax advisor
A critical success factor is the test phase. The interface should run in parallel with manual bookkeeping for at least one full month. The automatically generated journal entries are compared with manually created ones, and deviations are analyzed and corrected. Only when consistency is established is the switch to automated operation made. This parallel approach costs more time in the short term but avoids costly errors in production. Professional implementation by an experienced partner significantly reduces project risk.
Document Linking: Automatically Assigning Invoice PDFs
Beyond posting data, the tax advisor also expects the associated documents. In e-commerce, these are primarily the invoice PDFs that the shop automatically generates. DATEV document linking enables connecting these PDFs directly with the respective journal entry, allowing the tax advisor to navigate from the posting directly to the document.
The technical implementation occurs via DATEV Document Link or DATEV Unternehmen online. The shop generates a PDF for each invoice, names it according to a defined scheme (e.g., invoice number as filename), and provides it together with the posting data. With the DATEV XML interface, documents can be directly embedded or referenced as separate files.
For B2B shops with high document volumes, the automatic upload function to DATEV Unternehmen online is recommended. Invoice PDFs are uploaded directly to the document archive via API and automatically linked with the corresponding journal entries. This eliminates manual effort for document filing and ensures that digital document archiving meets GoBD requirements.
Error Handling and Monitoring of the DATEV Interface
A DATEV interface must handle errors robustly. Not every business transaction can be automatically assigned correctly. New tax scenarios, special cases like triangular transactions, or incomplete customer data can result in an invalid journal entry.
- Pre-export validation: Every journal entry is checked against DATEV format specifications before export
- Error queue: Invalid journal entries are moved to a separate queue and flagged with the error reason
- Notification: On errors, accounting automatically receives an email with a summary of faulty entries
- Manual correction: A back-office interface enables editing and re-validation of faulty postings
- Audit log: Every action is logged so it is traceable when each journal entry was created, validated, and exported
- Monitoring dashboard: Daily overview of exported postings, error rate, and pending corrections
A particularly critical aspect is ensuring completeness. No business transaction may be lost during transfer. A reconciliation of the count and total of exported journal entries against shop transactions ensures all transactions have been captured. Regular reconciliations between shop revenue and DATEV postings are an essential part of internal controls and interface quality assurance.
GoBD Compliance: Legal Requirements for Digital Bookkeeping
The GoBD (Principles for the proper keeping and storage of books, records, and documents in electronic form) establishes specific requirements for digital bookkeeping. A DATEV interface must consider these requirements so that automated bookkeeping complies with legal requirements.
- Immutability: Exported posting data may not be subsequently altered. Corrections are made exclusively through reversal and new postings
- Traceability: Every journal entry must be traceable via a document reference to the underlying business transaction
- Timely recording: Postings must be made promptly, ideally daily or at the latest within 10 days of the business transaction
- Retention obligation: Posting documents and associated data must be retained for 10 years, commercial correspondence for 6 years
- Process documentation: The functionality of the interface must be documented, including mapping rules, validation logic, and error handling
- Access control: Only authorized persons may access, modify, or export the posting data
Process documentation is an often underestimated aspect. It must describe in detail how the interface works, which data is transferred in which format, how account assignment occurs, and how errors are handled. In the event of a tax audit, this documentation must be available for the auditor. A professional B2B portal with DATEV connectivity delivers this documentation as part of the implementation.
Related Articles
Automate accounting and accelerate monthly closing
We implement a reliable DATEV interface for your B2B shop that automatically generates journal entries and simplifies collaboration with your tax advisor.
Plan DATEV integration