The supplier invoice arrives as a PDF on Monday, gets printed on Tuesday, checked against the delivery note on Wednesday, typed into the accounting tool on Thursday and filed on Friday, and the early-payment discount is gone by then. For a firm with two hundred invoices a month that chain costs a part-time position. Invoice processing automation collapses it to the one step a person should keep: the exception.

The system reads each invoice as it arrives, from the inbox, a scanner or a supplier portal. It extracts the vendor, the invoice number, the line items, the amounts and the due date. It matches the invoice to the purchase order and the delivery note. When everything agrees, it creates the bill in the accounting tool you already use and files the PDF. When something disagrees, a person gets the invoice with the reason, decides, and that decision becomes a rule.

It runs inside the tools you have: DATEV, Lexoffice or sevDesk in Germany, Xero or QuickBooks in English-speaking markets, and the ERP you run for purchasing. Nobody learns a new system. The bookkeeper keeps the final say on every mismatch.

This pays off from roughly a hundred supplier invoices a month, or earlier when the invoices are complex: many line items, part deliveries, freight surcharges, several currencies. Below that, a simpler tool or a better inbox rule is often enough, and we say so.

The part where AI matters is the reading. Older invoice software needs a template per supplier and breaks when the supplier changes the layout. A language model reads the invoice the way a person does, so the fiftieth supplier costs nothing extra to onboard.

Limits we name up front. Matching needs purchase orders that exist and are current; if your purchasing runs on phone calls, we fix that flow first. A person still signs off on mismatches, and in the first weeks that is a lot of them, until the rules settle. Your bookkeeper keeps his job and loses the typing.

Questions we get asked

  • Which accounting tools do you support?

    Any tool with an interface or an import: DATEV, Lexoffice, sevDesk, Xero, QuickBooks, Sage, and most ERPs. If yours is unusual, we check it before the quote.

  • How accurate is the extraction?

    Amounts, dates and invoice numbers are read reliably on clean PDFs and good scans. Every field carries a confidence value, and anything below your threshold goes to a person. You set the threshold; we start strict.

  • What about outgoing invoices and reminders?

    The same system can draft outgoing invoices from accepted quotes and send friendly reminders on overdue ones, with a person approving each send. Most clients start with the incoming side, because that is where the typing is.

  • How long until it runs?

    A first pipeline over your real invoices typically runs within weeks. We quote a fixed price after the call.