Upload bookings to DATEV Rechnungswesen

Your end user must first authorize your application to access their data in DATEV Rechnungswesen through maesn Connect.

Fetch the user info associated to your end users’s DATEV account using the GET /user-info endpoint. Display the retrieved information in your application’s UI as required by DATEV (see last step).

Fetch all the companies associated to your end users’s DATEV account using the GET /companies endpoint. The user will need to select a company to proceed, as the company ID will be needed for subsequent steps.

At this point, determine whether your use case requires attaching files (e.g. PDFs) to the booking data:

• If yes, proceed with the steps below to fetch document-related data and upload files.
• If not, skip directly to the “Create bookings” step below.

Fetch the relevant document types from your end users’s DATEV account using the GET /document-types endpoint. The document types will be used to categorize the files you will upload. These may, for example, be presented to the end user as a drop-down menu at the point of file upload.

IMPORTANT: the endpoint must be called only once per user, as the document types are not expected to change frequently.

If necessary, confirm the allowed file extensions for uploads to DATEV by calling the GET /document-extensions.

IMPORTANT: as the previous one, this endpoint must be called only once per user.

Upload the document to DATEV using the POST /files endpoint and save the retrieved file id . Make sure to include all the required fields in the request body. Ensure your application checks the file size before uploading to avoid performance issues (see last step).

Create the bookings batch and upload it to Rechnungswesen using the POST /bookings endpoint. Make sure to include all the required fields in the request body. You can include the file id of the uploaded document in the request.

Check the status of the bookings batch using the GET /asyncTask endpoint. This will allow you to verify if the batch was successfully processed by DATEV.

Review the DATEV interface requirements to ensure that your application complies with DATEV’s specifications.

If your user deletes their account, you may delete the end user from our API and revoke their token using the the POST /delete-end-users. This step ensures both actions are handled on the backend.