Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.maesn.com/llms.txt

Use this file to discover all available pages before exploring further.

​
Fetch data from Datev in 5 steps

Required: End users must have the Datenservice Export Rechnungswesen enabled in their DATEV accounts Speak to your customer success manager at Maesn to learn how to enable this service.
1

Authorize end user

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

Retrieve companies

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. Note that you can use the interactive authentication flow to eliminate this step.
3

Get user info (optional)

Fetch the user info associated to your end users’s DATEV account using the GET /userInfo endpoint. Display the retrieved information in your application’s UI as required by DATEV (see ‘general requirements’ below).
4

Retrieve the data you need

Fetch the data you always dreamed of retrieving from the API instead of CSV exports:
  • Retrieve GL accounts using the GET /accounts endpoint
  • Retrieve fiscal years through the GET /fiscalYears endpoint
  • Retrieve booking data using the GET /journalEntries endpoint
  • Retrieve payment terms through the GET /paymentTerms endpoint
  • Retrieve sums and balances for your accounts using the GET /trialBalance endpoint
5

Check DATEV general requirements

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

Delete end user

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.

​
Insights on endpoint GET /accounts

This endpoint retrieves general ledger accounts as well as customer and supplier accounts from DATEV Rechnungswesen. The maesn API maps the account number and description to the unified model. Since some fields returned by DATEV are DATEV-specific, they are not mapped to the unified model. However, they are still available in the raw response when using rawData=true. The three DATEV specific fields are:
  • mainFunction: the function type
  • mainFunctionNumber: the function number
  • functionExtension: the additional detail or extension
These fields are part of DATEV’s account-function model for SKR03 and SKR04. In addition to the account number and caption, DATEV can assign an account function to an account. This account function provides additional classification information that helps describe how the account is categorized within DATEV’s bookkeeping logic. In the API response, this account function is represented by the fields mainFunction, mainFunctionNumber, and functionExtension. To help interpret these values, DATEV publishes yearly Kontenfunktions-Tabellen for SKR03 and SKR04. These tables list the available account functions for a given year and provide the reference needed to understand the values returned in the API. DATEV account-function tables use the format ZZ YY XXX, where:
  • ZZ = function type
  • YY = main function number
  • XXX = function extension
In the API response, mainFunction corresponds to the function type (ZZ), mainFunctionNumber to the main function number (YY), and functionExtension to the function extension (XXX). The following mainFunction values are relevant:
  • 0 = no type
  • 1 = automatic input tax invoice (AV)
  • 2 = automatic VAT invoice (AM)
  • 3 = general function (F)
  • 4 = collective function (S)
  • 6 = collective function, automatic input tax (SAV)
  • 7 = collective function, automatic VAT (SAM)
  • 8 = standard function deactivated
Last modified on April 14, 2026