Receive the invoice
Take it in from email, scan or supplier portal.
Invoice data is read and matched to suppliers and cases. Check steps are prepared, and after approval the data goes to accounting or the ERP.
In short: The solution takes over the repetitive groundwork in accounts payable. It recognises invoices, extracts structured data and checks it against defined master data or cases. Decisions relevant to bookkeeping and approvals follow your rules.
Take it in from email, scan or supplier portal.
Supplier, invoice number, date, line items, amounts, VAT, QR reference (Swiss QR-bill).
To the supplier master data; new suppliers as a suggestion.
Flag duplicates, the order or project reference and discrepancies from the order.
Account coding suggestion and approval request to the person responsible.
Approved data to the ERP or accounting.
Examples from the workflow – no percentages, as only a measurement in your business can provide those.
| Situation | Today | With the solution |
|---|---|---|
| Receipt | paper and email attachment | recognised, read, in the case |
| Reference | search for the order | order or project reference suggested |
| Approval | on the desk | as a task with a deadline for the person responsible |
| Posting | entered again | approved data handed over |
Invoice data is extracted, not typed up.
The invoice arrives as a task, with all the details.
Supplier, reference and account coding follow the same rules.
Who checked and approved what, and when.
Sample images from our visual library – the interfaces shown are illustrations, not client data.



Approval, the final accounting treatment and every payment. The solution prepares the data and flags discrepancies.
The solution prepares, sorts and hands over – your staff make decisions and grant approvals, following rules you set.
For example – what exactly gets connected depends on interfaces and permissions and is checked in the AI potential assessment.
Solution building blocks are the technical components the solution is built from. Products are only named where they fit the task.
Recognise and read invoices.
View building blockCheck, approval and handover to the ERP.
View building blockPrepare matching and discrepancies.
View building blockProvided the process fits the product logic.
View productDepending on the product and interfaces, we run the solution on your premises, in a Swiss cloud or as a combination. Before the pilot, we clarify data flows, access rights and compliance requirements. Background: Private AI and On-premise & hybrid (running on your own servers or a mix of both).
| Topic | Implementation |
|---|---|
| Data | Financial and supplier data – confidential. |
| Approvals | Decisions relevant to bookkeeping, account coding and payment approval follow your rules; the default is preparation and controlled handover. |
| Roles & permissions | Who sees invoices, who approves, who maintains master data – according to your existing approval process. |
| Logging | Extraction, check, approval and handover traceable for each invoice. |
| Operating model | Private cloud or running on your own servers – depending on the ERP and accounting system; defined in the project. |
The pilot does not cover the whole process straight away. We pick a clearly defined part, set approvals and success criteria and test it with real data and the people who work with it. This approach is the same for every use case.
That depends on the rules and approvals you define. The default should be preparation and controlled handover.
Yes, if the reference data is available and can be linked reliably.
They can be prepared. The final accounting treatment must be checked according to your company’s process.
Companies with a regular volume of supplier invoices, an ERP or accounting system and a defined approval process – including accounting and fiduciary firms for their clients.
Describe your current workflow in two sentences. We check the benefit, data situation, integration effort and risks and show whether a product, a solution building block or a custom solution makes sense.