| Availability |
Odoo Online
Odoo.sh
On Premise
|
| Odoo Apps Dependencies |
•
Invoicing (account)
• Discuss (mail) |
| Lines of code | 73 |
| Technical Name |
customer_due_notification |
| License | AGPL-3 |
| Website | https://odooleap-solutions.odoo.com |
| Availability |
Odoo Online
Odoo.sh
On Premise
|
| Odoo Apps Dependencies |
•
Invoicing (account)
• Discuss (mail) |
| Lines of code | 73 |
| Technical Name |
customer_due_notification |
| License | AGPL-3 |
| Website | https://odooleap-solutions.odoo.com |
Customer Due Notification
Instantly flag overdue customer balances at the start of the sales cycle
The Customer Due Notification module automatically calculates a customer's total outstanding overdue invoices and displays a clear warning banner at the top of the Sales Order form view. To ensure strict data privacy, exact overdue amounts are visible only to authorized users, while others receive a generic warning.
Key Features
Immediate Warnings
Shows a warning banner at the very top of Sales Orders when a customer has outstanding overdue invoices, avoiding bad debts.
Granular Permissions
A new security group Overdue Amount Viewer controls who sees exact numbers. Non-group users only see a generic warning.
Fully Optimized
Computes overdue amounts on-the-fly directly from account.move using aggregated SQL queries, avoiding database pollution.
Parent-Child Aggregation
Automatically includes overdue amounts from all child contacts linked to the main commercial partner.
How It Works & Screenshots
1. Sales Order Overdue Warning (Authorized View)
Users with Overdue Amount Viewer permission see the exact outstanding overdue amount highlighted in the banner at the top of the sales order.
2. Configure Viewer Access Rights
Assign the Overdue Amount Viewer group to selected sales or accounting users in the User settings.
Compatibility
- Tested with Odoo 19.0
Support
For questions, customization requests, or technical support, please get in touch with us:
Email: odooleap@gmail.com
Website: odooleap-solutions.odoo.com
Please log in to comment on this module