Skip to Content

Ageing Alerts for Customers & Vendors

by
Odoo

$ 25.00

v 17.0 Third Party
Availability
Odoo Online
Odoo.sh
On Premise
Odoo Apps Dependencies • Discuss (mail)
• Invoicing (account)
Lines of code 313
Technical Name ageing_alerts
LicenseOPL-1
Websitehttps://www.techultrasolutions.com
Versions 17.0 18.0 19.0
You bought this module and need support? Click here!
Availability
Odoo Online
Odoo.sh
On Premise
Odoo Apps Dependencies • Discuss (mail)
• Invoicing (account)
Lines of code 313
Technical Name ageing_alerts
LicenseOPL-1
Websitehttps://www.techultrasolutions.com
Versions 17.0 18.0 19.0

Ageing Alerts for Customers & Vendors

The Ageing Alerts for Customers & Vendors module enhances accounting with an intelligent ageing-alert system that monitors outstanding customer invoices and vendor bills. It evaluates overdue documents, assigns risk levels, and produces actionable insights to support financial decision-making.

The module strengthens credit control, reduces payment delays, and improves cash-flow visibility by transforming raw ageing data into clear operational alerts.

https://wa.me/message/VENRAJRHMSWEB1 OR
Email Us Skype Us
  • Advanced ageing analysis
  • Intelligent alert engine
  • Automated daily monitoring
  • Seamless visibility inside Odoo
  • Configurable Alert Controls
  • Support for Customer and Vendor Workflows

1. Customer Configuration.

Setting -> General Settings
After installing the "Ageing Alerts for Customers & Vendors" module, you will be able to access this section where you can configure the settings according to your requirements. In this example, we have configured a customer with a due amount limit of 500 and a period of 1 day. The Critical Ageing Alert is set with a minimum amount of 250,000 and 60 days, the High Ageing Alert is set with a minimum amount of 100,000 and 45 days, and the Medium Ageing Alert is set with a minimum amount of 50,000 and 30 days.

2. John Customer Invoice.

Here, you can see that we have created an invoice with a due date of September 9, 2025, and a due amount of 233,500.

3. John Customer Alert Message.

Here, you can see that an Alert Message has been created in the chatter box of the customer.

4. Vendor Configure.

Now, we have configured a vendor with the same due amount limit of 500 and a cooldown period of 1 day. The Critical Ageing Alert is set with a minimum amount of 250,000 and 60 days, the High Ageing Alert is set with a minimum amount of 100,000 and 45 days, and the Medium Ageing Alert is set with a minimum amount of 50,000 and 30 days.

5. Sam Vendor Bill.

Here, you can see that we have created a bill of 11 Sep 2025 due date with 800 due amount.

6. Sam Vendor Alert Message.

Here, you can see that an Alert Message has been created in the chatter box of the Vendor.

6. Customer and Vendor Configure.

Here, you can see that we have configured both the vendor and the customer with the same due amount limit of 500 and cooldown period of 0 day. The Critical Ageing Alert is set with a minimum amount of 250,000 and 60 days, the High Ageing Alert is set with a minimum amount of 100,000 and 45 days, and the Medium Ageing Alert is set with a minimum amount of 50,000 and 30 days.

7. Tony Customer Invoice.

Here, we have created an invoice for Tony customer with a due date of August 27 and a due amount of 551,800.

8. Tony Vendor Bill.

Here, we have created a bill for Tony customer with a due date of August 31 and a due amount of 649,500.

9. Customer & Vendor Alert Message.

Ageing alerts have been created for both the customer and the vendor, in accordance with your configured cooldown period.

  • We are provide 90 days bug free support related to our module.
  • The support team is available from Monday to Friday 10:00 AM to 07:00 PM (IST).
  • To create ticket send email to support@techultra.in.

What problem does this module solve?

It improves financial oversight by identifying overdue invoices and vendor bills early and delivering actionable alerts.

Does it work for both customers and vendors?

Yes, It evaluates overdue customer invoices and overdue vendor bills.

Do alerts appear automatically?

Yes, The cron job checks overdue documents every day and creates new alerts according to your alert cooldown day configure.

Can I adjust the rules or thresholds?

Yes, you can update settings.

Is the cooldown applied per transaction type or per partner?

Cooldown is applied per partner, not per type. This ensures a single alert cycle per partner per day, even if multiple types of overdue entries exist.

When does the module create a new alert after the cooldown period?

A new alert is generated once the number of days since the last alert is equal to or greater than the configured cooldown days.
Example: Cooldown = 1 day -> Next alert appears after 24 hours or the next cron run.

Can I disable the alerts?

Yes, you can disable alerts in the Settings.

Can I receive alerts for only customer or only vendor overdue amounts?

Yes, you can enable or disable each type using the configuration options in Settings:
* Enable Customer Ageing Alerts
* Enable Vendor Ageing Alerts



Related Products


Our Apps 
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

  • The author can leave a single reply to each comment.
  • This section is meant to ask simple questions or leave a rating. Every report of a problem experienced while using the module should be addressed to the author directly (refer to the following point).
  • If you want to start a discussion with the author or have a question related to your purchase, please use the support page.