$ 25.01
| Availability |
Odoo Online
Odoo.sh
On Premise
|
| Odoo Apps Dependencies |
•
Accounting (accountant)
• Invoicing (account) • Discuss (mail) |
| Lines of code | 1587 |
| Technical Name |
oe_vendor_payment_dynamic_approval |
| License | LGPL-3 |
| Website | https://www.oaklandmena.com |
| Versions | 16.0 17.0 18.0 19.0 |
| Availability |
Odoo Online
Odoo.sh
On Premise
|
| Odoo Apps Dependencies |
•
Accounting (accountant)
• Invoicing (account) • Discuss (mail) |
| Lines of code | 1587 |
| Technical Name |
oe_vendor_payment_dynamic_approval |
| License | LGPL-3 |
| Website | https://www.oaklandmena.com |
| Versions | 16.0 17.0 18.0 19.0 |
Vendor Payment Dynamic Approval Guide
This guide explains how to configure multi-level approval rules for Vendor Payments (both single and batch) and the subsequent approval workflow.
Part 1: Configuration (Accounting/Finance Manager)
Before use, approval rules must be configured in **Accounting** settings.
1. Configure Single Payment Approval
- Navigate to Configuration: Go to the Accounting app ➡️ Configuration ➡️ Payment Approval Configuration (or a similar menu item).
- Create a Rule: Click Create.
-
Define Rule Parameters:
- Name: Give the rule a descriptive name (e.g., "High-Value Vendor Payments").
- Minimum Amount: Set the total amount threshold that triggers this rule. Any payment equal to or greater than this amount will enter the workflow.
-
Define Approval Levels (Payment Approval Line): Click Add a line.
- Level: Set a unique integer (e.g., `1`, `2`, `3`). Approvals must be completed in **sequential order**.
- Approve Process By: Choose **Group** or **User**.
- Users/Groups: Select the individual(s) or the security group responsible for this level.
- Save: Save the rule.
- Configure Batch Payment Approval: Repeat the steps above for **Batch Payment Approval Configuration**. (The minimum amount for batches is typically handled by the lines themselves).
Part 2: Single Vendor Payment Workflow
- Create a Payment: Create a new **Vendor Payment** record as usual.
-
Trigger Approval:
- If the payment amount is **below** the minimum configured threshold, the payment follows the standard Odoo workflow.
- If the payment amount is **equal to or above** the threshold, the state will show **Draft** and the **Send for Approval** button will be visible.
- Click **Send for Approval**. The payment status changes to **Waiting for Approval**, and the Level 1 approvers are notified.
Part 3: Approval / Rejection Process (Approver)
- Review: The approver receives a notification and opens the Payment record. The current **Next Approval Level** is visible.
To Approve:
- Click the Approve button.
- The approval is logged (Approval Information/Chatter).
- If it was the final required level, the payment status changes to **Confirmed** (ready for processing).
- If there are more levels, the payment moves to the next level's approvers.
To Reject:
- Click the Reject button.
- A Rejection Reason Wizard pop-up appears.
- Enter the **mandatory reason** for the rejection.
- Click Confirm.
- The payment status changes to **Reject**, and the rejection details (user, date, reason) are permanently recorded.
Frequently Asked Questions
1. Why is the standard 'Confirm' or 'Validate' button missing on my payment/batch payment?
This is because the payment's value (or the fact it's a batch payment) meets the criteria of an active approval configuration rule. The standard confirmation button is replaced by Send for Approval to enforce the mandatory multi-level workflow.
2. Can I modify a payment once it's been sent for approval?
No. Once a payment is in the Waiting for Approval state, it is read-only to ensure integrity during the review process. You would need the approver to Reject it first, or an administrator to cancel it and set it back to Draft.
3. What happens if a payment is rejected?
The payment status changes to Reject, and the rejection reason is permanently logged. The creator of the payment is notified. The payment cannot be processed until it is cancelled and a new payment or a revised version is created.
4. Can I set up different approval rules for different companies?
Yes. Both the single payment and batch payment approval configurations have a Company Ids field, allowing you to limit a specific rule to one or more legal entities.
5. If I assign a Group for an approval level, do all members have to approve it?
No. Only one user within the assigned group needs to click Approve to satisfy that level and move the payment forward to the next step.
Module Support & SLA
For any support related to this Odoo module, please contact us at apps@odooerp.ae
Our standard response time (SLA) for support queries is between 12 to 48 hours.
Our standard response time (SLA) for support queries is between 12 to 48 hours.
Please log in to comment on this module