Automating invoice reminders in Dolibarr: what is automated, what stays validated
Dolibarr can flag an overdue invoice. It cannot write the right reminder to the right customer. Here is how an assistant bridges the gap without ever sending an email on your behalf.

Article prepared with the help of artificial intelligence from our monitoring, then reviewed and approved by Christophe Delebarre before publication.
Dolibarr is a good ERP for a small organisation: invoices, customers, due dates, it is all there. But when an invoice passes its due date, Dolibarr just colours it red in a list. The reminder still has to be done: open the record, check the history, write an email that is neither too soft nor too harsh, send it, note that you did. Multiplied by twenty late invoices, that is half a day a week nobody wants to spend.
We have already explained how much time reminders cost an SME. This article describes how they are actually automated, and above all where the automation stops.
What Dolibarr does on its own
Dolibarr keeps the list of validated invoices, their due date and payment status. It can compute the delay. With a few modules it can even send a generic reminder on a fixed date. That is useful, and not enough: the same text goes to everyone, to the loyal customer who forgot as to the bad payer waiting for you to insist. And nobody proofreads before sending.
What an assistant adds
An Isalia assistant connected to Dolibarr through its API does four things, every day or at the frequency you choose.
- It reads overdue invoices and computes, for each one, the delay and the amount, taking deposits and credit notes into account.
- It applies your rules, not its own: a friendly first reminder at seven days, a second at twenty-one, a formal notice at forty-five, or whatever schedule you define. With exceptions: customers never to be reminded automatically, and an amount threshold above which you want to read line by line.
- It writes each reminder with the right amounts, the right references, the customer's history and the tone that fits the level of delay. A customer who always pays ten days late does not get the same message as an unknown customer at sixty days.
- It presents you the batch, ready to go, with the text, the recipient and the attachment for each reminder.
What stays in your hands
Sending. Nothing leaves without a click from you. That is the rule across the whole platform, not an option of this use case. You validate the batch in a minute, you edit one reminder, you pull another because you know that customer called yesterday. Every validation is traced and timestamped: who validated, what, when.
After sending, the assistant records the action in the customer's Dolibarr agenda. Your reminder history lives in the ERP, not in a mailbox. When payment arrives, the cycle stops by itself.
Your data does not leave you
Amounts, customer names and emails are company data, sometimes personal data. The assistant reads them in your Dolibarr, hosted wherever it is. Processing runs on the Isalia platform, hosted by OVH in France, with a European model whenever company data is involved. Nothing is used to train a model. Details are on our trust and compliance page.
What changes after a quarter
Organisations that set up regular reminders first see their average payment delay fall, because customers know a forgotten invoice will be chased at seven days, not three months. They then see "lost" invoices disappear, the ones nobody had chased. And time spent drops from half a day a week to a few minutes of validation.
The full use case, with a typical day, is described on the unpaid invoice reminders page. If you do not use Dolibarr, the principle is the same with any other ERP that has an API: tell us which one.
