| Availability |
Odoo Online
Odoo.sh
On Premise
|
| Odoo Apps Dependencies |
•
Invoicing (account)
• Discuss (mail) |
| Community Apps Dependencies | Show |
| Lines of code | 5355 |
| Technical Name |
eh_account_reconcile_pro |
| 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 | 5355 |
| Technical Name |
eh_account_reconcile_pro |
| License | LGPL-3 |
| Website | https://www.erpheritage.com.au/ |
ERP Heritage · Odoo Accounting Suite
Bank Reconciliation Pro
Reconciliation widget plus a user-defined rules engine. Five-signal scorer, atomic counters on rule fire-count, append-only override audit.
Day in the life
1,200 statement lines on the bank import. 940 auto-match.
The reconciliation workspace loads the statement. The suggestion engine scores each line against open AML rows: amount + date + reference text similarity + partner match. 940 land at confidence > 0.80 and auto-apply. The remaining 260 surface in the workspace with the suggestion ranked by confidence. The user-defined rules engine catches the bank-charge pattern automatically. The audit log records every match decision with the rules that fired and the confidence score. Closes the bank reconciliation in under an hour for a month that took half a day.
Overview
What this module does, in one read.
A pro reconciliation experience for Odoo 19 Community. The widget loads bank statement lines, runs the suggestion engine, and presents the operator with scored matches.
Every override is recorded. Every rule that fires bumps an atomic counter. Sessions and lines all live under company scope; the rules are user-editable and versioned.
Capabilities
Ten things this module gives you, with no padding.
Suggestion engine
Five-signal scorer combines amount, partner, reference, date proximity, and historical pattern. Suggestions are ranked; the operator confirms or overrides.
User-defined rules
Patterns the operator encodes for the deployment. Scope, partner, regex on memo, amount window, optional date offset. Rules carry a boost so reliable patterns rank higher.
Atomic fire-count
Each rule has a fire_count that increments via SQL UPDATE so a heavily-fired rule cannot lose increments under concurrent reconciliation.
Append-only override audit
When the operator overrides a suggestion the override is recorded with the user, the time, and the reason. The override log refuses write and unlink at the model level.
Workspace UI
OWL widget renders the lines list, the scored matches, and the override controls in one panel; per-session counters track work-in-progress.
Multi-company aware
Sessions are scoped to a journal which is scoped to a company. Record rules enforce that an operator only sees their own company workspaces.
Per-session savepoint
Each accept-suggestion writes through under a savepoint so a failed write rolls back only that match, never the whole session.
No vendor heuristics
Every rule is user-defined and stored in the database; no opaque black-box heuristic pretends to be smart on the operator behalf.
Reconciliation model application
Saved reconciliation models can be applied in bulk against staged statement lines. The application records which model fired, on which lines, and the resulting confidence.
Capped page size pagination
The workspace caps page size to a configurable maximum so a large statement never freezes the browser. Operators page through suggestions without the server fanning out to thousands of lines.
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.
- User-defined rules engine with five-signal scorer
- Atomic SQL counter on rule fire-count
- Append-only override audit log model
- Workspace UI with virtual scrolling
- Per-session savepoint
- Multi-company scoping
- Rules are deployment-specific (no shipped catalogue)
- Suggestions are heuristic-only, no machine-learned ranker yet
- Bank statement import lives in its own module
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