| Availability |
Odoo Online
Odoo.sh
On Premise
|
| Odoo Apps Dependencies |
•
Invoicing (account)
• Discuss (mail) |
| Community Apps Dependencies | Show |
| Lines of code | 3619 |
| Technical Name |
eh_account_batch_payment |
| 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 | 3619 |
| Technical Name |
eh_account_batch_payment |
| License | LGPL-3 |
| Website | https://www.erpheritage.com.au/ |
ERP Heritage · Odoo Accounting Suite
Batch Payment
Batch AR / AP payment runs with per-partner aggregation, CSV export, per-payment savepoint isolation.
Day in the life
Friday pay run. 47 vendor bills. Five different banks.
The wizard groups every open bill above the threshold into one batch, aggregates per partner so a vendor with three bills gets one payment line, and queues the batch for the controller. Confirm locks the batch from member edits. Post fires per-payment savepoints so a single bad partner record never freezes the whole batch. CSV export goes to the bank portal. The full audit trail (confirmed at, posted at, cancelled at, with user) sits on the batch header. Total: under 30 minutes for the run that took half a day before.
Overview
What this module does, in one read.
A payment-run module for Odoo 19 Community. Group invoices for a partner, set the payment date, post the batch; per-payment savepoint isolation means one broken payment never freezes the rest.
CSV export ships out of the box; the SEPA Credit Transfer module adds PAIN.001 generation; the SEPA Direct Debit module adds PAIN.008 with the mandate lifecycle.
Capabilities
Nine things this module gives you, with no padding.
Per-partner aggregation
Pick invoices for a partner, set the payment date, the batch creates one payment per partner.
Per-payment savepoint
Action_post wraps each payment in a savepoint; one broken payment is recorded and the rest of the batch posts.
CSV export
Plain CSV ships out of the box; downstream SEPA modules add PAIN.001 and PAIN.008 over the same batch.
Reconciliation handover
Batch posts reconcile the invoices and emit the bank-statement-ready CSV in one shot.
Inbound and outbound
Inbound batches collect (used by SEPA Direct Debit); outbound batches pay (used by SEPA Credit Transfer).
Multi-company aware
Batches and payments live under company scope.
Audit per batch
Every batch carries a chatter-tracked audit history; failed payments record the reason for review.
Plays with collections
Batches feed the collections case timeline when promises-to-pay are recorded.
Manager guard on post and cancel
Posting and cancelling a batch are restricted to the accounting manager group. Operators can build and stage batches; only the manager flips the post or cancel switch.
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.
- Per-payment savepoint inside batch post
- Inbound + outbound batches with the same model
- Foundation for SEPA CT + DD modules
- Per-partner aggregation
- CSV export
- Multi-company scoping
- No payment-provider integration (CSV / SEPA only)
- No printing template (deployment owns layout)
- Payment ordering by invoice due date
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