AI bookkeeping in Germany
AI bookkeeping software for German companies: full double-entry books, with the AI doing the legwork
"AI bookkeeping" is used for very different things. In this software it means a complete double-entry ledger on the German SKR03 or SKR04 charts of accounts, in which the AI reads receipts, proposes account and VAT code, matches bank transactions to open items and posts on its own once it is sure. You review exceptions, lock months under GoBD and get the advance VAT return, trial balance, HGB annual accounts and tax returns from the same data set. This page explains the mechanics, the limits of the automation, GoBD compliance and pricing for foreign owners and English-speaking finance teams.
Last reviewed: 2026-09-15
What AI bookkeeping means here, and what it does not
Many products call themselves AI bookkeeping because they read receipts with text recognition and write the amounts into a list. The actual bookkeeping — debit and credit, journal, account ledgers, open items, VAT, period locking — then happens elsewhere, usually at the tax adviser's office. In the narrow sense used here, AI bookkeeping means that the double-entry ledger runs in the same system and the AI works exactly where a person used to sort receipts, code accounts and match payments.
Three properties separate this from a receipt archive. First, every business transaction is a complete posting with account, contra account, VAT code and receipt; the trial balance (Summen- und Saldenliste) is derived from it, not estimated. Second, every posting is chained immutably under the German GoBD rules and periods are locked to the day. Third, the advance VAT return, management report figures, HGB annual accounts, E-Bilanz and corporate and trade tax returns all read the same ledger — no export, no second data entry.
The AI is one of four decision sources, and deliberately the last one. Before it come your own posting rules, the business partner with its confirmed history and a coding lexicon of typical transactions. That order is not distrust of the model: a rule and a history can be shown to a German tax auditor, a model probability cannot.
The path of a receipt: six stations
1. Intake
Receipts arrive by upload, phone photo, the company's own e-mail inbox, a cloud folder, e-invoice (XRechnung, ZUGFeRD) or connected systems. Forwarded e-mails are unwrapped. Logos, signature images and newsletters are recognised before saving and never become receipts.
2. Recognition
A PDF with a text layer is read as text; only scans and photos go through image recognition. Supplier, date, invoice number, net, VAT rate, gross and payment term are checked against the source text; a total that does not match the line items gets a flag instead of a silent correction. Byte-identical duplicates are not stored.
3. Proposal
Account, contra account, VAT code and cost centre come from the fixed order rule, partner, lexicon, AI. The company profile — industry, customers, staff, vehicles, premises — is context for the AI, never the decision. Every proposal carries its source and its confidence.
4. Review
Split screen: original receipt on the left, posting proposal with line items on the right. Confirm, change or split; a correction is remembered and applied to the next receipt from the same partner. From 85 % confidence the automation posts on its own, with the exceptions listed below.
5. Posting
Purchase invoices post expense and input VAT against the creditor and open the payable; sales invoices post the receivable, revenue and output VAT. The bank line later clears the open item — it never posts to the profit and loss account itself.
6. Locking
Periods are locked to the day; afterwards only reversal and correction entries are possible. Who posted, changed or reversed what and when is in the audit log.
Bank transactions: matching, not coding
A bank transaction is not an invoice. Posting it straight to an expense or revenue account produces the same transaction twice in the income statement as soon as the receipt is posted too. The rule is therefore fixed: expense and revenue arise with the document (expense to creditor, debtor to revenue); the cash movement afterwards only moves the balance sheet (creditor to bank, bank to debtor). For every bank line the AI first looks for the open item it settles — invoice number in the payment reference, amount, and a due-date window that follows the payment term rather than the invoice date.
If none is found, the line is parked on a creditor or debtor account and waits for its document. Three card charges spread over a month and one consolidated invoice at month end are brought together in the partner file, with a proposal and a plain-language reason. Deliberate exceptions: fees of payment providers (no invoice ever comes; the statement is the document), advance payments (VAT arises on receipt under § 13 UStG) and cash-basis accounting, where the cash flow itself is the point of recognition.
Payment providers state what each line is — payout, fee, customer payment, refund. Those facts are read rather than guessed from the reference: a payout is cash in transit, a fee is a bank charge, a customer payment clears a receivable. An identical amount on the same day is no proof of a transfer between own accounts; that requires two different accounts and compatible counterparties.
Automation: when the AI posts by itself, and when it never does
Posts on its own
Proposals with at least 85 % confidence from rule, partner history, lexicon or AI; bank lines that clear an open item unambiguously; fixed assets with useful life derived from the transaction (a laptop three years, not eight) and low-value assets up to 800 EUR net written off at once, posted with a note; prepaid and deferred items spread over the service period and released automatically.
Always stays a review
Reverse charge, intra-community acquisitions and import VAT — every posting with a reverse tax burden; receipts without reliable recognition; bank lines without a counterparty (you name the creditor or debtor, nothing is posted silently to a collective account); postings into locked periods or into a year whose annual accounts are already adopted; everything a company explicitly declares as review — amount limit, approved rules only, automation off.
Never from a learned entry alone
A proposal distilled from an imported posting batch or a not-yet-confirmed memory entry stays below the automation threshold until a person has confirmed it once. Whether the automation works well is measurable: the coding hit-rate card shows per source how often a proposal was posted as it came, over 90 days and only from 20 measurable lines upwards.
GoBD compliance: locking, reversals, audit log
The German principles for proper keeping and retention of books (GoBD, based on § 146 AO and § 239 HGB) require traceability, completeness, timely recording and immutability. Every posting here is part of an immutable chain; a later change is only possible as a reversal with a contra entry, never as silent overwriting. Periods are locked to the day — at the latest with the advance VAT return, which has a lock button next to the submit button.
Receipts stay linked to their posting and are retained in the original (§ 257 HGB, § 147 AO). The audit log records who posted, changed, approved or reversed what and when, and whether a proposal came from the AI, a rule or a person. For the tax adviser there is a posting-batch export in the format of the common German practice software, including the locking flag; for a tax audit, data access to journal, account ledgers and receipts.
Responsibility for proper bookkeeping stays with the merchant (§ 238 HGB). The software does not change that — it makes the books provable and takes over the work that can be automated without losing the evidence trail.
What the books feed: VAT, trial balance, annual accounts, taxes
Advance VAT return: every posting carries its own VAT period date following §§ 13 and 15 UStG — the date of supply for output VAT, supply plus invoice for input VAT. The return is derived from it, reconciled per VAT code and shown with box numbers, payable amount and a drill-down per box before it is sent directly to ELSTER. A late invoice lands in the correct month, not in the upload month.
Trial balance, management figures, preview: opening balance, movements and closing balance per account are always available; the management report compares with the prior year and drills down to the single posting; the balance sheet and income statement preview shows during the year where the accounts would stand today.
Annual accounts, E-Bilanz, taxes: the same trial balance is the basis for the HGB annual accounts with balance sheet, income statement, notes and management report, for the E-Bilanz under § 5b EStG and for the corporate and trade tax returns. Adopted accounts lock the year's journal so figures and postings cannot drift apart; a correction goes through a logged unlock.
Pricing and who it is for
Prices are per company and month, staggered by HGB size class. The solo plan for ongoing bookkeeping costs 95 EUR for micro companies, 120 EUR for small and 250 EUR for medium-sized companies. The full package with the supported tax processes and one set of HGB annual accounts per twelve months costs 125, 150 and 300 EUR respectively; large companies on request. One user is included, each additional user 20 EUR a month; 100 AI-recognised receipts per company and month are included, each further one 0.20 EUR; a bank connection through the PSD2 service finAPI costs 5 EUR per active connection and month, while the Qonto direct connection and CSV, MT940 and CAMT imports are free. The 14-day trial is free with a card on file; without cancellation the subscription starts on day 15.
The bookkeeping is open to every German legal form, from the sole trader and the GbR to the GmbH, UG, AG, SE, KGaA and the registered cooperative. Partnerships keep capital and private accounts per partner. Typical users are managing directors who want to own the ongoing bookkeeping, finance teams with several companies, and foreign parents that want their German subsidiary's books visible in English. The tax adviser can be invited as a reviewer and sees journal, receipts, open points and audit log; the software itself gives no individual tax or legal advice.
Frequently asked questions
Does the AI really post on its own?
Yes. By default it posts every proposal with at least 85 % confidence. Reverse-charge cases, intra-community acquisitions and import VAT always remain a mandatory review. Each company can switch the automation off, restrict it to approved rules or set an amount limit.
Is AI bookkeeping compliant with German GoBD rules?
Every posting is chained immutably, periods are locked to the day, and corrections run as reversals. Receipts stay linked to their posting and the audit log records every change. Responsibility for proper bookkeeping stays with the merchant under § 238 HGB; the software makes it provable.
Why does a bank line never post to the income statement?
Because the same transaction would otherwise be expense or revenue twice — once with the receipt, once with the payment. Expense and revenue arise with the document; the bank movement only clears the open item. Exceptions are payment-provider fees, advance payments and cash-basis accounting.
Can I migrate from another bookkeeping tool?
Yes. The last trial balance or closing balance sheet is enough to start: the balances are mapped to HGB balance sheet items and posted as opening values. If the whole year should sit in the journal, the posting batch of the previous software is imported and reconciled against the prior-year balances per account.
Is my data used to train AI models?
No. Permanently stored data sits in EU data centres (Ireland). Content required for receipt recognition is sent to contractually bound model providers with appropriate safeguards; no training on customer data takes place.
Does the software replace the German tax adviser?
It replaces the ongoing legwork, not the advice. Many companies keep the books themselves and invite their adviser as a reviewer into the workspace. The software gives no individual tax or legal advice.
Primary sources and scope
Authoritative references for the key claims on this page. Check the current text before making a filing or accounting decision.