Automatic unpaid invoice reminders Chasing late invoices
without the awkward call.
Three reminders leave on their own at 7, 15 and 30 days past due — a real email to your client, plus an internal task so you know what went out. The 60-day formal demand stays in your hands.
Three automatic, one deliberate
-
7days past dueAutomatic
A polite nudge
Most late payments are simply forgotten ones. A short, friendly email with the invoice and the payment link recovers a good share of them without any awkwardness.
-
15days past dueAutomatic
A firmer follow-up
The tone tightens. The email restates the amount, the original due date and how many days have passed.
-
30days past dueAutomatic
A formal warning
Thirty days late is no longer an oversight. The internal task is raised to urgent so it stops being invisible in your list.
-
60days past dueYou send it
Formal demand — you decide
A formal demand for payment carries legal weight in Quebec. It never leaves on its own: you send it from the invoice, after a confirmation — or you pick up the phone instead.
A formal demand for payment is a legal instrument in Quebec — it sets a deadline and announces what follows. Software that mails one on your behalf, on a timer, is software that commits you without asking. CRM PME never sends it on a timer: the email is in the software, and you decide whether to send it, from the invoice, after a confirmation.
Five minutes, once
Turn reminders on
Settings → Reminders. One switch. Off by default, because nobody should start emailing your clients without you saying so.
Check the impact first
Before you flip it, an impact panel lists exactly which invoices would be chased and at which stage. Invoices whose client has no email address are flagged separately.
The first two go out on their own
At 7 and 15 days past due, a real email reaches the client and an internal task lands in your list. You see what left, and when.
Day 30 raises the priority
Same mechanism, firmer wording, and the internal task is marked urgent.
You decide on the formal demand
The formal demand is never sent automatically — you send it from the invoice, after a confirmation, and that decision stays yours.
What stops it going wrong
Never the same email twice
Each reminder is recorded against the invoice and the stage, with a uniqueness constraint in the database. If the job runs twice, the client still receives one email.
Only the most advanced due stage is sent per run, so an invoice that has been forgotten for months does not receive three emails on the same morning.
You see the blast radius first
Before you switch reminders on, an impact panel lists the exact invoices that would be chased and at which stage. Nothing is guessed, and nothing leaves before you have looked.
Invoices whose client has no email address are listed separately — they would fail silently otherwise, and a silent failure in collection is the expensive kind.