Today
Accounts payable puts every invoice next to the order and delivery note and checks it by hand. Price deviations and duplicate invoices still slip through. And approvals sit in inboxes for days.
An example
Talwerk Antriebstechnik receives 860 invoices in October. 790 match their order and goods receipt cleanly. 41 charge more for 6205-2RS deep-groove ball bearings than the framework contract allows and 3 are duplicates with a new invoice number, so the AP clerk only sees these 44 cases, each with the contract clause.
Your data, wherever it lives
Invoices arrive today as e-invoices, as PDFs by e-mail, through supplier portals or on paper; purchase orders and goods receipts sit in the ERP, framework contracts in the DMS, and approvals wait in inboxes. demi reads, understands and links every invoice to its purchase order, goods receipt and contract, with your rights. The AI checks quantity, price and duplicates in seconds, and the person in charge decides on every deviation.
Where the data lives today
- PDFs
- E-mails
- Web & portals
- Scans & paper
- ERP
- DMS & archive
How demi solves it
Three layers in this order: connect the data first, then the rights, then the AI.
- 1 · ConnectData Layer
Data sources in this case: ERP, e-mail and DMS. demi replaces nothing and links every invoice to its supplier, purchase order, goods receipt, framework contract and chart of accounts. demi writes back only after approval.
- 2 · PermitPermission Layer
Whoever is responsible by value limit and cost centre in the org chart approves, and nothing is posted before that confirmation. Every approval is recorded with its reason.
- 3 · ActIntelligence Layer
The agent extracts the invoice and runs the three-way match by fixed rules, citing order line and contract clause for every deviation or duplicate. It proposes the coding from posting history.
How it runs
- 1
The invoice arrives by e-mail, portal or scan and is read.
- 2
demi matches quantity and price with order, goods receipt and contract.
- 3
Matching invoices go to approval with a proposed coding.
- 4
Deviations and duplicates go to the responsible person, with evidence.
- 5
demi writes back only after approval.
What changes
Less manual checking in accounts payable
Overpayments caught before payment
Faster approvals
What does it bring you?
Check it with your own numbers
Every starting value is an assumption you can change. The calculation sits right below, step by step.
Your numbers
Result
+900 hfreed per year
Assumptions and calculation
demi matches each invoice with order, goods receipt and contract and pre-codes it; you approve.
6 min → 3 min per case
How we calculate
1,500 supplier invoices × 6 min × 50% × 1.0 (manual) × 12 months = 54,000 min = 900 h
Value per year, before demi costs
Freed per year+900 h
Assumption: labour cost of €49.50 per hour in German manufacturing in 2025 (Destatis), plus workplace, IT and overheads.
= Value per year, before demi costs
+€58,500
gained per year
900 h ÷ 1,760 h per role = 0.5 full-time roles
An estimate, not a promise. The starting values are assumptions for an industrial company with 150 to 500 people.
Combine with more cases and get the packageQuestions about this use case
Which invoice formats can demi read?
PDF invoices, scans and e-invoicing formats such as XRechnung and ZUGFeRD. Structured formats are taken over directly; the agent reads PDFs and scans. Every field shows where its value came from, and uncertain fields are marked for review.
What happens when an invoice deviates?
It does not go to approval. It goes to the responsible person with the exact difference: quantity, price or condition, each with order line and contract clause. They decide whether to short-pay, dispute or knowingly approve, and the decision is recorded with its reason.
Does demi post invoices on its own?
Not without confirmation. demi proposes coding and posting, someone with approval rights confirms, and only then does demi write back. Whether you later let clear-cut cases through by rule is your decision, and that is recorded too.
What if the order or goods receipt in the ERP is wrong?
Then the match shows exactly that spot as a deviation. demi does not change ERP data on its own; it names the document where invoice and system disagree. Missing goods receipts surface this way too, before anything is paid.
