Skip to content
K W
GoBD-compliant §203 StGB-compliant Q3

Tax Audit Preparation Agent

Prepare for tax audit - compile data, identify risk areas, answer auditor questions.

Analyses the audit order, compiles relevant data in IDEA format, identifies risk areas, prepares draft answers for auditor questions and estimates provision requirements.

Score Dashboard

Agent Readiness 56-63%
Governance Complexity 44-51%
Economic Impact 68-75%
Lighthouse Effect 36-43%
Implementation Complexity 46-53%
Transaction Volume Episodic

What This Agent Does

A tax audit takes on average 6-8 weeks. The biggest time drain is not the audit itself but the preparation: compiling data, analysing the audit order, identifying risk areas, drafting answers to auditor questions. In many companies, a tax audit ties up one clerk for weeks.

The Decision Layer turns tax audit preparation into a structured process. The agent analyses the audit order and identifies the audit period and relevant tax types. Data is exported in IDEA format, Z1/Z2/Z3 access prepared. Risk areas are proactively identified - where might auditors probe deeper? Draft answers are prepared; the final argumentation strategy stays with the tax advisor.

The result: tax audit in 2 weeks instead of 8. All data available on day one. Risk areas identified and answers prepared. The tax advisor can focus on argumentation instead of data searches.

Micro-Decision Table

Human
Rules Engine
AI Agent
Each row is a decision. Expand to see the decision record and whether it can be challenged.
Analyse audit order Which period and which tax types are being audited? AI Agent

LLM interpretation of the audit decree

Decision Record

Model version and confidence score
Input data and classification result
Decision rationale (explainability)
Audit trail with full traceability

Challengeable: Yes - fully documented, reviewable by humans, objection via formal process.

Compile relevant data Which data is needed for the audit period? Rules Engine

Database query by period and tax type

Decision Record

Rule ID and version number
Input data that triggered the rule
Calculation result and applied formula

Challengeable: Yes - rule application verifiable. Objection possible for incorrect data or wrong rule version.

Export IDEA format Is data provided in the correct GDPdU/IDEA format? Rules Engine

Format standard for tax auditor access

Decision Record

Rule ID and version number
Input data that triggered the rule
Calculation result and applied formula

Challengeable: Yes - rule application verifiable. Objection possible for incorrect data or wrong rule version.

Prepare Z1/Z2/Z3 access Are all three access paths set up for the auditor? Rules Engine

Technical preparation of access paths

Decision Record

Rule ID and version number
Input data that triggered the rule
Calculation result and applied formula

Challengeable: Yes - rule application verifiable. Objection possible for incorrect data or wrong rule version.

Identify risk areas Where might auditors probe deeper? AI Agent Auditor

Historical audit patterns and industry knowledge

Decision Record

Model version and confidence score
Input data and classification result
Decision rationale (explainability)
Audit trail with full traceability

Challengeable: Yes - fully documented, reviewable by humans, objection via formal process.

Challengeable by: Auditor

Interpret auditor questions What exactly does this auditor question mean? AI Agent

LLM interpretation of the question in a tax context

Decision Record

Model version and confidence score
Input data and classification result
Decision rationale (explainability)
Audit trail with full traceability

Challengeable: Yes - fully documented, reviewable by humans, objection via formal process.

Prepare draft answers How should the auditor question be answered? Human Auditor

Argumentation strategy requires tax expertise

Decision Record

Decider ID and role
Decision rationale
Timestamp and context

Challengeable: Yes - via manager, works council, or formal objection process.

Challengeable by: Auditor

Prepare procedural documentation Is the procedural documentation prepared for the auditor? Rules Engine

Existing documentation = R, auditor-ready preparation = A

Decision Record

Rule ID and version number
Input data that triggered the rule
Calculation result and applied formula

Challengeable: Yes - rule application verifiable. Objection possible for incorrect data or wrong rule version.

Tax structuring risk assessment Are there tax structures the auditor might question? Human Auditor

Strategic risk assessment by tax advisor

Decision Record

Decider ID and role
Decision rationale
Timestamp and context

Challengeable: Yes - via manager, works council, or formal objection process.

Challengeable by: Auditor

Estimate provision requirement Must a provision be formed for potential tax back-payments? Human Auditor

Judgement in assessing back-payment risk

Decision Record

Decider ID and role
Decision rationale
Timestamp and context

Challengeable: Yes - via manager, works council, or formal objection process.

Challengeable by: Auditor

Decision Record and Right to Challenge

Every decision this agent makes or prepares is documented in a complete decision record. Affected parties (employees, suppliers, auditors) can review, understand, and challenge every individual decision.

Which rule in which version was applied?
What data was the decision based on?
Who (human, rules engine, or AI) decided - and why?
How can the affected person file an objection?
How the Decision Layer enforces this architecturally →

Prerequisites

  • Complete ERP data archive for the audit period
  • IDEA/GDPdU export functionality
  • Access to prior tax audit reports as pattern basis
  • Current procedural documentation of all tax-relevant processes

Governance Notes

GoBD-compliant §203 StGB-compliant

The tax audit is conducted per AO Paragraph 193 ff. The auditor has the right to Z1 access (direct data access), Z2 access (indirect access via evaluations) and Z3 access (data carrier provision in IDEA format). Missing or incomplete data can lead to estimation of the tax base.

The procedural documentation per GoBD is the most frequent point of objection. The Decision Layer generates this documentation automatically - it is not a retrospective document but technical proof of how every decision was made. Paragraph 203 StGB is particularly relevant for client support by tax advisors.

§203 StGB-relevant data is encrypted end-to-end and never passed to AI models in plain text.

Process Documentation Contribution

The Tax Audit Preparation Agent documents for the GoBD procedural documentation: which data was compiled for the auditor, which risk areas were identified, which auditor questions were received and how they were answered. This documentation itself becomes part of the audit file.

Infrastructure Contribution

The Tax Audit Preparation Agent uses the infrastructure of all other Finance agents: the GoBD-compliant archiving of the GoBD Compliance Agent, the posting data of the GL agents, the tax calculations of the VAT and Payroll Tax agents. It is the ultimate proof that the agent infrastructure works: when the tax audit runs smoothly, the Decision Layer has proven its value.

Builds Decision Logging and Audit Trail used by the Decision Layer for traceability and challengeability of every decision.

Does this agent fit your process?

We analyse your specific finance process and show how this agent fits into your system landscape. 30 minutes, no preparation needed.

Analyse your process

Frequently Asked Questions

Can the agent conduct or represent in the tax audit itself?

No. The agent prepares the audit and supports during the audit with data requests. The argumentation with the auditor, negotiation and legal remedy decisions remain with the tax advisor.

How does the agent identify risk areas?

The agent analyses frequent audit focus areas (entertainment receipts, transfer prices, VAT assignments), compares with industry-standard metrics and reviews prior audit reports for recurring objections.

What does a poorly prepared tax audit cost?

Beyond the direct staff time, missing data or incomplete procedural documentation often leads to estimations by the tax office - typically well above the actual values. Good preparation is an investment that pays for itself many times over.

What Happens Next?

1

30 minutes

Initial call

We analyse your process and identify the optimal starting point.

2

1 week

Discover

Mapping your decision logic. Rule sets documented, Decision Layer designed.

3

3-4 weeks

Build

Production agent in your infrastructure. Governance, audit trail, cert-ready from day 1.

4

12-18 months

Self-sufficient

Full access to source code, prompts and rule versions. No vendor lock-in.

Implement This Agent?

We assess your finance process landscape and show how this agent fits your infrastructure.