DATEV export
  1. Home
  2. Comparison

Comparison Built-in tools or a plugin?

Shopware knows documents, tax rates and payment statuses - but it writes no file that DATEV reads in. What the standard brings and what the plugin makes of it, line by line.

Line by line

The Shopware standard and DATEV Export.

QuestionShopware standardDATEV Export
File for DATEVCSV export of orders, but no DATEV formatEXTF booking batch, format version 13
Tax key per bookingper account and tax case
Debtor accountscustomer number per customer, but no debtor accountcollective debtor, per payment method, diverse addresses or per customer
Document field and linkdocument number in document field 1 (field 11), reference to the image in field 20
Document imagesinvoice PDF on the order once it is createdZIP with document.xml for the document transfer
OSS per destination countrytax rates per country in the tax rulesrevenue account per country or collective account with a key
Cash-basis taxationpayment status on the orderbooking on the payment date from the status history
Credit note and cancellationas a document on the ordergeneral reversal or side switch, refund booked only once money was actually paid back
Lock after the exportunbroken hash chain, duplicate protection across runs
Checking before the handoverpreview, test export, check report, reconciliation
Tracingprotocol per document, "DATEV" tab on every order
Schedule and emailscheduled tasks, but no exportrhythm per tenant, email to the tax firm
Several companiessales channelsone tenant per company with its own numbers and accounts
To be fair

When you manage without a plugin.

Few invoices, booking from PDFs

If your tax firm books a handful of invoices a month from the PDFs and wants it that way, you need no file. Up to 25 invoices a month the export is free anyway - trying it costs nothing.

A tax firm without DATEV

The plugin writes the DATEV format. If your tax firm works with different bookkeeping software, it is not the right tool.

The plans and what they cost