Skip to content
caadoo
de

GoBD and AI chatbots: what applies when an assistant touches tax-relevant work

The GoBD never mention AI or chatbots, but they cover any assistant that receives, creates or passes on tax-relevant data in a German company. What you have to keep, how a posting stays traceable back to its source document, and what to set up before the assistant goes live.

By T. Krause9 min read

An AI chatbot or assistant falls under the GoBD as soon as it receives, creates, processes or passes on data that matters for tax. Typical cases are an assistant that reads incoming invoices and suggests the account, a website bot that takes orders, or one that sends letters about a deal. From then on it is treated like the rest of your accounting software. Its records are kept for the statutory period, every posting it touches can be traced back to the source document, changes are logged, and the procedure is documented. An assistant that only helps your people draft text or answer internal questions usually sits outside the GoBD.

The GoBD are a letter from the Federal Ministry of Finance dated 28 November 2019. Its paragraph 185 says the version of 14 July 2025 applies from that date. I read the text in the official AO handbook for 2026, and it doesn't use the words AI, artificial intelligence or chatbot anywhere. So what follows is my reading of the general rules. Check it with your tax adviser before you rely on it.

Photo: Unsplash

When an assistant becomes part of your bookkeeping system

The GoBD define the data processing system broadly. Paragraph 20 covers any hardware and software used to capture, create, receive, take over, process, store or transmit tax-relevant data and documents. It names subsidiary systems such as invoicing, merchandise management and document management alongside the general ledger, and it includes the interfaces between them. The same paragraph says it makes no difference whether the software runs on your own hardware or in a cloud.

What decides it, then, is what the assistant does with tax-relevant data. Three common set-ups:

UseCovered by the GoBD?
Internal assistant for drafts, summaries and questions about company knowledgeUsually not, as long as nothing it produces goes out as business correspondence or into the books
Assistant reads supplier invoices, suggests account and tax code, hands over to accountingYes, it works as a subsidiary system
Website chatbot takes orders or cancellationsYes, for the conversations that concern a transaction

The website case is covered in our GDPR test plan for chatbots, including how to separate business conversations from the rest. This article is mostly about the second case, the assistant inside the finance team.

Responsibility stays with your company either way. Under paragraph 21, the taxpayer alone is responsible for compliance, and that holds when tasks are outsourced to a third party. The model vendor doesn't take it over.

What you have to keep

Section 147(1) of the Fiscal Code (AO) lists, among other things, books and records with the working instructions and organisational documents needed to understand them, business letters received, copies of business letters sent, accounting vouchers, and other documents that matter for tax. Section 147(3) sets the periods: ten years for books and records, eight for accounting vouchers and six for the rest. Section 257 of the Commercial Code (HGB) sets the same periods for merchants. Under the fifth sentence of section 147(3), the Fiscal Code periods do not run out as far and as long as the documents matter for taxes whose assessment period has not expired.

For an AI assistant, this comes down to three things.

What goes in. An invoice that reaches the assistant by email is kept in the form it arrived in. Paragraph 119 says such documents may not be deleted before the retention period ends and must stay unchanged. Its example is exactly this one, an invoice received as a PDF by email.

What comes out. Anything the assistant sends as business correspondence is kept as a copy. Paragraph 5 says drafts that were never sent don't have to be kept. A chat history in which someone worked on a letter doesn't automatically belong in the archive.

The assistant's own rules. Section 147(1) no. 1 AO covers the working instructions and organisational documents needed to understand the books. I count the instructions an assistant posts by among them: the prompt, the rules and the model version. Without them, nobody can later explain why an invoice ended up on a particular account.

Traceable from the voucher to the posting and back

Paragraph 32 says the books must give an expert third party an overview within a reasonable time, and that every transaction must be traceable from start to finish. Paragraph 33 describes the audit trail in both directions, from the voucher to the tax return and back again.

An assistant adds a step to that trail. For it to hold, each posting has to show which document the suggestion came from, what the assistant suggested and who approved or changed it. Under paragraph 64 the link between an electronic document and its posting can be electronic, for example through a unique index.

Two rules govern changes. Section 146(4) AO prohibits changing a posting in a way that hides its original content. Paragraph 111 adds that for program-generated records, changes to the underlying generation and control data must also be recorded, in particular changes to the software's settings and parameters. In my reading, an edited instruction to the assistant is such a change. Keep the prompt and rules under version control like program code, with a date and a name on every change.

Controls and documentation

Paragraph 100 requires an internal control system: controls that are set up, carried out and logged. It names access rights, separation of duties and plausibility checks at data entry, among others. For an assistant, that means in practice that it gets only the rights it needs, it can't finalise postings itself, and a person approves what it proposes.

Paragraph 151 requires a procedure documentation (Verfahrensdokumentation) for every data processing system, showing its content, structure, sequence and results completely and coherently. Paragraph 154 adds that the documented procedure must match the one actually in use. When the vendor swaps the model or you change the rules, the documentation changes too. Our article on process documentation has a template for the structure.

Think about data access as well. Under section 147(6) AO, the tax office can require data to be handed over in a machine-readable format during a tax audit. A log you can only read in the vendor's web interface won't help much then.

What the GoBD don't reach

Not every use of AI touches the books. An assistant that helps your people write, searches manuals or summarises meetings usually neither receives nor creates tax-relevant documents. For its histories the main rule is the GDPR, which says not to keep personal data longer than necessary. What that means for ChatGPT and similar tools is in using ChatGPT in line with the GDPR.

The question to ask is whether the data matters for tax. Whether the software uses AI makes no difference to that. Write down where the line runs for your company in your AI usage policy, so your people know which assistant they may use for what.

What to set up before go-live

  • Decide which assistants touch tax-relevant data, and treat them as part of your data processing system.
  • Archive every input in its original form, unchangeable and indexed to the posting.
  • Log the suggestion, the approval and any change for each transaction, with time and person.
  • Version the prompt, the rules and the model version, and keep old versions as long as the postings they produced.
  • Don't give the assistant rights to finalise postings.
  • Add the assistant to your procedure documentation, and check it again whenever the model changes.
  • Confirm you can export logs and archive in a machine-readable format.

Where to start

Pick the assistant closest to your accounting and follow one posting from the voucher to the approval. Can you find the document, the suggestion and the name of the person who approved it within five minutes? If not, that's where to begin. This article summarises legal texts and isn't tax or legal advice.

caadoo is a monthly subscription, and how it works explains the setup. For an assistant in accounting, I set up the archive, the log and the versioning so the trail from voucher to posting holds, and I write the part of the procedure documentation that covers the assistant. The tax assessment stays with your tax adviser. Tell me which process you have in mind.

Frequently asked questions

Do the GoBD apply to AI chatbots?

The GoBD don't mention AI or chatbots. They do apply to any system that captures, creates, receives, processes, stores or transmits tax-relevant data (paragraph 20). A chatbot that does any of that is covered.

Do we have to keep chat histories with an AI assistant?

Yes, where they are documents that must be retained, such as business letters received or sent, or accounting vouchers under section 147(1) AO. An internal history in which someone drafts a text usually isn't one. Under paragraph 5, drafts that were never sent don't have to be kept.

Can an AI post entries on its own?

The GoBD don't forbid it in so many words. They do require traceability, logged changes and an internal control system with separation of duties. That's why I have the assistant propose and a person approve.

Who is responsible if the assistant codes an invoice wrongly?

Your company. Under paragraph 21, the taxpayer alone is responsible for compliance, including when tasks are outsourced.

Does the prompt belong in the procedure documentation?

The GoBD don't say so explicitly. Paragraph 111 does require changes to the control data and settings behind program-generated records to be recorded, and paragraph 151 asks for documentation that shows the content and sequence of the procedure. So I include the prompt, the rules and the model version.

Topics

  • GoBD
  • Chatbot
  • AI assistant
  • Accounting
  • German Mittelstand
All articles

Keep reading

  • 11 min read

    How to test a chatbot for GDPR compliance before launch

    A vendor's GDPR badge tells you about the product, not about your deployment. To test a chatbot, you try to break it with made-up customers and then act out what a real customer will one day ask of you: show me my data, then delete it. Here is a one-day test with a pass line for each step.

  • 13 min read

    Automate outgoing e-invoices before Germany's 2027 deadline

    German businesses with more than €800,000 in prior-year turnover must issue e-invoices to domestic business customers from 1 January 2027, and most others from 2028, though on the wording of the law a December 2026 supply billed in January 2027 can catch smaller firms too. A foreign parent doesn't change that. This piece covers who is caught, which file counts, and how to automate sending without letting a bad invoice out.

  • 11 min read

    How to automate quoting, and where a person still signs off

    Automated quoting rarely means one tool that does everything. It means price rules and templates in the CRM or ERP you already run, an AI draft where requests arrive as free text, and a named person who approves anything unusual before it reaches the customer. Here is how that splits across the quoting process.

End of call

You can hang up now.

Or book 15 minutes. I'll ask you the questions I'd ask on the phone, and tell you at the end whether it fits. If it doesn't, we've both lost a quarter of an hour instead of a month.

Or call. Cold, if you like. My AI assistant picks up and I call you back. +49 5136 9414999

Analytics

With your consent I use Google Analytics to see which pages get read. Without it, no analytics code loads. Your answer is stored locally in your browser.

Privacy notice