amaiko Kanzlei vs LUIGI AI: DATEV Without a Copy, Right in Teams (2026)

Your client files: fetched on request, never mirrored

amaiko Kanzlei asks DATEV when someone on your team asks amaiko. It reads postings, balances (SuSa) and accounts from Rechnungswesen, payroll results and payroll reports from Lohn, or documents from the DMS, answers the question, and keeps no mirror of your data. For Rechnungswesen and Lohn, each person signs in with their own DATEV login, via SmartLogin, SmartCard or mIDentity. Your firm connects the DMS once, through the Cloud Gateway for DATEVconnect by Riecken, which DATEV itself names for cloud vendors, and the question goes to Haufe when you use Haufe.

LUIGI built the opposite. Per its security page, Werwolf GmbH from Bad Wurzach runs the “DATEV-Mirror-ETL — Spiegelung der DATEV-Bestände in die LUIGI-Datenbanken”, the mirroring of your DATEV holdings into LUIGI’s databases. LUIGI describes its own search like this: it searches “Ihr komplettes DATEV” (your entire DATEV). The onboarding step is called “DATEV-Daten laden”: “your client data is securely loaded and indexed”. The DATEV add-on in LUIGI’s price list adds “Laufender Sync & sichere Indexierung”, ongoing sync and indexing. LUIGI’s blog explains the choice itself: “LUIGI reads every document in advance”, and a plain live connection to your DATEV interface “cannot do that”. But what LUIGI read in advance is only as current as the last sync. amaiko Kanzlei reads the document as it stands when you ask.

Who is Werwolf GmbH? On its own website it describes itself as an IT service provider from Bad Wurzach: “Von einer Medienagentur… zum IT-Dienstleister?” (From a media agency … to an IT service provider?) “Mit drei ausgebildeten IT-Experten im Team entstand dann die Idee für Werwolf IT.” (With three trained IT experts on the team, the idea for Werwolf IT was born.) Its services there: IT consulting, IT support, IT security, IT and cloud infrastructure, and IT for schools. DATEV does not appear on its home page, and neither does a certificate. It was entered in the commercial register in 2021 as Werwolf Media GmbH.

What sits in that mirror is listed in Annex A of LUIGI’s data processing agreement template (as of 11 May 2026): client and personal accounts, postings, balance sheet and P&L figures, and the DMS documents, from tax returns and assessment notices to correspondence. For the payroll connection, whose go-live the same annex announces for Q2/2026, it lists wage and salary data, social security numbers, religious affiliation and, where applicable, health data from payslips. Per LUIGI’s compliance annex (as of 25 September 2026), DMS documents travel through the hardware box in your office into the cloud, DATEV master data is mirrored as a “Daily-Mirror”, and whatever you delete in DATEV, LUIGI deletes “beim nächsten Sync” (at the next sync), stated as 24 to 48 hours, unless someone also deletes it at LUIGI directly.

Your firm carries the risk: a continuously synchronised copy of your DATEV holdings sits outside your firm, filled by Werwolf GmbH, in Microsoft Azure, in the databases of LUIGI AI GmbH, which has been on the commercial register since June 2026 (Amtsgericht Ulm, HRB 752091).

Getting started: a Teams chat, not a box in the post

amaiko Kanzlei needs no hardware and no data import. amaiko sets up a sealed tenant for your firm, your team installs amaiko in Microsoft Teams, each person connects their DATEV login, and the first question goes into the chat window that is already open. Nothing loads for days, because amaiko does not load your data.

LUIGI’s home page describes eight steps to go-live. Step four: “You receive your LUIGI Connect package by post — the hardware for securely connecting your firm’s systems.” Step five sets up the interfaces, step six loads the DATEV data, “usually a few days”, and step seven is training for your staff. For your firm that means an extra device to connect your systems, a project before the first answer, and a new tool your team has to learn.

Price: flat, not by archive size

amaiko Kanzlei costs €41.58 per user per month billed annually (€499 per user per year), €49.90 billed monthly. DATEV Rechnungswesen, Lohn and DMS are included, and so is Haufe, using your firm’s own Haufe access. No hardware, no activation fee, no per-file fee.

LUIGI’s price has three parts, all on the luigiai.de home page:

• A request pool for the firm: LUIGI S at €300, M at €600, XL at €1,000 a month, labelled “Richtwerte” (guide prices). The smallest package includes ”≈ 260–382 requests / month” for the whole firm. For a 10-person firm that is fewer than two requests per person per working day, at €0.79 to €1.15 each. amaiko Kanzlei bills per user, not per question.
• DATEV activation, one-off: “from €500” plus “€5 per 1,000 files”, so €3,000 at 500,000 DMS files.
• A monthly DATEV fee, “tiered by the size of your holdings”: €250 up to 500,000 files, €540 up to 1 million, €1,100 up to 2 million.

Two firms, calculated with LUIGI’s own price calculator at its default of 60 requests per person per month. That puts the request pool at €541 for 10 people and €1,074 for 25. The smaller firm holds 500,000 DMS files, the larger one 1 million, and the archive stays the same size for three years. All prices net, amaiko billed annually.

And that table assumes your archive stops growing. It won’t. At 2 million files LUIGI’s price list charges €1,100 a month for DATEV, and by LUIGI’s formula activating a stock that size costs €10,500. With amaiko Kanzlei a bigger archive changes nothing about the price. With LUIGI you pay for a copy of your archive to be kept, and the bigger your archive, the more that copy costs.

Read LUIGI’s price calculator carefully. Above the packages it says “Alle Mitarbeitenden inklusive” (all staff included). The calculator then asks, first of all, how many internal staff will use LUIGI, and prices the pool from that: €541 for 10 people, €1,252 for 30, €2,318 for 60. Above the €300 minimum, at the default of 60 requests per person, every extra person adds about €35.50 a month. It is called a pool, but the price grows per head. Underneath, it counts tokens: ”≈ 512 Mio.” (512 million) for 60 people, which the calculator converts into 4,414 to 6,481 requests. How many questions your team actually gets out of that depends on how many tokens LUIGI spends on each answer.

For 60 staff and 2.5 million DMS files the calculator shows “Monatlich 3.708 €” (€3,708 a month) and below it ”≈ 39 € pro Arbeitsplatz” (≈ €39 per seat). The €39 is the request pool alone: €2,318 divided by 60. With the DATEV fee from the same calculation it is €61.80 per seat, plus €13,000 activation, €57,496 in year one. amaiko Kanzlei costs the same firm €2,494.80 a month and €29,940 in year one. Under the file-count slider the calculator says it “treibt nur die einmalige Aktivierung” (only drives the one-off activation); in the calculation right next to it, that same slider moves the monthly DATEV fee from €250 to €1,390. Without the DATEV package, Microsoft 365 costs €20 a month extra. And is DATEV part of the Enterprise plan, as the FAQ on the same page says (“Die Anbindung ist Teil des Enterprise-Plans”, the connection is part of the Enterprise plan), or an add-on to any package, as the price list says? LUIGI’s home page gives both answers.

Where you work: Teams, not another window

amaiko Kanzlei runs in Microsoft Teams, in the same chat your firm already works in, and in the amaiko web app. It reads and drafts across the Microsoft 365 workday: email, calendar, files, Word, Excel and PowerPoint documents, Teams chats, OneNote, To Do and SharePoint lists. In the sealed edition Microsoft 365 stays read-only: amaiko drafts, your team sends. And amaiko remembers how each person works; in the Kanzlei edition that knowledge stays personal.

LUIGI is a separate web application. LUIGI’s price calculator lists Microsoft 365 as “Mails & Kalender als Datenquelle”, mail and calendar as a data source. For your team that means one more window next to DATEV, Outlook and Teams, and every question starts with switching to it.

The promise and the small print

• Cited correctly, but without warranty. LUIGI’s home page puts a check mark next to “Paragraf & Randnummer korrekt zitiert” (section and margin number cited correctly) and says other AI assistants “halluziniert” (hallucinate). LUIGI won’t stand behind it; its terms say: “KI-Antworten sind nicht fehlerfrei. Für die Richtigkeit, Vollständigkeit und Aktualität der von LUIGI AI erzeugten Antworten übernehmen wir keine Gewähr.” (AI answers are not error-free. We give no warranty for the accuracy, completeness and currency of the answers LUIGI AI generates.)
• The AI that knows your whole firm? That is what the home page says. In the contract, § 2 of the terms, LUIGI is “ein KI-gestützter Rechercheassistent für Steuerkanzleien” (an AI-assisted research assistant for tax firms).
• Which model answers? LUIGI’s compliance annex lists eight models from four makers. Before the search runs, GPT-4.1-mini rewrites your question. A reranker that reads at most 3,500 characters of each hit sorts the results. And when AWS Bedrock is unavailable, GPT-4o-mini in its July 2024 version writes the answer. amaiko Kanzlei answers with GPT-6.
• Today or someday? LUIGI lists its app with voice features as “In Entwicklung” (in development), workflows as “Pilot”, and capacity planning as “voraussichtlich Q4/2026” (expected Q4/2026). amaiko runs today in Teams, in the browser and as an app for iPhone and Android, with voice mode, and scheduled tasks run under the Kanzlei seal too.

Sealed, not just promised in a contract

amaiko Kanzlei is built for firms bound by § 203 StGB. Its data processing agreement carries the confidentiality clauses of § 203 StGB and § 62a StBerG. Beyond that, amaiko sets a Kanzlei seal when it provisions your workspace, in its infrastructure, not as an admin toggle, and your data protection officer can verify it. The seal enforces:

• Only allowlisted specialists: Microsoft 365 work, knowledge, data analysis, scheduler, DATEV and Haufe. Anything added to the platform later is sealed out automatically.
• Read-only Microsoft 365: amaiko reads and drafts; no write action reaches Microsoft 365.
• Personal knowledge only: nothing is shared across the firm.
• No background reading: no inbox triage, no onboarding scan, no contact enrichment. Briefings and reminders a person sets up still run.
• Content-free notifications: one fixed line per category; the content stays inside amaiko.
• Content-free traces and logs: agent traces carry no content and no error text; logs never carry prompts, responses or file names.
• No web research, no image generation.
• EU-only AI: Azure OpenAI with processing in the EU only, hosted in Germany on amaiko’s own infrastructure, not in the Microsoft cloud.

For § 203 StGB, LUIGI points to contracts: a data processing agreement template, a confidentiality undertaking under § 203 StGB and a client consent template under § 62a StBerG, available “auf Anfrage” (on request), says its security page. We requested them. Data is stored in Microsoft Azure, and the AI runs on AWS Bedrock and Azure OpenAI. For both, Annex C of the agreement template (as of 11 May 2026) carries the same line: “KEINE gesonderte Berufsgeheimnis-Zusatzvereinbarung”, no separate professional-secrecy agreement signed. LUIGI’s compliance annex calls one “nicht zwingend” (not mandatory), arguing that Microsoft’s staff fall under § 203 StGB as contributing persons anyway. § 62a(3) StBerG requires your firm to oblige its service provider to bind any further persons “in Textform zur Verschwiegenheit” (to secrecy, in text form). Whether LUIGI’s reading holds is something you, as the professional bound by secrecy, will have to defend. amaiko has signed Microsoft’s supplementary agreement for professional secrecy holders.

Three more passages from the same documents. On Microsoft and AWS, the compliance annex says access by US authorities is “auf das gesetzliche Mindestmaß begrenzt” (limited to the legal minimum): limited, not excluded, and that is where the copy of your DATEV holdings sits. § 13 of the agreement template has you consent today to the contract passing to a legal successor that takes over all obligations, and a special termination right “entsteht aus dem bloßen Umstand der Rechtsnachfolge nicht” (does not arise from the succession itself). And per Annex A, LUIGI appointed a data protection officer effective 1 July 2026.

The certificates from ISO 27001 to BSI C5 that LUIGI’s home page shows under “Zertifizierte Infrastruktur” (certified infrastructure) belong to Microsoft and AWS. The security page says so itself: “Diese Zertifikate testieren die Infrastruktur — nicht LUIGI selbst” (these certificates attest the infrastructure — not LUIGI itself). Per its privacy policy, LUIGI processes “Ihre Suchanfragen, Antworten der KI” (your queries, the AI’s answers) also “zur Bereitstellung und Verbesserung der Plattform” (to provide and improve the platform), and per the security page, analytics tracking is “jederzeit in den Konto-Einstellungen abschaltbar (Opt-out)” (can be switched off in the account settings at any time), while the privacy policy says: “Eine darüber hinausgehende Produktanalyse oder ein Tracking durch Dritt-Tools findet nicht statt.” (No further product analytics or tracking by third-party tools takes place.) amaiko Kanzlei keeps prompts and answers out of logs and telemetry. No contract changes the fact that the copy of your DATEV holdings sits in LUIGI’s databases.

Questions to ask LUIGI before you sign

Get the answers in writing. Ours is under each one.

1. Your security page names Werwolf GmbH as the operator of the DATEV mirror. What certifications does it hold, and who there has access to our client data? Your agreement template of 11 May 2026 already lists it as bound to secrecy under § 203 StGB; your compliance annex dates its signature to 10 June 2026. What applied in between? amaiko Kanzlei: There is no copy. DATEV operations go to DATEV, DMS traffic through Riecken, a question to Haufe when you use Haufe.
2. If we cancel, or take a client out: is the mirrored file deleted, at Werwolf GmbH too, by when, and do we get a deletion confirmation? Your security page says “innerhalb von 30 Tagen” (within 30 days) of closing the account. amaiko Kanzlei: amaiko keeps no mirror of your DATEV holdings, so there is no mirror to delete.
3. Your compliance annex names a “Daily-Mirror” and 24 to 48 hours before a deletion in DATEV reaches you. How old can the data behind an answer be? amaiko Kanzlei: amaiko asks DATEV at the moment of the question. There is no intermediate copy to go stale.
4. What do we pay in year one and year three at our archive size, with activation, the monthly DATEV fee and the request pool, what changes as the archive grows, and what does each person we hire add? amaiko Kanzlei: Users × €499, every year, whatever the size of the archive.
5. What access does the LUIGI Connect hardware have in our network, who owns it, and who maintains and updates it? amaiko Kanzlei: There is no hardware.
6. Annex C of your agreement template: no supplementary professional-secrecy agreement with Microsoft or AWS. How do we meet § 62a(3) StBerG, under which our service provider has to bind further persons to secrecy in text form? amaiko Kanzlei: Our data processing agreement carries the clauses of § 203 StGB and § 62a StBerG, we have signed Microsoft’s supplementary agreement for professional secrecy holders, and amaiko holds no copy of your DATEV holdings.
7. Why is GPT-4o-mini from July 2024 on your model list, and when does it answer instead of Claude? amaiko Kanzlei: GPT-6 on Azure OpenAI, processing in the EU only, hosted in Germany on amaiko’s own infrastructure.
8. How many firms run LUIGI in production today, and can we speak to one our size? amaiko Kanzlei: Ask us the same in the demo. You will see amaiko Kanzlei answer your own questions, with no archive to load first.
9. What happens to our data and the service if LUIGI AI GmbH stops operating or is sold? § 13 of your agreement template has us consent today to the transfer to a legal successor that takes over all obligations, with no special termination right because of the succession. amaiko Kanzlei: Your DATEV holdings stay in DATEV. There is no mirror anyone would have to retrieve or delete.
10. Do you need our clients’ consent under § 62a StBerG? Your blog says LUIGI works “mandantenübergreifend” (across clients); your security page supplies a ready-made consent template. amaiko Kanzlei: We won’t explain your professional law to you. You get a data processing agreement with the clauses of § 203 StGB and § 62a StBerG, and a seal your data protection officer can verify.
11. Your home page promises “Paragraf & Randnummer korrekt zitiert” (section and margin number cited correctly). Do you stand behind that, when your terms give “keine Gewähr” (no warranty) for the correctness of answers? amaiko Kanzlei: We don’t promise error-free AI, because there is none. The decision stays with you.

See it for yourself

Book a demo and ask amaiko Kanzlei the questions your firm asks every day. How the seal works in detail is on the amaiko Kanzlei page. And if SOFI AI is on your list too: amaiko vs SOFI AI.