Customer Payment Follow-up & Dunning

This is a build-to-order module that ECOSIRE designs, builds, installs, and supports specifically for your dunning process — not a one-size download. Technically, we extend the accounting stack with configurable follow-up policies (a custom model carrying per-level day offsets, minimum-balance thresholds, channels, and template links), attach a policy to each res.partner or partner category, and wire a scheduled ir.cron that scans account.move / account.move.line for open, overdue receivables and advances each customer through their escalation ladder. Reminders are dispatched as mail.template emails and, where you use the SMS channel, via Odoo's sms framework; each step is stamped on the record with @api.depends computed fields (days overdue, current dunning level, next action date) so the state is always auditable. Dunning letters are rendered as branded QWeb PDF reports you can theme to your letterhead, and every touch is logged so a customer is never double-chased or escalated past a promise-to-pay hold.

Escalation is genuinely multi-level: a gentle reminder at day 7, a firmer notice at day 30, a formal dunning letter at day 60, and a final-demand / hand-to-legal flag beyond that — with thresholds and copy you define per policy. Automated actions (base.automation) let you fire a task, notify the account owner, or place an account on credit hold when a customer crosses a balance or age limit. Because everything is real Odoo data, the same fields drive filterable list/kanban views, an aged-dunning dashboard, and outbound triggers over the XML-RPC / JSON-RPC API so an external portal or BI tool can read collection status. Access is locked down with ir.model.access.csv plus record rules so collectors see only their assigned accounts and multi-company boundaries are respected.

Build-to-order means we start with a scoping call to map your reminder cadence, letter templates, channels, and approval rules, then deliver a working module on your target Odoo version (17.0, 18.0, or 19.0). We build and test on a staging copy of your database, run UAT with your collections team, and only then install to production with a rollback plan. Typical delivery is 2–4 weeks from confirmed scope depending on how many policies, languages, and integrations you need. You receive the full source, documentation, a training session, and a post-go-live support window — and the git repository is handed to you so you own what we build.