Today
The same invoice arrives by post and by e-mail and is entered twice. A supplier sends a reminder with a new number, a second site pays an invoice that head office has already paid, and the credit note for returned parts is never offset. The check at entry usually catches only identical invoice numbers, and nobody looks back: the money sits with the supplier, and the longer it sits there, the harder it is to get back.
An example
Nordhanse has demi review the payments of the past three years, around 41,000 supplier invoices from the ERP and the old system's database. The agent finds 63 suspected cases: an invoice for reach stacker tyres that came as a scan and as a PDF by e-mail and was entered twice, a workshop invoice paid by the second site although head office had already paid it, and 14 credit notes for returned spreader parts that were never offset. Accounting confirms 38 cases worth 87,400 euros in total. demi drafts recovery claims to 21 suppliers with a list of documents, and after release they go out.
Your data, wherever it lives
Payments, invoices and credit notes sit in the ERP today, older years often still in the database of the previous system, the documents as PDFs and scans in the DMS, supplier reminders and balance confirmations in the accounting mailboxes. demi reads, understands and links all of it, with your rights, across sites and years. The AI finds in hours what a manual review would need weeks for, and accounting decides what to reclaim.
Where the data lives today
- ERP
- DMS & archive
- PDFs
- Scans & paper
- E-mails
- Databases
How demi solves it
Three layers in this order: connect the data first, then the rights, then the AI.
- 1 · ConnectData Layer
The case needs data from the ERP, the DMS, e-mail and the previous system's database. demi replaces nothing and links every payment with its invoice, purchase order, goods receipt, credit note and document, across all sites, companies and years. Every invoice then sits next to all others that look too similar, even when they were booked under a different supplier number.
- 2 · PermitPermission Layer
Payments, supplier accounts and documents are visible only to accounting and finance management; a site sees its own cases. The agent only reads and posts nothing: accounting decides whether a case is a duplicate payment, and a recovery claim goes to the supplier only after release by an authorised person. Every case is logged with its decision and reason.
- 3 · ActIntelligence Layer
The agent compares invoices not just by number but by amount, date, supplier, purchase order reference, line items and document layout, also across different supplier numbers of the same supplier. It matches open credit notes against later payments, and demi calculates amounts exactly from the postings. Every hit comes with both documents side by side and the reason it stands out.
How it runs
- 1
demi reads payments, invoices and credit notes of past years from the ERP, the previous system and the DMS.
- 2
The agent looks for invoice pairs that are too similar: same amount, similar number, same items, same purchase order, different site.
- 3
It also finds credit notes that were never offset against a payment.
- 4
Accounting checks every hit with both documents side by side and decides.
- 5
For confirmed cases demi drafts the recovery claim per supplier with a list of documents, and accounting releases it.
What changes
Money paid twice comes back
Open credit notes finally get offset
New duplicate payments are caught before the payment run
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
+48 hfreed per year
Assumptions and calculation
demi finds duplicate payments and open credit notes with evidence; accounting decides.
40 min → 24 min per case
How we calculate
15 suspected duplicate payments × 40 min × 40% × 1.0 (manual) × 12 months = 2,880 min = 48 h
Value per year, before demi costs
Freed per year+48 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
+€3,120
gained per year
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
Does demi also find duplicate payments with different invoice numbers?
Yes, those above all. The check at entry usually catches only identical numbers. The agent compares amount, date, line items, purchase order reference and document layout, and so also finds a reminder with a new number, a copy with one extra character or the same invoice under two supplier numbers.
How far back can demi search for duplicate payments?
As far as postings and documents go. If older years still sit in the database of a previous system or as scans in the archive, demi includes them. How far back a claim is worth it and still legally possible is decided by finance management.
Does demi rebook or write to suppliers itself?
No. demi shows hits with both documents and drafts the recovery claim. Accounting decides whether it is a duplicate payment, postings are made in the ERP as before, and only what an authorised person releases goes to the supplier.
Does this also help against new duplicate payments?
Yes. Once the look-back has run, demi checks every new invoice against all earlier ones before the payment run, including those of other sites. If one stands out, accounting holds it before the money leaves.
