| Availability |
Odoo Online
Odoo.sh
On Premise
|
| Odoo Apps Dependencies |
•
Discuss (mail)
• Invoicing (account) |
| Lines of code | 334 |
| Technical Name |
no_late_payment_reminders |
| License | OPL-1 |
| Website | https://www.oudayet.com |
| Availability |
Odoo Online
Odoo.sh
On Premise
|
| Odoo Apps Dependencies |
•
Discuss (mail)
• Invoicing (account) |
| Lines of code | 334 |
| Technical Name |
no_late_payment_reminders |
| License | OPL-1 |
| Website | https://www.oudayet.com |
Late Payment Reminders
Auto-chase overdue invoices before they become bad debt.
3 escalation tiers · Daily cron · Bulk action · PDF auto-attached
Odoo 19 $44.99 · OPL-1 For Accounting Teams 9 LanguagesThe "I forgot to chase that invoice" problem
Odoo 19 Community ships zero dunning logic. The Enterprise follow-up addon isn't included. So overdue invoices sit unchased until someone notices the receivables aging report — usually the month after the cash should have arrived. This module adds a daily cron, three escalating templates, and a list-view bulk action.
Without this module
Run aging report Friday afternoon → export to spreadsheet → manually email each customer one by one → lose track of who got what tier → double-email some, ignore others.
With this module
Daily cron sends T1 at day 7, T2 at day 14, T3 at day 30 — per-invoice deduplicated. Or checkbox a row, Action → Send Payment Reminder, done.
Three escalation tiers
"Friendly reminder" tone. Banks are slow, emails get buried — benefit of the doubt before escalating.
"Following up." Asks for a payment date or an issue to resolve. Still polite, no longer optional.
FINAL NOTICE. References previous reminders, sets a firm follow-up expectation. The PDF is attached at every tier.
What you get
One scheduled action handles every overdue invoice at every tier. Per-invoice token tracking prevents duplicates.
Checkbox several invoices, Actions → Send Payment Reminder. Each row gets the next un-sent tier.
Every reminder includes the standard customer invoice PDF, so the customer never has to ask "which one?".
Search filters for "Overdue 7+ / 14+ / 30+ days" plus Group By Reminder Tier turn the regular Invoices list into an aging dashboard.
Subject, body, sender — all editable under Settings → Technical → Email Templates with no code.
Six Python TransactionCase tests cover cron firing, deduplication, draft skipping, no_followup compatibility, and bulk-action escalation.
See It In Action
The dunning workflow lives right inside the standard Invoices view — no new app to learn.
Dunning dashboard. The Invoices list grouped by Reminder Tier, with one-click "Overdue 7+ / 14+ / 30+ days" filters.
One-click bulk send. Tick the overdue invoices, Action → Send Payment Reminder — each gets its next un-sent tier.
Editable templates. The three escalating reminder emails — gentle, firm, final — fully editable, no code.
Per-invoice tracking. Each invoice records its current tier and last-reminder date, so the cron never double-sends.
Technical Details
| Odoo Version | 19.0 Community + Enterprise |
| License | OPL-1 (paid, $44.99 USD) |
| Dependencies | account, mail |
| Override point | account.move._cron_send_payment_reminders() |
| Compatibility | Yields to the standard no_followup flag, so an Enterprise follow-up addon installed later takes precedence automatically. |
Available in 9 Languages
Field labels, search filters and the three reminder email templates speak your customers' language. Each user sees the UI in their own Odoo language setting — no extra setup.
English (en_US)
Français (fr)
Español (es)
Deutsch (de)
Nederlands (nl)
Português (pt_BR)
Italiano (it)
中文 (zh_CN)
العربية (ar)
Installation
1. Download from the Odoo App Store.
2. Extract to your Odoo addons directory.
3. Apps → Update Apps List → Install Late Payment Reminders.
4. The cron is active out of the box. Adjust cadence under Settings → Technical → Scheduled Actions if you want to run it twice a day or weekly.
Found a bug?
Reach out via the Odoo App Store contact form.
Late Payment Reminders — $44.99 — Odoo 19
© Naim OUDAYET — OPL-1
Odoo Proprietary License v1.0 This software and associated files (the "Software") may only be used (executed, modified, executed after modifications) if you have purchased a valid license from the authors, typically via Odoo Apps, or if you have received a written agreement from the authors of the Software (see the COPYRIGHT file). You may develop Odoo modules that use the Software as a library (typically by depending on it, importing it and using its resources), but without copying any source code or material from the Software. You may distribute those modules under the license of your choice, provided that this license is compatible with the terms of the Odoo Proprietary License (For example: LGPL, MIT, or proprietary licenses similar to this one). It is forbidden to publish, distribute, sublicense, or sell copies of the Software or modified copies of the Software. The above copyright notice and this permission notice must be included in all copies or substantial portions of the Software. THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.
Please log in to comment on this module