| Availability |
Odoo Online
Odoo.sh
On Premise
|
| Odoo Apps Dependencies |
•
Invoicing (account)
• Discuss (mail) |
| Community Apps Dependencies | Show |
| Lines of code | 6107 |
| Technical Name |
eh_account_sepa_dd |
| 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 | 6107 |
| Technical Name |
eh_account_sepa_dd |
| License | LGPL-3 |
| Website | https://www.erpheritage.com.au/ |
ERP Heritage · Odoo Accounting Suite
SEPA Direct Debit
PAIN.008 plus full mandate lifecycle (FRST / RCUR / FNAL / OOFF / dormancy). Atomic consume-for-collection.
Day in the life
200 SEPA Direct Debit mandates across two schemes (CORE + B2B).
The mandate registry tracks every signed mandate with its status: draft, active, expired, cancelled, amended. The sequence flag (FRST / RCUR / OOFF / FNAL) auto-flips on the first collection (FRST) and subsequent ones (RCUR). The 36-month dormancy check expires inactive mandates automatically. Amendment table preserves the original mandate when key terms change. PAIN.008 export at scheme = CORE produces the right XML; B2B produces the alternate flavour. Sites need the mandate paperwork on file; the module manages the lifecycle, sequencing, and XML generation.
Overview
What this module does, in one read.
SEPA Direct Debit for Odoo 19 Community. Full mandate lifecycle including the 36-month dormancy rule from the EPC rulebook; atomic consume-for-collection so the FRST to RCUR counter cannot lose increments under concurrent collection.
Mandate amendments are tracked in an append-only log so the audit trail can show the IBAN at the point of every collection.
Capabilities
Ten things this module gives you, with no padding.
PAIN.008 generation
Targets the published namespace literal. Per sequence type one file per export; the audit log records each.
Mandate lifecycle
Draft, active, completed, revoked, expired. Transitions are guarded.
Atomic consume
On collection the mandate consume bumps the FRST to RCUR counter via SQL UPDATE so concurrent collections cannot lose an increment.
36-month dormancy
The dormancy cron expires mandates with no collection in the last 36 months per the EPC rulebook.
Mandate amendment audit
Every IBAN amendment writes an audit row recording the prior IBAN, the user, the time, the reason.
Per-record savepoint
The export iterates posted payments under a per-record savepoint.
Multi-company aware
Mandates, creditors, exports, and batches sit under company scope.
Built from public spec
PAIN.008 generator written from the published ISO 20022 schema.
CORE and B2B local instruments
Mandates carry a local-instrument tag for CORE or B2B. The exporter routes the right XML element so banks accept the file on the first send.
FRST RCUR FNAL OOFF transitions
The mandate sequence type is computed automatically across the lifecycle: first collection becomes FRST, recurrings become RCUR, final becomes FNAL, and one-offs are tagged OOFF.
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 consume-for-collection counter
- Mandate amendment append-only log
- 36-month dormancy cron with savepoint
- Full FRST/RCUR/FNAL/OOFF lifecycle
- PAIN.008 namespace fidelity
- Multi-company scoping
- No real-time direct debit variant (SDD-Inst not in scheme)
- No SMS confirmation flow
- Pre-notification follows configurable lead time
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