| Availability |
Odoo Online
Odoo.sh
On Premise
|
| Odoo Apps Dependencies |
•
Discuss (mail)
• Invoicing (account) |
| Lines of code | 38 |
| Technical Name |
amadio_account_invoice_reminder |
| License | OPL-1 |
| Website | https://amadio.io |
| Availability |
Odoo Online
Odoo.sh
On Premise
|
| Odoo Apps Dependencies |
•
Discuss (mail)
• Invoicing (account) |
| Lines of code | 38 |
| Technical Name |
amadio_account_invoice_reminder |
| License | OPL-1 |
| Website | https://amadio.io |
Automated AR Invoice Reminder Engine
Configure multi-stage dunning sequences with escalating tone and send automated overdue reminders — with a complete audit trail on every invoice.
The Challenge
Why organizations need Automated AR Invoice Reminder Engine
AR teams have hundreds of overdue invoices but no systematic process for following up. Reminders are sent inconsistently — or not at all — based on individual initiative.
AR staff manually draft reminder emails, find the right invoice, and send them one by one. Hours of their time each week goes to a process that could be fully automated.
Day-1 reminders sound the same as day-30 reminders. Without escalating tone and escalation contacts, customers learn they can ignore initial reminders indefinitely.
What Automated AR Invoice Reminder Engine Does
Six capabilities built specifically for this problem
Multi-Stage Reminder Sequences
Define sequences with multiple stages — e.g., friendly reminder at day 7, firm notice at day 14, final demand at day 30 — each with its own email template.
Escalating Tone per Stage
Each stage uses a different email template, allowing naturally escalating language from friendly to formal to final notice — appropriate for each point in the collection cycle.
Escalation Contacts
Late stages can CC internal contacts (credit manager, sales rep) and external escalation parties — ensuring the right people are aware as accounts age.
Pause per Partner
Individual customers can be marked reminder_paused — suspending all automatic reminders without affecting other customers or the sequence configuration.
Per-Invoice Audit Log
Every reminder sent is logged on the invoice record: which stage, sent by whom, on what date, and any notes. The audit trail is permanent.
Daily Automation
A scheduled job runs daily, scanning all overdue invoices, matching them to their partner's reminder sequence, and sending the appropriate stage automatically.
How It Works
Operational in minutes — not weeks
Build Your Dunning Sequence
Go to Accounting → AR Reminders → Sequences. Create a sequence with stages — set days-overdue trigger and assign an email template to each stage.
Assign to Customers
On each customer's contact record, select their reminder sequence (or leave blank for the default). Individual customers can be paused if needed.
Let the Cron Run
The daily job scans overdue invoices, matches to sequences, sends the next applicable stage, and logs the action on the invoice. No manual follow-up required.
Perfect For
Industries and organizations that rely on Automated AR Invoice Reminder Engine
B2B Service Businesses
Consulting firms, agencies, and professional service providers with net-30/60 terms need systematic follow-up to maintain cash flow without damaging relationships.
Distributors & Wholesalers
High-volume B2B distributors with hundreds of customer accounts need automated AR follow-up that scales — not a manual process dependent on individual AR staff.
Healthcare & Professional Practices
Medical practices, law firms, and other professional services billing insurance and patients need compliant, trackable follow-up on aging receivables.
Technical Specifications
Compatibility and deployment details
| Odoo Version | 18.0 |
|---|---|
| Platform | Odoo.sh & On-Premise |
| License | OPL-1 |
| Author | AMADIO |
| Support | info@amadio.io |
| Website | amadio.io |
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