Today
An e-mail from a supplier: new bank details, please pay the open invoice there. It looks genuine, the logo is right, and the sender address differs by one letter. Or the supposed managing director wants an urgent, confidential transfer on a Friday afternoon. Accounts payable has seconds to spot it, and a single wrong payment can run to six figures.
An example
At 4:40 pm on a Friday, Nordhanse receives an e-mail from its supplier of spreader spare parts: the bank has changed, and the open invoice of €48,600 should go to the new account today. demi blocks the payment in the payment run and names three reasons: the e-mail came from a domain spelled one letter differently, the new IBAN belongs to a bank in another country, and in six years the supplier has never changed its bank details. The accountant calls the number in the master data; nobody there knows of a new bank, and the invoice is paid to the old account as always.
Your data, wherever it lives
Bank details sit in the master data in the ERP, change requests arrive by e-mail, as PDF invoices or by phone, and the payment run goes through the banking software. demi reads, understands and links all of it, with your rights and across years of correspondence. The AI spots wrong bank details in seconds instead of after the loss, and a person calls back and releases.
Where the data lives today
- E-mails
- ERP
- PDFs
- Phone & voice
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 e-mail, the ERP and payment processing. demi replaces nothing and links every payment request and every change to bank details, address or payment terms with the supplier's master data, their earlier invoices and e-mails, the contracts and the planned payment run. Every new bank account then has a history it must be measured against.
- 2 · PermitPermission Layer
Master data and payments are visible only to accounting and finance management. The agent may block, only people may release: changed bank details take effect only after a second authorised person has confirmed the callback. Every block, callback and release is logged.
- 3 · ActIntelligence Layer
The agent checks every request against fixed rules, such as a new IBAN, a bank in another country or an account holder who does not match the supplier. It also compares sender domain, reply-to address, invoice layout, writing style and urgency with the sender's history. It shows every signal with its evidence, and whether the payment is held follows from your rules, not from a hunch.
How it runs
- 1
An e-mail with new bank details, an invoice or an urgent payment instruction comes in.
- 2
demi compares it with master data, earlier invoices, contracts and the sender's writing style.
- 3
If something does not fit, demi sets a payment block and names every reason with evidence.
- 4
Accounting calls back using the number in the master data, never the one in the e-mail.
- 5
Only when a second person releases the confirmation are the bank details changed and the payment freed.
What changes
Fake bank details caught before the payment
Every change of bank details with a callback and a second release
Pressure from the supposed boss goes nowhere
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 checks each change of bank details against master data and history; a person calls back and releases.
20 min → 14 min per case
How we calculate
40 checks of bank details and payments × 20 min × 30% × 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
How does demi recognise fake bank details?
By several signals at once: a new IBAN, a bank in a different country than before, an account holder who does not match the supplier, a sender domain with a swapped letter, a different reply-to address, a changed invoice layout or unusual urgency. The agent shows each signal with its evidence. Which combination triggers a block, you set in your rules.
Will demi also hold payments that are fine?
Yes, sometimes, for example when a supplier really changes banks. Then the callback takes two minutes, the second person releases, and the payment goes out in the next run. A short block costs less than a payment that never comes back.
Does this also help against the supposed boss?
Yes. demi holds any payment instruction meant to bypass the usual approval path, no matter how genuine the e-mail, voice message or voice seems. The agent checks it against your approval rules and that person's earlier e-mails, and the callback goes to the internal number, not the one in the message.
Does demi change master data or release payments itself?
No. demi can block a payment and prepare the callback, with number, contact person and the questions to ask. Only authorised people change the bank details and release the payment, under the four-eyes principle, and every step is logged.
