Post from five channels in one inbox
Email, client portal, paper, messenger and DATEV come together and are sorted by a rule set into baskets: deadline matter, official post, receipt, client request.
Integration
Connect to DATEV,
do not replace it
In a tax practice DATEV is not one application among several, it is where the truth is kept. Any suggestion of touching it is rightly treated with suspicion. We do not touch it: DATEV stays authoritative, we read, and what gets built is built around the routes that run by hand today.
This stays
What your application keeps doing
- Accounting and master data. DATEV stays the authoritative source; we do not take that over.
- The familiar interface and the workflows your people know by heart.
- Working with the data centre, if that is how your practice is set up.
- Your existing DATEV interfaces to other providers. We come alongside, not in between.
We do not replace anything
This is not a replacement and not a migration. Your application stays authoritative for its data and keeps its interface and its workflows. We sit alongside it and take over the routes that today run by hand between applications. Switch us off tomorrow and your application carries on exactly as before.
The boundary
Where we come in
DATEV and the partner products connected to it now ship AI features of their own. For summarising and searching that is often enough. But the time in a practice is lost elsewhere.
A basket for unclear cases
Whatever is not recognised with enough confidence lands there rather than somewhere. A module that always has an answer is the problem in a practice, not the solution.
Deadlines calculated, with the working shown
Four days of deemed service under section 122 (2) no. 1 AO, one month under section 355 AO, deferral to the next working day under section 108 (3) AO. The working sits alongside. A calculation aid, not legal advice.
The file that knows its own gaps
On the left the missing documents with waiting time and chase status, on the right what is there by subject and year. What is saved is the reference: your document system stays the document store.
Section 203 StGB as the starting point
Either pseudonymisation with visible human sign-off before anything goes out, or a language model entirely inside your own infrastructure. The AI part can be switched off.
Technically
How we connect
DATEV has three routes out: the file format, the DATEV data services, and the DATEVconnect programming interface. Which one fits depends on whether DATEV runs on your practice network or in the data centre. We take the route you already have, and we take it read-only.
- Through the DATEV format file, where no interface access exists or it is not worth setting up.
- Through DATEVconnect, where DATEV runs on the practice network and access is configured.
- Through a gateway, where DATEV sits in the data centre.
- In all three cases read-only. DATEV stays authoritative for master data, and no second set of books appears.
Objections
What you are wondering now
- Do we have to leave DATEV?
- No. What we build assumes DATEV. It reads from it and creates nothing DATEV already holds.
- Does this need DATEV certification?
- DATEV certification applies to providers offering an interface as a product in the DATEV marketplace. A connection built for your practice that only ever reads is a different thing. Which route is technically possible at your end is something we settle before any quote, not after.
- Where do the language models run?
- Wherever you require. With section 203 StGB that is not a matter of taste: either the model runs inside your own infrastructure, or things only go out pseudonymised and after visible sign-off. Without a key configured there is no AI part at all.
- What happens with a DATEV update?
- A read-only connection through a file format is barely affected. With DATEVconnect we check it as part of looking after the system. If the connection drops, the practice carries on as before, only by hand.
Information as at: Information on the DATEV interfaces taken from publicly available manufacturer material, as at 15 September 2026. DATEV is a trademark of DATEV eG; we have no business relationship with them and are not a certified DATEV interface provider.
Next step
Let us take your inbox
and cost it out.
45 minutes, free of charge. We walk through how post arrives at your end today, who matches it and how long that takes. From that it follows whether a connection pays off. Sometimes the answer is no.