DATEVconnect, DATEV API, or Export: Which Path for Which Integration

DATEVconnect, DATEV API, or file export: an overview of which integration path fits which use case.

Hand-drawn sketch: a signpost with three signs pointing in different directions, one sign is colored teal

DATEVconnect, the DATEV API, and the classic file export are three different ways to connect an upstream system to DATEV, and each fits different situations. DATEVconnect is the interface for the bidirectional connection of DATEV accounting and payroll programs, and it is split into a local "Desktop" part, which is only reachable within the local network, and an internet-based "Online" part, which runs through a data center and requires a subscription. The DATEV API world alongside it ranges from simple CSV/EXTF and XML exports with no certification requirement to modern REST interfaces, which require a DATEV partner certification and more technical know-how. The central point of contact for all three paths is the DATEV Developer Portal. As of: August 2026.

What Exactly Is DATEVconnect?

DATEVconnect is a programming interface for bidirectional data exchange between third-party systems and DATEV accounting applications. It is split into Desktop calls, which run exclusively locally within the network of the firm or company, and Online calls, which exchange data via a DATEV data center. Access to the Online interfaces requires a subscription, after which you first get access to a sandbox where the connection can be tested before it goes into production use. Details are provided by the DATEV Developer Portal.

How Does the DATEV API Differ from DATEVconnect?

Alongside DATEVconnect, DATEV offers further integration paths with varying entry barriers. CSV/EXTF and XML formats are the simplest tier; they require no certification but are best suited to file-based, recurring transfers rather than real-time connections. Modern REST interfaces are more powerful but require a DATEV partner certification as well as deeper technical knowledge. B2B APIs, which connect partner software, are accessible to third-party providers via the Developer Portal. In practice, a large part of DATEV integrations run via asynchronous, file-based processing: you submit a file as a job, which is placed in a queue and processed there, rather than a request delivering an immediate response.

Which Path Suits Which Integration?

A pure file export via CSV/EXTF fits when you regularly transfer large, plannable volumes of data and are not pursuing certification, for example for periodic posting batches. DATEVconnect Desktop fits when a local piece of software needs to talk directly to a DATEV application on the same network, without a detour via a data center. DATEVconnect Online or a certified REST interface fit when the integration should run in the cloud and be operated productively on an ongoing basis, for example when an upstream system automatically submits documents to DATEV Unternehmen online. For niche cases such as importing electronic cash register data, DATEV also provides its own REST endpoints, according to the Developer Portal for instance for the MeinFiskal cash register import. Anyone who wants to implement such a connection with an automation tool like n8n will find the right framework in NordFlux's n8n consulting.

What Should You Consider When Choosing?

According to the Developer Portal, DATEV's range of interfaces is under ongoing development, and the overview of available APIs is updated regularly. Before making a decision, you should therefore check the Developer Portal's help section to find out which certification level is currently required for your planned use case and whether the desired function already exists as a REST endpoint or still only runs via file export. Misjudging this point often leads to a project being planned around a certification that was not actually necessary for the intended use case.

Frequently Asked Questions About DATEVconnect, DATEV API, and Export

Do I Always Need Certification for DATEVconnect?

No, that depends on the path chosen. CSV/EXTF and XML export require no certification, while Online interfaces and modern REST APIs require a subscription or a DATEV partner certification, respectively.

What Is the Difference Between DATEVconnect Desktop and Online?

Desktop calls run exclusively locally within your own network and cannot be reached over the internet, while Online calls exchange data via a DATEV data center and require a subscription with sandbox access upstream.

Are Real-Time DATEV Integrations Possible?

Partially. A large part of the connections work file-based and asynchronously via a processing queue, while dedicated REST endpoints exist for individual niche products such as electronic cash register imports.

Where Can I Find the Current Overview of All DATEV Interfaces?

The authoritative source is the DATEV Developer Portal, since the range of offerings, according to DATEV, is continuously evolving and older overviews can quickly become outdated.

Simon Glowik, founder of NordFlux
About the author

Founder of NordFlux. Spent four years automating processes at enterprise scale at Dräger, and now brings that depth to the mid-market — pragmatic and with full data sovereignty.

Certifications

  • Microsoft certified — PL-900 and AZ-900
  • UiPath certified — Automation Developer Associate
  • UiPath zertifiziert — Automation Developer Associate
All articles
Free initial call

Concrete questions about automation or AI?

In a free 30-minute initial call we discuss your case directly. No strings attached.

DATEVconnect vs. DATEV API: The Integration Comparison