DATEVconnect Gateway in DATEVasp: data access for software vendors and tax firms

Many TaxTech vendors and software companies need repeatable technical access to DATEV data, for example from DMS, accounting, or master data. In DATEVasp, this access does not run through a local installation in the customer's environment. It runs through the DATEVasp process for integrating a third-party solution.

The Klardaten DATEVconnect Gateway provides a controlled access layer for this. The tax firm starts the integration in the DATEVasp portal. After that, users, DATEV users, permissions, and profiles are configured.

Who this article is for

This article is primarily for:

• TaxTech vendors that want to offer a DATEV integration for DATEVasp customers
• software vendors connecting DMS, accounting, or master data workflows
• CTOs and product teams that do not want to operate DATEVconnect infrastructure separately for every customer environment
• tax firms in DATEVasp that want to connect a third-party solution in a controlled way

For software vendors, the main point is repeatable access to DATEVasp environments without running separate connector infrastructure for each customer. For tax firms, the key questions are who starts the process, which users and permissions must be configured, and how access remains controlled.

What the DATEVconnect Gateway does in DATEVasp

The Klardaten DATEVconnect Gateway provides cloud access to DATEVconnect Desktop APIs so applications can access data from the DATEV desktop environment in a controlled way. It is relevant when this data cannot reasonably be reached via other API paths.

Typical data areas include:

• DATEV DMS
• DATEV Rechnungswesen (accounting)
• master data
• other DATEVconnect-supported modules and data areas

The important limitation: DATEVconnect is not a universal API for all DATEV data. Whether a specific use case can be covered depends on the DATEV product, the module, DATEVconnect coverage, the customer environment, and permissions.

The Gateway is access infrastructure. It is not a second data silo: DATEV data is not stored at Klardaten, but made available in a controlled way for a specific application or workflow.

DATEVasp and PARTNERasp differ

DATEVasp and PARTNERasp are both hosted DATEV environments, but their operational integration process differs. This article describes DATEVasp; for PARTNERasp, the process must be coordinated with the respective PARTNERasp operator.

Setup flow: configuring the DATEVconnect Gateway in DATEVasp

The following flow describes the typical DATEVasp setup for the Klardaten DATEVconnect Gateway.

Step 1: the tax firm orders “Drittanbieterlösung einbinden” (“connect third-party solution”)

The tax firm orders the “Drittanbieterlösung einbinden” option (“connect third-party solution”) in the DATEVasp portal.

The order references the Klardaten DATEVconnect Gateway and the product page:

DATEVconnect Gateway product page

This step is performed by the tax firm. The software vendor does not install anything directly in the DATEVasp environment, but needs to provide clear onboarding instructions for the firm.

Step 2: DATEVasp installs the Klardaten DATEVconnect Gateway

After the order, DATEVasp installs the Klardaten DATEVconnect Gateway in the DATEVasp environment.

Step 3: DATEVasp confirms successful installation

After successful installation, the tax firm receives confirmation from DATEVasp.

Step 4: the tax firm creates a new Windows user in the DATEVasp portal

The tax firm creates a new Windows user in the DATEVasp portal.

This Windows user later helps determine the context in which DATEV data is accessed.

Step 5: the tax firm configures DATEV users and permissions

The tax firm logs in to the DATEVasp portal with its own credentials and creates a new DATEV user. The previously created DATEVasp user is assigned to this DATEV user.

Permissions must match the specific use case. A DMS integration needs different permissions than accounting reporting or master data synchronization.

The simplest technical option can be the DATEV group “Alle Freigaben”.

The tax firm then logs in to Windows once with the new user and opens Arbeitsplatz, the DATEV workplace app, to replace the initial password and initialize the permissions.

Step 6: the tax firm enters technical credentials securely

The onboarding link provided by the software vendor or by Klardaten opens a page on the instance where the tax firm enters the Windows/DATEV credentials intended for the profile.

The credentials are not stored in systems operated by the software vendor or by Klardaten.

Profiles: using multiple Windows and DATEV users at the same time

Profiles are an important part of production DATEVasp integrations.

The DATEVconnect Gateway can run with different Windows and DATEV users at the same time. These user contexts are represented through profiles.

That means:

• A profile can correspond to a specific Windows/DATEV user.
• Multiple profiles can run in parallel.
• An application can work with different DATEV permissions depending on the profile.
• Visible data depends on the permissions of the respective DATEV user.
• Permissions come from the DATEV and Windows context, not from the external application.

This is especially important for DATEV DMS. Not every user is allowed to see every document. When an application retrieves DMS data, access must match the relevant user context. Profiles help represent these user contexts separately.

Typical data areas and use cases

DATEV DMS: Business applications can retrieve document metadata or document files and use them in external workflows, search functions, or assistant systems. Actual visibility depends on the profile and DATEV permissions.

DATEV Rechnungswesen: Reporting tools can repeatedly retrieve accounting data from DATEV Rechnungswesen if the required data area is covered by DATEVconnect. For deeper reporting requirements, Power BI, financial controlling, or specialized reporting, the Enterprise API may be the better option.

Master data: CRM, onboarding, or administration processes can synchronize client master data, addresses, or contacts with DATEV. Number ranges, existing client structures, and duplicate handling must be clarified on the business side.

AI and workflow systems: AI and workflow systems also need clearly scoped data paths, not blanket access. The Gateway can provide an access layer for applications, workflows, or systems such as Klarvos.

What the Gateway does not do

The DATEVconnect Gateway has clear limits.

The DATEVconnect Gateway is not:

• a universal API for all DATEV data
• a way to bypass DATEV permissions
• blanket access to DMS, accounting, and master data
• a replacement for all DATEV Online APIs
• automatically sufficient for every reporting or BI scenario

What matters is:

Which data does the use case need, which DATEV area contains it, is that area reachable through DATEVconnect, and which user context is allowed to access it?

Gateway or Enterprise API?

The DATEVconnect Gateway is the standard product for DATEVconnect-based integrations.

It is a good fit when:

• the required data area is reachable through DATEVconnect
• the application needs to connect DMS, accounting, or master data workflows
• the vendor does not want to operate connector infrastructure for every customer environment
• DATEVasp customers should be onboarded through a repeatable process

The Enterprise API becomes relevant when DATEVconnect is not enough.

Typical Enterprise cases include:

• deeper DATEV desktop data
• Power BI or financial controlling scenarios
• specialized reporting requirements
• use cases where DATEVconnect does not provide enough data coverage

Special case: Enterprise variant in DATEVasp

For the Enterprise variant, an additional database user may be required.

For this, the tax firm first contacts the DATEV EO Customizing team and asks them to create a database user. This request then needs to be forwarded to the DATEVasp team.

This is not part of the standard DATEVconnect Gateway flow and should be considered separately.

Questions before starting

Before a DATEVasp integration, the software vendor and the tax firm should clarify:

1. Which data areas are needed: DMS, accounting, master data, or something else?
2. Are these data areas reachable through DATEVconnect?
3. Which DATEV users should be used for access?
4. Does the application need one profile or multiple profiles?
5. Which permissions do these profiles need?
6. Does the application only need read access, or write access too?
7. Is DATEVasp or PARTNERasp in use?
8. Is the Gateway enough, or does the use case need an Enterprise integration?
9. How will access be monitored and supported during operation?

These questions matter more than an abstract API discussion. In production DATEV environments, the user context determines whether an integration works reliably.

Conclusion

DATEVconnect in DATEVasp is not a local installation in the customer's environment and not a simple API key. The tax firm starts the integration in the DATEVasp portal, DATEVasp installs the Klardaten DATEVconnect Gateway, and access is controlled through Windows/DATEV users, permissions, and profiles.

For TaxTech vendors and software companies, the value is clear: they do not need to operate custom connector infrastructure for every DATEVasp customer environment. Instead, they can use a controlled access layer for the right DATEV data.

FAQ

Does the Klardaten DATEVconnect Gateway work in DATEVasp?

Yes. In DATEVasp, integration happens through the “Drittanbieterlösung einbinden” (“connect third-party solution”) process in the DATEVasp portal. The tax firm starts this process itself.

Can the Gateway run with multiple DATEV users?

Yes. Profiles can run different Windows/DATEV user contexts in parallel. Visible data depends on the respective DATEV permissions.

What are profiles in the DATEVconnect Gateway?

Profiles represent different user contexts. A profile can work with a specific Windows/DATEV user and reflects that user’s permissions.

When do you need the Enterprise API instead of the Gateway?

When DATEVconnect does not sufficiently cover the required data area. Typical cases include deeper reporting, Power BI, financial controlling, or special requirements for DATEV desktop data.

Plan a DATEVconnect integration in DATEVasp

For DATEVconnect-based integrations in DATEVasp, we help assess the right access path: data area, DATEVconnect coverage, profiles, user permissions, and DATEVasp onboarding.

View DATEVconnect Gateway

For specific DMS, accounting, or master data workflows, we clarify in advance which profiles and permissions are required.

Request a technical review