Every invoice with the right project.
Exceptions included.

Sometimes it can. If you work in Odoo and mostly receive ordinary purchase invoices, Odoo can read them itself and turn them into a draft invoice, including when you send them to a fixed email address. Turn that on first and see how far it gets you. We help set it up or look at it together in a Pitstop. Read more about Odoo or about accounting and Peppol

Since 1 January 2026, Belgian VAT-registered businesses have had to send each other structured e-invoices via Peppol. For those invoices, retyping disappears. Checking, assigning and approving is still work. If your organisation is not VAT-registered, or only carries out exempt transactions, PDFs will keep coming in. Check with your accountant. Expense claims and certificates don’t come through Peppol anyway. Source: efactuur.belgium.be

If almost everything comes through Peppol, we only build what’s left: assigning to a project or grant, and the approval. A dedicated workflow pays off mainly when documents come in through different channels, go to more than one system or contain sensitive data.

After a 30-minute introductory call, the pilot runs for 4 to 6 weeks in your own environment, with real invoices. During those weeks we measure how long an invoice takes and how often your team has to change something. Then you decide with figures: roll out, adjust or stop. Want to know first whether it makes sense? Then start with a 1-hour Pitstop.

The model only sees the documents from the agreed mailbox or folder, and the fields it needs. We choose a model and hosting that suit how sensitive your data is, in the EU as standard. We only work with a provider that doesn’t use your data to train models. It’s all in the AI fact sheet.

That can happen. That is why a colleague approves every invoice before anything is booked. If the AI is unsure about a field, you see that straight away. A new account number or an amount above your threshold gets an extra check. During the pilot we count how often someone has to correct things.

The workflow checks itself: if a step stops working or the results look off, we get an alert. Fixing it is covered by the maintenance agreement. Zenjoy has been maintaining platforms and integrations for years after launch; your workflow gets the same care.

Your organisation uses the workflow and is therefore usually the deployer. We write down who has which role for each workflow in the AI fact sheet. A workflow that reads invoices doesn’t decide about people and generally doesn’t fall under the high-risk uses. Your team does need to know how it works and where it can go wrong. That is called AI literacy. We explain the workflow to the people who use it; if you want more, a training session is possible. This is not legal advice.

Yes, if that information is somewhere: on the invoice, in a purchase order or in earlier entries from the same supplier. The AI makes a suggestion and your team confirms. For invoices split across more than one grant, someone from your team always decides.