| Availability |
Odoo Online
Odoo.sh
On Premise
|
| Odoo Apps Dependencies |
•
Invoicing (account)
• Discuss (mail) |
| Community Apps Dependencies | Show |
| Lines of code | 3324 |
| Technical Name |
eh_account_intercompany |
| 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 | 3324 |
| Technical Name |
eh_account_intercompany |
| License | LGPL-3 |
| Website | https://www.erpheritage.com.au/ |
ERP Heritage · Odoo Accounting Suite
Inter-Company Rules
Auto-mirror sale on company A to purchase on company B with full chatter trail.
Day in the life
AU sub invoices NZ sub. Mirror entries auto-generated.
The AU Pty Ltd posts a customer invoice for AUD 50k to NZ Holdings Ltd. The IC rule fires: a corresponding vendor bill is created in the NZ company in the matching currency at the day's rate. Both sides are linked to the source invoice via eh_ic_mirror. Period-end, the consolidation entity (eh_account_consolidation) pulls both sides; the IC elimination journal cancels them out so the consolidated TB shows neither leg. Multi-company aware throughout; the rule supports per-company-pair routing for groups with more than two entities.
Overview
What this module does, in one read.
Inter-company rules for Odoo 19 Community. When a sale is posted on company A and the customer is a sister company, the mirror purchase is created on company B atomically; chatter trail captures the link on both sides.
No silent fallback: if the mirror cannot be created the original post fails with the explicit reason rather than silently leaving the sister company without the matching purchase.
Capabilities
Eight things this module gives you, with no padding.
Auto-mirror
Sale on A becomes purchase on B (and vice versa for purchase to sale) atomically on post.
sudo + with_company
The mirror is created under the destination company context with sudo so the operator does not need cross-company permissions.
Chatter trail
Both sides record the linkage in chatter; an auditor can trace the matching pair from either side.
No silent fallback
Missing journals, missing products, missing partners surface explicit messages; the original post fails clean.
Per-company configuration
Rules are per source company; a deployment encodes A and B separately so the rule is explicit.
Plays with reconciliation
The mirror invoices reconcile through the standard accounts-receivable / accounts-payable flow.
Multi-company aware
Rules and mirrors all sit under company scope.
Tested invariants
Regression tests cover the success path, the missing-journal path, and the partner-on-both-sides edge case.
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.
- Atomic mirror with sudo + with_company on post
- Explicit failure when mirror config is incomplete
- Audit linkage on both sides
- Sale-to-purchase auto mirror
- Per-source-company rules
- Standard reconciliation handover
- No automatic transfer pricing layer
- No multi-currency conversion built into the mirror
- One mirror per source move
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