Skip to content
Back office: finance, HR, legalFor every industry

Follow up receivables and draft reminders

demi prioritizes open items, spots complaints behind late payment and drafts fitting payment reminders.

Today

Reminders go out while the customer has an open complaint. The large overdue item gets the same treatment as the small one. And what was agreed with the customer on the phone is written down nowhere.

An example

A Talwerk Antriebstechnik customer is 40 days late on invoice RE-2026-04418 for 12 geared motors. The agent finds an open complaint about 2 motors with the wrong flange and passes the case to the head of inside sales instead of drafting the second reminder.
Fictional company, typical workflow.

Your data, wherever it lives

Today open items and due dates sit in the ERP, complaints and service cases in the CRM or in tickets, and agreements with the customer are buried in e-mails, if they were written down at all. demi reads, understands and links them per invoice and customer, with your rights. The AI checks every overdue item for complaints and agreements in seconds, instead of someone searching three systems, and drafts the right reminder, which accounting approves.

Where the data lives today

  • ERP
  • CRM
  • Tickets
  • E-mails
Data LayerOne view of everything, with your rights

How demi solves it

Three layers in this order: connect the data first, then the rights, then the AI.

  1. 1 · ConnectData Layer

    Data sources in this case: ERP, CRM and e-mail. demi replaces nothing and links every open item to its delivery, complaints, service cases and correspondence. demi writes back only after approval.

  2. 2 · PermitPermission Layer

    Accounting reviews and approves every reminder, for key accounts after checking with the account owner. Every reminder and agreement is recorded.

  3. 3 · ActIntelligence Layer

    The agent takes amounts and due dates exactly from the ledger and checks whether a complaint or dispute lies behind the item. Disputed cases go to sales or service; for the rest it drafts the reminder by dunning level and customer.

How it runs

  1. 1

    demi checks the open items every day.

  2. 2

    The agent checks every overdue invoice for complaints, service cases and e-mails.

  3. 3

    Disputed cases go to sales or service instead of the dunning run.

  4. 4

    For the rest, it drafts reminders by level and customer.

  5. 5

    Finance releases them; agreements go back only after approval.

What changes

  • Cash comes in faster

  • No reminders on disputed invoices

  • Better customer relationships

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.

Assumption, editable

Your numbers

Result

+240 hfreed per year

Assumptions and calculation

demi ranks open items, spots complaints behind them and drafts the reminder; you send it.

10 min → 6 min per case

How does it run today?

What is already digital saves less: the factor lowers the share demi brings.

How we calculate

300 open items × 10 min × 40% × 1.0 (manual) × 12 months = 14,400 min = 240 h

Value per year, before demi costs

Freed per year+240 h

Assumption: labor cost of $48.62 per hour in US manufacturing in June 2026 (BLS), plus workplace, IT and overhead.

= Value per year, before demi costs

+$15,600

gained per year

240 h ÷ 1,760 h per role = 0.1 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 package

Questions about this use case

How does demi know an invoice is disputed?

For every overdue invoice, the agent looks up the delivery, complaints, service cases and e-mails that belong to it. If it finds an open complaint or an e-mail saying "part of the delivery is missing", it shows where. The invoice is then clarified, not chased.

Can the tone of reminders be adjusted?

Yes. You set the levels and templates; the agent fits each draft to the customer, history and occasion: a friendly note for a long-standing customer, a firm reminder after repeated late payment. Every draft can be edited before it is sent.

Who sends the reminder?

Finance, after release. demi sends nothing on its own. For key accounts the draft goes to the account owner first, so no reminder lands in the middle of a negotiation.

What happens to payment agreements?

When finance agrees instalments or a new due date with a customer, the agent records it. Results go back only after confirmation. The next dunning run takes the agreement into account.

See this case with your data

In the demo we show you the workflow on your own systems.

Your configurator

No use cases yet

Your configurator is still empty

Add a use case from any card or case page and see what it brings per year, with the calculation. Free, no sign-up, no commitment: try it out and change any number.

Browse use cases