In short and in plain language
Many companies do their accounting with DATEV. This post shows how to connect your shop to it.
Without a link, someone types invoices and payments by hand. That takes a lot of time and causes errors.
There are several ways to send the data. The right accounts and tax rates matter most.
The system matches payments to invoices. It flags unclear cases for a manual check. Your tax advisor approves everything before it starts.
We can help you with this.
More than 51 million e-invoices passed through DATEV systems in the first half of 2026 (DATEV eG, 2026), compared with a good 64 million in the whole of 2025 (DATEV eG, 2026). For a B2B shop, this means that invoices, invoice corrections, payments and returns all end up in the tax advisor's books sooner or later, and every document keyed in by hand there costs time and creates reconciliation differences. A DATEV interface transfers this document flow automatically and traceably. This article walks through four transfer routes DATEV offers in 2026, what the e-invoicing mandate and the July 2025 GoBD amendment change about them, and how a purchase on account with cash discount, partial payment and invoice correction balances out in the debtor account.
Key takeaways
- More than 51 million e-invoices passed through DATEV systems in the first half of 2026 (DATEV eG, 2026). A shop that hands over invoices, payments and returns automatically spares the accountants from keying them in.
- Four common transfer routes: the DATEV format as CSV with the EXTF prefix and up to 99,999 postings per batch, the XML interface online, data services via the DATEV cloud, and DATEVconnect in your own network (DATEV Developer Portal).
- Since 1 January 2025, German businesses must be able to receive e-invoices; they must issue them for supplies from 2027, or from 2028 if prior-year turnover was at most 800,000 euros (Section 27(38) UStG).
- Since 2025, accounting vouchers must be kept for eight instead of ten years, books and annual accounts still for ten (Section 147(3) AO); for e-invoices, the structured XML part is sufficient (BMF, GoBD 2025).
- Revenue goes to 8400 at 19 percent and 8300 at 7 percent in SKR 03, to 4400 and 4300 in SKR 04; debtors sit in the number range 10000 to 69999 (DATEV-Kontenrahmen 2026).
- Purchase on account with 2 percent cash discount, partial payment and partial return: an open item of 11,900 euros clears with a 1,190 euro correction, two payments and 214.20 euros of discount (calculation example).
Why a DATEV Interface Pays Off in a B2B Shop
Financial accounting is one of the areas where online merchants have the greatest need for automation. Every order creates an invoice, every return a correction document, every incoming payment a journal entry. A shop with 500 orders per month therefore arrives at no fewer than 1,000 journal entries a month by simple arithmetic – one invoice and one incoming payment per order, plus corrections and payment differences. Captured by hand, this is error-prone, and the effort grows with every additional customer.
The German principles for the proper keeping and retention of books, records and documents in electronic form and for data access (GoBD) require completeness, accuracy, timely posting and traceability. They are set out in the Federal Ministry of Finance letter of 28 November 2019, which the ministry amended for the second time on 14 July 2025, mainly because of e-invoicing (BMF, GoBD 2025). An automated interface supports these requirements because documents are transferred and logged from the shop or ERP without a manual intermediate step.
On top of that comes timely accounting: postings reach DATEV daily instead of being collected at month-end. For growing B2B merchants, management reports and open items are therefore kept current.
Time Savings
Automated document transfer replaces typing and uploading documents by hand – the more documents, the greater the relief.
GoBD Requirements
Complete document chains, timely postings and unalterable storage of the originals support the GoBD requirements.
Fewer Errors
Machine-based transfer typically avoids typos, wrong account assignments and forgotten postings.
Current Overview
Daily postings give an ongoing view of revenue and open items without waiting for the month-end close.
EU Business
Intra-community supplies, reverse charge cases, distance sales to consumers and third-country exports go to separate accounts.
Scalability
The interface grows with the document volume without creating additional manual work in accounting.
Transfer Routes in 2026: DATEV Format, XML Online, Data Services, DATEVconnect
In its Developer Portal, DATEV documents, among others, two file formats for importing accounting data, the DATEV format and the XML interface online, and also offers data services via the DATEV cloud and the local interface DATEVconnect. Which route fits depends mainly on where the bookkeeping happens: at the tax firm, in the company itself, or first in DATEV Unternehmen online, which according to DATEV has more than 750,000 users (DATEV eG, 2026).
The DATEV format is the route for complete journal entries. DATEV describes it as a CSV file with the fixed file name prefix EXTF and a fixed record structure (DATEV Developer Portal): line 1 carries a header with metadata for processing, line 2 the column headings, and from line 3 onward the postings follow, with fields such as amount, debit/credit indicator, account, contra account, tax key, document date, document field 1, document field 2, cash discount and posting text. DATEV processes at most 99,999 postings per posting batch (DATEV Developer Portal); debtor and creditor master data have a separate format whose import has no volume limit. Import runs manually via batch processing, automatically via a local console program, or through the online interface accounting:extf-files at the DATEV data center. For Shopware-based shops, we generate these files from order and invoice data.
The DATEV XML interface online is a file-based interface for structured invoice and cash register data, including digitized documents, sent to DATEV Unternehmen online (DATEV Developer Portal). It transfers a package of an administration file, a ledger record file and the document files, either with the free DATEV Belegtransfer app or via the online interface accounting:dxso-jobs. DATEV states explicitly what this route does not cover: pure general-ledger postings such as payment postings, and the transfer of debtor and creditor master data (DATEV Developer Portal). Anyone who needs to hand over payments and personal accounts therefore also needs the DATEV format or a data service.
The accounting data services work via the DATEV cloud without a separate file handover. The DATEV Buchungsdatenservice transfers posting data, master data and the associated document images from a software solution to DATEV Kanzlei-Rechnungswesen; the document images are then stored in Belege online and linked to the journal entry (DATEV). Rechnungsdatenservice 1.0 sends structured document data and document images to DATEV Unternehmen online and in the process creates posting proposals for the DATEV accounting programs (DATEV), while Belegbilderservice Rechnungswesen only transfers the documents. DATEV is discontinuing Rechnungsdatenservice 2.0 completely as of 31.12.2026, and it has no longer been available to order since 01.01.2026 (DATEV). All data services require the shop or ERP software to have implemented the respective service.
DATEVconnect is the interface for DATEV programs in your own network, that is, for tax firms and companies that run DATEV on premises. For DATEVconnect Rechnungswesen, DATEV describes a bidirectional data exchange between third-party solutions and DATEV accounting applications that is based on the fields of the DATEV format (DATEV). It requires a license and third-party software that has implemented DATEVconnect. For a shop without a local DATEV installation, this is rarely the first route; it pays off when the company does its own bookkeeping and wants to synchronize debtors in both directions.
| Feature | DATEV Format | XML Interface Online | Buchungsdatenservice | DATEVconnect |
|---|---|---|---|---|
| Target | DATEV Rechnungswesen | DATEV Unternehmen online | Kanzlei-Rechnungswesen via the DATEV cloud | DATEV programs in your own network |
| Postings incl. payments | included | No, no general-ledger postings | included | included |
| Document images | No, only a document link field | Yes, in the package | Yes, in Belege online | Via DATEVconnect Dokumentenmanagement |
| Debtor master data | Yes, separate format | not included | included | Yes, bidirectional |
| Transfer | File or online interface | Belegtransfer app or online interface | Data service, activated by the tax firm | Local interface with license |
| Fits | Shop or ERP that assigns accounts itself | Invoice output with document review | Software with a DATEV data service | Companies with a local DATEV installation |
Decision Guide: Which Route Fits Which Shop Scenario
Three questions decide: who assigns the accounts, who does the bookkeeping, and where does the document archive live? If the ERP already assigns debtor, revenue account and tax key completely, the DATEV format is the direct route, as a file or via the online interface. If the tax firm does the bookkeeping and the company wants to see its sales invoices in DATEV Unternehmen online first, the XML interface online or Rechnungsdatenservice 1.0 fits; payments are then added via bank transactions or a payment data service. If the shop software supports the Buchungsdatenservice, the file handover disappears altogether. DATEVconnect is an option when the company runs DATEV on premises and does its own bookkeeping.
For a typical B2B shop with purchase on account, where invoices originate in the ERP, payments come from the bank and the tax firm does the bookkeeping, the DATEV format for postings and debtors, supplemented by document images in Belege online, usually works well. A shop without its own ERP often reaches the goal faster with a data service built into the shop software.
E-Invoicing in B2B: Receipt Since 2025, Issuing From 2027
Mandatory e-invoicing for supplies between domestic businesses has applied since 1 January 2025 (BMF, GoBD 2025). Since then, domestic businesses must create the technical prerequisites for receiving e-invoices (BMF, UStAE 14.1); for receipt by email, an existing mailbox is sufficient (BMF, UStAE 14.1). An e-invoice is an invoice that is issued, transmitted and received in a structured electronic format and enables electronic processing (Section 14(1) UStG). A PDF file sent by email, by contrast, is an other invoice (Section 14(1) UStG).
The format must comply with the European standard or, if issuer and recipient agree on it, allow the required details to be extracted correctly and completely into a format that complies with the standard (Section 14(1) UStG). XRechnung complies with the EN 16931 series of standards (BMF, UStAE 14.1), as does ZUGFeRD from version 2.0.1, except for the MINIMUM and BASIC-WL profiles (BMF, UStAE 14.1). How a shop generates both formats from the same order data and hands over incoming documents is described on our page on e-invoicing in the B2B shop.
Transitional rules apply to issuing. Invoices for supplies made in 2025 and 2026 may still be sent on paper or, with the recipient's consent, in another electronic format until 31 December 2026 (Section 27(38) UStG). For supplies made in 2027, this only applies until 31 December 2027 if the issuer's total turnover in the previous year was no more than 800,000 euros (Section 27(38) UStG); EDI procedures that do not follow the standard also remain permitted with the recipient's consent until the end of 2027 (Section 27(38) UStG). For supplies from 1 January 2028, the provision no longer provides an exception. According to DATEV, many clients intend to use the transition period to the full (DATEV eG, 2026) – for the interface, 2026 is therefore the year in which the outgoing and incoming routes should be tested with real documents.
| Invoice for supplies made in | Sales invoice to domestic businesses | Legal basis |
|---|---|---|
| Receipt | Since 1 January 2025, domestic businesses must be able to receive e-invoices | BMF, UStAE 14.1 |
| 2025 and 2026 | E-invoice, or until 31.12.2026 still paper or another electronic format with consent | Section 27(38) no. 1 UStG |
| 2027 | E-invoice; exception until 31.12.2027 for prior-year turnover up to 800,000 euros or EDI with consent | Section 27(38) nos. 2 and 3 UStG |
| From 2028 | E-invoice in a structured format | Section 14(1) and (2) UStG |
For the DATEV handover, the most important consequence is: the original is the XML file, not the PDF. For an e-invoice, at least the structured part must be retained intact in its original form (BMF, UStAE 14b.1). An interface that passes on only the invoice image from a ZUGFeRD file and discards the embedded XML loses exactly this part. For sales invoices from an invoicing program, no pictorial copy needs to be stored if a copy with identical content can be produced at any time (BMF, GoBD 2025). In practice, the shop or ERP generates XRechnung or ZUGFeRD, stores the XML unalterably and hands over the journal entry and the document to DATEV with the same invoice number in document field 1.
Which fields become tricky with collective invoices and cash discounts is shown in XRechnung 4.0: Collective Invoices and Cash Discounts in B2B; how to prepare shop and ERP as a whole is covered in E-Invoicing Mandate 2027: Prepare B2B Shop and ERP.
Correct Account Assignment and Tax Rate Mapping
Account assignment is the heart of every DATEV integration: every journal entry needs a revenue account, a tax key and a debtor, and in online retail tax rates change with the delivery country and customer type.
As a rule, the tax firm works with the standard chart of accounts SKR 03 or SKR 04. Revenue from sales of goods goes to separate accounts depending on the tax rate: in SKR 03 to 8400 at 19 percent and 8300 at 7 percent VAT, in SKR 04 to 4400 and 4300 (DATEV-Kontenrahmen 2026). The rates themselves are set by law: 19 percent standard (Section 12(1) UStG), 7 percent reduced (Section 12(2) UStG). Intra-community supplies to businesses with a valid VAT ID are tax-exempt and go to separate revenue accounts. The mapping is defined once with the tax advisor and then applied by the interface; how the VAT ID can already be checked at checkout is described in the article VAT in the B2B shop: validating VAT IDs correctly.
Tax rate mapping needs particular attention for deliveries to consumers in other EU countries, for example when a B2B shop also supplies private customers. Since 1 July 2021, merchants can opt into the One-Stop-Shop procedure for such sales (Section 18j UStG). If intra-community distance sales and certain services to consumers in other member states exceed 10,000 euros in the previous or the current year, the tax rate of the country of destination applies (Section 3c(4) UStG). Since June 2021, the DATEV format has carried dedicated fields for the EU country, VAT ID and tax rate of origin and destination (DATEV Developer Portal). The interface must recognize these rates and post to separate accounts – with manual entry, this is a frequent source of errors.
Automating Debtor Management
Every business customer in the shop needs a matching debtor account in DATEV. For B2B shops with hundreds or thousands of business customers, creating and maintaining these accounts by hand is considerable effort. Automated debtor management creates new debtors on the first order or takes them over from the ERP, and synchronizes master data changes such as address, VAT ID and payment terms.
The DATEV standard chart of accounts provides fixed ranges for personal accounts: 10000 to 69999 for debtors and 70000 to 99999 for creditors (DATEV-Kontenrahmen 2026). If the ERP holds the debtor number, the interface takes it over unchanged; otherwise the assignment of shop customer number to DATEV debtor is kept in a mapping table that is resolved with every transfer. The master data itself goes via the debtor format of the DATEV format or a data service; the XML interface online cannot transfer it (DATEV Developer Portal). For business customers with several ordering addresses or group structures, separate invoice recipients and debtors per company can be set up.
Payment Matching and Open Items
Payment matching is one of the most time-consuming tasks in online retail. Payments via different channels – credit card, PayPal, SEPA direct debit, purchase on account, prepayment – must be assigned to the right invoices. For individual payment providers, DATEV offers its own payment data services whose transactions can be assigned to the invoice data automatically (DATEV).
The interface detects the incoming payment in the shop, at the payment provider or in the bank account, matches it via invoice number, amount and debtor, and posts it to the right cash account. It flags partial payments, overpayments and differences for clarification instead of writing them off silently. Business customers often settle several invoices with one SEPA transfer; the structured payment reference then carries the matching.
Posting Returns and Invoice Corrections Correctly
Returns require particular care in DATEV accounting. The correction document must reference the original invoice, use the tax rate of the original line and reduce the revenue account. For partial returns, it lists the returned lines individually while the remaining ones stay untouched.
For VAT purposes, a return usually reverses the delivery in whole or in part. If the taxable amount decreases after the invoice has been issued, an invoice correction is not required – the BMF explicitly names cash discounts and the reversal of a supply as examples (BMF, para. 51a). If the scope of the supply changes, by contrast, the invoice generally has to be corrected (BMF, para. 51b). Be careful with the term: in German VAT law, a Gutschrift is self-billing by the recipient of the supply based on a prior agreement (Section 14(2) UStG). The correction document after a return is not such a self-billing credit note, even though retail often calls it one.
The interface maps the process from the return notification through the goods-receipt inspection to the correction document and attaches the document to the posting as a document image.
GoBD 2025: Eight Years for Accounting Vouchers, XML as the Original
Since 2025, accounting vouchers must be kept for eight instead of ten years. Ten years still apply to books, records, inventories and annual accounts, including the work instructions and organizational documents needed to understand them; eight years apply to accounting vouchers and six years to the remaining documents such as business letters received and sent (Section 147(3) AO). The shorter period applies to all documents whose previous period had not yet expired on 31 December 2024 (Art. 97 Section 19a EGAO); credit institutions, insurers and investment firms have their own transitional rule. For invoices, the VAT Act also sets eight years (Section 14b UStG).
The period starts at the end of the calendar year in which the accounting voucher was created (Section 147(4) AO), and it does not expire as long as the documents are relevant for taxes whose assessment period is still open (Section 147(3) AO). A sales invoice from March 2026 must therefore be kept at least until the end of 31 December 2034. The account mapping used for postings in 2026, by contrast, usually counts among the organizational documents of the books and thus falls under the ten-year period. Deletion runs in the shop or ERP must therefore not be based on the order date but on the document type, the start of the period and any open audits.
The second GoBD amendment of 14 July 2025 applies from that day (BMF, GoBD 2025) and adapts the rules to e-invoicing. For e-invoices, it is sufficient to keep the structured part; the human-readable part of a hybrid invoice, such as the PDF of a ZUGFeRD file, is only needed if it carries additional tax-relevant information such as posting notes (BMF, GoBD 2025). Incoming documents must be kept in the format in which they were received (BMF, GoBD 2025). Records from a payment service about the technical processing of a payment do not have to be retained as long as they do not serve as an accounting voucher (BMF, GoBD 2025).
| Document from the shop process | Period | Legal basis |
|---|---|---|
| Books, journal, annual accounts, organizational documents such as account mapping and procedure documentation | 10 years | Section 147(1) no. 1, (3) AO |
| Accounting vouchers: sales invoices, invoice corrections, bank statements | 8 years | Section 147(1) no. 4, (3) AO |
| Invoice copies and invoices received | 8 years | Section 14b(1) UStG |
| Business letters, for example order confirmations | 6 years | Section 147(1) nos. 2 and 3, (3) AO |
| Delivery notes sent that are not accounting vouchers | until the invoice is sent | Section 147(3) AO |
| E-invoice | structured part is sufficient, PDF only with additional information | BMF, GoBD 2025, para. 119 |
Where customers find their invoices in the customer account and how long they should stay there is described in Where Order Documents Live and How Long They Stay. For the interface, what counts is that shop, ERP and DATEV hold the same version of a document.
Implementation: Project Workflow and Timeline
Implementing a DATEV interface follows a fixed sequence. In the first phase, we analyze the accounting process, the chart of accounts and the requirements for document transfer together with the tax advisor and decide on the transfer route. This phase typically takes 1–2 weeks (project experience).
In the second phase, the account mapping is defined: which product groups go to which revenue accounts, how tax keys are assigned and which scheme creates debtor numbers. The third phase covers the technical implementation of the interface to DATEV, including error handling, retry logic and logging. In the fourth phase, all document types are run through with test data and checked by the tax advisor. A pure posting transfer can be implemented in three to four weeks; with debtor master data, payment matching and document images, a project usually takes 4–6 weeks (project experience).
Involve Your Tax Advisor Early
Common Pitfalls and How to Avoid Them
In DATEV projects we see recurring errors that can be avoided with a little planning. The most common is inconsistent account mapping: if the tax advisor changes the chart of accounts and the interface does not follow, postings land on the wrong accounts. We solve this with a central configuration that is changed in one place only and versioned with a date.
A second classic is rounding differences. With tiered prices and volume discounts, cent differences can arise between the shop calculation and the DATEV posting. The interface must detect them and handle them according to a rule agreed with the tax advisor instead of rejecting the transfer. With high order volumes, the differences add up and must remain traceable.
Then there are errors that only show up on import or in day-to-day operation:
- Character set: the default for import is ISO-8859-1 or code page 1252; DATEV Rechnungswesen only recognizes UTF-8 if the file starts with a byte order mark (DATEV Developer Portal). Without it, umlauts in customer names and posting texts are imported incorrectly. Anyone importing via the local console program delivers ISO-8859-1 or code page 1252, because Unicode only works with manual import or via the online interface accounting:extf-files (DATEV Developer Portal).
- Batch size: a posting batch holds at most 99,999 postings (DATEV Developer Portal). Large merchants split the transfer by period or document type.
- Service being discontinued: anyone still using Rechnungsdatenservice 2.0 loses retrieval as of 31.12.2026 (DATEV) and must test the successor route beforehand.
- Two routes for one document: if Rechnungsdatenservice and posting batch run in parallel for the same invoices, duplicate postings result.
Finally, test coverage is decisive. Before go-live, we test every document type with test data: standard invoices, partial deliveries, invoice corrections, cancellations, foreign invoices, reverse charge documents and collective invoices. The tax advisor checks the posting results in a test client. Only after all document types have been approved does the interface go into production.
DATEV and Multi-Channel: Unified Accounting
Many B2B merchants sell through their own shop, marketplaces and direct sales. Each channel generates its own document streams, which must come together in DATEV with the same debtor numbers and revenue accounts.
Your own Shopware store delivers structured data, marketplaces send settlements with their own reference numbers, and direct sales invoices from the ERP. An intermediate layer brings these formats into a uniform schema for DATEV.
With marketplace sales, the commission settlement is a posting process of its own. The retained commission is posted as an expense, and because the payout differs from the invoice amount, the interface matches the payout against the individual open items instead of posting a lump sum to a single account.
Advance VAT Returns and the OSS Procedure
When invoices and corrections are posted with the right tax keys, the tax firm can prepare the advance VAT return directly from DATEV; manual corrections become much rarer.
If the merchant uses the One-Stop-Shop procedure for distance sales to consumers in other EU countries, the One-Stop-Shop return is added. In Germany, the competent tax authority for this is the Federal Central Tax Office (Section 18j UStG). The interface provides the basis by posting sales per country of destination at the local tax rate to separate accounts; the return per country can be derived from them. For B2B merchants who also supply private customers in other EU countries, this belongs in the account mapping from the start.
Data Security and Audit Compliance
Document data is transferred encrypted, sign-in to DATEV services uses token-based procedures, and only authorized systems and people may transfer or view posting data.
For audit compliance, a complete log is essential. Every transfer is recorded with timestamp, document type, amount and processing status. In a tax audit, it is then possible to trace for every journal entry when it was created, when it went to DATEV and whether errors occurred. The original documents are stored unalterably and retained for the periods set by the Fiscal Code, that is, eight years for accounting vouchers and ten years for books (Section 147(3) AO).
This includes the error resilience of the interface. During temporary connection problems, posting data is held in a queue and resent automatically. A dead-letter queue catches records that cannot be processed and alerts the operations team. This keeps every document that has not been transferred visible until it has been resolved.
DATEV Integration for Different Store Scenarios
Requirements differ by business model: a pure B2B shop with purchase on account needs something different from a shop with private customers, several payment methods and international shipping.
For pure B2B shops, the focus is on accounts receivable: each business customer is kept as a separate debtor, invoices go to DATEV with payment terms and cash discount information, and payment matching runs via the invoice number in the payment reference. Invoices, invoice corrections and payments are transferred. Regular customers with framework agreements receive their own terms, which must be reflected in the posting logic.
Worked Example: Purchase on Account With Cash Discount, Partial Payment and Partial Return
A business customer with debtor number 10050 from the ERP orders goods worth 10,000 euros net. The shop issues invoice 2026-1042 for 11,900 euros gross with 19 percent VAT, payment terms of 30 days net and 2 percent cash discount for payment within 14 days. On the invoice, a statement such as "2 % Skonto bei Zahlung bis" with a date is sufficient (BMF, UStAE 14.5); it does not have to show the discount amount (BMF, UStAE 14.5). After five days the customer returns goods worth 1,000 euros net, on day ten they transfer 5,000 euros, and on day 14 the remainder less cash discount. The figures are freely chosen; the accounts follow SKR 03 (DATEV-Kontenrahmen 2026).
| Step | Document | Debit | Credit | Amount | Open item afterwards |
|---|---|---|---|---|---|
| Day 0: invoice | 2026-1042 | 10050 debtor | 8400 revenue 19 % VAT | €11,900.00 | €11,900.00 |
| Day 5: invoice correction after partial return | Correction document referencing 2026-1042 | 8400 revenue 19 % VAT | 10050 debtor | €1,190.00 | €10,710.00 |
| Day 10: partial payment | 2026-1042 | 1200 bank | 10050 debtor | €5,000.00 | €5,710.00 |
| Day 14: remaining payment | 2026-1042 | 1200 bank | 10050 debtor | €5,495.80 | €214.20 |
| Day 14: 2 % cash discount on €10,710.00, VAT correction under Section 17 UStG | 2026-1042 | 8736 cash discounts granted 19 % VAT | 10050 debtor | €214.20 | €0.00 |
DATEV calculates the VAT itself via the automatic accounts (DATEV-Kontenrahmen 2026): the 11,900 euros contain 1,900 euros of tax, the invoice correction 190 euros and the cash discount 34.20 euros. Because the cash discount reduces the taxable amount and the same applies to the partial return as a reversal of the supply (Section 17(2) no. 3 UStG), the merchant corrects the tax owed (Section 17(1) UStG) and the customer their input tax deduction (Section 17(1) UStG). No new invoice is needed for this (BMF, para. 51a). In the end, debtor 10050 shows 11,900.00 euros on the debit side and 1,190.00 + 5,000.00 + 5,495.80 + 214.20 = 11,900.00 euros on the credit side; the open item is cleared.
Where things go wrong in practice: if the customer transfers only 5,400 euros on day 14, 95.80 euros remain open. The interface does not post this difference as cash discount or write-off on its own authority but flags the item; whether a very small difference is written off is decided by accounting according to a fixed tolerance rule. The order matters just as much: if the payment reaches DATEV before the invoice correction, the item temporarily looks like an overpayment. That is why we transfer correction documents on the same day and match payments via the invoice number, not via the amount.
For the example to balance, payment terms must match in shop, ERP and DATEV: the payment period and cash discount scale of the customer group belong to the debtor as payment terms and on the invoice. Which payment methods, payment terms and credit limits work well in a B2B checkout is shown on our page on B2B payment methods with purchase on account and credit limits. The DATEV format treats payment terms as a separate master data format (DATEV Developer Portal), and since format version 13 of February 2024, a deviating cash discount account can be passed in the posting batch (DATEV Developer Portal).
Subscriptions, Discounts and Third-Country Shipping
With subscriptions, recurring invoices are created that go to DATEV like any other invoice; changes of scope or cancellations run as invoice corrections.
Discounts and vouchers can reduce revenue or run as a separate expense: volume discounts usually reduce revenue, promotional vouchers can be advertising expense. The tax advisor decides which treatment applies, and the interface applies the rule.
With shipping to third countries, the posting of customs duties and import VAT is added: if the merchant delivers duty paid (Incoterm DDP), they advance the import charges and post them as an expense; with delivery without customs clearance (Incoterm DAP), the buyer bears them.
A DATEV interface takes one of the most laborious tasks in accounting off the shop. With the e-invoicing mandate from 2027 and the GoBD as amended in July 2025, what counts most is a clean route from the XML original to the cleared open item – defined and tested once with the tax advisor, it grows with the order volume.
Related Articles
ERP Integration in B2B E-Commerce: SAP, DATEV, Dynamics
ERP integration in B2B e-commerce: How to seamlessly connect SAP, DATEV and Microsoft Dynamics with your online store and automate your processes.
API Architecture in B2B: REST, GraphQL and Message Queues
Integration patterns for B2B e-commerce: REST, GraphQL, SAP OData, message queues, asynchronous processing and robust error handling compared side by side.
Variant Matrix in the B2B Shop: Sizes and Colors in One Go
A variant matrix lets B2B buyers order sizes and colors in one table: stock per cell, tier pricing across the total, a mobile list. What Shopware CE offers.