| Availability |
Odoo Online
Odoo.sh
On Premise
|
| Odoo Apps Dependencies |
•
Invoicing (account)
• Discuss (mail) |
| Community Apps Dependencies | Show |
| Lines of code | 4694 |
| Technical Name |
eh_account_sepa_ct |
| 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 | 4694 |
| Technical Name |
eh_account_sepa_ct |
| License | LGPL-3 |
| Website | https://www.erpheritage.com.au/ |
ERP Heritage · Odoo Accounting Suite
SEPA Credit Transfer
PAIN.001.001.03 generator built directly from the ISO 20022 specification with lxml namespace fidelity.
Day in the life
European pay run. 47 vendor bills. PAIN.001.001.09 required.
The batch payment opens 47 bills, aggregates per partner, and queues for confirm. The SEPA Credit Transfer export reads the configured PAIN version on the journal originator (.03 or .09). The XML emits the right namespace: BIC element for .03, BICFI for .09. Validation refuses any bill missing the IBAN; the originator IBAN passes mod-97 ISO 13616 at write time. Single-currency check refuses mixed-currency batches. Download the XML, upload to the bank portal, done. SHA-256 of the file goes on the export record for audit.
Overview
What this module does, in one read.
A SEPA Credit Transfer file generator for Odoo 19 Community. Built from the public ISO 20022 PAIN.001.001.03 specification with lxml so the namespace literal stamps onto the root and tests parse the output back to assert structure.
IBAN is validated mod-97; BIC is validated for structure; amounts round half-up to two decimals.
Capabilities
Eight things this module gives you, with no padding.
PAIN.001.001.03 generation
Targets the published namespace literal. The XML is written under lxml so the namespace stamps on the root.
IBAN and BIC validation
Mod-97 IBAN check, BIC structure check, amount precision validation. Failures surface explicit messages naming the bad field.
Schema-validated tests
Tests parse the rendered output back with lxml and assert on namespace, MsgId, count, sum, every payment block.
Idempotent export
A re-export marks the prior generation as superseded and produces a fresh file; the file hash detects accidental duplicate generation.
Originator config
One originator per journal; the originator carries the IBAN, BIC, initiating party name, and identifier.
Audit log per export
Every export records the user, the time, the file hash, the count, the control sum.
Multi-company aware
Originators, exports, and batches all sit under company scope through the journal.
Built from public spec
No third-party SEPA implementation referenced; every line of the generator is original work.
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.
- Schema-validated round-trip tests
- Idempotent export with audit-log supersession
- Originality from the published ISO spec
- PAIN.001.001.03 namespace fidelity
- IBAN mod-97 + BIC structure validation
- Multi-company scoping through the journal
- No automatic upload to the bank (the file is downloaded and the user delivers it)
- No SCT Inst real-time variant
- Currency hardcoded to EUR per scheme
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