| Availability |
Odoo Online
Odoo.sh
On Premise
|
| Odoo Apps Dependencies |
•
Discuss (mail)
• Invoicing (account) |
| Lines of code | 890 |
| Technical Name |
cons_ai_ar_collections |
| License | OPL-1 |
| Website | https://kabranov.com |
| Availability |
Odoo Online
Odoo.sh
On Premise
|
| Odoo Apps Dependencies |
•
Discuss (mail)
• Invoicing (account) |
| Lines of code | 890 |
| Technical Name |
cons_ai_ar_collections |
| License | OPL-1 |
| Website | https://kabranov.com |
Get paid faster
Every customer with overdue invoices gets a collection dossier with a payment-risk score computed from their real payment history — and the AI drafts the reminder email for you, with escalating tone. You review, you send, you get paid.
Risk-scored work queue
A daily cron turns your overdue receivables into one dossier per customer, scored 0–100 from average days late, late-payment rate, current aging and broken promises. Work the riskiest first.
AI dunning emails
Three tone levels — friendly, firm, final notice — grounded in the customer's actual invoices and payment history, written in the customer's language. Edit, then send via the standard composer.
Promise-to-pay tracking
Log what the customer promised. Kept promises settle the dossier; broken promises are detected automatically and raise the risk score.
Your collections work queue
Kanban by stage with risk badges, or a list with aging buckets (1–30 / 31–60 / 61–90 / 90+) and totals. Filters for high risk, broken promises and 90+ days.
€12,400 overdue · oldest 74 days · 1 broken promise ● 87 High
€5,150 overdue · oldest 41 days · reminded once ● 54 Medium
€1,980 overdue · oldest 12 days · usually pays on time ● 22 Low
One dossier per customer — everything you need to collect
Overdue position, aging, payment history statistics, risk score, reminder history and promises — on one screen, with the overdue invoices one click away.
The AI writes the email. You stay in control.
The draft includes a table of the open invoices and adapts to the customer's history (a loyal early payer gets a different email than a chronic late payer). Sending it stamps the reminder date and moves the dossier forward.
Dear Acme Industries team,
Despite our reminder of 28 May, the following invoices remain unpaid. As your account now includes a balance more than 60 days past due, we kindly ask for settlement within 7 days:
| INV/2026/0142 | due 12 Mar 2026 | €5,200 |
| INV/2026/0177 | due 02 Apr 2026 | €4,750 |
| INV/2026/0203 | due 30 Apr 2026 | €2,450 |
How the risk score works
| Component | Weight | Source |
|---|---|---|
| Payment history | 40% | Average days late and late-payment rate over the last 24 months, from your reconciliations |
| Current overdue aging | 40% | Amount-weighted days overdue of the open invoices |
| Broken promises | 20% | Promises to pay that passed their date unpaid |
100% deterministic and explainable — the score is computed in SQL from your own data, not by the LLM.
FAQ
Does customer data leave my server?
Only when you click "Draft AI Reminder": the customer's open invoice list and payment aggregates are sent to the AI provider you configured. The risk scoring itself runs 100% locally in SQL.
Do I need Odoo Enterprise?
No. The module runs on Odoo 19 Community and Enterprise and replaces the need for the Enterprise follow-up levels with something smarter.
Can the AI send emails on its own?
No — by design. The AI drafts, you review and send. Every send is logged in the chatter and stamps the dossier.
Multi-company? Multi-language?
Yes. Dossiers are per company, and reminders are drafted in the customer's configured language.
Pairs perfectly with the AI Month-End Close Copilot
Both modules share one AI configuration — paste your API key once.
Author & support: Riste Kabranov • Odoo 19 • License: 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