| Availability |
Odoo Online
Odoo.sh
On Premise
|
| Odoo Apps Dependencies |
•
Invoicing (account)
• Discuss (mail) |
| Community Apps Dependencies | Show |
| Lines of code | 4468 |
| Technical Name |
eh_account_bank_statement_import |
| 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 | 4468 |
| Technical Name |
eh_account_bank_statement_import |
| License | LGPL-3 |
| Website | https://www.erpheritage.com.au/ |
ERP Heritage · Odoo Accounting Suite
Bank Statement Import
CSV (per-bank profiles) plus OFX plus CAMT.053 with idempotent re-import guard. Live bank connector framework.
Day in the life
Monday morning. 5 banks across 3 currencies. 1,200 statement lines.
The OFX from the US bank, CAMT.053 from the EU bank, MT940 from the SWIFT bank, and CSV from the AU bank all land via separate routes. The framework picks the right parser per file. The duplicate guard refuses to re-import any line that already ran (idempotent on (account, statement reference, amount, date)). The framework stops on bad rows with a precise message rather than silently dropping. Once parsed, statements pop straight into the reconcile workspace for matching. Plaid, Basiq, and the manual stub adapters register against the live-feed cron so future deployments can flip on real-time pulling without changing any view or migration.
Overview
What this module does, in one read.
A bank-statement importer for Odoo 19 Community. Accepts CSV with per-bank column profiles, OFX through the public ofxparse, and CAMT.053 directly against the ISO 20022 element tree.
Re-import guard runs on file hash plus journal scope; per-line unique reference dedup catches the partial-overlap case. The live connector framework lets partner packages plug in named-bank connectors without forking the importer.
Capabilities
Eight things this module gives you, with no padding.
Three formats
CSV with per-bank profiles, OFX through the public ofxparse, CAMT.053 directly against the ISO 20022 element tree.
Per-bank profile
A profile encodes column mapping, date format, decimal separator, currency for the bank.
Idempotent re-import
File hash plus journal scope detects a duplicate import; the duplicate is logged with linkage to the original.
Per-line dedup
Even on partial overlap the unique import ref guards against double-importing a line.
Live connector framework
eh.bank.live.connector.profile plus an abstract LiveBankConnector contract; partner packages register a connector key.
Per-record savepoint
The cron iterates active profiles under a per-record savepoint; one stuck connector never freezes the rest.
Audit on every run
Every import writes an audit row with file hash, user, count, and outcome. Append-only at the framework level.
Multi-company aware
Profiles and statements live under company scope through the journal.
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.
- Idempotent re-import guard with file-hash dedup
- Live connector framework with per-profile savepoint
- Per-line unique-ref dedup
- CSV / OFX / CAMT.053 support
- Per-bank column profiles
- Multi-company scoping
- No bundled bank connectors (framework only, partners ship the bank-specific code)
- OFX uses the public ofxparse library
- No MT940 yet (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