Skip to content
Guide

AI in accounting: what it actually does today — and what it doesn't

AI in accounting gets talked about bigger at conferences than it plays out day to day. What actually runs today is specific: automatic invoice capture, posting suggestions, and categorizing bank transactions and open items by recognized pattern. What doesn’t run: an AI that books, values or signs off on a close by itself. This guide sorts out both sides soberly — including the legal line that applies to every machine-generated posting under German bookkeeping law.

The distinction that matters most upfront: AI in accounting automates capture and pattern recognition, not the decision. German bookkeeping law doesn’t distinguish between a posting suggestion created by hand or by a machine — the same standard applies either way.

What AI actually handles in accounting today

A large share of accounting work is repetitive and follows recognizable patterns — that’s exactly where AI has the biggest lever:

TaskWhat AI takes over
Invoice captureIncoming invoices get read automatically, instead of typing in the amount, date and vendor by hand.
Posting suggestionsBased on past, correctly posted entries, the system proposes an account — a suggestion, not a posting.
Transaction categorizationIncoming and outgoing payments get sorted into categories instead of being checked line by line.
Open-item matchingIncoming payments get matched to invoices even when the amount or reference is slightly off.
Flagging anomaliesDuplicate postings or outliers get flagged before they make it into the close.

The common thread: structured data exists in volume, and the pattern being automated is already known from the past. If your books run on DATEV (the accounting and payroll platform used by most German small and mid-sized companies) or a comparable system, that data foundation — open items, bank statements, posting history — is usually already there.

Where German bookkeeping law draws the line

German commercial and tax law sets the same bookkeeping standard (the GoB — Grundsätze ordnungsmäßiger Buchführung, the generally accepted bookkeeping principles that apply to every German company’s books) regardless of who or what produces the entry. Three rules matter most for AI in accounting:

  • Complete, accurate, timely and orderly. Postings and other required records must be made individually, completely, accurately, promptly and in an orderly manner (Section 146(1) AO, Germany’s General Fiscal Code) — whether the posting suggestion comes from a person or a machine makes no difference.
  • Immutability. A posting may not be altered in a way that makes the original content unrecoverable (Section 146(4) AO; Section 239(3) HGB, the Commercial Code). An AI suggestion that changes an existing posting has to keep the original content traceable.
  • Traceability for a third party. The books must give a knowledgeable third party an overview of the business’s transactions and financial position within a reasonable time, and transactions must be traceable in how they arose and were processed (Section 238(1) sentences 2 and 3 HGB).

Automated methods are explicitly permitted: commercial books may be kept on electronic media as long as the method used complies with the GoB (Section 239(4) sentence 1 HGB). So automation is allowed — it just isn’t exempt from those principles. The test for a machine-generated posting suggestion isn’t the model’s hit rate; it’s the same knowledgeable third party a hand-written entry has to satisfy.

What stays with people

That legal line directly implies which steps stay with the accounting team: anything that calls for professional judgment rather than pattern matching.

  • Posting in unclear cases. A posting suggestion is a suggestion — whether it’s substantively correct, especially for a new or unusual transaction, is still a human call.
  • Valuation. Whether a receivable is still collectible, an accrual is substantively right, or a document is missing is a judgment a pattern can’t replace.
  • Exceptions. Anything a rule can’t confidently match belongs on a visible exception list and gets decided — not quietly posted somewhere.
  • Sign-off. Approving a posting, a close, or the annual financial statements is a responsibility decision, not a calculation.

The same split — where automation fits and where professional review stays — shows up concretely in month-end close: which specific steps are a good fit and which aren’t is worked through step by step there. For a broader view of AI use cases across finance — beyond accounting, up to forecasting — see AI in finance.

Categorized transactions become a forecast

LiquidityLens takes care of categorization and matching from CSV, DATEV, or direct bank data and builds the rolling 13-week outlook from it — every number stays traceable back to the source data.

See the Liquidity Control Sprint

The next step: from accounting to cash flow forecasting

If you already use AI in accounting for categorization and matching, you’ve done the heaviest lifting a cash flow forecast needs: bank transactions and open items already exist in structured, current form. That same data is the foundation for a rolling 13-week outlook — no second data model required, just analysis of what accounting already produces.

To get a feel for how bank transactions turn into a cash flow view, try the free cash flow calculator. How AI goes further — forecasting incoming payments and flagging a shortfall early — is covered in the guide to AI-powered cash flow forecasting.

Where to start

The practical entry point isn’t the hardest task — it’s the one with the best ratio of benefit to effort, usually transaction categorization, because the data already exists and the result is easy to check immediately. Two things need to be settled first: a documented chart of accounts with posting rules, so the system has a consistent pattern to learn from, and an exception list for anything a rule can’t confidently match. Skip that groundwork and the effort just shifts from data entry to correction instead of disappearing.

Free Excel template: 13-week cash flow forecast

A weekly grid with receipts and payments and an automatic low-point warning — a solid starting point before you automate.

Get the free template

Frequently asked questions

The most important questions on AI in accounting are gathered at the end of this page.

Frequently asked questions

What does AI actually do in accounting today?
Mostly invoice capture (reading and extracting data from incoming invoices automatically), posting suggestions, and categorizing bank transactions and open items by recognized pattern. It also flags anomalies such as duplicate postings or outliers. The professional review and the decision stay with the accounting team.
Is AI-assisted bookkeeping compliant with German accounting law?
Automated methods are explicitly allowed: commercial books may be kept on electronic media as long as the method used complies with the GoB (Grundsätze ordnungsmäßiger Buchführung, Germany's generally accepted bookkeeping principles), per Section 239(4) HGB (the Commercial Code). That permission does not exempt automation from those principles, though: every posting must stay complete, accurate, timely and orderly (Section 146(1) AO, the General Fiscal Code) and traceable in how it arose and was processed (Section 238(1) HGB). How that plays out in your specific software is a question for your tax advisor or auditor.
Does AI replace the bookkeeper or the tax advisor?
No. AI takes over recurring capture and pattern matching, not professional judgment. Whether a posting is substantively correct, an accrual fits, or a document is missing is still a human call — as is sign-off on the close.