Shopify DATEV integration
What DATEV actually does in this chain
DATEV is financial accounting and tax advisory software, not an inventory management system. It holds no product master data, no stock levels and no prices. Anyone looking for a "DATEV integration" almost always means something else: that Shopify revenue, refunds and fees arrive at the tax advisor as journal entries, posted to the right accounts and with the right tax keys.
That is why the task looks different from an ERP project. It is not about synchronisation in both directions, but about a clean handover in one direction: out of Shopify, or out of the ERP upstream of it, into a format DATEV can read. Everything to do with stock or products belongs in another system, and if there is none, that is the real gap.
Which objects run in which direction
The many empty rows are the result, not an oversight: DATEV cares about documents and accounts, not about catalogue data.
| Object | Direction | Leading system | Note |
|---|---|---|---|
| Products | no sync | - | DATEV holds no product master data. That needs an ERP or a PIM. |
| Inventory | no sync | - | Stock management is not a DATEV topic. |
| Prices | no sync | - | Prices are set in the store or the ERP, not in accounting. |
| Orders | Shopify → | Shopify | Orders become revenue postings with an account and a tax key. |
| Credit notes | Shopify → | Shopify | Refunds and cancellations as separate journal entries, not as a correction to the original. |
| Customers | Shopify → | Split by field | Only where customer accounts are kept. A collective customer account is often enough. |
| Journal entries | Shopify → | DATEV | Journal-entry batches in the DATEV format, usually once per month. |
Which route holds up
Handover from the ERP
The cleanest route when an ERP is involved. Invoices and credit notes are created there anyway, so the accounting handover hangs off that system. Shopify stays a sales channel and does not need to know anything about accounting.
A specialised accounting app
Without an ERP, apps take on the job: they read orders, refunds and payouts out of Shopify and produce a journal-entry batch DATEV can read. The work sits in the one-off account mapping, not in the technology.
Your own export
Worth it with unusual account logic or several legal entities in one store. A custom export reproduces exactly your rules, but it needs your accounting firm at the table before the first line is written.
Common pitfalls
Payment providers not reconciled
Shopify Payments, PayPal and Klarna pay out in batches and net of fees. If you only post orders, the payout will never reconcile cleanly. You need a clearing account per provider and the payout data to go with it.
Tax keys and cross-border sales
Sales into other EU countries, small-business exemptions and reporting through the One Stop Shop scheme all need different keys. The mapping should be agreed with your tax advisor, not worked out by trial and error in the journal-entry batch.
Credit notes treated as corrections
Refunds must not overwrite the original document. They are their own postings with their own date. Reducing the original revenue instead destroys the audit trail between the store, the payment provider and accounting.
Frequently asked questions
Can DATEV take over products and stock levels from Shopify?
What is handed over to DATEV?
How are Shopify Payments and PayPal posted correctly?
Do I need an ERP for this?
Who decides on the account mapping?
Related integrations
More projects
Not sure which pattern carries your setup?
A 30-minute intro call. We look at your systems, ask which data belongs where and give you a clear assessment before anything gets built.
Free and non-binding · 30 min.





























