Important Information
Some error messages are caused by settings in DATEV, while others are related to data or files in finway. Therefore, always check both the relevant request in finway and the DATEV configuration.
This article covers the following issues:
A request cannot be exported to DATEV Unternehmen online (DUO).
A specific DATEV error message appears in the import log.
An invoice or request is not transferred to DATEV as expected.
1. Common Error Messages and Solutions
Error message or issue | Likely cause | Recommended solution |
“Belegkreis im Rechnungseingangsbuch bzw. Belege Bearbeitungsform 'Erweitert' für Lieferanten-Rechnungen nicht gefunden” | The Eingangsrechnungen invoice folder is missing in DATEV or has been created under the wrong fiscal year. | Check the invoice folder in DATEV and create or rename it as required. |
“Belegkreis/Belegordner im Rechnungseingangsbuch für Lieferanten-Rechnungen nicht gefunden” | The folder name provided by finway does not match the folder name configured in DATEV. | Rename the folder in DATEV to Eingangsrechnungen. |
“Parserfehler … 'extension' can occur a maximum of '50' times” | More than 50 files are attached to a single request. | Reduce the number of attachments to a maximum of 50 and restart the export. |
“Fehler in der Dokumenteninformation (doppelter Dateiname)” | A file with the same name has already been exported. | Rename the file, upload it again, and repeat the export. |
“Die Skontoinformationen entsprechen nicht der Spezifikation” | The due date or service date is earlier than the invoice date. | Correct the date fields and export the request again. |
“Rechnung passt nicht zu Rechnungsschema” or an error referring to special characters or spaces | Invalid characters or additional spaces in fields such as invoice number, cost center, cost object, or supplier name. | Clean up the affected fields and remove unwanted characters or spaces. |
The file is rejected by DATEV | The invoice file is technically invalid or is not a valid PDF file. | Obtain a new copy of the original file, upload it again, and repeat the export. |
The export only works on the second attempt, or duplicate entries are created | A temporary issue with DATEV or the data transmission service. | First check whether the request has already been received by DATEV before attempting another export. |
“Element buCode entspricht nicht der Spezifikation (Belegsatz 1)” | The DATEV tax code transmitted for the relevant account is invalid and cannot be processed by DATEV. | Check the VAT rate used in finway. In the company settings, edit the VAT rate, remove the BU number, save the changes, and synchronize the settings. Then repeat the export. |
The import log is missing | Rechnungsdatenservice 1.0 (RDS 1.0) is not enabled, or the connected SmartLogin/SmartCard does not have sufficient permissions. | Ask your tax advisor to verify that RDS 1.0 is enabled and that the connected SmartLogin/SmartCard has the required permissions. |
2. Troubleshooting Instructions
2.1. Error: Invoice Folder or Document Category Not Found
If DATEV reports that the document category (Belegkreis) or invoice folder (Belegordner) could not be found, the required invoice folder is usually missing in DUO or has been configured under the wrong fiscal year.
How to resolve the issue:
Open DATEV Unternehmen online.
Click Konfiguration in the top-right corner.
Select Rechnungsordner.
Check whether a folder named Eingangsrechnungen exists for the relevant fiscal year.
If the folder is missing, create it or rename an existing folder accordingly.
Also verify that the correct fiscal year is selected.
Save your changes.
Restart the DUO export in finway.
Expected result: The export completes without displaying the same error message.
2.2. Error: Document Category Not Configured
If DATEV reports that the document category (Ordnungsbegriff) has not been configured, the extended processing settings for supplier invoices or the selected fiscal year may be incorrect.
How to resolve the issue:
Open the supplier invoice settings in DATEV.
Check whether the document processing mode (Belege-Bearbeitungsform) is set to Erweitert, if required by your DATEV configuration.
Verify the active fiscal year.
Ensure that the request can be exported to the fiscal year currently selected in DATEV.
Run the export again.
Expected result: DATEV accepts the transfer for the correct fiscal year.
2.3. Error: More Than 50 Files Attached to a Request
DATEV allows a maximum of 50 files per request. If more files are attached, the export will fail.
How to resolve the issue:
Open the affected request in finway.
Review the attachments and count the files.
Remove attachments until no more than 50 files remain.
If several receipts belong together, check whether they can be distributed across multiple requests.
Save your changes.
Restart the DUO export.
Expected result: The export is no longer blocked by the DATEV file limit.
Note: If a request contains a large number of individual receipts, it is often more practical to split them across multiple requests.
2.4. Error: Duplicate File Name
DATEV may reject files with identical names.
How to resolve the issue:
Download the affected invoice file from finway.
Rename the file locally, for example by adding the invoice date or an additional number.
Upload the renamed file to the request again.
If necessary, remove the previous file from the request.
Run the export again.
Expected result: DATEV processes the file without a file name conflict.
2.5. Error: Discount Information Does Not Match the Specification
This error occurs when the due date or service date is earlier than the invoice date.
How to resolve the issue:
Open the request in finway.
Check the invoice date.
Check the due date.
Check the service date, if one has been entered.
Ensure that neither the due date nor the service date is earlier than the invoice date.
Save your changes.
Run the export again.
Expected result: The DATEV discount information or date validation is passed successfully.
2.6. Error: Invoice Does Not Match the Invoice Schema
If DATEV reports that an invoice does not match the invoice schema, the issue is often caused by an invalid format in one of the fields.
How to resolve the issue:
Open the request in finway.
Pay particular attention to the following fields:
Invoice number
Description
Cost center
Cost object
Supplier name
Remove unnecessary special characters.
Remove any leading or trailing spaces.
Save the request.
Run the export again.
Expected result: DATEV accepts the field values during the export.
Important: Even a single trailing space at the end of a field value may be enough to cause the export to be rejected.
2.7. Error: DATEV Rejects the Invoice File
In some cases, the uploaded file is not a valid PDF, even if it appears to be a PDF file.
How to resolve the issue:
Open the affected file locally and check whether it can be displayed correctly.
If the file originated from a portal or email, download it again from the original source.
Replace the existing file in the finway request with the newly downloaded original file.
Save the request.
Run the export again.
Expected result: DATEV accepts the file as a valid document.
2.8. Error: Export Only Works on the Second Attempt or Creates Duplicates
In some cases, the issue is not caused by the request itself but by a temporary disruption at DATEV or within the data transmission service.
How to resolve the issue:
First, check whether the request has already been received by DATEV.
Verify whether the document has already been imported or whether a duplicate entry exists.
If the request has not been received, wait briefly and retry the export.
If the request has already been imported, do not run the export again.
Expected result: You avoid duplicate exports and can determine whether the issue was caused by a temporary disruption.
Important: Before retrying an export after a temporary technical error, always check DATEV first to ensure that the request has not already been transferred successfully.
You can also check the DATEV service status and maintenance announcements here:
3. Expected Results
After applying the relevant troubleshooting steps, you should be able to confirm the following:
The DUO export can be restarted without the same error message appearing.
The request or document is visible in DATEV Unternehmen online.
No new errors related to the same issue appear in the import log.
4. Best Practices to Prevent Export Errors
To reduce the likelihood of export issues, follow these recommendations:
Use clear and unique file names.
Do not attach more than 50 files to a single request.
Carefully verify all date fields before exporting.
Remove unnecessary special characters and spaces from relevant fields.
Regularly check that the Eingangsrechnungen folder exists in DATEV for the correct fiscal year.
5. When to Contact Support
Contact Support if any of the following applies:
The error persists despite following the troubleshooting steps described above.
The export status is unclear, and you cannot determine whether the request has already reached DATEV.
Technical errors occur repeatedly without an identifiable cause.
The request meets all requirements but continues to be rejected by DATEV.
6. Frequently Asked Questions (FAQ)
Why was only the invoice transferred to DATEV, rather than the complete request?
This typically happens when DATEV cannot process certain export information, for example because a required invoice folder is missing.
Can I simply export the same request again?
Yes, but only after verifying that the request has not already been received by DATEV. Otherwise, duplicate entries may be created.
Why is my file rejected even though it looks like a PDF?
Some files have a PDF extension but are technically corrupted or incomplete. In such cases, downloading the file again from the original source is usually the best solution.
Last updated: 21 October 2026