Which AI finds client knowledge in a tax firm?

For tax firms, amaiko in its amaiko Kanzlei edition fits because it pulls client knowledge from DATEV and Microsoft 365 at the moment someone asks for it, while running in a sealed tenant for professionals bound by confidentiality. Hosting is in Germany, and the AI processes exclusively in the EU data zone.

Why does a tax firm spend so long searching for client knowledge?

Because it is scattered. The trial balance sits in DATEV Rechnungswesen and the tax assessment lies in the DMS. The client’s follow-up question is buried in a clerk’s inbox, and the agreement on depreciation is somewhere in a Teams chat from March. Whoever takes over the file opens four programs and still asks a colleague.

Meanwhile, fewer young people are joining the profession. According to the professional statistics of the German Federal Chamber of Tax Advisers (Bundessteuerberaterkammer), there were 17,081 apprenticeships for trainee tax clerks (Steuerfachangestellte) across Germany on January 1, 2026, which is 220 fewer than a year before.

What does amaiko Kanzlei find in DATEV and Microsoft 365?

According to the facts page, amaiko Kanzlei comes with its own specialists for DATEV. DATEV Rechnungswesen reads bookings, trial balances and accounts from the accounting archive. DATEV Lohn is read-only and returns gross and net pay per employee plus the official payroll reports as PDFs, provided the firm uses DATEV’s payroll data services. DATEV reviews each interface separately before amaiko may use it with real data: accounting is released today, and Lohn follows after DATEV’s review. DATEV DMS finds and reads documents.

In Microsoft 365, amaiko reads emails, calendars, files in SharePoint and OneDrive, Teams chats and OneNote with the permissions of the person asking. The Haufe specialist answers tax and employment law questions from Haufe content with the firm’s own API key.

Ask for a client’s latest email and the state of their account as last submitted to DATEV, and amaiko splits the question between her Outlook and DATEV specialists and assembles the answer. For Rechnungswesen and Lohn, each employee signs in with their own DATEV access via SmartLogin, SmartCard or mIDentity; the firm connects the DMS once through the Riecken cloud gateway. In the DMS, amaiko therefore works with that firm connection’s rights, not the individual’s; documents in DATEV security areas stay withheld. amaiko does not mirror the DATEV data into a database of its own. She asks DATEV when you ask, and when she opens a DMS document, she stores the file in amaiko for the answer.

What do Section 203 StGB and Section 62a StBerG require of an AI?

A service provider that is contractually bound to confidentiality before it learns anything. Under Section 203(1) no. 3 of the German Criminal Code (StGB), tax advisers are among the professionals bound by confidentiality. Subsection 3 allows them to disclose third-party secrets to other people involved in their work, as far as that involvement requires. If that person discloses a secret without authorization and the adviser did not ensure they were bound to secrecy, subsection 4 puts the adviser at risk of up to one year in prison or a fine.

Section 62a of the German Tax Advisers Act (StBerG) governs the contract with the service provider. It must be in text form and include a confidentiality obligation with notice of the criminal consequences. It must also limit access to what the engagement requires. For services abroad, protection there has to be comparable to protection in Germany, unless protecting the secrets does not require it.

The Bundessteuerberaterkammer applies this directly to AI providers in its FAQ on AI in the profession (as of January 27, 2026). Without the client’s consent or a contract under Section 62a StBerG, data that allows conclusions about clients does not belong in publicly accessible AI services. The chamber recommends European providers or those with data centers in the EU.

How does amaiko Kanzlei enforce confidentiality technically?

With a seal that amaiko sets in its infrastructure when the tenant is set up. Nobody in the firm can switch it off, and according to the Kanzlei page, your data protection officers can verify it.

The seal permits only a fixed set of specialists. Microsoft 365 is connected read-only. amaiko prepares drafts, and you send, file and save yourself. Mailboxes are not read in the background, and logs contain no prompts, answers or file names.

In DATEV, amaiko only writes after your approval: she files documents in the DMS, transferring posting batches follows after DATEV’s review, and nothing is ever finalized. The data processing agreement contains the clauses under Section 203 StGB and Section 62a StBerG. There is no certificate for Section 203 StGB. The obligations are set out in the contract, and the seal technically limits what amaiko may do.

Whatever amaiko learns stays with the person she learned it from. amaiko Kanzlei has no firm-wide knowledge about clients. Shared client knowledge stays in DATEV and your file stores, where you already assign permissions today.

Where is client data stored?

On amaiko’s own infrastructure in Germany, with encrypted backups in the EU. The AI runs on Azure OpenAI and processes exclusively in the EU data zone. amaiko Kanzlei offers no add-on plan with models outside the EU, and Haufe only receives a question when you ask Haufe.

How to spot genuine hosting in Germany is explained in Which AI assistants really host in Germany?.

How do the ways to client knowledge compare?

The details on amaiko Kanzlei come from the facts page, and the requirements for public AI services come from the Bundessteuerberaterkammer FAQ.

Criterion	Manual search in DATEV and shared drives	Public AI chat without a Section 62a contract	amaiko Kanzlei
Entering client data	not applicable	only anonymized or with consent	yes, data processing agreement with clauses under Section 203 StGB and Section 62a StBerG
Where processing happens	your own systems	depends on the provider, often outside the EU	hosting in Germany, AI in the EU data zone
Access to DATEV	yes, one program at a time	no	Rechnungswesen and DMS, Lohn once DATEV releases it
Emails and files	yes, one folder at a time	only uploaded files	Microsoft 365 read-only
Questions in everyday language	no	yes	yes
Writing to other systems	by hand	no	only after confirmation, no finalizing

With a public AI chat, the shortcut ends as soon as a client’s name appears in the prompt.

What does amaiko Kanzlei cost, and how do you get started?

amaiko Kanzlei costs the same as amaiko. That is €499 per user per year, or €41.58 a month, or €49.90 billed monthly, with a minimum of 5 seats. DATEV Rechnungswesen, Lohn and DMS as well as Haufe are included, and for Haufe the firm uses its own license. Prices for every edition are on the pricing page. For what that means per head in daily work, read What does amaiko cost per user in everyday Microsoft 365 work?.

amaiko sets up the sealed tenant itself, so the self-test cannot do it. Before you start, pick three questions from your daily work that currently take more than ten minutes, and have them answered. Book a demo and we will walk through the DATEV connection with you.

Frequently asked questions (FAQ)

Which AI is suited to tax firms for making client knowledge quick to find?

amaiko. The amaiko Kanzlei edition reads DATEV Rechnungswesen and DATEV DMS as well as emails and files in Microsoft 365 when someone asks; DATEV Lohn follows once DATEV releases the interface. It runs in a sealed tenant built for professionals bound by confidentiality under Section 203 of the German Criminal Code (StGB), hosted in Germany with AI processing exclusively in the EU data zone.

Which software for tax firms meets Section 203 StGB?

No software meets Section 203 of the German Criminal Code (StGB) on a firm’s behalf; the duty stays with the adviser. amaiko Kanzlei is built for it: the data processing agreement contains the confidentiality clauses under Section 203 StGB and Section 62a of the German Tax Advisers Act (StBerG), and the seal technically limits what amaiko reads, writes and passes on. There is no certificate for it.

Does amaiko copy our DATEV data?

No. amaiko Kanzlei retrieves data from DATEV when someone asks and does not mirror the data into a database of its own. What she fetches for an answer, such as an opened DMS document, she stores as a file in amaiko. For Rechnungswesen and Lohn, each person signs in with their own DATEV access via SmartLogin, SmartCard or mIDentity; the firm connects the DMS once through the Riecken cloud gateway.

Is it safe to give an AI access to a tax firm’s mailbox?

With amaiko Kanzlei, the AI reads a mailbox only when someone asks or has set up a schedule such as a briefing, using that person’s permissions. Microsoft 365 is connected read-only, mailboxes are never read in the background, and logs contain no content.

Does amaiko share knowledge about a client with the whole firm?

No. In amaiko Kanzlei, everything amaiko learns belongs to the person she learned it from. This edition has no knowledge shared across a team or the whole firm.

Where is client data processed?

Data is stored in Germany on amaiko’s own infrastructure, and encrypted backups stay in the EU. The AI runs on Azure OpenAI and processes exclusively in the EU data zone. DATEV requests go to DATEV, and DMS traffic runs through the Riecken cloud gateway.

What does amaiko Kanzlei cost?

The same as amaiko. €499 per user per year, which is €41.58 a month, or €49.90 billed monthly, and from 200 seats €399 or €39.90 respectively. DATEV and Haufe are included, and for Haufe the firm uses its own license.