Frequently Asked Support Topics (FAQ)
When requesting the access token, the error message "The client info could not be requested." appears
In most cases, the cause of this message is on the DATEV side. It is displayed when something went wrong during authentication. The first step in diagnosing the issue is to check the SIEVERS DATEV Posting Data Service Log, which you can access via the SIEVERS DATEV Posting Data Service. For each token request, log entries with the Type equal to Acquire Client Info are created there. Read what is stated in the Messagetext of these entries. If you select one of the entries and display the detail information via Show Log Entries, these details contain the complete request from the Posting Data Service to DATEV and the complete response from DATEV to the Posting Data Service. Often, at the very bottom of the DATEV response, there is a hint about why the access token was rejected, such as a "Forbidden" or similar. In most cases with this error message, it is necessary to check with the tax office whether the Posting Data Service has actually been activated on the DATEV side. If you are unsure, you can send the content of the detail information to SIEVERS-GROUP Support at support@sievers-group.com.
When requesting the access token, no sign-in window opens or an error message about it appears
After clicking the Open DATEV sign-in button, the DATEV sign-in page opens in a separate browser window. If this window does not open, it is usually because pop-ups for Business Central are blocked in the browser. In this case, allow pop-ups for the Business Central page and try again. If the window is instead closed before the sign-in is completed, a corresponding error message also appears. In both cases, you can restart the sign-in process directly in the dialog without having to reload the page.
After exporting, I have to sign in to DATEV again even though I signed in shortly before
Before every data transfer, the system verifies that the access token is still valid and actually present. If the short-lived access token has expired, it is automatically renewed using the longer-lived refresh token, without requiring you to sign in again. Signing in again is only necessary if this automatic renewal also fails, for example because the refresh token has expired as well.