| Availability |
Odoo Online
Odoo.sh
On Premise
|
| Odoo Apps Dependencies |
•
Invoicing (account)
• Discuss (mail) |
| Lines of code | 673 |
| Technical Name |
gb_ap_invoice_approval_workflow |
| 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 | 673 |
| Technical Name |
gb_ap_invoice_approval_workflow |
| License | OPL-1 |
| Website | https://gencbaris.com/odoo_plugins/ |
| Versions | 18.0 19.0 |
AP Invoice Approval Workf
Multi-level vendor bill approval by amount, department and budget
Approving supplier bills over email and spreadsheets is how organisations end up paying invoices that were never properly authorised, breaching segregation of duties and failing audit. Odoo has no native accounts-payable approval matrix to stop it. This module adds a configurable multi-level workflow to vendor bills: ordered rules select the right flow by amount band, department and optional budget breach, then route the bill through sequential approval steps, each owned by a named approver group with self-approval blocking. A posting guard makes the control absolute — a governed bill simply cannot be posted until every required step is signed off — while delegation, SLA tracking and an overdue-escalation cron keep approvals flowing. AP teams, controllers and auditors get an enforceable, fully traceable authorisation trail tied directly to each bill.
Key Features
Amount/Department/Budget Approval Matrix
ap.approval.rule records carry an amount_min/amount_max band, an optional department (analytic account) and a requires_budget flag. find_rule walks them in sequence and the first whose _matches passes defines the step set, so routing is fully data-driven.
Ordered Multi-Step Sign-Off
Each rule holds ap.approval.rule.step lines, each pinned to an approver res.groups. On submit the bill instantiates one ap.approval.request per step; only the first is 'active', and _advance_approval activates the next waiting step as each is approved.
Enforced Posting Guard
account.move._post is overridden so a governed vendor bill (in_invoice/in_refund) raises a UserError unless ap_approval_state is 'approved'. The control is impossible to bypass — an unapproved bill simply cannot be posted.
Self-Approval Block and Group Checks
_user_can_act verifies the user is in the step's approver group (or an AP manager) and, when self_approve_allowed is off, blocks the bill's own submitter from approving their step — enforcing segregation of duties at every decision.
Delegation of Active Steps
action_delegate lets a current approver hand an active step to a specific user via delegated_to_id; that delegate may then sign off even if they are outside the approver group, keeping approvals moving during absences.
SLA Tracking and Overdue Escalation Cron
Each step has an sla_hours target (default 48) and an activated_on stamp; is_overdue flags breaches. The _cron_escalate_overdue job posts an overdue notice on the bill once per step (guarded by the escalated flag) so stuck approvals surface automatically.
My Approvals Inbox
get_my_ap_approvals returns every bill whose active step the current user is entitled to action, filtered through _user_can_act, giving each approver a focused queue of exactly what is waiting on them.
Bulk Approve / Reject Wizard
The ap.bulk.approve wizard takes the selected bills, applies the decision and shared note to each bill's active step where the user is permitted, and reports how many were processed — clearing a backlog in one action.
Use Cases
Screenshots
All Approval Steps
Approval Rules
Bulk Approve Reject
Why Choose This Module
Stop approving bills over email. This module adds a configurable multi-level approval matrix to vendor bills: rules select an approval flow by amount band, department and optional budget breach, then route the bill through ordered approval steps with sign-off, rejection and a complete audit trail. A bill cannot be posted until its workflow is fully approved.
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