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 or documents from the DMS, answers the question, and keeps no mirror of your data. Payroll results and reports from Lohn follow after DATEV’s review of the interface. 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. 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”. LUIGI’s price calculator adds “Einmalig Daten laden, laufend nach Dateizahl”, load the data once, ongoing by file count. 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.

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.

Who LUIGI used for this is in the same documents. Annex C of the agreement template (template 2.0, as of 11 May 2026) lists Werwolf GmbH of Bad Wurzach as a subcontractor that reads the DATEV data through your firm’s DATEV Connect interface, and the compliance annex (version 2.5, as of 25 September 2026) names it as the operator of the “DATEV-Mirror-ETL”. LUIGI informed us on 10 November 2026 that it now runs the DATEV connection itself. Ask to see the current Annex C, and ask since when that has applied.

Your firm carries the risk: a continuously synchronised copy of your DATEV holdings sits outside your firm, 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 in the price calculator on the luigiai.de home page (as of 10 November 2026):

• A monthly budget for the firm: The calculator suggests €30 per employee, €15 from the 31st employee on, at least €300 a month. For firms with up to 10 staff there are two fixed packages: €149 for up to 3 staff, €199 for up to 10. The budget includes an allowance: at €300 about 259 to 380 requests a month, on the €199 fixed package about 172 to 253, each for the whole firm. For a 10-person firm on the fixed package that is about one request per person per working day, at €0.79 to €1.16 each. amaiko Kanzlei bills per user, not per question.
• Data transfer, one-off: a €500 base amount plus €5 per 1,000 files in DATEV DMS (€3 for the initial load of the semantic search, €2 for building the knowledge graph), so €3,000 at 500,000 files.
• A monthly DMS update, “ongoing by file count”: €0.50 per 1,000 files (€0.36 for the search, €0.14 for the knowledge graph), at least €99. That is €250 at 500,000 files, €500 at 1 million, €1,000 at 2 million.

Two firms, calculated with LUIGI’s own price calculator (as of 10 November 2026) and the budget it suggests: €300 for 10 people, €750 for 25. The smaller firm holds 500,000 DMS files, the larger one 1 million, each with semantic search and knowledge graph, and the archive stays the same size for three years. All prices net, for the whole firm, amaiko billed annually.

If the smaller firm takes the €199 fixed package instead of the suggested budget, it pays LUIGI €449 a month, €8,388 in year one and €19,164 over three years, and all 10 people share 172 to 253 requests a month. amaiko Kanzlei is cheaper even then.

And that table assumes your archive stops growing. It won’t. At 2 million files LUIGI’s price calculator charges €1,000 a month for the DMS update, and the data transfer for 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 it, it says “Ein Monatsbudget für die ganze Kanzlei” (one monthly budget for the whole firm). The calculator then asks how many staff will use LUIGI, and derives its suggested budget from that: €300 for 10 people, €900 for 30, €1,350 for 60. You can choose a smaller budget. The number of requests available to your firm each month then shrinks with it. Underneath, it counts tokens: how many questions your team can actually ask depends on how many tokens LUIGI spends on each answer.

For 60 staff and 2.5 million DMS files the calculator comes to €2,600 a month and €13,000 for the data transfer, €44,200 in year one. amaiko Kanzlei costs the same firm €2,494.80 a month and €29,940 in year one. Without the DATEV connection, Microsoft 365 costs €50 a month extra at LUIGI.

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, plus an Outlook add-in. LUIGI’s price calculator lists Microsoft 365 like this: “Mails und Termine Ihrer Postfächer als Quelle”, mail and appointments from your mailboxes as a source. LUIGI’s home page names no app for Microsoft Teams (as of 10 November 2026). For your team that means one more window next to DATEV and Teams.

The promise and the small print

• Verifiable, but without warranty. LUIGI’s home page advertises “Norm & Randnummer mit verlinkter Fundstelle” (provision and margin number with a linked source) and promises: “Jeder Pfad führt zu einer belegbaren Antwort.” (Every path leads to a verifiable answer.) 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? “LUIGI kennt jetzt Ihre ganze Kanzlei” (LUIGI now knows your whole firm), says the home page. 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 (version 2.5, as of 25 September 2026) 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 as the fallback for the answer if AWS Bedrock is unavailable, the annex lists GPT-4o-mini in its July 2024 version, with a share under 1%. LUIGI’s privacy policy names both routes for the models that answer your questions: Azure OpenAI and AWS Bedrock. amaiko Kanzlei answers with GPT-6.
• Today or someday? LUIGI’s roadmap lists the iPhone app as “Pilot”, and the same for agents, capacity planning and writing back to the DATEV DMS (as of 10 November 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, encrypted backups in the EU.

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 (template 2.0, as of 11 May 2026) 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). According to LUIGI’s statement of 10 November 2026, the current version allows extraordinary termination if the succession leads to material changes. And per Annex A, LUIGI appointed a data protection officer effective 1 July 2026.

The certificates that LUIGI’s home page shows under “Zertifizierte Infrastruktur” (certified infrastructure) belong to Microsoft and AWS. The security page says so itself: “LUIGI selbst ist nicht zertifiziert.” (LUIGI itself is not certified.) 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 compliance annex of 25 September 2026 names Werwolf GmbH as the operator of the “DATEV-Mirror-ETL”; by your own account, you now run the DATEV connection yourselves. Since when, who had access to our client data until then, and what has become of that access? Ask to see the current Annex C of the data processing agreement. 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, by when, and do we get a deletion confirmation? Your security page names eight weeks after the contract ends during which the content stays deactivated on your side. 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 the data transfer, the monthly DMS update and the monthly budget, how many requests does that include, 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. Your compliance annex of 25 September 2026 lists GPT-4o-mini from July 2024 as the fallback for the answer if AWS Bedrock is unavailable. Does that still apply, and which model answers then? 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 of 11 May 2026 has us consent today to the transfer to a legal successor that takes over all obligations, with no special termination right from the succession alone. Which “wesentlichen Änderungen” (material changes) entitle us to terminate under your current version? 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: “Jeder Pfad führt zu einer belegbaren Antwort.” (Every path leads to a verifiable answer.) 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.