| Availability |
Odoo Online
Odoo.sh
On Premise
|
| Odoo Apps Dependencies |
•
Discuss (mail)
• Invoicing (account) |
| Community Apps Dependencies | Show |
| Lines of code | 4930 |
| Technical Name |
eh_account_fx_revaluation |
| 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 | 4930 |
| Technical Name |
eh_account_fx_revaluation |
| License | LGPL-3 |
| Website | https://www.erpheritage.com.au/ |
ERP Heritage · Odoo Accounting Suite
FX Period End Revaluation
IAS 21 monthly FX revaluation with auto-reverse on the next period.
Day in the life
Period-end. EUR receivable opened at 1.10. Today it's 1.18.
The revaluation run picks every account flagged eh_fx_revalue with a non-zero foreign-currency residual at period-end. New rate vs. opening rate produces the gain or loss per line. Auto-reverse next-day-of-next-period option means the revaluation does not pollute next period's closing. For sites running hedge accounting under IFRS 9: the cash-flow hedge moves the effective portion to OCI; the fair-value hedge routes everything to P&L; the net-investment hedge follows the same OCI pattern as CFH. Reclassification when the hedged transaction occurs.
Overview
What this module does, in one read.
Period-end multi-currency revaluation for Odoo 19 Community. The wizard fetches non-functional-currency journal items as at the revaluation date, retranslates at the spot rate, and posts the period-end adjustment with optional automatic reversal.
Every run produces a balanced journal entry. Every line is traceable to a source journal item.
Capabilities
Eight things this module gives you, with no padding.
IAS 21 retranslation
Monetary items in non-functional currency are retranslated at the period-end spot rate; the adjustment posts to a configurable gain or loss account.
Auto-reverse
Optional auto-reverse on the first of next period so the trial balance does not carry the revaluation forward into the next period accidentally.
Per-run audit
Every revaluation run is recorded with the rate, date, user, lines covered, and resulting adjustment; the audit log is append-only.
Aggregate by partner
Optional roll-up by partner so the adjustment line is per-partner rather than per-line.
Balanced by construction
The wizard validates the output before posting; mismatches surface explicitly rather than silently.
Per-record savepoint
A per-line savepoint isolates a bad rate or a missing account from the rest of the run.
Multi-company aware
Each run scopes to a single company; runs across companies require explicit re-runs per company.
Tested numerics
Regression tests cover zero-rate edge cases, asset and liability accounts, partner aggregation, and the auto-reverse path.
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.
- Auto-reverse toggle on the run record
- Per-line savepoint inside the run
- Run audit log with rate snapshot
- IAS 21 retranslation methodology
- Aggregate-by-partner option
- Multi-company scoping
- No live rate-feed integration (rates configured on res.currency)
- Hedge accounting not implemented
- One run per (company, date) by unique constraint
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