The n8n DATEV interface: what actually works and what does not

A ready-made n8n DATEV interface as a dedicated node does not exist, as of July 2026. n8n and DATEV can still be connected: via the official DATEV data services through the HTTP request node, via a community node verified by n8n, or via the DATEV file export. In every case the prerequisite is that your tax firm enables the services.

In practice the problem looks like this: invoices arrive by email, receipts sit in the ERP or the web shop, and at the end of the month someone retypes it all for the tax advisor. This exact media break is what an n8n DATEV interface closes. The relevant services are the Rechnungsdatenservice 1.0 and the Belegbilderservice, which n8n addresses via the HTTP request node, plus a verified community node from the DATEV partner Klardaten.

The real problem: media breaks on the way to accounting

Most businesses digitised their accounting long ago, just not the path leading to it. Receipts get printed, scanned, forwarded by email or uploaded into the firm portal by hand. Each of these steps costs time, and each produces errors that the firm later has to chase up by phone. The month-end close is delayed not by the posting, but by the delivery.

How the front part of this chain can be automated, meaning receiving, reading and checking incoming invoices, we described in the article Processing invoices automatically. This piece is about the last stretch: the handover to DATEV.

Which interfaces DATEV offers

DATEV provides around 15 online interfaces via its developer platform developer.datev.de. For businesses that want to hand receipts over to their firm, three data services above all are relevant:

• Rechnungsdatenservice 1.0 (formerly DATEVconnect online): transfers structured invoice data together with the receipt image to DATEV Unternehmen online
• Belegbilderservice: transfers only the receipt images as PDF or scan, the firm captures the data itself
• Buchungsdatenservice: transfers finished accounting records, intended for systems that already pre-assign accounts

All three services have to be requested from DATEV by the tax firm and enabled per client. The running costs are tiered by receipt volume and start, according to the DATEV price list, in the low single-digit euro range per month and client. So the expensive part is not running it, but setting it up.

The n8n DATEV interface: three routes to a connection

There are three practical routes to the n8n DATEV interface: the HTTP request node against the DATEV data services, a verified community node, and the classic file export. The first route is the most direct. n8n calls the DATEV APIs itself, which requires registration on the DATEV developer platform, an OAuth2 connection with DATEV login, and enablement by the firm. The second route uses the DATEVconnect node from Klardaten GmbH, which is verified by n8n and shortcuts the API part, but depends on that partner's offering. The third route dispenses with the API entirely: n8n generates posting batches in the DATEV format (EXTF/CSV) that the firm imports in the regular way. This works without developer access and without enablements, but it contains a manual import step.

Which route fits depends on your receipt volume, your systems and your firm. In our n8n projects we clarify this before the first workflow, because a DATEV connection that the firm does not support is worthless.

An example: incoming invoice from email to DATEV

A typical workflow begins in the invoice inbox: an IMAP trigger in n8n monitors the inbox and pulls out PDF attachments. An AI step reads out the supplier, invoice number, date, net and tax amounts. Then a plausibility check follows, for example whether the totals add up and the supplier is known. Only when everything fits does n8n hand the receipt together with the structured data over to DATEV Unternehmen online via the Rechnungsdatenservice, where the firm finds it ready for posting. Uncertain cases do not land in DATEV but in a review list for a human. This approval loop is not a blemish, it is the reason the firm can trust the system.

Where the limits lie

The biggest hurdle is not the technology but access: the DATEV online APIs are open only to registered developers, and productive access requires the firm to enable the data services per client. On top of that comes OAuth2 authentication with DATEV login and short-lived tokens that a workflow has to manage cleanly. In terms of content: the data services deliver receipts and accounting data to the DATEV data centre, the posting still happens at the firm. So n8n replaces neither DATEV nor the tax advisor, it replaces the retyping beforehand. And one point for planning: from autumn 2026 DATEV is reshaping its product portfolio step by step towards the cloud, which means the interface landscape is in motion.

lexoffice as a lightweight alternative

Lexware Office, called lexoffice until 2024, offers an open public API in contrast to DATEV: you generate the API key yourself in the settings, no partner registration needed. Several community nodes exist for n8n, including triggers for events such as new invoices or payments. Anyone who already runs their accounting in Lexware Office has shortened the automation route considerably. And the link to the firm is preserved, because Lexware Office in turn hands data to DATEV via the Rechnungsdatenservice. This is no disparagement of DATEV: if your firm works firmly with DATEV Unternehmen online, the direct route is usually the right one. The open API is an argument for smaller businesses with their own accounting software.

Frequently asked questions

Is there an official n8n node for DATEV?

No, as of July 2026 there is no official DATEV node in n8n. There is a community node verified by n8n from the DATEV partner Klardaten, as well as the option to address the DATEV online APIs directly via the HTTP request node.

Do I need my tax advisor for the connection?

Yes. The DATEV data services are requested through the tax firm and enabled per client. Without this enablement no third-party system can transfer data to DATEV Unternehmen online. So involve the firm before the first workflow.

What does connecting n8n and DATEV cost?

The running DATEV fees are tiered by receipt volume and, for small volumes, lie in the low single-digit euro range per month and client. The real effort sits in the setup: developer access, OAuth2 connection, firm enablements and building the workflow.

Can the handover to DATEV also work without an API?

Yes. n8n can generate posting batches in the DATEV format (EXTF/CSV) that your firm imports in the regular way. This is robust and needs no enablements, but it contains a manual import step and does not transfer receipt images automatically.

Can n8n post directly into DATEV?

No. The data services transfer receipts and accounting data to DATEV Unternehmen online or the DATEV data centre. The actual posting and the professional responsibility stay with your firm, which also makes sense.