| Availability |
Odoo Online
Odoo.sh
On Premise
|
| Odoo Apps Dependencies |
•
Discuss (mail)
• Invoicing (account) |
| Community Apps Dependencies | Show |
| Lines of code | 5129 |
| Technical Name |
eh_account_collections |
| License | LGPL-3 |
| Website | https://www.erpheritage.com.au/ |
| Availability |
Odoo Online
Odoo.sh
On Premise
|
| Odoo Apps Dependencies |
•
Discuss (mail)
• Invoicing (account) |
| Community Apps Dependencies | Show |
| Lines of code | 5129 |
| Technical Name |
eh_account_collections |
| License | LGPL-3 |
| Website | https://www.erpheritage.com.au/ |
ERP Heritage · Odoo Accounting Suite
Collections Workbench
Kanban workbench with a configurable ladder of follow-up letters and activity scheduling per stage.
Day in the life
DSO is 62 days. Goal is 47.
The auto-create cron walks aged AR and creates one open case per partner with overdue invoices. The kanban surfaces 80 cases across stages: New, Contacted, Promise to Pay, Escalated, Disputed, Resolved. The follow-up engine fires templated reminders on the days-overdue ladder (15-day soft, 30-day firm, 60-day demand). When a customer's promised date lapses, the broken-promise cron escalates the case overnight: priority bump, stage move to Escalated, next follow-up level. Dunning auto-progression handles the routine cases so the collector spends time on the genuinely-disputed ones. DSO drops 8-15 days within the first quarter.
Overview
What this module does, in one read.
A workbench for the collections team. A case is opened per partner with overdue balance; the case progresses through configurable stages; each stage triggers an activity (call, email, letter) and optionally renders a templated letter for download.
The follow-up engine is configurable per company; the kanban groups by stage with badges for overdue days; promises-to-pay are tracked and roll back the case timer.
Capabilities
Ten things this module gives you, with no padding.
Kanban workbench
One column per stage, one card per case, drag to advance. Color and badge surface case priority based on configurable thresholds.
Configurable letter ladder
A deployment encodes its house style: friendly reminder, second notice, demand letter, legal handover. Each stage defines the activity scheduled and the letter rendered.
Promise-to-pay
A partner promise pauses the case timer and surfaces on the card. Missed promises trigger an automatic re-escalation.
Activity scheduling
Each stage can schedule a call, email, or to-do on the case as it advances; activities live on standard Odoo mail.activity infrastructure.
Templated letters
PDF letters render through the same brand-footer template as the rest of the suite. Download or attach to the case.
Per-cron savepoint
The age-and-escalate cron processes cases under a per-record savepoint; one stuck partner cannot freeze the rest of the queue.
Multi-company aware
Cases, stages, and templates all sit under company scope; record rules enforce per-company isolation.
Audit on stage change
Every stage change is logged on the chatter so a reviewer can trace how the case moved.
Pause auto follow-ups per case
A case can be paused with a reason and a resume date. Auto follow-ups respect the pause; the pause itself is logged so the audit trail explains why a stage stalled.
Auto creation from aged AR
A cron seeds cases for partners whose aged receivables cross the configured bucket. New invoices on existing cases extend the case rather than creating a duplicate.
Compared
How this module stacks up.
Workflow
Configure once. Operate. Audit. Report.
Four steps, the same across every ERP Heritage module so a finance team learns the suite once.
Configure
Settings > Accounting > ERP Heritage. Multi-company, multi-currency, journals, accounts. One-time setup, persisted on the company record.
Operate
The user works inside the standard Odoo accounting flow. The module surfaces only the controls relevant to its scope.
Audit
Every action that changes accounting state writes an audit row. The audit log is append-only at the framework level.
Report
Reports flow through the same reproducible audit pipeline, with cache invalidation by per-company move version.
Why Heritage
Where this module leads, where it matches, what we are honest about.
- Configurable letter ladder per company
- Promise-to-pay tracking with automatic re-escalation
- Per-cron savepoint isolation
- Kanban workbench
- Activity scheduling on standard mail.activity
- PDF letter render
- No SMS provider integration (deployment plugs its own)
- Letter copy is deployment-specific
- No automatic dispute escalation (roadmap)
The full ERP Heritage Accounting Suite (26 modules)
Engineering
Ten engineering rules we hold ourselves to.
No silent fallbacks.Missing config, missing accounts, malformed input each surface explicit messages naming the bad field.
Tests cover the bug, not just the feature.Every defect found in review has a regression test attached to the fix, kept in the repository.
Plain Python where possible.Algorithms that do not need the ORM live under tools/ with unit tests that run without Odoo.
Atomic counters via SQL.Concurrent counters use UPDATE col = col + 1, never read-modify-write loops.
Per-record savepoints in cron loops.A single bad record never freezes the batch; failing rows are recorded, the rest of the batch keeps moving.
Schema-first XML output.PAIN.001 and PAIN.008 generators target the published namespace; tests parse output back and assert structure.
ValidationError versus UserError.Constraint failures raise ValidationError; action failures raise UserError with a remedy.
Privilege groups, not direct upstream references.ACL CSVs reference suite-specific groups; the post-migration script promotes upstream-only users.
Append-only audit logs.Approval log, override log, reconciliation audit, mandate amendment log all override write and unlink at the model level.
Originality from public spec.Every standard implementation is built from the published technical specification, not from another vendor codebase.
The standard we hold: every shipped capability is original code from a public technical specification, with regression tests, with a documented engineering rule for the invariant the code preserves, and with no vendor names in code or user-facing docs. From the suite contributing process
Frequently asked questions
Honest answers to the questions a buyer asks.
Does this run on Odoo 19 Community?
Yes. Every module is built and tested against Odoo 19 Community. No Enterprise dependency anywhere in the stack.
What is the licence?
LGPL-3, the same licence as Odoo Community. You can read the source, modify it, and ship it inside your own Odoo deployment without restriction.
Will this conflict with another accounting addon I already use?
Probably not. The modules add new models in their own namespace (eh.*) and inherit standard models without overriding behaviour silently. If your existing addon also extends the same standard model, ordinary Odoo inheritance rules apply.
Are the engineering principles documented?
Yes. The contributing process and ten engineering rules are kept in the repository so a reviewer can verify the code holds itself to them.
Is there a test suite?
Yes. Every module ships its own integration tests; the engine module ships a full unit test suite for the SQL builder, cache, and report orchestrator.
How do I get support?
Reach the team via info@erpheritage.com.au. Training, deployment, and custom extension work is handled by ERP Heritage directly.
Built by ERP Heritage
ERP Heritage builds enterprise-grade accounting software for the Odoo community. Our suite covers the operational accounting cycle end to end: invoice intake, posting, reconciliation, reporting, period close, payment runs, customer portal, multi-step approvals, and year-end. Every module ships with explicit licensing posture, documented engineering principles, comprehensive tests, and a clear differentiation story.
Ready to deploy?
Install this module, run the test suite, and inspect the structured audit log. For training, deployment, or a custom extension, reach our team.
Talk to ERP Heritage about Odoo implementation, customisation, training, or support.
End-to-end engagement across the Odoo platform: implementation, customisation, reimplementation, functional and technical training, ongoing support, integration planning, and scoped extensions. One team, one response within a business day.
Please log in to comment on this module