| Availability |
Odoo Online
Odoo.sh
On Premise
|
| Odoo Apps Dependencies |
•
Discuss (mail)
• Invoicing (account) |
| Community Apps Dependencies | Show |
| Lines of code | 4283 |
| Technical Name |
eh_account_pdc |
| License | LGPL-3 |
| Website | https://www.erpheritage.com.au/ |
| Availability |
Odoo Online
Odoo.sh
On Premise
|
| Odoo Apps Dependencies |
•
Discuss (mail)
• Invoicing (account) |
| Community Apps Dependencies | Show |
| Lines of code | 4283 |
| Technical Name |
eh_account_pdc |
| License | LGPL-3 |
| Website | https://www.erpheritage.com.au/ |
ERP Heritage · Odoo Accounting Suite
Post Dated Cheques (PDC)
Cheque registers and books with full lifecycle: draft, registered, presented, cleared, bounced, replaced, written off.
Day in the life
Customer pays with a 90-day post-dated cheque.
The cheque is registered in the PDC book with maturity date 90 days out. The PDC clearing account holds the carrying amount; AR is left untouched. The cron sweeps daily for matured cheques and posts the bank movement automatically. If the bank rejects the cheque on maturity, the bounce wizard reverses the entry and records a configurable bank charge to the FX gain/loss account. The replace-cheque wizard handles the customer's replacement instrument with linkage from the original.
Overview
What this module does, in one read.
A first-class post-dated cheque module for Odoo 19 Community. Cheques have a state machine; books carry per-book sequencing; bounces and replacements are explicit transitions with their own audit trail.
Where standard accounting needs a cheque journal plus a memo on a payment, this module gives the team a register, a book, a state per cheque, and the wizards that match how a finance team actually thinks about cheques.
Capabilities
Ten things this module gives you, with no padding.
Full state machine
Draft, registered, presented, cleared, bounced, replaced, written off, cancelled. Transitions are guarded; audit on every change.
Cheque book
Per-book sequence; one register per company; partner-aware metadata.
Bounce and replace
Bouncing a presented cheque writes the standard reversal and opens the replacement wizard.
Write-off
Where collection is impossible the write-off path produces a balanced expense entry with a reason code on the audit row.
Multi-company aware
Every book, every cheque, every wizard is scoped to a company.
Plays with reconciliation
Cleared cheques surface in the bank statement reconciliation widget like any other movement.
Period-close ready
Outstanding cheques at period end are surfaced on the close checklist so finance reviews them before locking.
Reporting
A cheque ledger view drills into the journal entries; the partner ledger shows cheques alongside ordinary moves.
Cron-driven auto presentation
A scheduled cron presents matured cheques to the bank journal automatically. Each cheque is wrapped in a per-record savepoint so one bad row never blocks the batch.
Replacement chain tracking
A bounced cheque can be replaced by a new instrument; the chain is recorded so the audit trail shows the full lineage from original through every replacement.
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.
- First-class PDC register and book in Community
- Bounce / replace flow with full audit
- Period-close integration
- State machine with chatter audit
- Cheque sequence per book
- Multi-company isolation
- No cheque-printing template shipped (deployment owns layout)
- No automatic clearing-broker integration
- Bank-feed clearing is manual or via reconciliation rules
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