Invoices, documents and contracts
At month end the invoices arrive from four directions. Some by mail, some on paper from the letterbox, some as a phone photo from the technician, some still attached to an order nobody can find. Then somebody starts typing. We build the software that takes over that path: read the document, suggest the posting, collect the approval, hand it cleanly to accounting.
Overview
A reminder arrives for an invoice that was paid three weeks ago. The maintenance contract has renewed for another year because the notice period sat in a folder nobody has opened since February. The delivery note from the yard is filled in by biro, half smudged, and the invoice for it does not add up.
The early payment discount was there for the taking, but the document sat on a desk for nine days because the approver was on holiday and nobody knew who was covering. And when the accountant asks in January why an item went to that account, the only person who knows now works in another department.
What we deliver
Technology
How we proceed
Frequently asked
Structured e-invoices such as XRechnung and ZUGFeRD are read straight from the file. PDF, scan and photo go through text recognition and field extraction, with every field carrying its own confidence value.
Yes. Handwritten delivery notes, stamps and phone photos go through the same recognition as a clean scan, only with more cautious thresholds. Anything uncertain goes into the review queue.
The existing stock is read out and assigned to the relevant business partner. Term, notice period and price clause then sit in the system as data and report in before renewal.
The AI models and your data run on our machines in Germany. Processing does not require sending anything to third party model providers.
No. It replaces the typing and the chasing. Accounting checks suggestions, decides the doubtful cases and approves. No payment is triggered without a person approving it.
