How to push order data to accounting (DATEV, Xero, QuickBooks)?
Quick Answer
You push Shopware order data into DATEV, Xero, or QuickBooks by connecting Shopware order events to an integration layer (API, middleware, or ERP connector). Most setups use Shopware Flow Builder + webhooks + accounting APIs. The key is normalizing tax, currency, and invoice data before sync so each system receives clean accounting-ready entries.
In Shopware, order data does not automatically match accounting systems out of the box. DATEV, Xero, and QuickBooks all expect structured accounting entries, not raw ecommerce orders. That means you need a translation layer between checkout events and bookkeeping formats.
The good news is Shopware is flexible. You can push orders in real time or batch mode using Flow Builder, webhooks, or middleware tools like Make or custom API services. The approach depends on how strict your accounting requirements are and how much automation you want.
Before You Start
- ✦Shopware admin access — needed to configure Flow Builder and API settings
- ✦Accounting API credentials — DATEV, Xero, or QuickBooks developer access
- ✦Clear tax rules — VAT, OSS, or region-based tax mapping defined first
Define integration architecture
Start by deciding how Shopware will communicate with your accounting system. You can go direct API (Shopware → Xero/QuickBooks), or use middleware (Shopware → Make/Zapier → accounting). DATEV setups usually require file-based or ERP-style exports instead of direct API calls.
- Choose API, middleware, or export-based sync
- Decide real-time vs batch processing
Configure Shopware order events
Use Shopware Flow Builder to trigger events when an order is placed, paid, or fulfilled. These events act as the starting point for your accounting sync. Without event triggers, you will end up with manual exports or inconsistent data timing.
- Trigger on order completed or paid status
- Attach webhook or API call action
Map order data to accounting format
Accounting systems do not accept raw ecommerce orders. You must map Shopware data like line items, taxes, discounts, and shipping into accounting entries. This is where most integrations fail because tax handling differs across systems.
- Normalize VAT and tax breakdowns
- Align currency and rounding rules
Connect accounting API or exporter
Now connect Shopware to your accounting tool. Xero and QuickBooks support REST APIs for invoices and contacts. DATEV usually requires structured exports or ERP connectors depending on your accountant setup.
- Authenticate using API keys or OAuth
- Send invoice or journal entries payload
Implement sync reliability layer
Add retry logic, logging, and idempotency checks so orders are not duplicated in accounting. This is critical when dealing with payment retries or webhook replays.
- Prevent duplicate invoices using order IDs
- Log failed sync attempts for review
Shopware Accounting Sync Checklist
0 of 6 completeMistakes Most Developers Make
! Ignoring tax structure differences
What happens: VAT mismatches break reconciliation in accounting systems.
Fix: Normalize tax rules in Shopware before sending data.
! Sending raw order payloads
What happens: Accounting tools reject or misinterpret data.
Fix: Map orders into invoice or journal formats first.
Key Takeaway
The short version: Shopware does not send accounting-ready data by default, so you must sit an integration layer between orders and tools like DATEV, Xero, or QuickBooks. The real work is not sending the order — it is mapping taxes, invoices, and currency correctly. Start with Flow Builder and API mapping first — that covers most setups cleanly.
Related Answers
Was this answer helpful?
Your feedback helps us improve our answers.
Still need help?
Talk to our Shopware experts
We've handled GDPR/CCPA compliance for dozens of EU & US Shopware stores.