AI-bookkeeping in Deutschland: DATEV, sevDesk, oder Lexware — welches passt zu welcher Skala in 2026

If you run a small German business in 2026 (Einzelunternehmer, GmbH-Geschäftsführer, freiberuflich) and you have read the jurisdiction-neutral case for DIY AI-bookkeeping (OPS-031), the question that keeps coming up is which German Buchhaltungssoftware actually takes AI-drafted Buchungssätze cleanly without breaking the GoBD audit trail. The honest answer is that the choice depends on Umsatz tier and Steuerberater relationship more than on AI capability, and the wrong tool choice produces an audit trail that fails Betriebsprüfung scrutiny regardless of how good the AI got at drafting the entries.

This piece walks where OPS-031 breaks on the German audit trail, the three tools that dominate German Mittelstand bookkeeping in 2026, the decision tree per Umsatz tier, the OSS-Verfahren and reverse-charge VAT prompt-prefix that AI-bookkeeping requires for German operators, and the 4-question filter for the category.

Where OPS-031 breaks on the GoBD audit trail

The jurisdiction-neutral OPS-031 piece makes the case that solo founders under €30K MRR can run DIY AI-bookkeeping with Claude or ChatGPT and a structured prompt-pack. That case holds in Germany too, with one binding caveat: the AI-drafted Buchungssatz has to land in a Buchhaltungstool that preserves the GoBD audit trail.

The Grundsätze ordnungsmäßiger Buchführung und Speicherung in elektronischer Form (GoBD) require every accounting entry to be traceable to its source document (Beleg), with the VAT-rate reasoning visible, the entry’s change history preserved, and the entire substrate readable in a Betriebsprüfung at the speed the Finanzamt requires. The published GoBD framework is at the Bundesministerium der Finanzen GoBD page.

An AI that drafts Buchungssätze in a spreadsheet, with the operator then manually transcribing them into a system, produces no GoBD audit trail. The operator owns the transcription error rate plus the missing documentation. A Betriebsprüfung that hits this configuration produces a Schätzung at the Finanzamt’s discretion and an HInzuschätzung that almost always exceeds what the proper trail would have shown.

The German-specific layer is therefore not optional. The AI drafts; the German tool preserves the trail. The choice between DATEV, sevDesk, and Lexware is the choice that makes the AI-bookkeeping case actually work in Germany.

DATEV (€20-€80/month plus Steuerberater-coupling): best fit above €100K Umsatz

DATEV is the dominant Buchhaltungs-Plattform in the German Mittelstand and is the system most German Steuerberater are native in. The platform covers the full accounting stack, Belegerfassung, Buchungssätze, USt-Voranmeldung, Jahresabschluss, Lohnbuchhaltung, and integrates directly into the Steuerberater’s workflow.

The strengths that matter for AI-bookkeeping. (1) Native API and structured-data import, DATEV Unternehmen Online accepts AI-drafted entries through documented import formats (DATEV-CSV, DATEV-XML, the DATEV-Kontenrahmen mapping). (2) Audit-trail completeness, every entry carries the full GoBD substrate including change history, source-document linkage, and Steuerberater-side review log. (3) Steuerberater-coupling, the Steuerberater works directly in the customer’s data, which means corrections, USt-Voranmeldung filings, and Jahresabschluss preparation happen without re-export.

The cost structure splits into the platform fees (€20-€80/month depending on tier) plus the Steuerberater-coupling fees (DATEV charges the Steuerberater per active customer; the Steuerberater typically passes some or all of that through). The total monthly cost for a Mittelstand business runs €100-€300/month for the customer-side software plus Steuerberater fees.

DATEV is the right choice when. (1) The operator’s Steuerberater is DATEV-native (most are). (2) The business is approaching GmbH conversion within 12 months, DATEV handles the conversion better than the alternatives. (3) Multi-currency invoicing is a current or near-term requirement. (4) Intercompany Buchungen between DE and an EU sister company are part of the business model. (5) The Steuerberater requires DATEV for the Jahresabschluss workflow.

DATEV is procurement-defensible above €100K Umsatz and becomes the default above €500K. Below €100K, the Steuerberater-coupling fees and the platform tier costs typically exceed the AI-bookkeeping saving, and the procurement-defensible choice is usually sevDesk.

sevDesk (€8-€48/month): best fit under €100K Umsatz

sevDesk is the cheap-and-fast option for German solo founders, Einzelunternehmer, and small Mittelstand businesses under €100K Umsatz who want a GoBD-compliant audit trail without the DATEV cost stack.

The strengths that matter. (1) Direct API support for AI-drafted invoice and receipt entries, the sevDesk API is documented and the typical AI-bookkeeping prompt-pack writes directly into the API. (2) GoBD-compliant audit trail at the platform level, every entry carries source-document linkage and change history. (3) USt-Voranmeldung integration, the platform produces the ELSTER-ready filing without manual export. (4) Steuerberater-portal, the Steuerberater can read the data without forcing a DATEV migration; many small-firm Steuerberater accept sevDesk customers, even DATEV-native ones for clients under their €100K tier.

The cost structure is flat. €8/month for the entry tier (Belege, Rechnungen, basic accounting). €18/month for the Buchhaltung tier that adds GoBD-compliant Buchungssätze. €48/month for the Pro tier that adds payroll, multi-user, and broader integration. Most solo founders run the €18 tier; the €48 tier becomes appropriate when payroll arrives.

sevDesk is the right choice when. (1) Umsatz is under €100K and the Steuerberater accepts the platform. (2) The operator wants the cheapest path to GoBD-compliant AI-bookkeeping. (3) The business is unlikely to convert to GmbH within the next 12 months. (4) Payroll is not a current requirement, or the payroll volume is small enough that sevDesk’s payroll module suffices.

The procurement-defensible read for sevDesk is that it covers the AI-bookkeeping use case at the lowest cost point that still produces a Betriebsprüfung-defensible substrate. The trade-off against DATEV is the Steuerberater-coupling, sevDesk requires the Steuerberater to read the data through the customer’s portal rather than working directly in shared substrate. For most under-€100K operators, that trade-off is acceptable.

Lexware (€10-€40/month): legacy-Mittelstand fallback

Lexware (Haufe-Lexware) is the legacy German Mittelstand option. It has the broadest installed base in the under-€500K-Umsatz cohort because of its long history (Lexware has been the default for desktop-based Mittelstand bookkeeping since the late 1990s), and it is the natural fallback for businesses with existing Lexware deployments.

The strengths that matter. (1) Established GoBD compliance and audit-trail patterns, Lexware has been doing this for decades, and the Betriebsprüfung-acceptance is well-documented. (2) Cloud and desktop offerings, Lexware Office is the cloud product; the desktop product is still actively supported for businesses that prefer local deployment. (3) Reasonable API for AI-bookkeeping import, the Lexware Office API is documented and accepts AI-drafted entries, though the documentation is less comprehensive than sevDesk’s.

The weakness for AI-bookkeeping is that Lexware was built for a desktop-era Mittelstand workflow and the AI-bookkeeping pattern is a 2025-2026 addition rather than a native capability. The integration works but requires more manual setup than sevDesk.

Lexware is the right choice when. (1) The business has an existing Lexware deployment and migrating to sevDesk or DATEV would consume more effort than the AI-bookkeeping saving justifies. (2) The Steuerberater is Lexware-comfortable and not pushing for migration. (3) The operator prefers the desktop product for offline-capable bookkeeping.

The procurement-defensible read for Lexware is that it is a fallback rather than a default. New deployments in 2026 should default to sevDesk under €100K and DATEV above €100K; Lexware is the right choice when migration cost exceeds the better-fit value.

The decision tree per Umsatz tier

Under €30K Umsatz, no employees, simple VAT situation. sevDesk entry tier (€8/month) plus Claude Pro or ChatGPT Plus for the AI-bookkeeping prompt-pack. The Steuerberater handles the Jahresabschluss; the operator handles everything else. Cheapest path that produces a GoBD-defensible substrate.

€30K-€100K Umsatz, no employees, OSS-Verfahren or reverse-charge VAT in play. sevDesk Buchhaltung tier (€18/month) plus Claude Pro. The OSS prompt-prefix becomes load-bearing here because the VAT logic across EU jurisdictions is where AI errors cluster. The Steuerberater coupling moves from quarterly check-in to monthly review.

€100K-€500K Umsatz, employees or multi-currency. DATEV Unternehmen Online plus DATEV Lohn for payroll, plus the AI-bookkeeping prompt-pack adapted for DATEV’s Kontenrahmen. The Steuerberater-coupling fees become acceptable at this Umsatz tier and the cross-currency / payroll integration is worth the cost.

Above €500K Umsatz or approaching GmbH conversion. DATEV is the procurement-defensible default. The migration from sevDesk or Lexware to DATEV is more expensive in mid-Geschäftsjahr than at conversion, so businesses approaching GmbH should make the migration decision deliberately rather than under conversion pressure.

Existing Lexware deployment with established workflows. Lexware Office or Lexware desktop continues. Migration cost typically exceeds the better-fit value of sevDesk or DATEV unless the business is approaching GmbH conversion or growing past €500K Umsatz.

The OSS-Verfahren and reverse-charge VAT prompt-prefix

The single largest source of AI-bookkeeping error in German operators with EU customers is the VAT-rate logic. The operator-facing prompt-prefix that prevents this looks roughly like:

“I am a German Einzelunternehmer / GmbH with [primary VAT status: Kleinunternehmer §19 UStG / OSS-participant / IOSS-participant / normal Regelbesteuerung]. My customer base is [primary segment: DE-only B2C / DE+EU B2B / DE+EU B2C / DE+non-EU export]. For each invoice or receipt I share, apply the following rules. (1) DE B2C: 19% standard rate or 7% reduced rate as applicable. (2) DE B2B: 19% standard or 7% reduced. (3) EU B2B with valid USt-IdNr: 0% reverse-charge with USt-IdNr citation in the Buchungssatz commentary. (4) EU B2C under OSS-Verfahren below the €10K annual threshold: DE rate. (5) EU B2C under OSS above the €10K threshold: destination-country rate. (6) Non-EU export: 0% Ausfuhrlieferung with Ausfuhrnachweis required. Where the VAT logic is ambiguous, flag the ambiguity rather than guessing. Where the input document is missing a required field (e.g., USt-IdNr for EU B2B), flag the missing field.”

The prefix lives in a Claude or ChatGPT workspace project so every AI-bookkeeping session starts from the same baseline. The operator updates the prefix when VAT status changes (e.g., crossing the OSS €10K threshold) or when the customer base shifts.

The error rate without the prefix is roughly 5-8% on EU-cross-border invoices in the AI-bookkeeping logs operators publish. With the prefix, it drops to under 1%. The Steuerberater-side correction cost on the un-prefixed pattern typically exceeds €30/month, more than the sevDesk subscription.

What 4-question OPS-011 filter says

The 4-question OPS-011 filter for first-AI-buy applies cleanly here.

Question 1: does the AI-bookkeeping workflow have a defined output you can audit at the end of each session? Yes, the Buchungssätze in the German tool are the auditable output, with the source documents linked and the VAT logic visible.

Question 2: can the operator handle the failure mode without specialist help? Mostly, VAT errors are catchable in monthly review with the Steuerberater. The operator does not need to be a tax expert; they need to be a careful reviewer.

Question 3: does the cost structure scale with usage in a way the operator can predict? Yes for sevDesk (flat tier), partly for DATEV (Steuerberater-coupling has variable component), yes for Lexware (flat tier). The AI-side cost (Claude Pro or ChatGPT Plus) is flat.

Question 4: is the buy reversible if it does not work out? Yes, sevDesk to DATEV migration is well-trodden, sevDesk to Lexware is straightforward, AI-side cancellation is monthly. Reversibility is high.

The category passes the filter cleanly. AI-bookkeeping with German tools is one of the strongest first-AI-buys for German solo founders and small Mittelstand operators.

The procurement order

For a German operator new to AI-bookkeeping in 2026.

1. Pick the German tool by Umsatz tier (sevDesk under €100K, DATEV above, Lexware as fallback).
2. Sign up for Claude Pro or ChatGPT Plus.
3. Build the OSS-Verfahren prompt-prefix in a workspace project.
4. Run the prompt-pack against last month’s invoices and receipts as a test.
5. Validate the AI-drafted Buchungssätze with the Steuerberater in the next quarterly check-in.
6. Iterate the prefix where the Steuerberater finds errors.
7. Run production from month 2.

The first-month cost is under €40/month for a sevDesk-tier operator. The first-month time saving is typically 4-8 hours that the operator now reinvests in customer-facing work. The Steuerberater-side cost stays roughly flat because the AI-side review takes about as long as the manual-side review used to. The system is in production from week 4.

The companion piece that walks the broader AI-bookkeeping case for German operators is OPS-031 the jurisdiction-neutral case. The NL-specific sister piece is at OPS-045. The Mittelstand-specific BetrVG and DSGVO deployment piece is at OPS-049.