FAQ

The questions asked most often about Customer Payment Reminders, answered.

Does this work on Odoo Community? Yes, and that is largely the point. Community has no follow-up or dunning feature at all. On Enterprise it is a simpler and more transparent alternative to the built-in follow-up levels — one list, one history, and a stated reason whenever somebody is skipped.

Will it start emailing my customers as soon as I install it? No. The master switch is off. Nothing is sent until you tick Chase Overdue Customers in Settings. Install it, look at Customers to Chase, and send a few by hand first.

One email per customer, or one per invoice? One per customer, listing all their overdue invoices. Six emails about six invoices is not six reminders; it is harassment, and it gets your address filtered.

What if the invoice was addressed to a contact rather than the company? It counts against the company. Reminders are grouped by the commercial partner, so a customer with three contacts and eight invoices still gets one email.

Who receives it? The customer's invoicing contact if they have one — a child contact of type Invoice with an email address. Otherwise the company itself. Otherwise the partner the invoice was addressed to.

A customer has an old invoice and a new one. Which level applies? The one for the oldest overdue invoice. A customer 90 days late on anything has a 90-day problem, whatever else is on their account.

Somebody was never chased and is now four months late. Do they get all three? No — they get the sixty-day letter. The most severe applicable level wins. Walking them politely through an escalation everybody knows is theatre wastes two more months.

A customer paid up and has now fallen behind again. Do they resume at the final notice? No. They start at the polite letter. The invoice that earned them the final notice is paid; they are not a sixty-day problem any more, and punishing somebody who has just paid you is how you lose them.

Can I send the same level twice? Not automatically — each level fires once. Use Force a Level in the send wizard when you want to chase again at the same level.

Can I add a level? Yes, any number, with any day counts. Levels are ordinary records. A new one slots into the escalation by its day count and nothing else needs changing.

Can I chase before the due date? Not with a reminder level — negative day counts are refused, and a "reminder" before the money is owed is a different kind of message. Send it as an ordinary email from the invoice.

Are draft invoices chased? Never. Asking somebody to pay an invoice you have not sent them is the fastest way to lose an account.

Partially paid invoices? Yes, for the remainder. Somebody who pays half and stops is exactly who needs chasing.

Does it charge late-payment interest? No, deliberately. Interest is a legal and contractual matter that varies by jurisdiction and by contract, and getting it subtly wrong inside an automated email is worse than not offering it at all. Say what you charge in the template wording if you need to.

Does it block orders or change credit limits? No. Chasing is a communication problem; blocking an account is a policy decision, and it should stay a human one.

Can I stop chasing one customer without excluding them forever? Pause them until a date, with a reason. The pause clears itself and they rejoin the escalation where they left off. Never Chase is the permanent option, and it is Credit Manager only.

Why does the wizard say a customer will be skipped? Because "nothing happened" is the most annoying thing software can say. Every skip has a stated reason: nothing overdue, paused, below the minimum, not overdue enough yet, or that level already sent.

Does it modify my invoices? No. It reads them. It never changes an invoice's state, payment state or due date.

What happens if one customer's send fails? The rest still go. A missing email address on one account does not mean nobody else gets chased that day; the failure is reported and the run continues.

Does it send anything to you, the publisher? No. There is no telemetry, no activation key, no licence check and no outbound connection other than the reminder email through your own mail server.

How long is the history kept? Three years, then pruned automatically — long enough to answer a dispute, short enough that the list stays usable. Change the Prune History scheduled action if you need a different period.

Multi-company? Yes. Levels can be shared or per company, and history is scoped by company through a record rule.

Will an upgrade overwrite the wording I have edited? No. The shipped levels and templates are loaded with noupdate, so your edits survive.

Will you support Odoo 19? A 19.0 branch is planned once 19.0 is released and stable. This release targets 18.0 only and does not claim otherwise.