| Availability |
Odoo Online
Odoo.sh
On Premise
|
| Odoo Apps Dependencies |
•
Invoicing (account)
• Discuss (mail) |
| Community Apps Dependencies | Show |
| Lines of code | 3664 |
| Technical Name |
eh_account_recurring_invoices |
| License | LGPL-3 |
| Website | https://www.erpheritage.com.au/ |
| Availability |
Odoo Online
Odoo.sh
On Premise
|
| Odoo Apps Dependencies |
•
Invoicing (account)
• Discuss (mail) |
| Community Apps Dependencies | Show |
| Lines of code | 3664 |
| Technical Name |
eh_account_recurring_invoices |
| License | LGPL-3 |
| Website | https://www.erpheritage.com.au/ |
ERP Heritage · Odoo Accounting Suite
Recurring Invoices Pro
Cadence-driven recurring invoice engine with per-record savepoint in the cron loop.
Day in the life
Subscription customer base of 320 at month start.
The cadence engine fires on the configured schedule (monthly / quarterly / annually) and creates invoices for every active subscription. Pro-rated mid-period adjustments calculate down to the day. End-of-cycle automation sends the invoice via email template, posts to AR, and awaits payment. Cancellation halts future invoicing. The audit log captures every cycle.
Overview
What this module does, in one read.
Issue recurring invoices on a cadence (daily, weekly, monthly, quarterly, yearly) from a template. The cron iterates due templates and issues one invoice per template under a per-record savepoint so a single broken template never freezes the queue.
On plan change the proration wizard issues a credit plus a new-price invoice in one savepoint and updates the template, so the customer balance is correct without manual journals.
Capabilities
Eight things this module gives you, with no padding.
Cadence engine
Daily, weekly, monthly, quarterly, yearly. Start date and end date or count-based termination; the next-run date moves forward atomically on issuance.
Auto-post or draft
Per template, choose to issue invoices in draft for review or auto-post directly. Mixed templates in the same cron run are isolated.
Subscription proration
On plan change the proration wizard issues a credit plus a new-price invoice and updates the template under one savepoint.
Per-record savepoint
The cron iterates due templates inside a savepoint per template; a single broken template never freezes the rest of the queue.
Atomic next-run advance
Next-run date moves forward via SQL UPDATE on issuance so a concurrent cron run cannot double-issue.
Counts and end conditions
Templates carry a count_total / count_generated pair so a fixed-term subscription terminates automatically.
Multi-company aware
Templates and lines all live under company scope.
Plays with reconciliation
Issued invoices flow through standard reconciliation and the customer statement on the portal.
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.
- Subscription proration wizard with savepoint
- Atomic next-run date advance
- Mixed-template cron isolation
- Cadence-driven generation
- Auto-post or draft option
- Standard reconciliation handover
- No usage-based billing (fixed cadences only)
- No customer self-service plan-change UI yet
- Cron cadence is calendar-relative, not metered
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