When using the DATEV Rechnungswesen native integration, you may occasionally encounter error messages during the export process. These messages are designed to help you quickly identify and resolve issues with your accounting setup and prepared payables.
Common reasons for export failures include:
Connection errors — the Chift Local Agent is not running on the DATEV server, or the Windows credentials have changed.
Accounting settings errors — a supplier account, tax code or cost dimension is missing or incorrectly mapped in Spendesk.
Failed export errors — an individual payable has a data issue that prevents it from being pushed to DATEV Rechnungswesen.
How to resolve export errors
For a comprehensive guide on setting up and troubleshooting your accounting integration, please refer to our detailed article on Main error messages and solutions with native integrations.
Most export issues can be resolved by reviewing and updating your accounting settings. Each error message provides specific guidance on what needs to be corrected.
Verifying the Local Agent connection
If you encounter a connection error, verify that the Chift Local Agent is running correctly on your DATEV server:
On the DATEV server, open the Windows Start menu and search for Services.
Open Services and locate LocalAPIService.
The status should be Running. If it is stopped, right-click and select Start.
Note that the the local agent package contains a unique connection number. For each connection initiated from Spendesk, there is one and only one version of the local agent that will work. This connection information is stored in settings.json file.
If you destroy the current connection in Spendesk, you need to uninstall the local agent from the DATEV server. A newly created connection will not be able connect to the old local agent. A new local agent will need to be installed for the newly created connection. Alternatively, you can replace the settings.json file with a new one and restart the LocalAPIService service.
If restarting the service does not resolve the issue, or if the Windows credentials linked to the DATEV account have changed, you may need to re-run the connection flow from Spendesk to generate a new installer. Follow the steps in Connect Spendesk to DATEV Rechnungswesen and Install the Chift Local Agent on your DATEV server.
What to do if you are still blocked
If you encounter persistent errors or need additional assistance with the DATEV Rechnungswesen integration, contact our support team.