| Availability |
Odoo Online
Odoo.sh
On Premise
|
| Odoo Apps Dependencies |
•
Invoicing (account)
• Discuss (mail) |
| Lines of code | 829 |
| Technical Name |
gb_journal_entry_approval_maker_checker |
| License | OPL-1 |
| Website | https://gencbaris.com/odoo_plugins/ |
| Versions | 18.0 19.0 |
| Availability |
Odoo Online
Odoo.sh
On Premise
|
| Odoo Apps Dependencies |
•
Invoicing (account)
• Discuss (mail) |
| Lines of code | 829 |
| Technical Name |
gb_journal_entry_approval_maker_checker |
| License | OPL-1 |
| Website | https://gencbaris.com/odoo_plugins/ |
| Versions | 18.0 19.0 |
Journal Entry Approval
Maker-checker approval workflow for manual journal entries over a threshold
When a manual journal entry exceeds a configurable monetary threshold, it can no longer be posted by the person who created it. A second authorised approver — the checker — must review and approve it first. Odoo has no native maker-checker control on journal entries; this module fills that internal-control gap for finance and audit teams who need provable separation of duties.
Key Features
Configurable Approval Policies
Per-company approval threshold with the journals it applies to. Limit a policy to specific journals or apply it to all general journals, and restrict it to manual entries only (no source document).
Maker-Checker Enforcement
The approver may not be the entry creator. The rule is hard-enforced at approval time, blocking self-approval to guarantee segregation of duties.
Multi-Level Approval Tiers
Sequential approver tiers, each tied to an approver group and an activation amount, so very high-value entries can require additional sign-off levels before posting.
Hard Posting Block
A governed journal entry cannot be posted until it is fully approved. Rejections send it back to draft with a mandatory reason and a logged decision.
Full Audit Trail
Every approval request records who requested, who approved or rejected, when, and any comment — tracked on the chatter for a complete, auditable history.
Approval Dashboard
A dedicated view lists the journal entries waiting on the current user, so approvers always know what needs their attention.
Screenshots
Approval Policies
Approval Requests
Pending My Approval
Why Choose This Module
Odoo provides no maker-checker workflow on journal entries out of the box. This module adds the segregation-of-duties controls auditors expect, computed entirely from your real accounting data, with no external service and no vendor lock-in.
Specifications
- Compatible: Odoo 18.0 / 19.0
- License: LGPL-3
- Languages: 35+
- Author: Baris Genc
- Dependencies: account
- Support: odoo@gencbaris.com
Odoo Proprietary License v1.0 This software and associated files (the "Software") may only be used (executed, modified, executed after modifications) if you have purchased a valid license from the authors, typically via Odoo Apps, or if you have received a written agreement from the authors of the Software (see the COPYRIGHT file). You may develop Odoo modules that use the Software as a library (typically by depending on it, importing it and using its resources), but without copying any source code or material from the Software. You may distribute those modules under the license of your choice, provided that this license is compatible with the terms of the Odoo Proprietary License (For example: LGPL, MIT, or proprietary licenses similar to this one). It is forbidden to publish, distribute, sublicense, or sell copies of the Software or modified copies of the Software. The above copyright notice and this permission notice must be included in all copies or substantial portions of the Software. THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.
Please log in to comment on this module