| Availability |
Odoo Online
Odoo.sh
On Premise
|
| Odoo Apps Dependencies |
•
Invoicing (account)
• Discuss (mail) |
| Community Apps Dependencies | Show |
| Lines of code | 3516 |
| Technical Name |
eh_account_credit_limit |
| 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 | 3516 |
| Technical Name |
eh_account_credit_limit |
| License | LGPL-3 |
| Website | https://www.erpheritage.com.au/ |
ERP Heritage · Odoo Accounting Suite
Customer Credit Limit
Hard credit-limit gate at the framework level on customer invoice post, manager override with audit log, per-partner override.
Day in the life
A new customer order would push exposure to 120% of the limit.
The compute exposure live as the SO is being drafted: open AR + draft invoices + not-yet-invoiced confirmed orders, all in company currency (multi-currency lines convert at order date). The status flips to over and shows red on the partner. The hard-block policy refuses the SO confirm. The sales manager opens the override flow: capture a reason, the override creates an immutable log row with the user, exposure at override, limit at override, move amount, and the excess. Audit gets a full chain. Per-partner override on top of the company default lets credit ops dial down problem accounts without affecting the rest.
Overview
What this module does, in one read.
A credit-limit control for Odoo 19 Community. The post action on a customer invoice runs the credit-limit gate; if the partner is over limit the post is blocked. Manager override is explicit and audited.
Per-partner override allows a deployment to set a different limit for an individual partner without changing the company default.
Capabilities
Ten things this module gives you, with no padding.
Hard post gate
On action_post for a customer invoice, the gate checks open exposure plus the new invoice against the limit.
Manager override
The override action is in a separate group; the override writes to an append-only audit log.
Per-partner override
A partner can carry a custom limit that overrides the company default.
Append-only audit
The override log refuses unlink and refuses write on every field except an optional resolution comment.
Computed exposure
Exposure is the sum of unpaid customer invoices plus the new draft total; the compute uses the dynamic-reports SQL builder for consistency.
Plays with portal
The customer portal AR balance card surfaces the current exposure and the limit.
Multi-company aware
Limits and exposures are per company.
Tested invariants
Regression tests cover the over-limit block, the manager override, the per-partner override, and the audit-log append-only enforcement.
Per-company policy configuration
Each company carries its own policy with default limit, override approver, and post-time enforcement mode. Policies are independent per company in a multi-company tenant.
Draft-move inclusion option
Exposure can include or exclude draft moves on a per-policy switch. Conservative tenants count draft commitments; cash-tight ones count posted only.
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.
- Hard post gate (Enterprise ships informational warning)
- Per-override audit row with reason code
- Per-partner override layered on company default
- Computed exposure across open invoices
- Manager override action
- Multi-company scoping
- Limit is in company currency (no per-currency limit yet)
- Override is action-based, not auto-approval-flow
- Limits do not block sales orders by default (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
There are no comments yet!