Dynamic Purchase Approval
by BeyonData Solutions Private Limited https://www.beyondatagroup.com$ 32.48
| Availability |
Odoo Online
Odoo.sh
On Premise
|
| Odoo Apps Dependencies |
•
Purchase (purchase)
• Invoicing (account) • Discuss (mail) |
| Lines of code | 777 |
| Technical Name |
bd_purchase_dynamic_approval |
| License | OPL-1 |
| Website | https://www.beyondatagroup.com |
| Versions | 16.0 17.0 18.0 19.0 |
| Availability |
Odoo Online
Odoo.sh
On Premise
|
| Odoo Apps Dependencies |
•
Purchase (purchase)
• Invoicing (account) • Discuss (mail) |
| Lines of code | 777 |
| Technical Name |
bd_purchase_dynamic_approval |
| License | OPL-1 |
| Website | https://www.beyondatagroup.com |
| Versions | 16.0 17.0 18.0 19.0 |
Dynamic Purchase Approval
Key Highlights
Dynamic Purchase Approval
Configurable Amount-Based Rules
Set minimum total or untaxed amount thresholds to automatically trigger purchase approval workflows, with support for multiple sequential approval levels.
Company-Specific
In a multi-company environment, each company can define its own purchase approval rules and authorized approvers.
Multi-Level User/Group Approvals
Assign approvers by specific users, user groups, or purchase teams, enabling flexible approval workflows based on purchase order value or conditions.
Automated Notifications
Automatically send email notifications to approvers on submission, approval, or rejection, keeping procurement teams informed at every stage.
Approval History Tracking
View complete approval history, current approval status, and approver details directly in the Purchase Order form under the Approval Info tab.
Rejection Handling
Approvers can reject with reasons via wizard, moving the quotation to rejected status without further approvals.
Overview
Dynamic Purchase Approval
Dynamic Purchase Approval for Odoo enables companies to implement multi-level and conditional approval workflows for purchase orders and requests for quotations (RFQs). This module ensures that purchase approvals are managed dynamically based on configurable rules such as purchase amounts, involving designated users or groups for enhanced control and compliance.
SCREENSHOTS
Configuration
- Go to Purchase Module → Configuration → Settings, then enable the ‘Dynamic Purchase Approval’ checkbox.
- Set the approval rule based on the minimum amount of either ‘Total’ or ‘Before Tax Amount’.
Approval Configuration :
- Go to Purchase Module → Configuration → Approval Configuration.
- Create a company-specific purchase order approval rule by setting the minimum approval amount and defining the approval details.
-
There are two types of approval processes: 1) User and 2) Group.
Select ‘User’ as the approval type and specify the person responsible for approving the RFQ/PO.
- Select the approval process as ‘Group’, then choose the group name. The RFQ/PO will be approved by any user from the selected group.
Confirm Purchase Order :
- The user can click the ‘CONFIRM ORDER’ button on the RFQ to start the approval process.
- If approval is based on 'Total', the system will check the total amount. Otherwise, it will use the 'Before Tax Amount'.
- The approval levels will be fetched automatically based on the configured rules and the minimum amount set.
Email Notification of Submit for First Approval :
- An email notification will be sent to the first approver when the RFQ/PO is submitted for approval
Approve Purchase Order by First Approver :
- The first approver can open the RFQ/PO and click the ‘Approve’ button to approve the purchase order.
Email Notification for Second Approval :
- An email notification will be sent to the second approver when the RFQ/PO is submitted for approval.
Approve Purchase Order by Second Approver :
- The second approver can click the ‘Approve’ button to approve the purchase order.
- Once the purchase order is approved by the second approver, it gets confirmed automatically. You can view the details of all approvers under the ‘Approval Info’ tab.
Reject Purchase Order :
- The approver can click the ‘Reject’ button to reject the purchase order.
Purchase Reject Wizard :
- When the 'Reject' button is clicked, the approver must enter a rejection reason in the popup wizard.
Rejected Purchase Order:
- After the purchase order is rejected by the approver, it moves to the ‘Rejected’ stage and no further approvals are required.
- The user can view the rejection details under the 'Approval Info' tab.
Email Notification for Rejected Purchase Order :
Waiting Approval Menu :
- Go to Purchase Module → Orders → Waiting Approval to view all purchase orders assigned to the logged-in user for approval.
- The user can access and view their own POs that are in the ‘Waiting for Approval’ stage and take action to Approve or Reject from there.
Suggested Applications
Our Service
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.
For any Query
Checkout our Apps
Check App Demo
Please log in to comment on this module