Invoice automation
Invoices into your books, without silent errors
A custom invoice flow where checks decide what is accepted and a person sees everything the checks doubt. Less typing, and no wrong totals slipping into your VAT return.
Prefer to write first? Send a message instead.
Fixed prices, excl. VAT · You own everything · Reply within 24 hours
Why most invoice automation is hard to trust
Errors look like correct answers
AI readers are right most of the time, but a wrong total looks exactly like a right one. You end up proofreading every row, which is typing by another name.
Nobody says what was uncertain
Many tools give you a spreadsheet and a confidence claim. They rarely show which invoices they could not read, so doubt stays hidden until your bookkeeper finds it.
Invoices hold personal data
Sole traders' invoices carry names, addresses and bank details. Sending them to an AI service raises questions about processing, storage and training that need clear answers.
How I build an invoice flow you can rely on
-
Sort what you receive
We count your invoices and split them into e-invoices, text-based PDFs and scans. Each needs a different tool, and only scans really need heavy AI.
-
Test on your own invoices
We build a small test set from your real invoices with hand-checked values. That is the only accuracy figure that says anything about your business.
-
Checks decide, the model only helps
Arithmetic, VAT, IBAN checksums and a rule that every value must be printed on the page. A model may help find a value, but it never has the final say.
-
Doubt goes to a review folder
Anything that fails a check lands with the original PDF, the proposed values and the reason. You confirm or fix it. Nothing is auto-corrected.
-
Measure every month
We track how many invoices pass untouched and how many errors were found later. Each silent error becomes a new check.
My own invoice-to-CSV tool
I built this for my own use, so it is not client work, and it is not published. On 800 generated test invoices it accepted all 640 clean ones, sent all 160 broken ones to review and let nothing wrong through. These were synthetic invoices; real-invoice testing is still ahead.
An 8B language model lost to plain code
In my own testing, a local 8B model read amounts right about 47% of the time and took 60 minutes for 50 invoices. Plain code with checks reads amounts exactly, in about 1 ms per invoice.
What it looks like in practice
Most small businesses start with a short audit of their invoice flow, then move to a custom build if it makes sense. Current prices are shown below.
What you get
Custom Solutions · from €2,500
The build step: automations, custom apps and integrations, scoped after the audit
- Workflow automation inside the tools you already use
- Custom apps and internal tools built around how you actually work
- Agent and API integrations between the systems you already pay for
- Model selection: which model, running where, and why
- Scoped in writing before any work starts, with defined success criteria
- A one-page data map: what enters, what leaves, where it is processed
- Documentation, a walkthrough call, and ownership of everything
What you get
AI Audit & Roadmap · €549
Workflow review ending in a written, prioritised roadmap within 5 working days
- Intake call + workflow review
- Written report in plain language
- Prioritised roadmap with effort estimates
- Delivered within 5 working days
- Credited against any build booked within 60 days
Common questions
Can invoices be processed automatically without errors?
Not without a safety net. A well-built flow accepts the invoices that pass every check and sends the rest to a person. The aim is zero silent errors, accepting that some invoices need a human look.
Do I need AI to extract invoice data?
Often not. E-invoices and born-digital PDFs can be read exactly by plain code. AI helps mainly with scans and unfamiliar layouts, and even then the checks make the final call.
Is it safe to send invoices to an AI tool under the GDPR?
Invoices often contain personal data, so an AI service becomes a processor. You need a data processing agreement, clarity on where data is processed and kept, and no training on it. Code-only extraction on your own machine avoids the question for the invoices it can read.
What happens to invoices the system cannot read?
They go to a review folder with the original PDF, the proposed values and the failed check. You decide, and only then does the invoice enter your books.
Which accounting software does it work with?
That depends on your setup. We would look at your software and export format in the first call, and it is part of what an audit checks.
Want a second pair of eyes on your invoices?
Tell me how many invoices you handle and how they arrive. I will tell you honestly whether you need a tool, a build, or just a few checks in a spreadsheet.
Prefer to write first? Send a message instead.
Fixed prices, excl. VAT · You own everything · Reply within 24 hours