Are tax advisers allowed to use AI tools at all?

The question is not whether, but how: where the data is processed, whether it is used to train third-party models and whether professional secrecy is preserved. Public chatbots into which staff type client information are hard to square with this. A knowledge base with data held in the EU, no training on your documents and clear access rights is a different matter – but each firm has to make the detailed assessment itself.

What should go into a tax advisory firm’s knowledge base?

Start with the firm’s internal knowledge: work guidelines, checklists for annual accounts and tax returns, templates and standard wording, instructions for the firm’s software and portals, and documented solutions to recurring special cases. None of this contains client data, and all of it is useful from day one. Client files and accounting data stay in the practice management software.

Does client data stay in the practice management software?

Yes. The practice management software remains the system of record for accounting, deadlines, client document filing and time recording. The knowledge base answers how the firm works – not what was posted for a particular client. Many firms deliberately start with internal knowledge only, with no link to client data.

Are the firm’s documents used for AI training?

Not with a properly set-up knowledge base: the documents are used only to answer questions from the firm’s own staff and are not used to train third-party AI models. The data is also held on servers in the EU. A firm should get both guarantees in writing before deciding.

How does a knowledge base help with onboarding new staff?

New trainee tax advisers and clerks ask the same questions for weeks: how do we set up clients, which checklist applies, what is our standard procedure? If the answers are documented and can be found simply by asking, experienced colleagues get noticeably more time back. Onboarding then depends less on who happens to be free to answer questions.

AI knowledge base for tax advisory firms: a practical guide

An AI knowledge base is most useful to a tax advisory firm when it starts with the firm’s internal knowledge: staff ask a question in plain language and find the relevant work guideline, checklist, template or documented special case – with a link to the original document. Client data and accounting stay in the practice management software; the knowledge base explains how the firm works. For professionals bound by secrecy, the architecture is what counts: data held in the EU, no third-party AI training on the documents, and clear access rights.

In brief

The best way for tax advisers to start with AI is the firm’s internal knowledge – standards, checklists, instructions – not the client file.
Firms rely on a huge amount of process knowledge held by a handful of people; when an experienced employee resigns or retires, it goes with them.
An AI knowledge base answers questions from your own documents and always names the source, so every answer can be checked.
Professional secrecy and data protection call for data held in the EU, no third-party training and role-based access – the minimum standard for any AI in a firm.
The practice management software remains the system of record for accounting, deadlines and client files; the knowledge base adds the how.

Why is internal knowledge the best place for a firm to start with AI?

Because that is where the bottleneck lies. Tax advisory firms are well served when it comes to technical research – specialist databases, commentaries, seminars. What is rarely written down is how your own firm works. Which checklist do we follow to complete annual accounts? How do we set up a new payroll client? Which standard wording do we use to request a deadline extension? The answers sit in the heads of a few experienced employees and in scattered Word files.

This gets expensive in two places. The first is onboarding: new trainee tax advisers and clerks take up experienced colleagues’ time for months, because every process question is answered in person. The second is when people leave: when the long-serving payroll accountant leaves the firm, she takes with her the countless special cases she has solved over the years – from partial retirement to cross-border employment.

There is a third argument for starting here: internal firm knowledge contains no client data. The firm can gain experience with AI search without touching sensitive data, and tackle the trickier client-related questions later, on a secure footing.

What knowledge does a tax advisory firm hold?

Knowledge area	Typical content	Everyday benefit
Firm standards and work guidelines	Procedures for annual accounts, payroll, processing receipts	Consistent quality across all staff
Checklists	Annual accounts, tax returns, client onboarding	Nothing gets forgotten, even under deadline pressure
Templates and standard wording	Letters to authorities, client letters, fee agreements	Faster, more consistent correspondence
Software and portal instructions	Practice management software, FinanzOnline (the Austrian tax authority’s online portal), public authority portals	Fewer questions about routine tasks
Documented special cases	Solved special cases from payroll and annual accounts	Each special case only has to be worked out once
Onboarding documents	Induction plans, internal responsibilities, firm A–Z	New staff get up to speed faster

What these have in common: they are instructions, standards and documented experience – not receipts. A receipt belongs in the client’s accounts; the work instruction on how the firm handles that type of receipt belongs in the knowledge base.

What questions does the team ask day to day?

You can see the benefit in the questions that are currently shouted across the office or emailed to the same colleagues over and over again:

“Which checklist applies to this year’s annual accounts for a GmbH (limited company), and what has changed since last year?”
“How do we set up a new payroll client – from the power of attorney to the registration?”
“Do we have an internal work instruction on company cars in payroll?”
“Where is our standard wording for requesting a deadline extension, and who signs it off?”

The AI answers questions like these from the firm’s documents and cites the source; one click opens the original. That matters particularly in tax work: an AI can get things wrong, and an answer can only be relied on once the underlying guideline has been checked. So the knowledge base replaces neither the specialist database nor professional judgement – it makes the firm’s own know-how easy to find. The junova product overview shows how this works technically and what role and permission set-ups are possible.

What do professional secrecy and data protection mean for your choice?

Tax advisers are bound by a strict duty of confidentiality – and that sets the boundaries for every AI tool in the firm. From a firm’s point of view, three criteria are the minimum:

First, where the data is stored: documents should be processed and stored on servers in the EU, under a data processing agreement (DPA). Second, no training: the firm’s documents must not be used to train third-party AI models, and this should be guaranteed in the contract. Third, access control: role-based permissions must reflect the fact that not every employee may see everything, from fee calculations to partner matters.

The contrast with a free chatbot is stark: if there is no internal solution, staff type questions and their context into public AI tools, and information leaves the firm unchecked. A dedicated knowledge base with clearly defined data storage also tackles this shadow IT problem: it gives the team the convenience of AI search on terms the firm controls.

How does the practice management software stay the system of record?

The division of labour is the same as between an ERP system and a knowledge base in any other business: the practice management software knows what has been done – the knowledge base knows how it is done. Accounting, deadline management, client document filing, time recording and fee notes stay in the practice management software; that is what it is built for, and that does not change.

The knowledge base sits alongside it, holding the processes, standards and experience that appear in no client file. It does not answer “What was posted for client Meier?”, but “What is our standard way of handling this, and where is it written down?”

How should a firm introduce the knowledge base in practice?

A four-step start has proven effective: first, the firm collects the questions the team actually asks day to day over two weeks. Next, it defines the structure and access rights – split by specialist area, management level and administration. Then the initial material goes in: checklists, guidelines, templates and software instructions, all with no link to client data. Finally, two or three employees check the answers against the source documents before the whole firm gets access.

The guide AI knowledge base in your company describes the general, cross-industry basis for these steps. One point is specific to firms: a works council is not the issue here, but the firm’s own governance is – who approves content, who keeps it up to date, and who decides on later expansion.

Your next step: see how the introduction works step by step – from the intro call and the permissions structure to a test with your own firm standards. A firm that already has its checklists and guidelines in order can usually tell within a few weeks whether AI search lightens the day-to-day workload.