Connecting an AI Agent to DATEV: DATEVconnect, APIs and Exports
DATEV is the accounting and payroll software used by many German tax advisers and their clients, often run by the company's external tax adviser rather than by the company itself. International groups with a German entity meet it sooner or later. If you want an AI agent to handle invoices, open items or financial reports for that entity, you need to know how the agent gets at DATEV data and how it hands anything back. DATEV does not offer one API for this but three very different routes. Everything below reflects DATEV's developer documentation as of November 2026.
What does connecting an AI agent to DATEV actually mean?
It means giving the agent a small set of controlled tools that read accounting data, submit documents or prepare postings. The language model never talks to DATEV directly. A layer of ordinary code sits in between and handles permissions, data formats and logging.
A typical flow: the model decides, through tool use, that it needs the open items for a supplier. The tool calls the relevant DATEV interface, trims the response and returns only what the task needs. Whether you package these tools as an MCP server or embed them in the agent is an architecture choice; DATEV does not care either way.
Tasks that fit this pattern:
- Document intake: pick supplier invoices out of a mailbox, check the mandatory fields and pass them to DATEV as accounting documents.
- Posting proposals: turn invoice data into a batch of bookings with account, contra account, document date and posting text.
- Report explanations: read trial balances or open-item lists and summarise them in plain language for management, including non-German speakers at group level.
- Query lists: collect missing receipts or unclear bookings and send one consolidated list to the tax adviser.
What are the three routes into DATEV?
DATEV offers locally installed desktop APIs (DATEVconnect), online APIs hosted in its data centre (called data services) and file formats such as the DATEV format. They differ in where they run, how they authenticate, what approval DATEV requires and whether the tax adviser has to pull the data in.
| Criterion | DATEVconnect (desktop APIs) | Online APIs (data services) | DATEV format (EXTF file) |
|---|---|---|---|
| Reachable from | local network only | internet, via DATEV data centre | file imported into DATEV accounting |
| Authentication | local, inside the DATEV setup | OpenID Connect with PKCE | none, the file is imported |
| DATEV approval | no subscription, terms apply | onboarding with technical review | none for the file itself |
| Read or write | both | depends on the service | write only (import) |
| Fits when | DATEV runs in-house | the tax adviser runs DATEV | effort must stay low |
DATEVconnect: the local desktop APIs
DATEV's developer portal describes the desktop APIs as interfaces that are not available over the internet, only within the local network. They suit companies and accounting firms that run DATEV software themselves, for example on their own server.
Modules listed in the portal include (as of November 2026):
- Accounting (version 1.7.4): exchange of master and transaction data and reading of accounting reports.
- Client Master Data (version 1.7.0): reading and writing central master data such as clients and addressees.
- Document Management (version 2.4.0): storing, querying and editing documents in DATEV DMS.
- Payroll (version 3.1.4): two-way exchange of employee master and transaction data with DATEV Lohn und Gehalt.
- Identity and Access Management (version 1.1.0): access to DATEV users and groups.
- Diagnostics and Functional Tests (version 1.1.0): a basic function test for development.
For an agent, DATEVconnect is the most direct option: read and write without going through a data centre. The catch is the network boundary. If your agent runs in the cloud, you need a component inside the local network that receives calls and forwards them, and you need to secure that path properly. DATEV's developer FAQ notes that desktop APIs need no subscription, though DATEV's interface terms still apply.
Online APIs: DATEV data services
DATEV calls its authenticated data-centre APIs data services. Per the FAQ, sign-in uses OAuth 2.0 and OpenID Connect. For accounting, the product catalogue lists, among others:
- accounting:documents (version 2.0): send digital receipts through the DATEV data centre to the tax adviser.
- accounting:dxso-jobs (version 2.0): send document images plus structured invoice and cash-register data.
- accounting:extf-files (version 2.0): upload master and transaction data in the DATEV format for retrieval in DATEV accounting.
- accounting:clients (version 2.0): list the accounting data services available per client.
- accounting:dataexchange (version 1): query accounting data from DATEV Rechnungswesen; marked as a paid API with additional terms.
The key difference from DATEVconnect is direction. Most of these services are built to deliver data towards the tax adviser. Your agent drops off a receipt or a booking batch, and the adviser processes it in their DATEV. Reading accounting data online is limited to selected services, some of them paid.
DATEV format: the file route
According to DATEV's documentation, the DATEV format is a CSV file with the fixed prefix EXTF_ and a fixed record layout. Line 1 holds header metadata, line 2 the column names, and data starts on line 3. Fields are separated by semicolons, text fields are quoted, and decimals use a comma, German style.
DATEV's sample booking batch starts like this:
"EXTF";700;21;"Buchungsstapel";13;20240130140440439;;"RE";"";"";29098;55003;20240101;4;20240101;20240831;...
Umsatz (ohne Soll/Haben-Kz);Soll/Haben-Kennzeichen;WKZ Umsatz;Kurs;Basis-Umsatz;...
Note that field names are German only. For an agent this is the lowest-effort route: it generates a file, a person checks it, and the finance team or tax adviser imports it. The agent cannot read anything this way. You can also upload the file through the accounting:extf-files online service, in which case the online API rules apply.
Why does the tax adviser matter so much?
With DATEV, the external tax adviser is nearly always part of the integration, because they often keep the books and take in the data you deliver. An agent inside the company therefore usually feeds the adviser rather than posting on its own. Agree early on which data the adviser wants and in what form.
This is the part of DATEV that surprises teams from other countries. In many markets the finance team owns the ledger in its own ERP. In Germany, many smaller companies outsource bookkeeping to a tax adviser who runs DATEV. DATEV's own developer FAQ recommends involving a tax adviser as a potential user when building an interface. It is not mandatory, but DATEV says the functional quality of integrations is noticeably higher when they do.
Questions to settle with the adviser:
- Who keeps the books? If the adviser does, they decide whether documents arrive through DATEV Unternehmen online, as a booking batch or another way.
- Who grants access? Online APIs require a DATEV user to sign in. For long-lived access, DATEV's authentication guide binds the token to exactly one adviser and client number.
- Who pays running costs? DATEV states that per-call running costs are usually borne by the end user, meaning the tax adviser or their client.
- Who finalises entries? Locking postings stays a human decision in the finance team or at the adviser's office.
If DATEV runs entirely in-house, for instance in a group accounting department, DATEVconnect is often the obvious route and the adviser only joins for year-end closing and tax returns.
What do you need before you start?
You need clarity on where DATEV is installed, a test environment, tight permissions and a tool layer the agent is allowed to call. For online APIs you also need an account in the DATEV developer portal, an organisation, an app and DATEV's guided onboarding. None of the three routes should be built without a test system.
Technical prerequisites:
- Where DATEV runs: on-site, with a hosting provider or only at the tax adviser's office. This decides whether DATEVconnect is reachable at all.
- Test environment: DATEV's FAQ lists solution partners that offer online test and development environments with current DATEV versions. The online API onboarding requires a DATEV test system.
- Network: a cloud agent using DATEVconnect needs a secured connection into the local network. DATEV also notes that its APIs are addressed by DNS names and that IP addresses can change.
- Authentication: online APIs require the authorization code flow with PKCE (method S256), per DATEV's guide. Access tokens last 15 minutes; refresh tokens without offline access last at most 11 hours. With the
offline_accessscope you get a refresh token valid for two years, tied to a single client.
Organisational prerequisites:
- Least privilege: an agent that handles receipts has no business seeing payroll data.
- Approval path: who reviews posting proposals, who imports, who locks entries?
- Data protection: accounting and payroll data are sensitive. An agent with DATEV access can be operated in line with the GDPR once model choice, storage location and data processing agreements are settled. If you prefer not to send this data to a cloud model provider at all, see the options for sovereign AI.
How do you build the integration step by step?
Start with one narrow process, pick the DATEV route second, and begin with read-only access or proposals rather than direct postings. The order process, access, tools, testing, approval keeps a technically working agent from delivering financially wrong data.
- Define the process. One flow, one measurable result, such as "pass incoming supplier invoices to the tax adviser as documents with a posting proposal".
- Agree the data flow with the adviser. Which route will they accept? Which fields of the booking batch should be filled?
- Choose the route. DATEV in-house and read access needed: DATEVconnect. Adviser runs DATEV: an online service such as accounting:documents or accounting:extf-files. Low volume and minimal effort: a DATEV-format file.
- Set up access. For online APIs, follow the steps in the developer portal: register, create an organisation, create an app, subscribe to API products and build in the sandbox, then request the production upgrade with a technical review.
- Build narrow tools. One tool per task, for example "read supplier open items" or "propose booking batch". Each tool validates input before anything reaches DATEV.
- Keep a human in the loop. Write actions go through an approval step (human in the loop). The agent shows its proposal and reasoning; a person confirms.
- Test against a test client. Use real but low-risk transactions and log every difference between proposal and final posting.
- Go live and operate. For online APIs, DATEV performs the acceptance review. After that: monitoring, token handling and a named owner for errors.
On cost, DATEV's FAQ lists a one-off charge of 1,500 euros plus VAT for onboarding the first data service, including four hours of consulting; further consulting is billed by DATEV at 210 euros plus VAT per hour or part thereof. DATEV states there is no simplified procedure for internal-only use.
What are the limits and risks?
The main risks are wrong posting proposals, overly broad permissions and an underestimated approval process. A language model can confuse accounts or infer the wrong tax code. Every write action therefore belongs behind human review, and the agent should only see the data its process needs.
- Accounting errors: account coding and tax keys depend on the chart of accounts and on the individual case. An agent can produce a plausible but wrong proposal. Always review and track the deviation rate.
- Prompt injection through documents: invoices and emails come from outside. A manipulated document may try to steer the agent. Tools with write access must never act on document text alone.
- Format details: the DATEV format demands exact syntax, such as doubled quotation marks inside text fields and no line breaks within fields. Errors often only surface at import.
- Token scope: long-lived offline access is bound to a single client and only works with APIs whose path contains the client ID. An agent serving many clients needs proper token management and the revocation option DATEV requires.
- Approval effort: online API onboarding is a guided process with an appointment and acceptance review. Plan time for it, even for internal tools.
- Language and locale: field names, sample files and much of the documentation are in German, and numbers use decimal commas. International teams should budget for that.
When this approach does not fit: if your German entity books only a handful of invoices a month and the adviser already uses DATEV Unternehmen online, a dedicated DATEV-connected agent rarely pays off. An agent that sorts and names documents without touching DATEV is often enough. Similar trade-offs apply to ERP systems; for SAP, see connecting an AI agent to SAP S/4HANA. The main difference: SAP usually sits entirely within the company, whereas DATEV almost always puts the tax adviser into the data flow.
Where should you start?
Start with a conversation with your tax adviser and a short inventory: where DATEV runs, how data moves today and where most manual effort goes. The answers usually point straight to one of the three routes and to the process best suited for a first agent.
A practical sequence:
- One-hour inventory: DATEV location, adviser involved, current document flow, monthly volume.
- Pick one process: document intake or posting proposals are good first candidates because the results are easy to check.
- Prototype on the simplest route: often a DATEV-format file that a person reviews and imports.
- Move to an API once it works: only when quality and volume justify it is DATEVconnect or the online onboarding worth the effort.
For an overview of which agent types work in finance and neighbouring departments and how they are built, see AI agents for business functions. To connect one agent to several systems through a standard interface, read the guide to MCP servers.
Note: this article describes technical options for orientation and is not tax or legal advice.
Frequently asked questions
What is DATEV, for readers outside Germany?
DATEV is a German cooperative whose accounting, payroll and tax software is used by many tax advisers and their business clients. If your German subsidiary's books are kept by a local tax adviser, they very likely sit in DATEV.
Can I skip DATEV's onboarding if the integration is only for internal use?
No. DATEV's developer FAQ states that there is one onboarding process for all online API integrations, whether or not they are commercial.
Do the local DATEVconnect APIs need a subscription?
According to DATEV's developer FAQ, desktop APIs do not require a subscription in the developer portal. DATEV's terms of use for interfaces still apply.
Should the agent post entries in DATEV on its own?
It is safer to let the agent prepare postings or documents and have a person in the finance team or at the tax adviser review and finalise them. Account coding depends on the chart of accounts and on individual cases.
Is this tax or legal advice?
No. The article describes technical options for orientation. Questions on bookkeeping rules, retention and liability belong with your tax adviser.
Sources
- DATEV Developer Portal: API products (online APIs and desktop APIs) developer.datev.de
- DATEV Developer Portal: FAQ on onboarding, approval and costs developer.datev.de
- DATEV Developer Portal: Cloud integration authentication (OpenID Connect) developer.datev.de
- DATEV Developer Portal: DATEV format, getting started developer.datev.de
- DATEV Developer Portal: steps to an integration developer.datev.de
- DATEV: interface providers datev.de