If your DATEV export aborts or reports errors, you will find the most common error messages here with their cause and solution. After you have fixed the cause, create the export again.
Where can I see the errors of an export?
If you are told that the export is faulty, you can see all errors under Settings → Shop → Pickware Import/Export Modul (Pickware Import/Export module) in the detail view of the respective export.
To make sure the orders are included in the next export, it is usually enough to check the individual line items and add additional accounts in the configuration for the respective business transaction.
With our DATEV module, it will also be possible in the future to create several exports for the same business transactions within a time range, so that the documents will be included in the next export after you have adjusted the configuration.
Common error messages and their solution
Revenue account for the tax rate X % could not be determined
This message appears when no revenue account is found in the DATEV configuration for a combination of shipping country and tax rate. Under Settings → Extensions → DATEV (Einstellungen → Erweiterungen → DATEV), every combination of shipping country and tax rate needs an account: either a country-specific revenue account or the default revenue account for this tax rate.
The shipping country is what matters, not the billing country. If the billing address is in France or Poland, for example, and the order is shipped to Germany, German tax applies, and the country-specific account for France or Poland does not take effect.
If a country changes its tax rate, for example Romania from 19 to 21 %, you need an additional account for the new rate. Multiple entries per country are normal. If Switzerland is set up as a third country, the export assumes a tax-free export delivery; in that case, also add a country-specific account for Switzerland.
Save the configuration and then create the export again. To find out which account ranges exist, see How do I configure my DATEV extension?
Document date index is still being built
This message, sometimes also shown as error 503, can appear after installing or updating Pickware. Wait a moment and start the export again.
If the message does not go away, a known error may be the cause, which has been fixed in current versions of Pickware ERP Pro. In this case, update your plugin.
In addition, the Shopware Message Queue must be running. You can check whether it is running with the Frosh Tools plugin, for example. If it is not running, your hosting provider must set up the CLI worker permanently.
Argument #10 ($documentInfoContent1) must be of type string, null given
This message means that the Sales Channel is missing a name in the English language. Enter the name for the English language in the Sales Channel, save, and create the export again.
Missing permissions for the DATEV export
If the export cannot be started because of missing permissions, add the privileges to the user's role under Settings → System → Users & Permissions (Einstellungen → System → Benutzer & Rechte). To do so, give the role the permission DATEV-Export (DATEV export). In older versions, you open the role and select Detaillierte Privilegien (Detailed privileges). The role then needs, among others, these privileges:
pickware_datev_configpickware_datev_payment_capturepickware_datev_individual_debtor_account_informationpickware_datev_accounting_document_guidpickware_datev_import_export_accounting_document_guid_mappingpickware_documentpickware_erp_import_exportpickware_erp_import_export_profilesales_channel
WMS and POS roles are mainly intended for the apps.
Duplicate entry … individual_debtor (duplicate customer number)
If you use individual debtor accounts and the export aborts or an SQL error with Duplicate entry … individual_debtor appears, two customers share the same customer number. For one of the two customers, enter a separate debtor account under Custom fields → DATEV (Zusatzfelder → DATEV) and create the export again.
Tip: Keep Pickware ERP or ERP Pro up to date.
