MCP for DATEV
Find documents and reports in DATEV with targeted queries
Find documents, prepare client meetings and check open issues before closing: a clearly scoped pilot makes agreed DATEV data available through your AI application. We check interfaces, client separation and reference results before implementation. Retrieved content may be transmitted to the approved model.
The way in: DATEVconnect
For local DATEV installations, we assess DATEVconnect as a connection option. The MCP server communicates with the interface over an approved network connection; DATEVconnect is not published directly on the internet for this purpose. We agree connectivity and hosting with your IT team or hosting provider.
For document management, the DATEVconnect document management module is added. The search capabilities this module provides differ from what the DATEV user interface can do. Full-text search across document contents is not available in every case. We clarify this before the proposal, because this is exactly where projects fail.
Test client separation before pilot acceptance
We check how DATEVconnect maps Windows and DATEV users and their permissions in your installation. A shared technical account does not automatically reproduce individual permissions. A pilot is therefore limited to explicitly approved data and people.
For production operation, we agree a traceable mapping between the requesting person and their permission context. User- or group-specific accounts may be one way to achieve this. Tests covering permitted and denied access must demonstrate client separation; if it cannot be enforced, the connection is not approved in that form.
Possible tasks for a DATEV pilot
- Searching documents across years
- “Find all incoming invoices from this supplier since 2023 over EUR 5,000” instead of a manual search across several financial years.
- Preparing client meetings
- Have anomalies and developments in the records summarised before the meeting takes place.
- Onboarding new staff
- Questions about the client base in plain language, without anyone having to learn DATEV navigation first.
- Deadlines and completeness
- Find missing documents and open points across the records instead of tracking them in an Excel list.
Data protection
Before client data is used, we document its flow from DATEV through the MCP server to the AI application and model provider. This includes data fields, processing locations, chat histories, logs, retention and access rights.
Your data protection and legal teams assess required agreements, confidentiality duties and whether the planned processing is permitted. We provide the technical information and implement the approved architecture. This does not constitute legal advice.
Limits we state up front
- No write access to DATEV. No postings, no changes to master data.
- No circumvention of the DATEV permission model. What a user is not allowed to see in DATEV, they do not see in the chat either.
- No commitment to full-text search across document contents before it has been verified for your DATEV installation.
- No additional storage of client data without an agreed purpose, approved location and retention rules.
Frequently asked questions
Does our DATEV data leave the firm?
That depends on the approved architecture. The original records stay in DATEV; retrieved content is transmitted to the AI application and potentially an external model provider for processing. A local MCP server does not prevent this transmission. Model destination, logs, retention and provider terms are reviewed separately.
Will every employee then see all clients?
The connection must only expose approved clients and documents. We check permission mapping in your installation and test denied access as well. A shared technical account is not automatically sufficient; pilot and production operation each need an approved permission scope.
Which DATEV components are required?
DATEVconnect in the appropriate edition, plus the document management module for document access. Which items your installation specifically needs and which of them are already licensed, we check in the feasibility phase with your IT or your hosting provider.
Does this also work with DATEV in the cloud?
That depends on your operating model. With hosted installations, the hosting provider needs to be involved early, because the MCP server needs network access to DATEVconnect. We hold this conversation together with the hosting provider in the feasibility phase.
Do we need a DPA with the AI provider?
Your data protection or legal team assesses which agreements are needed based on the providers, data and processing locations involved. We supply the architectural details. An agreement not to retain data permanently does not remove the transmission to a provider.
Let’s check whether it holds up for your systems.
We first clarify your use case, data sources, permissions and acceptance criteria. The feasibility review documents prerequisites and limits before a pilot is agreed.
Discuss your use case