Configuration

Every setting in Customer Payment Reminders, and what each one changes.

Everything the module does is driven by two things: the settings, and the reminder levels. There is nothing else to set up.

Settings

Invoicing → Configuration → Settings → Customer Payments → Payment Reminders.

Setting	What it does
Chase Overdue Customers	The master switch. Off, the daily run does nothing at all. Reminders can still be sent by hand.
Do not chase below	A minimum outstanding amount. A customer whose total overdue is under it is skipped, and the interface says so. Leave at 0 to chase everything.

The block also shows two live counts — how many customers are overdue, and how many are due a reminder today — with links straight to both lists. Read those before you switch anything on.

The minimum is compared against the customer's total overdue, not against each invoice. Somebody with six invoices of £3 is chased once for £18; that is usually what you want.

Reminder levels

Invoicing → Customers → Payment Reminders → Reminder Levels. (Credit Manager only.)

A level is a threshold plus what happens when it is crossed.

Field	Meaning
Name	Shown in the history and on the customer. Make it recognisable — "Final notice (60 days)" beats "Level 3".
Days Overdue	How many days past due the customer's oldest overdue invoice must be.
Then	Send an email, Schedule an activity, or Both.
Email Template	Required for email levels. Rendered against the customer, with the overdue invoices listed.
Attach the Invoices	Attaches a PDF of each overdue invoice. On by default for the first level.
Activity Type	Defaults to Call.
Assign To	Leave empty to use the customer's salesperson — usually the person who can actually get it paid.
Activity Summary	The activity's title.
Company	Leave empty for a level every company uses.
Internal Note	Why this level exists, for whoever inherits it.

The three shipped levels

	Days	Action	Attaches
First reminder	7	Email	Yes
Second reminder	30	Email	Yes
Final notice	60	Email and a scheduled call	Yes

They assume it was simply missed at 7 days, that it was not at 30, and that a person should be involved at 60. Change the thresholds to match how your trade actually behaves — 7/30/60 suits monthly terms and is wrong for weekly ones.

Rules the module enforces

Days cannot be negative. A reminder before the invoice is due is not a reminder.
No two levels a company can see may share a day count. They would fight over which applies, and the winner would be whichever the database returned first. Note this includes a company-specific level clashing with a global one.
An email level needs a template; an activity level needs an activity type.
Archiving a level takes it out of the escalation without deleting the history that refers to it.

Adding a level

Levels are just records — add a 90-day one, or a 3-day "your invoice is due tomorrow" if your terms suit it. A new level slots into the escalation by its day count; nothing else needs changing.

Editing the wording

The shipped templates are deliberately plain and slightly formal. They are not your voice, and a dunning letter that does not sound like you is worse than none.

Reminder Levels → (a level) → Email Template → Internal link.

The template renders against res.partner with the overdue invoices available, so it can list them, total them, and name your payment details. Send one to yourself before you send it to a customer.

Per-customer settings

A customer form → Payment Reminders tab.

Field	Who	Meaning
Pause Until	Credit Controller	Stop chasing until a date. A reason is required — a silent pause is one nobody can explain three weeks later. Clears itself when the date passes.
Pause Reason	Credit Controller	Free text. Shows in the skip explanation.
Never Chase	Credit Manager	Permanent exclusion, for accounts handled elsewhere. Deliberately manager-only.
Responsible	Credit Controller	Who gets the activities for this customer. Falls back to the salesperson.

The tab also shows the overdue total, the current level, when they were last chased, and every reminder ever sent to them.

Scheduled actions

Settings → Technical → Scheduled Actions.

Action	Every	Does
Payment Reminders: Chase Overdue Customers	1 day	The actual sending. Honours the master switch.
Payment Reminders: Refresh Levels	1 day	Keeps the level shown on each customer in step with reality. Sends nothing.
Payment Reminders: Prune History	30 days	Deletes reminder history older than three years.

Set the chase to run at an hour your customers will read — mid-morning beats 02:00, and Monday beats Friday afternoon.

Multi-company

Levels with no company are shared. Levels with a company apply only there, and a company-specific level cannot duplicate a shared one's day count. History is scoped by company through a record rule, so a user only sees reminders for their own companies.