| Availability |
Odoo Online
Odoo.sh
On Premise
|
| Odoo Apps Dependencies |
•
Discuss (mail)
• Inventory (stock) • Invoicing (account) • Purchase (purchase) |
| Community Apps Dependencies | Show |
| Lines of code | 4309 |
| Technical Name |
eh_account_ap_automation |
| License | LGPL-3 |
| Website | https://www.erpheritage.com.au/ |
| Availability |
Odoo Online
Odoo.sh
On Premise
|
| Odoo Apps Dependencies |
•
Discuss (mail)
• Inventory (stock) • Invoicing (account) • Purchase (purchase) |
| Community Apps Dependencies | Show |
| Lines of code | 4309 |
| Technical Name |
eh_account_ap_automation |
| License | LGPL-3 |
| Website | https://www.erpheritage.com.au/ |
ERP Heritage · Odoo Accounting Suite
Vendor Bill Automation
Vendor bill intake with three-way match (PO, goods receipt, invoice), tolerance profiles per partner, regex parser, append-only override audit.
Day in the life
100 vendor bills land Monday morning. Three of them are duplicates.
The mail alias drops every incoming bill into the intake inbox as PDFs. The regex parser pulls vendor reference and total from each. The duplicate detector hashes (vendor, ref, amount, date) and flags two bills that arrived twice and one that already posted last week. The three-way match against the open POs surfaces a quantity exception on a fourth bill. The bookkeeper resolves the four flagged cases first; the remaining 96 auto-post in a single batch. Total time: under an hour vs. half a day of manual entry.
Overview
What this module does, in one read.
A vendor bill intake pipeline. Bills arrive via email or upload; the regex parser recognises supplier, total, due date; the three-way match validates against the matching purchase order and goods receipt.
The extractor adapter is pluggable: a partner package can register its own OCR or LLM-based line extractor without forking the suite. By default the regex parser ships and no remote calls are made.
Capabilities
Eight things this module gives you, with no padding.
Email-to-bill alias
Bills arrive as email attachments; the alias creates an intake row and parses the body for supplier and total.
Three-way match
The match validates qty and price against the PO line and the goods receipt; over-tolerance breaks pop into exception state with the explicit reason.
Tolerance profiles
Per-partner tolerance profiles encode the deployment policy; defaults ship as demo data.
Regex parser
A pure-Python parser recognises supplier, total, due date from the raw text. Confidence is recorded on the intake.
Pluggable extractor
Partner packages can register an OCR or LLM line extractor; the suite ships no built-in remote dependency.
Append-only override audit
When the operator overrides a tolerance breach the override is recorded with reason; the audit log refuses write and unlink.
Multi-company aware
Intakes, profiles, and matches all sit under company scope; partner email resolution scopes to the active company.
Plays with batch payment
Posted bills flow into the batch payment selection so the team pays the matched bills in one batch.
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.
- Three-way match with explicit exception state
- Pluggable extractor adapter (OCR / LLM-ready)
- Append-only override audit log
- Email alias intake
- Tolerance profiles per partner
- Standard purchase + receipt linkage
- No default OCR shipped (deployment chooses)
- Regex parser is a baseline, partner packages add depth
- No automatic payment scheduling on post
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