| Availability |
Odoo Online
Odoo.sh
On Premise
|
| Odoo Apps Dependencies |
•
Invoicing (account)
• Discuss (mail) |
| Lines of code | 177 |
| Technical Name |
codex_invoice_approvals |
| License | LGPL-3 |
| Website | http://www.codeexperts.com |
| Availability |
Odoo Online
Odoo.sh
On Premise
|
| Odoo Apps Dependencies |
•
Invoicing (account)
• Discuss (mail) |
| Lines of code | 177 |
| Technical Name |
codex_invoice_approvals |
| License | LGPL-3 |
| Website | http://www.codeexperts.com |
Invoice Approvals Management
Key Features
Multi-Level Approval Workflow
Five distinct approval states: Waiting Support Approval, Waiting Accounting Approval, Waiting General Approval, and two-step validation for Payment Validator 1 & 2.
Amount-Based Routing
Configurable threshold amount automatically routes invoices. Below threshold goes to Support/Accounting approvers; above requires General Manager authorization.
Vendor Bill Two-Step Validation
Specialized chain for vendor bills: Payment Validator 1 reviews and forwards, Payment Validator 2 performs final authorization independent of amount thresholds.
Role-Based Access Control
Five distinct security groups ensure strict authorization: Support Approver, Accounting Approver, General Approver, and Payment Validators 1 & 2.
Smart Request Workflow
Single Request Approval button automatically determines the correct approval path based on document type and amount, replacing the standard Post button when enabled.
Instant Rejection & Reset
Reject button immediately returns documents to draft state for corrections. No need to create new recordsâsimply edit and resubmit for approval.
Detailed Usage Guide
Configuration & Threshold Setup
Enable the approval workflow from Accounting Settings and define the Threshold Amount. When activated, the standard Post button is hidden and replaced by Request Approval, enforcing mandatory validation chains before any invoice or refund can be posted.
Role-Based Access Control
Assign users to specific approval groups: Support Approver, Accounting Approver, General Approver, Payment Validator 1, and Payment Validator 2. Each group carries distinct authorization limits enforced at the code level.
Workflow Initiation
In draft state, users must click Request Approval to submit documents for validation. The system evaluates document type and amount to determine routing: vendor bills go to Payment Validators, while customer invoices and refunds route based on the threshold setting.
Intelligent Amount-Based Routing
Documents automatically route to appropriate approvers based on value. Amounts below threshold await Support or Accounting approval, while high-value documents require General Manager authorization. Approve and Reject buttons appear only for authorized users.
Vendor Bill Two-Step Validation
Vendor bills follow a dedicated chain through Payment Validator 1 then Payment Validator 2. Validator 1 forwards the bill, Validator 2 performs final authorization. Upon final approval, the system automatically posts the bill and creates journal entries.
Strict Authorization Enforcement
Unauthorized users attempting to approve receive immediate ValidationError messages. Authorized approvers see contextual Approve and Reject buttons. Clicking Reject instantly returns the document to draft state for corrections.
Need Support?
Our dedicated support team is here to help you with installation, configuration, and any questions you may have about the Invoice Approvals Management.
| hello@code-experts.co |
+973 1722 4488
|
WhatsApp: +973 1722 4488
|
www.code-experts.co
|
© 2026 Code Experts IT Solutions. All Rights Reserved.
Please log in to comment on this module