Integration · DATEV
Your finance agent and DATEV. Through access you set up.
Hedi works with your DATEV data through an MCP server or API access that you connect, or with exports such as the open items list. It checks what’s overdue, drafts reminders and prepares documents for your accounting team.
Choose how Hedi reaches DATEV. Then pick what it may use.
There are two ways in, and you decide which one fits your setup.
- 01
Pick the access
Connect an MCP server for your DATEV data, run by you or a provider you trust, or save DATEV exports such as the open items list to a folder in OneDrive or SharePoint.
- 02
Add it in zwrm
Paste the server’s URL in the dashboard and choose how it signs in: API key, headers or OAuth. For exports, connect Microsoft 365.
- 03
Choose the tools
Select what the finance agent may use. Start with reading tools and add writing ones once the routine has proven itself.
- 04
Describe the routine
Tell Hedi in plain words what to check and when, for example every Friday at 14:00.
Which DATEV access fits depends on how you and your tax advisor work. We’re glad to go through it with you in a demo.
Read the docsWhat Hedi can do with DATEV data. Exactly what your access allows.
What an agent reads and writes depends on the server or export you connect. This is what the routines on this page need.
Agents can read
- The data your DATEV MCP server or API access provides
- DATEV exports in a shared folder, such as the open items list
- Invoices and payment notices in the finance mailbox
Agents can write
- Payment reminders as drafts in Outlook
- Lists and files for your accounting team or tax advisor
- Changes in DATEV only if your server offers them and you select the tool
Agents can’t
- Reach DATEV without access you set up
- Use tools you didn’t select for it
- Make a call you marked for approval before someone approves it
Approval works per connection: attach the DATEV server with approval, and every call waits for a yes on the run page.
Nothing without your setup. And nothing you didn’t approve.
Access you set up
Hedi reaches DATEV data only through the server, API access or exports you connect. Switch the connection off and the access ends for every agent.
Reading first
Select only reading tools to start. Add writing ones when the routine has proven itself, one agent at a time.
Approval before a call
Attach the connection with approval, and each call waits on the run page until someone approves or denies it. The agent’s machine waits, suspended.
Credentials stay in the gateway
Keys and tokens for the server are stored encrypted in the zwrm gateway. The agent’s machine only gets a short-lived token for its run.
Every run is logged in the dashboard, with the tools the agent called and what came back.
How zwrm handles securityRoutines with DATEV data. Explained once, they run on their own.
- Fri · 14:00 →
Open invoices check
Compares open receivables in DATEV with incoming payments and drafts a friendly reminder for anything older than 14 days.
Hedi · Finance - 3rd of the month →
Documents for the tax advisor
Collects last month’s incoming invoices from the finance mailbox, checks that each has a document and prepares them for upload to DATEV, with a list of what’s missing.
Hedi · Finance - On every new order →
Order to invoice
When Shopify reports a new order, creates the invoice, files it for DATEV and sends the customer a confirmation.
Wanda · Operations
More integrations. Same setup, other tools.
-
Mention an agent on a shared page. It answers in the thread as its own Notion user.
-
Mail, calendars, files and Teams chats, through a Microsoft 365 user of the agent’s own.
-
Contacts, companies and deals, read and updated through the agent’s own HubSpot user.
-
Conversations in your shared inboxes: reply drafts, comments and tags.
-
Mention it in an issue. It works on a branch and opens a pull request.
Tell us what lands on your desk every week. We’ll show you an agent doing it.
A demo with our team, in English or German. Bring one recurring task and the tools it touches.