DATEV Export
In-App Purchases
Subscriptions
Description
Highlights
- Hours of manual work each month turn into one click - and with the schedule the handover happens by itself
- What was invoiced is what gets booked: the basis is the Shopware document, not the order
- Every tax case, not just the ordinary one: cash basis, OSS, small-business rule, reverse charge, foreign currency
- Audit-proof: a freeze with an unbroken hash chain, and every figure traces back to the order
- However large the shop: the run works step by step and splits booking batches and document packages by itself
Features
- Several clients with their own accounts, tax keys, document types, cost centre rules and sales channels
- Debtors collective, with diverse addresses or individual; one booking per document or condensed; payments booked along on request
- Document image ZIP with a DATEV XML for the document management, split by count and size
- Reporting with a CSV: revenue per account and tax rate, payments per cash account, invoices, credit notes, cancellations
- Export in the administration, as a scheduled task with a mail to your tax firm, or as a console command
- Setup wizard and readiness check: they tell you what is still missing before the first export
- Preview without a file and a test export without a freeze, repeatable as often as you like
- After every run: a report sorted by severity, a protocol with one line per document, a reconciliation of the sums
- OSS per EU destination country, separate for goods and electronic services, with distance-selling threshold monitoring
- Hand the batch straight to the DATEV booking data service - no download, no mail
About the Extension
Your monthly handover to the tax firm in one click: orders, invoices, credit notes and cancellations become a finished DATEV booking batch, with debtor master data, document images and a protocol that explains every single booking.
You pick the period, see in the preview what will be booked, and export. Out comes the file your tax firm can import directly, together with a ZIP holding the matching document images. If you like, a scheduled task does that every month by itself and mails the file to the firm - or hands the batch straight to the DATEV booking data service. The document packages wait in the history for download.
The problem you know
The same job every month: the figures have to leave the shop and enter the bookkeeping. The usual ways there cost time and produce errors.
- The CSV export from Shopware knows no tax keys, no debtor accounts and no document field. Whatever is missing gets rebuilt in a spreadsheet.
- The tax firm types from the PDF invoices. That is slow and billed by the hour.
- An export that only covers the ordinary case. As soon as OSS, cash-basis taxation, the small-business rule or credit notes come into play, the manual work is back.
- Afterwards nobody knows why a figure is in the file. Every question from the firm turns into a search through the orders.
How DATEV Export solves it
- What was actually invoiced is what gets booked. The basis is the document in Shopware, not the order: the invoice, the credit note, the correction. An order without an invoice does not appear in the batch, and a cancelled invoice is booked as a cancellation. That is the view your tax firm takes anyway.
- Every tax case is provided for. Accrual and cash-basis taxation, OSS per EU destination country, the small-business rule under section 19, reverse charge, intra-community supply, third country and foreign currency. Not as a workaround, but as an ordinary setting.
- The setup guides you. A wizard asks for everything DATEV needs when you create your first client. The DATEV standard accounts are offered as suggestions, and a readiness check tells you what is still missing before the first export.
- The documents come along. Every run carries a ZIP with the document images, linked through the document field so your tax firm can attach them on import.
- Every booking is justified. The protocol records per document which tax case applied, which date and account were used, and why a document was not booked if it was skipped.
- The export runs by itself. As a scheduled task at the cadence you choose, with a mail to the tax firm. An empty month can be reported too, so nobody waits for a file that does not exist.
The benefit at a glance
- Hours of manual work each month turn into one click.
- Your tax firm receives bookings and documents from the same run and types nothing.
- Every figure in the file can be traced back to the order.
- You see your revenue figures in the shop before the bookkeeping does.
- The size of the shop does not matter: the run works step by step and splits booking batches and document packages by itself.
Typical use cases
The monthly run: at the start of the month the scheduled task exports the previous month and mails the file to your tax firm. You see in the history that it worked, and the document packages are waiting there too.
Switching over: before you switch, you run a test export. It produces a real, complete file but freezes nothing and can be repeated as often as you like. Your tax firm imports it for a trial and reconciles it. A handout in the client detail explains every convention of the file to them.
Several companies in one shop: you create one client per company, with its own accounts, its own consultant number and its own sales channels. Each client exports only what belongs to it.
Selling into the EU: you store one revenue account per destination country. The rates come from your Shopware tax rules, and the threshold monitoring warns you before the distance-selling limit is reached.
Catching up on a year: a period covering twelve months with hundreds of thousands of bookings runs through in the administration, without a time limit and without a console.
What you set per client
Everything below belongs to the client, not to the shop. Every setting carries a help text that says what it does.
- Tax firm: consultant number, client number, the firm's mail address and a copy, your own address as the operator.
- Bookkeeping: chart of accounts SKR03 or SKR04, account length from four to eight digits, start of the fiscal year, interface version, country of establishment, booking timezone.
- Taxation: accrual or cash basis, the small-business rule under section 19, the freeze flag.
- How it books: one booking per document or a condensed collective booking, cancellations as a general reversal or as a counter booking, the behaviour for documents already exported, and whether warnings alone block the export.
- Document types: which Shopware document types count as an invoice, as a credit note and as a cancellation.
- Debtors: a collective account, a collective account per payment method, a collective account with diverse addresses, or individual accounts; plus the rule for the number and whether contact data travels along.
- OSS: on or off, the path (a revenue account per EU destination country, or a collective account with a tax key), and for both paths separate accounts and keys for goods and for electronic services.
- Fields in the file: the performance date from the order or the shipping date, the Shopware order number as the order reference, the posting text separately for documents and payments, tax keys shown or hidden.
- Payments: whether the money side from the Shopware payment state is booked along.
- Schedule: on or off, daily, weekly or monthly, and the hour in the client's own timezone.
- Sales channels: which channels this client exports.
Rules you write yourself
- The debtor account rule. An expression that turns the customer into an account number, from the customer number or a custom field for example. With a preview over the first customers before you save.
- Cost centre rules. As many as you like, each with its own priority. They match by sales channel, payment method, delivery country and tax rate, and set KOST1 and KOST2 individually.
Before you export
- Setup wizard. Guides you through every mandatory field of your first client.
- Readiness check. Tells you what is still missing before the first export and links straight to it.
- Preview. Computes the period without writing anything: the number of documents, bookings and the volume.
- Test export. A real, complete file that freezes nothing and can be repeated as often as you like. The way to reconcile with your tax firm.
- Handout for the tax accountant. Explains every convention of the file to the firm.
After the run
- Report. Every finding sorted by severity, each one acknowledgeable.
- Protocol. One line per document: tax case, date, account, booked or skipped and why.
- Reconciliation. The run checks itself for completeness and balances the sums.
- Reporting. Revenue per account and tax rate, payments per cash account, invoices, credit notes and cancellations, VAT and net revenue, with a CSV.
- History. Every run with its state, file and document package, downloadable again at any time.
Automatic
- Scheduled task. Exports the period that is due and mails the file to your tax firm; the document packages wait in the history. An empty month can be reported too, and so can a failed run.
- Console command. The same export for your own automation.
- Threshold monitoring. Totals the EU-wide distance-selling revenue daily and warns on the client, on the dashboard and in the report before the threshold is reached.
The file and the documents
- EXTF booking batch in format 13, the way DATEV expects it for the import.
- Debtor master data and diverse addresses as files of their own, matching the debtor mode you chose.
- If a batch grows too large for one file, several are written, along the limits DATEV sets.
- Document images as a ZIP with a DATEV XML for the document management, split by count and size.
- Large periods run step by step in small portions and are assembled at the end; an interrupted run continues where it stood.
GoBD: frozen and unbroken
A run that produces a file freezes its documents and joins an unbroken hash chain. On top of that comes a duplicate check across runs. A second export of the same period books nothing twice unless you say so explicitly.
Direct handover to DATEV
The booking batch goes straight to the DATEV booking data service if you want it to - no download, no mail. That gives you three outlets and you pick the one that suits your tax firm: download the file yourself, have it mailed to the firm automatically, or hand it to DATEV directly.
Who this pays off for
For shops whose bookkeeping is done by a DATEV tax firm and where the monthly handover no longer fits into a spare hour: from a few hundred orders a month upwards, with EU sales, several sales channels or several companies in one shop. You set it up once together with your tax accountant, and from then on your shop's bookkeeping is finished every month at the same hour, complete and traceable.
Your monthly handover to the tax firm in one click: orders, invoices, credit notes and cancellations become a finished DATEV booking batch, with debtor master data, document images and a protocol that explains every single booking.
You pick the period, see in the preview what will be booked, and export. Out comes the file your tax firm can import directly, together with a ZIP holding the matching document images. If you like, a scheduled task does that every month by itself and mails the file to the firm - or hands the batch straight to the DATEV booking data service. The document packages wait in the history for download.
The problem you know
The same job every month: the figures have to leave the shop and enter the bookkeeping. The usual ways there cost time and produce errors.
- The CSV export from Shopware knows no tax keys, no debtor accounts and no document field. Whatever is missing gets rebuilt in a spreadsheet.
- The tax firm types from the PDF invoices. That is slow and billed by the hour.
- An export that only covers the ordinary case. As soon as OSS, cash-basis taxation, the small-business rule or credit notes come into play, the manual work is back.
- Afterwards nobody knows why a figure is in the file. Every question from the firm turns into a search through the orders.
How DATEV Export solves it
- What was actually invoiced is what gets booked. The basis is the document in Shopware, not the order: the invoice, the credit note, the correction. An order without an invoice does not appear in the batch, and a cancelled invoice is booked as a cancellation. That is the view your tax firm takes anyway.
- Every tax case is provided for. Accrual and cash-basis taxation, OSS per EU destination country, the small-business rule under section 19, reverse charge, intra-community supply, third country and foreign currency. Not as a workaround, but as an ordinary setting.
- The setup guides you. A wizard asks for everything DATEV needs when you create your first client. The DATEV standard accounts are offered as suggestions, and a readiness check tells you what is still missing before the first export.
- The documents come along. Every run carries a ZIP with the document images, linked through the document field so your tax firm can attach them on import.
- Every booking is justified. The protocol records per document which tax case applied, which date and account were used, and why a document was not booked if it was skipped.
- The export runs by itself. As a scheduled task at the cadence you choose, with a mail to the tax firm. An empty month can be reported too, so nobody waits for a file that does not exist.
The benefit at a glance
- Hours of manual work each month turn into one click.
- Your tax firm receives bookings and documents from the same run and types nothing.
- Every figure in the file can be traced back to the order.
- You see your revenue figures in the shop before the bookkeeping does.
- The size of the shop does not matter: the run works step by step and splits booking batches and document packages by itself.
Typical use cases
The monthly run: at the start of the month the scheduled task exports the previous month and mails the file to your tax firm. You see in the history that it worked, and the document packages are waiting there too.
Switching over: before you switch, you run a test export. It produces a real, complete file but freezes nothing and can be repeated as often as you like. Your tax firm imports it for a trial and reconciles it. A handout in the client detail explains every convention of the file to them.
Several companies in one shop: you create one client per company, with its own accounts, its own consultant number and its own sales channels. Each client exports only what belongs to it.
Selling into the EU: you store one revenue account per destination country. The rates come from your Shopware tax rules, and the threshold monitoring warns you before the distance-selling limit is reached.
Catching up on a year: a period covering twelve months with hundreds of thousands of bookings runs through in the administration, without a time limit and without a console.
What you set per client
Everything below belongs to the client, not to the shop. Every setting carries a help text that says what it does.
- Tax firm: consultant number, client number, the firm's mail address and a copy, your own address as the operator.
- Bookkeeping: chart of accounts SKR03 or SKR04, account length from four to eight digits, start of the fiscal year, interface version, country of establishment, booking timezone.
- Taxation: accrual or cash basis, the small-business rule under section 19, the freeze flag.
- How it books: one booking per document or a condensed collective booking, cancellations as a general reversal or as a counter booking, the behaviour for documents already exported, and whether warnings alone block the export.
- Document types: which Shopware document types count as an invoice, as a credit note and as a cancellation.
- Debtors: a collective account, a collective account per payment method, a collective account with diverse addresses, or individual accounts; plus the rule for the number and whether contact data travels along.
- OSS: on or off, the path (a revenue account per EU destination country, or a collective account with a tax key), and for both paths separate accounts and keys for goods and for electronic services.
- Fields in the file: the performance date from the order or the shipping date, the Shopware order number as the order reference, the posting text separately for documents and payments, tax keys shown or hidden.
- Payments: whether the money side from the Shopware payment state is booked along.
- Schedule: on or off, daily, weekly or monthly, and the hour in the client's own timezone.
- Sales channels: which channels this client exports.
Rules you write yourself
- The debtor account rule. An expression that turns the customer into an account number, from the customer number or a custom field for example. With a preview over the first customers before you save.
- Cost centre rules. As many as you like, each with its own priority. They match by sales channel, payment method, delivery country and tax rate, and set KOST1 and KOST2 individually.
Before you export
- Setup wizard. Guides you through every mandatory field of your first client.
- Readiness check. Tells you what is still missing before the first export and links straight to it.
- Preview. Computes the period without writing anything: the number of documents, bookings and the volume.
- Test export. A real, complete file that freezes nothing and can be repeated as often as you like. The way to reconcile with your tax firm.
- Handout for the tax accountant. Explains every convention of the file to the firm.
After the run
- Report. Every finding sorted by severity, each one acknowledgeable.
- Protocol. One line per document: tax case, date, account, booked or skipped and why.
- Reconciliation. The run checks itself for completeness and balances the sums.
- Reporting. Revenue per account and tax rate, payments per cash account, invoices, credit notes and cancellations, VAT and net revenue, with a CSV.
- History. Every run with its state, file and document package, downloadable again at any time.
Automatic
- Scheduled task. Exports the period that is due and mails the file to your tax firm; the document packages wait in the history. An empty month can be reported too, and so can a failed run.
- Console command. The same export for your own automation.
- Threshold monitoring. Totals the EU-wide distance-selling revenue daily and warns on the client, on the dashboard and in the report before the threshold is reached.
The file and the documents
- EXTF booking batch in format 13, the way DATEV expects it for the import.
- Debtor master data and diverse addresses as files of their own, matching the debtor mode you chose.
- If a batch grows too large for one file, several are written, along the limits DATEV sets.
- Document images as a ZIP with a DATEV XML for the document management, split by count and size.
- Large periods run step by step in small portions and are assembled at the end; an interrupted run continues where it stood.
GoBD: frozen and unbroken
A run that produces a file freezes its documents and joins an unbroken hash chain. On top of that comes a duplicate check across runs. A second export of the same period books nothing twice unless you say so explicitly.
Direct handover to DATEV
The booking batch goes straight to the DATEV booking data service if you want it to - no download, no mail. That gives you three outlets and you pick the one that suits your tax firm: download the file yourself, have it mailed to the firm automatically, or hand it to DATEV directly.
Who this pays off for
For shops whose bookkeeping is done by a DATEV tax firm and where the monthly handover no longer fits into a spare hour: from a few hundred orders a month upwards, with EU sales, several sales channels or several companies in one shop. You set it up once together with your tax accountant, and from then on your shop's bookkeeping is finished every month at the same hour, complete and traceable.
Details
- Available: English, German
- Latest update: 21 September 2026
- Publication date: 21 September 2026
- Version: 2.0.5
- Category: Middleware & Connectors
Resources
Reviews (0)
About the Extension Partner
digitvision
Partner Status
-
Shopware
Premium Extension Partner
Details
-
Ø-Rating:
4.9
Average rating of 4.9 out of 5 stars
- Partner since: 2018
- Extensions: 107
Support
- Based in: Germany
- Speaks: German, English
- Response time: Very quickly
Setting up takes a few minutes. Have the consultant and client number of your tax firm at hand, together with the accounts your tax accountant specifies.
- Install and activate the extension and open the DATEV Export menu in the administration.
- Create your first client. The wizard guides you through everything DATEV needs: chart of accounts, consultant and client number, fiscal year, account length and taxation type.
- Assign the accounts on the Accounts tab: revenue accounts per tax rate, cash accounts per payment method and the debtor account. The DATEV standard accounts are offered as suggestions.
- Maintain OSS on the Tax & OSS tab if you sell to private customers in the EU: one revenue account per destination country.
- Assign the sales channels. A client exports exactly the channels that belong to it.
- Check the readiness. The card on the dashboard lists what is still missing and links straight to it.
- Run a test export. Pick a period, compute the preview, then choose test export: a real, complete file that freezes nothing and can be repeated as often as you like.
- Hand the file and the document ZIP to your tax firm and have both imported and checked. The handout in the client detail explains every convention of the file to them.
- Set up the scheduled export on the Export tab: cadence, hour and the mail address of your tax firm. From then on the monthly handover happens by itself.
A hint on almost every setting tells you what it does. Orders created before the installation are fully included, and a catch-up run over past months is possible at any time.
2.0.5 6.7.0.0 - 6.7.14.1
- fixed the plan limit texts writing tenant(s) instead of one active tenant or several active tenants
- fixed the placeholder of an empty revenue account for foreign sales being cut off
- fixed the date of the last runs on the dashboard breaking onto a second line
- fixed the header of a new tenant staying empty until a name is typed
- fixed a new tenant asking the server for the schedule of a tenant that is not saved yet
- fixed the extra space below the last card on the reconciliation, protocol and mail tabs of a run
2.0.4 6.7.0.0 - 6.7.14.1
- fixed the export help saying a preview is not recorded
- fixed the DATEV tab of an order calling test exports and given-up runs a preview
- fixed the run page calling a given-up run without a file a preview
2.0.3 6.7.0.0 - 6.7.14.1
- fixed the decision window describing the file wrongly for stored previews and runs without a valid file
- fixed the export page promising an immediate download
- fixed the spacing around the preview on the export page
- fixed the missing space above the summary in the decision window
- refactored deprecated admin buttons and icons to their Meteor components
2.0.2 6.7.0.0 - 6.7.14.1
- fixed the cost centre rule page staying empty
- fixed selects that must not be empty offering to clear their value
2.0.1 6.7.0.0 - 6.7.14.1
- added a switch to turn off the mail after the scheduled export, the mail settings are now on the export tab of the tenant
- added loading placeholders to the export, statistics and run pages
- added field errors in the setup assistant for the fields a step still needs
- changed the payment export settings into a card of their own with the notes for the tax advisor
- fixed in-app purchases
- fixed the export and statistics pages showing no tenants when every tenant is inactive
- fixed the console export writing a second copy of each file into var/dvsn-datev, the option --out is removed
- refactored the document package to be written as a stream without a temporary file
- refactored the export job into smaller services