AI in accounting: the draft yes, the posting no

A lot gets promised about AI in accounting and very little gets said about what actually happens. The sentence “the AI does your bookkeeping” is not only advertising, it is also the wrong description: a machine does not post, because posting is the moment after which nothing may be changed any more. Everything before that, though, it can take over, and that is where most of the work is.

The entry, written from one sentence

You write what happened. “Fuel for the company car, 87.40 euro gross, paid in cash, yesterday.” Back comes the finished double entry: debit, credit, VAT split out, date.

Two things about it matter more than the trick itself.

First, the AI sees only your chart of accounts. Not SKR03 as a generic template, but the accounts that actually exist and are active in your company. A proposal on an account you do not have is not a proposal, it is an error somebody has to clean up by hand.

Second, it sees the last fifteen posted entries. That is the difference between an entry that is formally correct and one that looks like your business: if fuel has gone to one particular account for two years, it should not suddenly land somewhere else today. Booking the same case the same way is not fussiness, it is the condition for your year-end figures to mean anything.

The receipt from your phone

The second route starts with a photo. Upload an image or a PDF, text recognition works in four languages, and from it the AI reads the date, the vendor, the amount, the tax amount and rate, the currency, the document number and the individual lines. The document number is searched for deliberately, under every name it carries on European receipts: Rechnungsnummer, Beleg-Nr., fattura n., invoice no.

Then comes the proposal for the accounts, again only from your chart. You check it, change what needs changing, and confirm. From then on the receipt hangs on the entry, not in a folder where nobody finds it when it matters.

What does not add up, before your accountant sees it

Four things are flagged without anyone having to look for them:

• Duplicate entries: same date, same amount, same text. The classic after an import.
• Amounts out of line: not “large”, but large compared with what usually happens on that account.
• Payments left open although the money arrived long ago.
• Entries without a tax key, the ones that go missing from the VAT return later.

One detail that is not a detail: the message is written in the language of your company, not the language of the software. Before, a German business got English warnings, because nobody had told the model which language to answer in. Warnings like that do not get read, and a warning nobody reads is not one.

The bank statement: a proposal, not automation

On bank reconciliation the AI says which payment belongs to which journal line. It says it as a proposal. The matching, with one click, is done by a person.

That is a deliberate boundary. A wrongly matched payment does not show: the total is right, the account is right, only the customer’s open item is the wrong one. You notice it three weeks later, through a reminder going out to somebody who had already paid.

Cash: why the forecast starts from the bank balance

The forecast runs from 30 to 365 days and starts from the bank balance. That is a correction a test company taught us: before, the starting point was “bank plus all open receivables”, and the first column jumped from 491,000 to 1,637,000 euro within a month, as if every open invoice were collected immediately. A number that looks too good gets believed, and decisions get built on top of it.

With at least three months of bank statements, the forecast computes on real payments. Without them, it computes on revenue and costs and states which of the two bases it used. A forecast that does not tell you what it rests on is not a forecast, it is an opinion.

The boundary, and why it is written into the law

Everything described above ends at the same point: the word “posted”. On posting, the database hands out a running number with no gaps, and from then on header and lines are immutable. No editing, no deleting, a reversal only. That is what § 146 AO requires, and the rule sits in the database, not in the screen.

That is why the AI produces drafts. Not out of caution, but because a draft is the only thing that can still be corrected. Anyone wanting to automate the posting itself would have to remove the very part that makes bookkeeping auditable.

What else the module computes, from the chart of accounts through the VAT return to the DATEV batch for your accountant, is on the accounting page.